Shame.css – Documenting your CSS downfall

When I’m pushed to get a website done on time or just struggling to find a cure for some niggling error, I’m not ashamed to admit using some hacky CSS. Everyone does it. I normally comment my code to make it clear I’m using a hack. But Harry Roberts of suggests using a shame.css file specifically for this purpose. This will make life so much easier for future changes to the site especially if someone else has to make changes to my legacy code. I’m definitely going to start doing something like this. My only issue is that technically I already use a ‘shame’ file… mine is just called ie-all.css and sits behind <!– [if it IE]>.