Career advice without BS
More than a few people repeat the same career advice:
“Quit your job. Build a SaaS. Make 10K/month.”
That advice is 99% wrong
I’ve built around 20 side projects over 5 years.
Only one really worked as a business — and that was the only one I did not want to make money with.
All the others made zero meaningful revenue.
But here’s the part people don’t talk about:
Those projects landed me 3 great jobs.
Not because they were successful.
Because they existed.
They showed that I could ship, iterate, abandon, restart, and keep going.
One concrete example.
I built TechLens.app & StoreRadar.io
Nothing fancy. Basically a clone that fingerprints the stack behind a website.
Who cares about BtoB data?
Turns out: Hunter.io does.
The CTO reached out because of those projects.
That conversation led to me joining Hunter as a Growth Engineer.
No pitch.
Just shipped projects doing something real.
“quit your job and make 10K MRR” is bad advice.
But this is solid advice:
Build things you’re happy to work on at night or on weekends.
Not for revenue.
For learning, visibility, leverage, and optionality.
Good things tend to happen when you ship.
Nothing happens when you wait.
Cool Rails jobs this week 🧠
Two strong Ruby roles, both Paris-based
Senior / Staff Ruby on Rails Engineer
📍 Paris - 60-90K€ / year
High ownership role. Strong expectations on architecture, code quality, and mentoring.
If you like being a technical reference rather than just “a senior dev”, this one matters.
Head of Engineering 80K€
📍 Paris
Leadership role with real scope: team structure, technical direction, and hiring.
Ruby is central, not legacy.
Building this next layer
Ruby on Rails Jobs is expanding beyond the job board.
A podcast / interview format is launching soon on Youtube
Short, focused conversations with CTOs and engineering leaders actually using Ruby in production.
The angle is simple:
how Ruby fits their stack today
how teams are structured
what they are hiring for now or next
what working there really looks like
I’m looking for the first CTO to record the opening episode.
Profile:
hands-on CTO or Head of Engineering
genuinely passionate about Ruby
currently recruiting, or planning to recruit in the next months
able to talk concretely about teams, tradeoffs, and reality
If you know someone who fits, make the intro by replying to this email.
If that person is you, same rule.
This will stay curated, low volume, and signal-first.