Virtual Surreality

Lots of technology blogs piled up, but first thing’s first.

Last week I was in Chicago for some meetings at the ThoughtWorks head office. On the Monday night one of my colleagues hosted a charity fund raising dinner which included some magnificent Ethiopian food (and beer).

During a presentation, she told us personal anecdotes about a trip to Africa and her visit to the AHOPE orphanage. We were told a number of stories of the adoption of kids into the few countries that allow foreign adoption of children with HIV and how now, with the anti-retroviral medicines becoming more readily available, those kids have more than just short-term palliative care in the orphanage, they have a chance at being raised in a healthy, comfortable (albeit Western) home and leading an independent adult life.

As they say on the site, ‘Are you looking for just the right gift that isn’t just “stuff” for a person who has everything and needs nothing, whose heart would be touched by reaching out to a child who has nothing and needs everything?’ Even if you’re not the next Brangelina, have a look at what you might want to donate to provide a lot of help for just a small amount.

This short video reminded me of being at my daughter’s pre-school – except of course these kids don’t have their parents picking them up after the songs are done.

My colleague Jay Fields recently blogged about the value of test names.

We had a little discussion about it yesterday on IM. Here’s a summary.

Josh Graham

I feel the test name is important for two reasons:
1) it is intentional programming – a neural pathway is established in your brain as you write the name of the test method so your mind tries to think about what the hell you are trying to achieve by doing all that typing
2) for those test consumers you speak of to get a sense of the behaviour of the system as specified by the stories and high level acceptance criteria

Jay Fields

2) [is] fair enough. Before introducing expectations on any client project I’ve brought it up as “what do you think about” and let the team decide. The last thing I want is an idea to be branded as bad because the wrong ppl used it
1) I think is based on the person. I always found it 10 times harder to write a sentence, I just want to get to the code but, I’m crazy for making the code intention revealing

Josh Graham

Picking a reasonable moniker for the test name is useful too, when something breaks (particularly if it occurs often)… “That #$%#$%! shouldRejectLostOrStolenCard test is failing again – must be the clearing house API has changed or they’ve crashed once more”.

Jay Fields

yeah, that’s an interesting point
wish you would have replied with that one, I’d have put it in my entry

We then talked about how to attach a moniker to the test on different languages – method names in Java being the easiest, while anonymous inner classes being a way to do so without having a moniker (other than perhaps a comment) at all.

I still contended that a method was a reasonable level of granularity to contain a test and use the method name as the moniker. A method (it’s declaration and its body) is location independent – it can be moved around in its module and you can still find it and its moniker appears in the abstract syntax tree so it’s very easy to find when using an editor that maintains an AST.

Jay’s responses to my scenarios in which this proves useful assume a short TDD cycle and also good developers.

So, while the test name may be superfluous in some cases, I don’t mind the extra mental effort of summarising the intent of the test into its name – and if that is overly difficult or not needed (both of which are plausible) then a banal label like enclosing the test in a method called “test1″ is a small price for me to package it up in a manageable, easy-to-find chunk.

YMMV.

I am in IT. I think it’s pretty easy to find that out about me. Nothing in my CV indicates the ability to fly aeroplanes or helicopters.

Either the pattern matching spamming software has gone wonky, or this dude has set a new low watermark…

(with apologies to the half dozen recruiters I have met that are anything but lame)

I have 1750 hours on Saab 340B and 340B Plus with American Eagle and
Pacific Coastal in the US and Canada respectively.

Is this a job for Rex?

> Hello Joshua
>
> Apologies if this has made it to you by mistake…..
>
> I am looking for EMB120 Pilots, Bell Helicopter pilots and Metroliner 23
> Pilots and SAAB 340 pilots for FO and captain roles.
>
> If you have 500+ hours on these types, please contact me as soon as you can.
>
> Thanks.
>
> Best Regards
>
> (name removed to protect the stupid)
> Recruitment Consultant

JoshG is a busy bee:

• Australian Architecture Forum 2008 (Melbourne May 16 & Sydney May 19): Final keynote (with Richard Durnall and Jim Webber respectively)
• JAOO Australia 2008 (Brisbane May 28-30 & Sydney June 2-4): organising
• Enterprise 2.0 (Boston June 9-12): attending
• Agile 2008 (Toronto August 4-8): speaking

If you are a software technologist in Australia, I strongly encourage you to attend JAOO Australia as it is arguably the best technical conference in the world and it is certainly a boon to have it come to our neck of the woods. We are getting some superb international speakers that you’ll be able to interact with throughout the conference (they stay around at JAOO to learn too), and the more we support it, the more we’ll get next year.

Hot on the heals of the Mingle 2.0 announcement, ThoughtWorks Studios has released information on the next generation of the world’s most popular Continuous Integration engine, CruiseControl, called Cruise.

It is a ground-up rewrite accomplished in around 8 months with an emphasis on catering to enterprise software development teams and large-scale applications. It combines sequential build pipelines (for, say, progressively more complicated or longer-running tests) with concurrent build tasks using a grid of agents.

The Cruise server can dispatch work to agents on ye olde CruiseControl servers. Although the Cruise product is not Open Source Software, the licensing terms are generous and in line with Mingle. Pricing is yet to be released.

