login
Blurts on the Art of Software Development

Today | RSS | RDF | Atom | Other Tags
Categories : All | All | CI | .NET | General | Humour | Java | Personal | Reviews | Ruby | SW Eng

Jeffrey Phillips talks about him belonging to the prototype-oriented quick and dirty camp rather than the flesh-it-all-out-as-you-go camp.

Where I think Jeffrey fell off the sled a bit was the "dirty" part. What he describes as the benefits of his innate approach (failing early and learning from it rather than failing late) is almost synonymous with risk-driven, incremental development. That is, he could be talking about pretty much any agile method.

Except that he said "dirty."

It's easy for organizations to jump on the agile bandwagon and get all the benefits of quick-and-dirty. It takes a more thorough understanding of the discipline and craftsmanship needed to go beyond quick-and-dirty and into the realm of truly sustainable agile development. The world of quick-and-clean.


Of course you could say that in XP or in the TDD cycle, the initial "simplest thing that could possibly work" is often quick-and-dirty. When doing work, you often produce a lot of dirt (in Finnish "rapatessa roiskuu").

It's just very important to clean up immediately after.



Add a comment

Title
Body
HTML : b, i, blockquote, br, p, pre, a href="", ul, ol, li
Math Quiz 9 + 3 = (Helps stop blog spam)
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).

TrackBack to http://radio.javaranch.com/lasse/addTrackBack.action?entry=1146310209092