Ahhh… that’s the first production release of my latest project at work out the door today. I can’t talk too much about specifics, but it’s not a big secret that Wotif is enabling various B2B aspects of our web site, mainly with the registered hotels. Today saw the first big step in that direction. :) And it feels great to see a new project go out and get used.
(more…)
A bloody excellent IT Conversation podcast by Jason Fried of 37signals, taken from O’Reilly ETech 2005.
Jason covers a lot of issues that are at the heart of Agile Development, particularly when it comes to keeping your codebase lean-and-mean, and the YAGNI principle.
Seriously: everyone should listen to this.
Tags: agile
From Ron Jeffries, courtesty of the XP Mailing list:
“YAGNI is about coding, not about thinking”
Tags: agile, common sense, quote
From the JUnit mailing list, courtesy of J.B "JUnit Recipies" Rainsberger
JBR’s postulate 1. For every testable design that requires exposing elements “just for testing”, there exists an equivalent testable design that does not require exposing elements “just for testing”.
A very interesting article, originally published in 1992, on Code as Design Yet more proof that there isn’t anything new about Agile (and that’s it’s best part! ;)
Tags: agile
This has been said before, I know, but it’s worth re-iterating: a test should test one thing, and one thing only.
First, some scope definition. Using Kent Beck’s terminology, I’m talking about developer tests, not acceptance tests. Also, by one thing, I mean that there should be only one thing that breaks the test (which is very different from saying any failure should only break one test…). In addition, the one thing that breaks should provide diagnostic information – a test failure shouldn’t leave you scratching your head to determine the immediate cause
Two interesting examples of how the word “accountability” can mean different things.
Tags: accountability
I had a comment lodged on an older article recently. The poster was complaining about the poor quality of the JWebFit sub-project of JWebUnit In particular, he was complaining about how it meant their project wasn’t delivered on time. There’s an anti-pattern here.
(more…)
I love it when I get to delete code. Deleting code, particularly dead code, is such a wonderfully therapeutic exercise. You should try it some time.
Tags: refactoring
You are currently browsing the archives for the Agile Development category.
Del.icio.us Feed