Welcome to the diplomacy of development, where style guides prevent wars, linters keep the peace, and process discipline separates sustainable teams from those perpetually firefighting. These standards stories capture the evolution from wild west coding to civilised collaboration.
Welcome to the diplomacy of development, where style guides prevent wars, linters keep the peace, and process discipline separates sustainable teams from those perpetually firefighting. These standards stories capture the evolution from wild west coding to civilised collaboration.
The software industry has spent 25 years learning a simple truth: broken products ship faster, cost less, and often face limited legal consequence. Now the same industry deploys AI systems alongside formal arguments that hallucination cannot be fully eliminated in general-purpose use. AI didn't start this trend. It scaled it.
AI coding assistants promise dramatic productivity gains, but independent research tells a contradictory story. When controlled studies, delivery metrics, and 211 million lines of analysed code all point in the same uncomfortable direction, the industry narrative deserves scrutiny.
Velocity metrics were meant to help teams predict and improve, but they have become weapons of productivity theatre that incentivise gaming the system while destroying actual productivity. Understanding how story points, velocity tracking, and sprint metrics create perverse incentives is essential for building truly effective development teams.
Three features in parallel, each "nearly done". The authentication refactor sits at 85% complete. The payment integration passed initial testing. The dashboard redesign awaits final review. None will ship this sprint—all will introduce bugs next sprint. Research shows teams planning above 70% capacity experience 60% more defects whilst delivering 40% less actual value.
Simple CSV export: one day estimated, three weeks actual. User data spread across seven tables with inconsistent types—strings, epochs, ISO 8601 timestamps. Technical debt's real cost isn't messy code; it's velocity degradation. Features take weeks instead of days. Developers spend 17 hours weekly on maintenance from accumulated debt.