As a Websphere shop we acquired licenses to IBM’s nascent ESB product, Websphere Process Server about a year ago. Since that time only one developer at the company, our architect, has been able to successfully develop anything with it.

The partial secret to getting it up and running successfully was revealed to me recently. Another developer kept asking our architect if he was getting a number of random crashes, constant slowdowns, and was unable to run even an email client and Process Server/WID on his machine. Turns out our architect never runs it on his main machine. He has a dedicated box with 4GB of RAM that only runs Process Server. Mystery resolved. Maybe when we get to refresh our dev boxes we might actually be capable of running Process Server successfully.

I stumbled across a post by Mike Clark on rcov and how easy it was to get code coverage metrics. I’d installed rcov 0.6 like a year ago and it took forever to run and had other issues so I dropped any idea of seriously using it. Now trying 0.7 it appears to run perfectly well. So if you’re like me and really like coverage tools like Clover in the Java/.NET land rcov 0.7 appears to be a keeper.

Software Engineering Radio is a fairly heady podcast on computing topics. I’ve left it on my list for a long time even if I end up skipping through the occasional episode that delves into too many details on Remoting or Model Driven Development. Lately though I’ve really enjoyed their turn towards more interviews with people like Guy Steele working on a Fortran replacement or Werner Vogels of Amazon talking about massive scaling approaches. Might give it a try if you have some available listening time.

Turns out the first developer in our organization to actually bring in Rails and use it for something real is a Unix sysadmin. He needed to transform a spreadsheet of inventory into a little web based system and he had heard some stuff about Ruby on Rails and wanted to try it out. 8 hours later he had popped out his first app to replace a spreadsheet. And this is coming cold from no background in Ruby. He’s pretty jazzed about how nice and productive it is for web applications.

Setting up one-on-ones today:

• 10 employees.
• 1 30 minute one-on-one per employee per week.
• 6 months of meetings scheduled through the end of June.

Turns out this is 260 meetings over the next six months. The raw number of meetings would be enough to send the average developer running to Monster. Luckily the one-on-ones are really a handy tool to make sure at a minimum everyone gets at least 30 uninterrupted minutes with their manager to communicate concerns up, get help, vent, and get coaching or mentoring.