I call shenanigans!
You see, due to the nature of our templating system (and that I wasn’t involved in originally coding it), code for one simple html container is all -over- the place.
For instance, a table consists of at least these items – a table begin, row begin, cell begin, cell end, row end, table end.
SO! Fixing a broken table may require me going into anywhere between one and six different files … or a dozen, as there are more complicated rules based on the position of the news item being called, etc.
Sometimes I’ll work on something and realize by the time I’ve put together what’s happening in a table, it’s a miracle it works in any browser at all. For instance, the inner cells in a given row add up to 555 pixels, but the table width is 250.
Huh?
No wonder IE shits its pants, that kind of math is exactly how evil AI empires were destroyed, back in the 70’s.

Kirk and Spock defeated an AI in the Enterprise computer by telling what was left of the original computer to calculate PI to its ending decimal place.
Awwwww, yeah. Kickin’ it oldschool.
Seriously, good example.
Also, I should note that my job does not involve going through and restructuring code for “Best Practices”. Our site doesn’t use stylesheets for positioning at the moment (though the redesign in january may change that significantly).
Fixing the problem I originally stated is actually one of the more entertaining parts of the coding part of my job. I am quite relieved that, as we get closer to the new year, less and less of my job will involve things outside of multimedia work.
And yes, I know web pages count as a media. :p
Excellent.