The 10x developer is one of the most repeated and least understood ideas in our industry. It’s used to justify hiring decisions, set compensation bands, and influence entire management philosophies. But the source material, a 1968 study called “Exploratory experimental studies comparing online and offline programming performance” has been largely debunked when looking at individual developers working within a team or organization.
Most of the variance in developer output, even with AI augmentation, is not about the developer, it’s about friction. It’s about how many times a day someone gets interrupted, how long the builds or tests take, how quickly a review is turned around, how confident they feel deploying on a Friday afternoon, whether the test suite is trustworthy, and whether they spend their week on work they consider meaningful.
100% this! If you want to improve developer output, then protect them from unnecessary meetings and distractions.
And give them time and incentives to write maintainable code. If devs only get recognition for getting a lot of tickets “done”, your code quality will very quickly deteriorate. Which means everything will take forever.
Exactly this. Organizations often have a far larger influence. They can easily turn a very effective and competent developer into a 0.01x developer. Especially if they have huge technical debt.
Fire HR
