Christian Ross has a confession: he codes in tables.
First off, let’s get this out of the way, clients don’t care. If it shows up well on their screen and is close in all of the major browsers, they’re happy. It doesn’t matter to them if their site can pass the W3C Validator.Of course, not always. Only if the circumstances dictate that this is the best approach for his clients.
And yet, he’s worried that including this work in his portfolio has potentially lost him some work. One only has to look at the excellent design of his personal site to know that he has talent. If that is the case, I’d say he’s better off not having got the jobs — an employer that is not willing to dig a little probably would not be all that enjoyable to work for.
Reblogged, because it is quite an interesting and well-written article. I don’t know that I can bring myself to fully agree, but bills have to be paid. If clients approve and the site looks okay in most or all browsers, maybe there’s a particular subset of clients for which you can develop table-based websites.
Very interesting. While I tend to stay away from tables unless I’m dealing in tabular data, it was funny that more than a few people took issue with Forrst’s homepage using a table for the application form. It’s okay to not stick to the rules 100% of the time. I promise.
