Rocket Surgery

In my last post I talked about getting involved with the Hudson project. In this post I will describe the steps I took to set up my build environment.

1. Get JDK 6.0 (Hudson cannot be built using 5.0 or earlier) and install it.
2. Get Subversion and install it.

Read the rest of this entry »

I was messing with the Google Web Toolkit yesterday. My friend Jeff is a big fan of it, and he is actually using it for a Navy system that I once worked on. He’s gotten a couple of his coworkers on the bandwagon, so I started messing with it.

If you don’t know, GWT is a tool for creating AJAX applications. You write code in Java, and the GWT compiler translates it into Javascript instead of byte code. Separating the client side from the server side is built in, and they have done things to simplify RPC calls back to the server from the client.

First thing I liked is that the installation is dead easy. Download a zip file, explode it somewhere, and to make things simple, add it to your execution path. There is nice eclipse integration too. Adding and removing widgets (UI elements) from the page was also dead easy, and hooking up listeners to react when things are messed with was a breeze.
Read the rest of this entry »

Those of you who know me or who have read my earlier posts know that I am a static code analysis fan, and some of my favorite tools are PMD, Checkstyle, FindBugs, and JDepend, for their excellent feedback on the state of the quality of your code. In fact, I regularly use all of them and usually in combination with other tools (such as JUnit, Emma, etc) to gather code metrics.

The reports from each of these tools naturally identify problems — why else would you run them? And once you see a problem, you naturally want to run right out and fix them. The report shows them all, rated by severity, with counts and everything, and you can see the types of errors. It’s just a simple refactoring, right?

Better think twice before activating that refactoring in your IDE.

Read the rest of this entry »

In a previous job, I had a trainer for a CASE tool who gave me a phrase that has stuck with me for the past 15 years: “A fool with a tool is just a faster fool.” The truth of this is obvious on the surface, of course, but many times we developers don’t see it happening to us as it happens - the onset is too gradual. I am beginning to see an emergent anti-pattern, particularly among my less experienced colleagues, which has cropped up as a result of Eclipse usage - something I call “Squiggly-Driven Development”.

Read the rest of this entry »