What is Broken Windows Theory (Software)?
The Broken Windows Theory in software development, drawn from urban criminology, states that visible signs of disorder (like poor code quality, ignored warnings, or failing tests) encourage further negligence.
The Broken Windows Theory in software development, drawn from urban criminology, states that visible signs of disorder (like poor code quality, ignored warnings, or failing tests) encourage further negligence. One broken window — one ignored linting error, one skipped test, one hacky workaround — makes the next broken window more acceptable.
In codebases, broken windows compound: a few ignored compiler warnings become hundreds. One untested module becomes several. One hardcoded configuration becomes a pattern. Once the team accepts "that's just how it is," the standard permanently drops.
The practical implication: maintaining high standards requires constant vigilance. Allowing "just this once" exceptions creates a ratchet effect where quality only moves in one direction — down. This is why CI/CD pipelines should have zero-tolerance policies for critical issues: if warnings are allowed to accumulate, they will.
Why It Matters
The Broken Windows Theory explains why technical debt accelerates. The first broken window (ignored warning, skipped test) makes the second one easier to justify. Maintaining a strict zero-tolerance policy for critical issues is the most effective prevention strategy.
Frequently Asked Questions
What is the broken windows theory in programming?
One visible quality problem (an ignored warning, a skipped test) normalizes future quality problems. Quality degrades as standards become more permissive over time.
How do you prevent broken windows in code?
Enforce zero-tolerance CI/CD policies for critical issues. Fix broken tests immediately. Never ignore compiler warnings. The boy scout rule helps: always leave code better than you found it.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →