Not it won't. It will just prove that the rewrite was justified.
>Good developers turn into Dungeon Masters because this is what the system demands.
They really don't. Good developers realize that there is an endless of cycle of the old being replaced by the new and if you can't deal with that you are not suited to a career producing software.
The whole thing reads like the author encountered one or more people whose self esteem is so fragile that they are unsuited to the commercial software industry. It sounds like those individuals had a lot of trouble keeping their own (fragile) ego out of technical and business decisions.
>The moment a different implementation shows that a lot money could have been saved, then the cost of keeping the old software for too long is exposed too. And this can be scary: imagine you discover a wrong design decision you made 10 years ago costed millions to your company… would you happily expose it?
Yes. Exposing it presumably then saves the company millions going forward and any halfway competent boss will respect you for putting the organization first. Shelve your ego, it's called being a professional. Never mind being professional, its also a matter of acting like an adult.
The article isn't so much about dungeon masters as it is about people who shouldn't be programmers.