Although it's a useful example, it doesn't necessarily show an advantage of Perl over Java -- it shows an advantage of modifying an existing system, as opposed to restarting from scratch.

Depending on the exact details, it could also show that bringing in programmers who aren't familiar with the underlying business processes can hurt the development of new systems -- sometimes (most times?), it's better to take the time to training current employees in new technologies, than to bring in a contractor or outsource it.

(and I say that, currently doing long term contract work ... and I still don't understand most of the data that I deal with, 3 versions and 18 months later)

I'm not saying that good project management can rescue a surreal ship date no matter what, but bad project management with 30 people involved is never, ever gonna work out, regardless of the language used.

The way you describe how the slip date is handled is a red flag, and I've also seen it up close a saddening number of times. No small slips would be a nice pattern to apply here (and the book, Organizational Patterns of Agile Software Development is one of the most encouraging books I've ever read about software project management).

/J

Update: changed the pattern url to a more recent one

Language is just one detail of a project. A project in Java failed does not prove or indicate Java is a bad language. In this case, I would rather say that this proves in-house developement are usually cheaper and easier to control than using outside consultant.

In this case, I would rather say that this proves in-house developement are usually cheaper and easier to control than using outside consultant.

Huh? What makes you say that? There were no outside consultants used! Both the Java team and the Perl team were in-house.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Amazing. This stuff needs to get out there more. Too bad I don't have permission to reveal more details.

It would be interesting if you could set up a meeting between a Perl advocacy group and businesses with Perl success stories like that, given the right price/agreement the company might agree to have the story published. Perhaps this is a bad example because it sounds like the company's management made a mistake by hiring the Java team in the first place, but I'll bet that you (and others) know some good stories that would reflect well on a company.

Just a random thought before bed. :)