News for hackers. Stuff that matters.

A comment on Test-Driven Development vs. Test-After Development. Parent comment

Re:Test-Driven Development vs. Test-After Development by ZeroGravitas on Sunday May 10, 2009 @11:47AM (#602201)
If something as simple as a checklist [1] can have a meaningful impact on patient care in hospitals, I think it's worth talking about the equivalent in software.

Neither claims to be any kind of science, but both can save the day by compensating for the natural human foibles of the practitioner.

[1]: http://www.newyorker.com/reporting/2007/12/10/071210fa_fact_...

[ Parent | on HN ]
Re:Test-Driven Development vs. Test-After Development by mistercow on Monday May 11, 2009 @12:45PM (#603775)
Sure, having an organization strategy is a good plan, and I didn't mean to imply otherwise. The problem I have is with people claiming that their way is the "right" way without having any legitimate scientific backing for the claim.
[ Parent | on HN ]