Web Design

My thoughts on Web 2.0. Let me know what you think...

I had recently been using Alex Robinson's 3-column CSS technique called "ordered columns, float-margin/float-margin" for some website designs. But he has superceded that with the One True Layout.

Editor's note: after a friendly reader (see comment below) pointed out that this article was a pretty much word-for-word copy of another article, we have removed the text of the original article posted here and instead direct you to the article that was copied, "CSS Crib sheet #3 - Centering a Div," by Andy Budd.

Ahh, the glory of a good Flash Gordon reference; it never fails to brighten one's day. But today I am not following the orders of General Kala, or doing the bidding of Ming the Merciless. Today, I am playing The Curmudgeon on the subject of Web 2.0 and the mysteries of Asynchronous JavaScript And XML--better known to the digerati these days as AJAX.

The techniques for addressing error handling from a technical standpoint are well known (trapping, display, logging, tracking, emailing), but in my view this is not purely a technical concern. There's a business policy and practice element to it also. What resources, if any, does an organization want to commit to keeping up with and addressing system errors?

You may be able to deal with this situation when buying a book online, but it's just unacceptable when you have 30+ paperwork packets per day to process. So even though you have your new web app, you're not using it, and the machine with the vulture on top is still humming away.