PaddyCorry

Great article, thanks.

Kudos to Volkswagen for enforcing the blackberry 'opening hours'. (And here's hoping more companies start to ban internal email!)

Great post.

Nice article, thanks.

My first job out of college was in a support centre, supporting voice recognition software: an early ancestor of Siri if you like! One weekend without our knowledge, the parent company stuck a prior version of the software onto a free bundle cd that came with a PC magazine in the UK... a great marketing move sure, but the amount of calls we got as a result of that free software was incredible. People can get irate when voice recognition software doesn't work as well as they expect (for a variety of reasons, generally either hardware or accent related!), but with this free version, people really lost the run of themselves altogether... some of the calls we took that week were from some very angry people indeed!

The writer of this article summed up this confusing paradox quite well by offering a refund... for this free item... which was a gift!

Nice idea! Where I work, agile is very successful in the development teams, but interaction with Ops is a constant source of frustration.

Implementing something like this in my organisation would involve a real culture shift, but I can really see the value of the idea. Thanks for that.

The recommendation to 'dismember' the project is particularly harsh! Killer line towards the end though: "we will be moving to an innovative new system."

Nice piece. Something my female friends always do on FB, and that I half-expected the article to mention, is the 'perfect day' status update.. ie one along the lines of 'walk in the park, dinner at Mario's, curled up on the couch with <insert partner name here> and a glass of wine, perfect!' ... the scenarios described might be different, but the common factors are the veneer of amazingness, and the fact that they always end with a declaration: 'lovely', or 'great', or 'perfect'.

(This is one of David O'Doherty's 'beefs', towards the end here: http://www.youtube.com/watch?v=GCgYIP-v-e0 )

Nice article. Good to see a positive Java piece.

I'm formerly a COBOL developer, now working with Java. Did anyone else think that his main argument for learning Java could also work for learning COBOL? (substitute COBOL for Java in the quote below)

<quote> It's not going to go away any time soon. There's too much momentum. There's no need to worry. Ever since the launch of Java I've heard that it's going to be gone or unusable tomorrow. History shows that just doesn't happen to popular programming languages.

If you learn Java now, you may still be using it 20 years from now. Or 30. </quote>

Think this is also true for anyone who works in an open plan office. Any number of halfalogues can be going on at any one time, tough to tune them all out without an mp3 player of some kind.

I work on enterprise software in a financial company, and IMO, this quote from Zawinski would lead to a dangerous short-term view in that context: "unit tests are not critical. If there’s no unit test the customer isn’t going to complain about that."

When you work in enterprise software, this approach might work on the first project, maybe the second, but eventually a point will arrive where a requirement will take longer to deliver for the simple reason that there are no unit tests. Without unit tests, bugs will be found later in the project life-cycle, possibly even after delivery. If customers have delivered software that is unusable, the fact of delivery becomes a negative pretty quickly..

On the positive side though, the tension between what's essential for the customer, and what developers need to learn to keep their careers alive is an interesting idea, and is something we've been looking recently at where I work. Is it a good idea to introduce a technology just because a programmer feels s/he should learn it? I'm not so sure.

Effect / affect is a bugbear of mine, it pops up every now and again in bug descriptions and so on i.e. "this bug has effected a number of users".

Great reference site, thanks.