>Basically nothing here is specific to software. You can talk about a piece of writing exactly the same way. Even the part about patching; lots of books have revisions.
>I don't really see the point of focusing on software in particular before answering the general question. It's not being used to bring any special insight, and to my eye it's a false narrowing that makes it harder to answer.
I agree with the substance of this remark (the OP is indeed a general information-theoretic observation), except for the part where it's framed as a negative value judgement against the initial work.
It seems like this feedback could be trivially recopywritten in a way that elevates, rather than denigrates.
--
One thing that would seem to bear mentioning is that software seems to be highly compressible. Indeed, good software seems better represented by the path, rather than the current state. An analogy here would be chess, where a state can be represented by the sequence of moves or the current board state. The analogy isn't perfect, eg since in chess the board state tends to reduce information over time. I would expect, for software, when the (dead-end pruned) sequence representation exceeds the information content of the current 'board' state, that's when you know it's time for a refactor.