I would not say that it's just "entropy" in the sense that there are far more disordered states than there are ordered ones. There are. But also in software, t

I would not say that it's just "entropy" in the sense that there are far more disordered states than there are ordered ones. There are. But also in software, the article says that ordered states are "easy to change" and disordered ones "difficult to modify". So the disordered states have more "friction" i.e. from there it is harder to to safely move to an ordered state. But possible to step further into disorder and yet more friction. I have observed this in cases where past a certain point people give up on refactoring and just add code to workaround - they just wrap the code that does most of what they want in a special case for their specific needs. Which in turn makes it harder to understand and refactor. After a while, it's a big pile of nested special cases and workarounds. Fighting that tendency is harder. It is going uphill, against the path of least resistance.