> So even if poor developers improve by 1/3 while great developers are downgraded by 1, we're better off. Ye... No. Note that your made-up productivity algebr

> So even if poor developers improve by 1/3 while great developers are downgraded by 1, we're better off. Ye... No. Note that your made-up productivity algebra model crumbles as soon as you stop seeing developers as code churning machine and instead as what they should be, problem solvers. That's because quantity is not the only metric by which you can measure problems. Complexity and ease are others. A dozen average problems do not necessarily equate a single hard one. Hard problems can prove elusive to average devs and they're usually where you see materialize the limitations of the thinking that a single great developer can simply be replaced with a dozen average ones. One such manifestation is commonly called "technical debt".