I think this is right; the chaos of shifting or contradictory requirements can leave scars on the physical codebase reflecting this history, and so can attaining a better understanding of the problem from working on it, if one isn't careful to refactor (original sense) rather than adding new hacks on top. But the prescription for addressing each situation is pretty different.