A provocative challenge to conventional wisdom in software development has emerged, arguing that code is run more than read. This perspective shifts focus from maintainability to operational realities, emphasizing that the long-term costs of keeping systems working reliably exceed development inconveniences. Dan McKinley's observation about operational costs forming the majority of software expenses supports this thinking.

The author proposes a priority hierarchy: business needs must guide development, followed by user experience, operations, and finally developers themselves. This model reveals common dysfunctions like unmaintainable code (author > maintainer), unusable software (dev > user), and imaginary projects built without real user problems. Each represents a misalignment with proper priorities.

This framework exposes uncomfortable truths about modern software production. Many professionals feel discomfort when business objectives override user needs, yet acknowledging the ethical imperative not to harm users becomes essential. The tension between creating valuable software for users and satisfying business demands reflects a fundamental challenge in contemporary software development practices.