>>And taking a stand that says crappy code should be accepted will never advance the craft.
>
>In practical terms, I always loved a crappy coder. If he was working for someone else, and sold an app to my future customer. Walking in over his dead body is always a pleasure,

Problematic are those bodies not in this state - for instance if you tested all your stuff to be running for release after lockdown of source control but crappy coder manages to insert his "tested! code somewhere near the base classes. Of course killing functionality I was depending on and the "testing" was done in his specific application only.

>and the customer's satisfaction is the cherry on top.

Which did not help customer satisfaction for my parts... So I decided to go theatrical (not really my typical mode of operation...) and chew him out before large segment of devs. His defense of the code he changed in high class did help: "That code works! You can copy it!"...