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.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 30 points 1 week ago

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.

  • source