I always have regrets about software I build. No exceptions. I've been designing and building applications for over a decade, but I still can't make all the right choices.
I've come to the conclusion that you always make the wrong choice for for each piece of software at some point. This has taught me two important lessons.

One of the things I've run into several times as a developer, is something I'd like to call "Framework Inertia".
Framework Inertia is the the inability to move your code to use a new framework, even though the framework you're currently using is rapidly becoming obsolete.

Merry Christmas everyone!

I like the way the tablet/smartphone revolution is going. I like it that I can finally use a tablet as a calendar and have it automatically sync with my internet calendar, that I can check my e-mail with my phone, and that when a friend rings me, their Facebook picture is automatically shown.
These devices offer numerous great possibilities. One thing developers will have to learn, though, is that a tablet is not a PC.

The Data Access Object pattern is an Enterprise Architecture Pattern, and it's one of those patterns that everybody (in the Java EE community) says you should use. So what if you don't? And what if you use it in the wrong way?

It was time for a change and a time to start updating again.
Actually, it has been time for that for a few years now.

One of the reasons for my lack of updates was the content management system I was using - one I'd built myself in a flash of hubris.
I've now started using a real CMS, and I've restyled the site.

Now to think of some new content marginally related to software design...