Front End Development
There is a reason why I prefer to develop things in the back-end of a site, and that reason is because I know the setup of a server if I'm not in a position to dictate it myself. That means that everything just works! A recent dicussion on the PHP General mailing list about CSS highlights the problem with front-end development. Essentially, websites can be viewed on a huge variety of devices, none of which behave the same. The discussion on the mailing list was generally about tables vs CSS for laying out pages. Now, I'm an advocate of the latter, and prefer to keep my code free of tables that shouldn't be there. I'll use tables only for tabular data, and leave it at that. The crux of the issue though, is not developers intent, but support on the part of UA's. I won't turn this into a browser bashing rant as all browsers have their idiosyncracies, but it is well know that some have more than others. Time and again my testing period has been greatly increased because of the problems associated with browser compatibility, as each and every part has to be tested across as many platforms as possible, the sort of test which is impossible to automate.
read full post for "Front End Development"