Namespace crash in HTML forms

Today’s evil headache was caused by something as simple - yet annoying - as a two HTML form elements having the same name (but different types and uses in the form). The lesson learned is that if a field in a form is submitted but contains nothing - check if another object in the form has the same name and make changes if you need to.

To Mac or not

So, I’ve been wondering if I should by a Mac. Windows works for me, but causes a fairly large number of headaches. Linux is nice for server use, but I’m not nerdish enough to get a desktop running. With the many positive reviews, switching stories and others I was thinking of going Mac. Since OS X was introduced Mac machines runs on a BSD core which makes it almost familiar grounds for people who knows the Unix world. Since the introduction they kept an amazing pace and regularly introduced new innovative features at regular intervals.

SQL and beyond

SQL is a common language implemented by most databases. While it’s a nice language it does lack some features available in some databases (which often differ from database to database). Some argue, that you shouldn’t go beyond the contrains and limitations in SQL because that removes your ability to switch to a different database. That’s just wrong (in my opinion). SQL usually allows you to do all the searches and CRUD operations you need, and by not going beyond the limitations posed by SQL you can switch your application to another database with an absolute minimum number of changes in your application - especially if you utilize the Perl DBI or the Pear DB (in PHP).