In a new post to his PHP in Action blog Dagfinn asks the question "is bad code good for you?" He wonders if bad code really is a good thing and how it can be split out from the good parts of your application.
This is an interesting idea that struck me as novel. But after thinking more about it, I believe it's not a radical departure from what we're all implicitly accepting, no matter how fanatical we might be about clean code.
He includes a quote from Luke Welling on the subject talking about how bad code, despite the headaches it may cause for maintenance and future development, can be a good thing if it does good for the project.