James Lorenzen had an excellent blog post about the importance of a descriptive commit comment. I can't agree more.
ObjectWeb ASM is a great library that's used to parse Java class files. It's used in all kinds of projects, such as Hibernate, Corba, JAX-WS, Jersey, Spring, Hudson, to name a few.
But I have a pet peeve to this otherwise great library, namely its insistence on small size (which by itself isn't a bad thing), and its consequences.
At work, I have two monitors hooked up to my workstation, which gives me about 4300x1600 combined screen real estate (one of them had to come out of my own pocket, but that's a separate story.) When I switched from a single monitor set up, my behavior changed a bit.
As a programmer, I spend a lot of time fixing bugs. And a considerable portion of that is the time spent on reproducing a problem. Here is how a typical such session goes. Your user reports that your program doesn't work and throws such and such exception. Or given the symptom he's describing, you suspect some "if" statements to be evaluating to false.
I'll be doing a webinar and Q&A sessions on Hudson tomorrow.
One of the problems of doing a presentation for the general audience is that I normally can't spend too much time on the advanced topics. So in this webinar, I'll be talking about several topics that are oriented more toward people who have already evaluated Hudson and/or are already deploying Hudson.
Due to the recent availability problem in java.net, I've set up Subversion mirrors for Hudson and various GlassFish related projects at http://svn-mirror.glassfish.org/
Today I've digged deeper into one of the nastiest problems I ever encounted since I became a Java programmer.
The problem was this — I have the Hudson slave agent program, which blocks on stdin for read almost all the time.
I wrote and deployed an OpenID provider service for java.net users.