Jomo Fisher uses the whole Test-First whale: "Famously, subsistence hunters use every part of their kill. This makes sense because it’s hard to catch a whale. If you expend that kind of effort, you need to maximize your return. If you don’t then you’ll freeze tail all winter while your neighbor down the coast is toasty warm next to their blubber-oil stove."
Johanna Rothman wants an end to bugs: "The first step in solving problems is to acknowledge that you have them. If you want to deal with the defect problem, stop calling those problems bugs. Bugs may be an acceptable name, but it’s not a helpful name. Call the problems defects or problems or faults — something that will help people realize they need to examine why it’s acceptable to allow defects into the code." Also read Johanna’s follow-up and Keith Ray’s take.
Paul Kenney decides legacy changes are too costly, and that now is the right time: [url=http://www.pjk.us/pjk/blog/index.cfm?event=showEntryForID&entry=EC6B804B-3048-28E9-DABD0EA0A812D44A]Unit tests to the rescue![/url]David J. Anderson publishes some Feature Driven Development benchmark metrics, based on his experience with real projects over the last 6 years.
Chris Jones wonders about the place of iterative development in game development and asks for pointers.
Sven Gorts re-considers the Single-Assert rule: "A single assert per test is generally considered good unit testing practice. Yet there are times when I prefer to deviate from this rule."
Mathias Meyer reviews Xcode.
Patrick Cauldwell states [url=http://www.cauldwell.net/patrick/blog/PermaLink,guid,f4963798-16fe-49d5-8beb-7d847a0631b1.aspx]code-freeze or tree-locking is counter productive[/url], and suggests using labels: "Code freezes pretty much take the continuous right out of [continuous integration]. The solution, you ask? Labels. I think most people don’t realize how many groovy things you can do with good labeling policy."
Keith Ray also addresses frequent releases in "Can do" not "Have to do": "There’s an idea that XP is only useful for frequently-released projects, and not so useful for projects that ship annually or less often. I would say that XP is useful for both."
Michael Mahemoff discusses Patterns as Refactoring Tools and identifies two main themes: Pattern refactoring for education and Pattern refactoring for development work.
Brian Button posts his slides on Programmer Tests as Agile Documentation from a recent talk at St. Louis OOSIG.
Microsoft recently published a paper on [url=http://research.microsoft.com/research/pubs/view.aspx?type=technical report&id=917]Parameterized Unit Tests[/url]: "Parameterized unit tests extend the current industry practice of using closed unit tests defined as parameterless methods."
Brian Button introduces the next concept in conferencing with "iterative talk" in Agile Speaking.
Just when we thought April Fool was behind us, K. Scott Allen announces DICA as a pairing facilitator.
On your agenda:
Jonathan Cogley will present an MSDN Webcast on Test-Driven Development with NUnitAsp on June 1, 2005, 1pm, in which he intends to transition from TDD principles to UI test driving to the Thycotic.TddStarterKit.
On Tuesday June 7th, Kent Beck will discuss his latest insights on eXtreme Programming and Developer Accountability in a webinar organized by Agitar Software. Details here.
Neil Roodyn is to present on "eXtreme .NET, An Introduction to Better Software Development" at a July half-day conference organized by Scottish Developers in Edinburgh on the 21st of July.