User Avatar

Frontend platform team lead | Dad | French expat in Slovakia

3 Pieces of Advice That Defined My Early Career As A Developer
Robin Cussol

In seven years as a software developer, three pieces of advice have significantly shaped my career.

They've pushed me past self-limiting beliefs and spurred me to action—from starting to write online to advocating for myself.

Do what's best for you – Joshua Crass

At my first startup job, this was Josh's constant refrain when I asked about our dwindling runway.

It felt like a cop-out from someone whose stories of Google and Facebook's early days had always been so inspiring. How could such simple advice come from such an accomplished manager? As a junior, it left me all the more confused.

Months later, I understood: Josh wasn't being lazy—he was teaching me to take ownership of my career.

To take responsibility for what's next. Not to stay helpless. To take risks.

Doing what's best for yourself isn't selfish—it's ensuring your path aligns with your goals rather than letting circumstances or others choose your direction.

The alternative might very well be burnout.

Better done than perfect ­– Michal Sänger

I used to write mathematical proofs for my PhD. Every detail had to be correct or the whole result might go straight to the bin. Done meant perfect.

Michal just wanted things to get done.

He knew that businesses do not care about diminishing returns. Startups especially need to rapidly experiment to find product market fit and bring in revenue. Agonising over the perfect solution was counterproductive.

What's more, I later realised there are no perfect solutions. It's always a question of trade-offs. Context is key.

The mantra went:

1. Make it work.

2. Make it right, if necessary.

3. Make it fast, when it matters.

It's easy to miss business realities when we're deep in the code.

You can learn so much on the Internet for the low, low price of your Ego – Shawn Wang

People cannot help themselves but correct you when you're wrong.

Not because they're bad people, mind you. It's in fact because people love to help. So when you stop defending your ego so fiercely, you open yourself to great learning opportunities.

I then started writing on my blog.

  1. When I needed to build standalone Expo applications with Turtle CLI and found no documentation, I didn't just solve the problem—I wrote the guide I wished I'd found. Writing deepened my understanding.

  2. Later, when I started an "Awesome List of JS Tools Not Written in JS," developers I'd never met contributed tools I hadn't discovered, expanding my knowledge further.

  3. Even sharing a post about optimizing image tags with Eleventy and WebC led to insightful exchanges with Eleventy’s creator on Twitter.

Learning in public creates opportunities you can't predict.


Whether it’s taking ownership, embracing imperfection, or learning in public, these principles have stayed with me through every career challenge. I hope they can do the same for you.