2 ms·
A related concept is "normalization of deviance", but it's not quite the same as "broken windows" as it's meant to apply to processes (so does apply to software
by Jtsummers 5y ago
A related concept is "normalization of deviance", but it's not quite the same as "broken windows" as it's meant to apply to processes (so does apply to software engineering practices and discipline) and not artifacts (that is, the code itself).
Basically, you have a, reasonably, safe and disciplined process. You have controls in place for a good reason, but you relax them. Possibly for a good reason, possibly not, and nothing bad happens (at least not yet). This relaxation gradually becomes normalized (think about a safety critical system turning off alarms and leaving them off, "because they're always false alarms"). The odds of a problem occurring is increased by this relaxation of controls and potentially shifts from being "possible" to "inevitable" (in sysadmin stuffs, consider manual data entry at a critical juncture, a fat-fingered value can cause catastrophic problems when it could have been automated and pulled from a regularly reviewed data source).