The best engineer on my team ships the least code

A recent article on Dev.to highlights the growing disconnect between traditional engineering productivity metrics and actual value. The author notes that while output-based metrics like commit counts and lines of code were once reliable proxies for performance, the rise of automated code generation has made high-volume output cheap and abundant. Consequently, the most valuable skill has shifted toward critical judgment and the ability to prevent costly errors. The author argues that modern management often fails to recognize engineers who prioritize quality and risk mitigation over sheer volume, as 'prevented disasters' are invisible to standard dashboards. To address this, the author suggests that managers must actively track and reward the 'no'—the act of blocking flawed code—to ensure that high-judgment engineers are properly valued. Ultimately, the piece serves as a call to update performance review processes to reflect the reality of the current software development landscape.