With the usability innovations of cc.rb and the great foundation laid by CruiseControl and CruiseControl.NET we’re excited at the prospect of using the newest and best Continuous Integration tool on the market, from the company who changed the way developers integrate their software changes and who wrote the book on build pipelines.

In response to Dr Nick’s technological feat, Ajey suggested I take on the much more challenging task of running OS X on a PC.

Result!!

Also, Mingle 2.0 is released! Another fantastic effort from the ThoughtWorks Studios crew.

Software intelligence has come of age!

My colleagues at ThoughtWorks Studios have cracked the automation of the software development process. Compuware, IBM and Borland have been trying for years. MDA is the useless love-child of CASE and UML. It takes true genius to solve this problem:

http://studios.thoughtworks.com/mingle-hidden/introducing-mingle-proj-o-matic

My erstwhile colleague, Jon Tirsen, now at Google in Sydney, has also announced a truly amazing feat in blending statistical analysis, complex hypercube maths, and their super clever search engine. I’m proud that Jon, although Swedish, has embraced the Aussie vernacular and called the product “gDay” (which is supposed to be “Google Day” but we all know where he keeps his surfboard). I’m also happy that they put Graham’s number to good use in this truly extraordinary achievement.

http://google.com.au/gday

My CTO, Rebecca Parsons, announced the publication of the ThoughtWorks Anthology a few days ago:

I am thrilled to announce that the ThoughtWorks Anthology is now ON SALE!

http://www.pragprog.com/titles/twa

There are essays by Roy and Michael Robinson, Martin, Neal Ford, Tiffany Lentz, Stelios Pantazopoulos, Ian Robinson, Erik Doernenburg, Kristan Vingrys and James Bull, as well as ex-TWers Dave Farley, Jeff Bay and Julian Simpson. (And of course your’s truly made her own contribution). Mike Aguilar wrote the introduction.

Some comments that appear in the book:

Jim Fischer writes, “The anthology provides a peek into the diversity of views and perspectives held by a company that dares to take on the long-accepted tenet of the IT industry that custom software is too hard and too costly.”

Big Dave Thomas writes, “Software is in many ways a team sport, and the leaders shape the software culture. Often successful organizations don’t take the time to document them, and hence others don’t benefit from them. This interesting collection of personal essays gives a glimpse into the culture of ThoughtWorks through some of its leaders.”

I’m really excited that this project has come to fruition and I hope you all enjoy what you see.

Rebecca

I was lucky enough to review the content earlier this year. It’s a keeper.

UPDATE: Some press… http://www.sys-con.com/read/541124.htm

http://money.cnn.com/2008/03/14/technology/kirkpatrick_thoughtworks.fortune/index.htm

Nuff said (although journalists never quite get it.)

After a meeting of the office of the CTO, most of us stayed around in our San Francisco office for a few days to do some podcasts and to participate in a Code Jam for Inveneo, a not-for-profit who provide computers and connectivity to developing countries (especially their schools, hospitals, and poorer villages).

They install a server in, say, a hospital with a few lower-powered, custom desktops (almost iMac in configuration). These, as well as the servers, can run off solar panels for power.

We were presented with a worthwhile problem with a number of interesting constraints:

• Low-power server running Ubuntu, with two small SATA hard disks in a Linux software RAID-1 array
• VMWare images of the servers for testing
• Python, bash, mdadm, and beep as our “programming languages”

When a RAID array fails, we need to alert any (if any) humans who are near the server. This can be interesting as the only things nearby might be the tree it is mounted in with a long-range WiFi, or the goat who uses it as a heat source at night. This means that any alert should be sufficiently frequent and annoying for the locals to contact someone who can let the support technician know. The conflict is that it also might be the nurses in their office at the hospital who have work to do and don’t want to be disturbed.

The solution was to use the PC speaker to beep. We can control the pitch and duration of the beep. Some combinations sounded too much like an ECG machine so that was no good. In the end, we chose a simple rising scale that would sound odd in any environment (except, perhaps, in a Mike Oldfield recording). This is repeated by default every 30 minutes.

We also had to send an email to the support technician. This doesn’t work when the server doesn’t actually have any connectivity (as some are used only as a local communications hub), or when connectivity is unreliable. Even then, many of the technicians are hours or even days away from the servers.

As many of the technicians aren’t particularly technical, we also had help by identifying which of the two disks had failed and allow them to simply change the one labelled “Disk 1″ or “Disk 2″. Serial numbers are good for this but VM hard disks don’t have serial numbers (I think that’s a feature request to both VMWare and Parallels).

We had Jeff Wishnie from Inveneo as the customer, Anda Abramovici as IM, Jonny Leroy as BA, Paul Hammant and Chad Wathington as QA, and the star developer crew of Drew Olson, Sammy Zahabi, Ola Bini, Erik Doernenburg and your’s truly. We quickly learned the following:

• The skills we needed (and had, just a little rusty) were more along the lines of Unix devices, shell, ASCII control characters, and simulation
• Python sucks (a bad tradesman blames his tools? perhaps – but it still sucks)

Anyway, we got most of what we wanted done in the time, and given the context, more than we anticipated. But we all would have liked to get a lot more done and would have if we were using our tools of choice (which are chosen for very good reasons).

Nonetheless, we’re doing it for the kids and it was great!

What a buzz. Super Agile. Super Fun. Go Inveneo, you rock!!