FavouriteExtremePractice

I vote for Wiki.DoTheSimplestThingThatCouldPossiblyWork?, but at the moment I am in to Wiki.UnitTests (especially writing them first). PaulSimmons

I also vote for Wiki.UnitTests - however recently we have been concentrating on Wiki.RefactorMercilessly? especially with respect to both Unit and Functional tests. Its too easy to be lazier with your tests and it really slows you down when you want to make changes -- TimM

Difficult decisions ...

I vote for Wiki.DoTheSimplestThingThatCouldPossiblyWork?, but at the moment I am in to Wiki.UnitTests (especially writing them first). PaulSimmons

I also vote for Wiki.UnitTests - however recently we have been concentrating on Wiki.RefactorMercilessly? especially with respect to both Unit and Functional tests. Its too easy to be lazier with your tests and it really slows you down when you want to make changes -- TimM

I'd pitch for the Wiki.PlanningGame. It's the first technique I've seen for ensuring that the appropriate people make the decisions. Writing code more effectively is meaningless (well, you know what I mean) unless somebody really wants it. -- SteveFreeman ³³agent³Mozilla/4.5 en? (WinNT?; I)³FavouriteExtremePractice