Why Your Code Rots Even When No One Touches It
Software entropy is the phenomenon where code degrades over time without any direct changes, driven by the same statistical principles as the second law of thermodynamics. Outdated dependencies, failing tests, and obsolete abstractions accumulate as the surrounding ecosystem evolves, even if the codebase itself remains untouched. Criminologists Wilson and Kelling's 1982 'broken windows' theory was adapted by Hunt and Thomas in 'The Pragmatic Programmer' (1999) to describe how small, unaddressed code flaws signal declining standards and invite further deterioration. Software researcher Meir Lehman reinforced this with his laws of software evolution, showing that systems must continuously change or grow increasingly complex and unsatisfactory. Preventing software rot requires active maintenance, prompt repair of code 'broken windows,' and recognising that order in a codebase demands deliberate, ongoing effort.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in