Just a pointer: Peter Provost decided to re-do a piece of C# in Ruby and ended up creating a nice little portrait of Ruby's flexibility.

I just noticed going through my blogroll that Jeremy had referred to my CruiseControl article--that is, Part 1 of the article. There's also a Part 2 but I've more than once forgotten to add a forward link from Part 1 to Part 2. I'll try to get that link up there one of these days...

Actually, I've been planning on pulling the articles I've written on my website as well but that might take a while.

In his recent blog entry titled programmers don't make projects fail, Udi Dahan argues (quite correctly, in my opinion) that, well, programmers don't make projects fail. I'll leave reading the blog entry to you but I would like to focus your attention on Udi's closing paragraph on the blog:

Not to end on a doom-and-gloom note, you'd be surprised how quickly you can identify real issues by checking overtime. Of course, the faster you identify these issues, the sooner you can resolve them.

While it's very true that programmers doing overtime is a good indicator of timely delivery being at risk, most projects--I'd dare to speculate--are in fact not aware of the need for overtime until very late in the project when it's already {drum roll, please} too late.

If you're dying to know the solution I have to offer for resolving that problem, don't hesitate to call my 24/7 telephone consulting line at 1-800-ITERATIVE ...