Now that I have been in the software engineering game for about twelve years, I thought this would be the right time to list some bad developer habits. Some habits that may remind you of a few colleagues, and possibly yourself. It goes without saying that I have never exhibited any of them, personally.
Recently, Dutch Rail (called NS in Holland) made an API available. I thought I would put it to use.
Recently I enabled one of those “here’s a contract you might like” email services again. I was horrified.
Over the past months, I have been working on my own niche social network site. In this rather personal post I try to look back and reflect, post-mortem. Maybe there’s something in it for you.
For a private project, I have been using Grails for a couple of months now, and altogether it was a very pleasant experience. In this post I would like to highlight some aspects of it.
I ran into a little gotcha the other day. Appengine was refusing to compile and process my .jspx files. The solution was horribly simple.
So much has been happening in the GWT community lately that I wanted to write a posting summarizing those developments and why they matter.
In recent projects, I have found that developers often avoid company politics, even if it is detrimental to the quality of the software they’re working on. I think they should join the political arena.
I have been experimenting with writing an application for the Java edition of Google Appengine, which I blogged about before. Back then, I was still trying to use JPA with the Datastore, but the longer I was trying, the more I got the feeling that JPA (and JDO) just don’t fit Google’s Datastore very well. […]
In his most recent posting about distributed version control, in the final paragraph, Joel calls it a day….