I did this once, I quickly abandoned it as I felt it was madness. It was for my personal site (just like his) that's a testing ground more than anything. After

I did this once, I quickly abandoned it as I felt it was madness. It was for my personal site (just like his) that's a testing ground more than anything. After writing far more styles than I felt was necessary for such a simple page it was easy to see future problems once it was done. Biggest example as many pointed out is that if I moved HTML elements around in the markup then I would have to rewrite huge chunks of the style sheet even though I wasn't changing the actual design of the elements. My soon former job involves two websites that have a large chunk of its markup with no classes or ids provided by the CMS. It is a nightmare to support or to add a new feature. I have a selector that is eight elements deep, all to target one cell in a table embedded in other tables. Well, to be fair, I'm guessing the author wasn't considering that kind of site. I can scare you at the campfire with stories of the tables I deal with that have no classes or ids. We've rewritten a good chunk of the CMS to clean up the markup and add classes to make my life as a front-end guy much easier. This reminded me of the tables, I need some quiet time now.