Skip to content

Tag Archives: test first

JAOO Brisbane 2009 highlights and thoughts

I spent last Monday and Tuesday at the JAOO conference in Brisbane, and I have a couple of things which I want to say I thought interesting. (‘JAOO’ btw, because I see people asking about it on Twitter, is pronounced a bit like “yow” but with the “j” from German/Dutch like “jah”). Firstly, I found […]

Let it fail then learn to succeed

On the scrum development mailing list, Dave Nicollette recommended shortening sprint length until it failed, then backing up one step: “Oh, my God! You’re going to let a sprint fail, just so you can determine the optimum length?” Yes. In other words, failure lets you learn your limits. But more importantly, as suggested here, is […]

Incremental test running with JUnit Max

Well looks like Joel Spolsky’s ignorant rant about Test Driven Design (TDD) resulted in some good after all. Kent Beck posted a brief response to Joel, which was pointed out in a mailing list discussion about the issue. But that’s not what I wanted to talk about here. Anyway it turns out that Kent is […]

Programmerless programming is just a mirage

“Programmerless programming” is a fad that never dies. It’s a mirage that never fades but always recedes to just out of reach. Every few years a vendor, or a group of vendors comes out with some bright idea to allow some class of end-user, or business analyst, or what have you to build their own […]

Unit testing as a discipline

In Emergent Design Scott L. Bain dedicates a chapter to Paying attention to Disciplines: Unit testing. To an experienced agilist this may seem a little basic: of course the discipline of unit testing pays dividends! But I think that we agilists forget sometimes that there are still many programmers – or their management – who don’t value the investment […]

Emergent Design & Professional Software Development

Recently I read Emergent Design: The Evolutionary Nature of Professional Software Development by Scott L. Bain (on Amazon). It’s a very interesting read. [E]mergent design works by refactoring and enhancing code, due to the changes, bugs, and extensions that have to accommodate, while paying close attention to these principles of coding. (152) In order to deal with the […]