> If you’re stuck working with people who think they are the only ones ever to have written good code, I’m sorry.
I didn't say that.
> Usually because I learned new information, past choices turned out to have regrettable unforeseen consequences, etc.
Indeed, that "awful" code may have been written by the same developer from one or two years ago and now they're not comfortable with it anymore either.
Of course I'm being a bit hyperbolic, but what I'm saying is basically true and applies to pretty much everyone.
It's not all bad either, without some push towards renewal, we would be stuck with old ideas forever. The key point is that permanent renewal has a cost that the business must carry. Sometimes no renewal at all is the right business decision.
I didn't say that.
> Usually because I learned new information, past choices turned out to have regrettable unforeseen consequences, etc.
Indeed, that "awful" code may have been written by the same developer from one or two years ago and now they're not comfortable with it anymore either.
Of course I'm being a bit hyperbolic, but what I'm saying is basically true and applies to pretty much everyone.
It's not all bad either, without some push towards renewal, we would be stuck with old ideas forever. The key point is that permanent renewal has a cost that the business must carry. Sometimes no renewal at all is the right business decision.
reply