Developer and CSS Wizardry writer Harry Roberts:
The problem with leaving hacks and nasty code is obvious; it’s hacky and nasty. However, other problems with leaving this code can arise…The first bits of bad code set a precedent and make subsequent developers feel less bad about using poor code themselves. It was like that when I got here! Give developers a clean slate and they’ll really think twice about messing it all up.
What is needed is a way of allowing these hacks when necessary, but making sure that they don’t go unnoticed and unresolved.
There has been some controversy online about this, but I actually think Harry’s suggestion of a separate file to isolate and focus on crappy CSS to be refactored later is really smart. I might give it a try in an upcoming side project.