Here’s an interesting approach to manage CSS hacks. The idea is to have a css file called Shame.css or hacks.css. The ONLY thing put into this file are the ugly hacks that are necessary either because of browser oddities, or lack of time, or some other reasonable reason.
The css in here is intended to be replaced as soon as time, techniques or skills allow. The hacks will be well documented so that anyone looking at the file will know why it’s there, and can potentially address the issue.
The idea is not to shame the developer doing it, but to recognize the necessity of hacks occasionally, and ensuring that they’re clearly documented, and potentially corrected.
Another assumption of this technique is that you’re using a css pre-processor so that the file doesn’t explicitly appear in your markup.