The idea of the "10x engineer" has been around for decades. It suggests that some engineers are inherently more productive, more impactful, or more valuable than others. But is that really the right way to think about excellence in software development?
In this episode of Le Podcast on Emerging Leadership, I had the pleasure of welcoming Julien Danjou, an open source software hacker with more than 20 years of experience and the author of several books on Python.
Questioning the 10x engineer myth. I invited Julien to discuss the myth of 10x engineers and to share his perspective on how engineers actually grow their skills and impact over time. Very quickly, the conversation moved beyond code. According to Julien, while technical skills are important, two other dimensions are essential: understanding the business, and understanding the social component of work.
Beyond technical excellence. Great engineers do more than write efficient code. They understand the context in which their work creates value, communicate effectively with others, collaborate across roles and disciplines, and take responsibility for outcomes, not just tasks. These capabilities multiply impact far more reliably than individual technical speed.
Examples you can apply immediately. One of the strengths of this conversation is how concrete it is. Julien shares examples drawn from real experience, all of which can be applied immediately by engineers who want to grow. The discussion resonated strongly with me and aligns closely with the ideas Michael and I share in our book I am a Software Engineer and I am in Charge.
The real multiplier is not being 10x faster, but being 10x more connected to people, context, and purpose.
In this episode, we discuss
- •Why the 10x engineer myth doesn't capture how engineers actually create impact.
- •The two dimensions beyond code: understanding the business and the social component of work.
- •Understanding the context in which engineering work creates value.
- •Communicating effectively and collaborating across roles and disciplines.
- •Taking responsibility for outcomes, not just tasks.
- •Concrete examples engineers can apply immediately to grow.
- •Why the real multiplier is being more connected to people, context, and purpose.

Listen on Spotify
Apple Podcasts
Castbox
Amazon Music