>>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, and the customer's satisfaction is the cherry on top. Ah, BTW, after all those years in the US I never bothered to ask: is that sweet or sour cherry?

Same here. Except when the previous shaman has entrenched his crap all over the place, and management has delusions over his ability, then it is nothing but cursing.