4 ms·
Empirical Studies on Software Quality Mythology
- 10ren 17y agoTDD improves quality but takes longer this increase in development time is offset by the by the reduced maintenance costs [in future] Seems it's better to forgo TDD if you need something out the door ASAP, but you'll have increased future maintenance cost if you stick with that codebase (i.e. it's not a throwaway prototype).
- swombat 17y agoThat's pretty much the intuitive conclusion too. I've never quite bought the "TDD makes you faster all the time" mentality. There is an initial slow-down.
- narag 17y agoI'd like to see a study that compares TDD not with "nothing" but with other methods of achieving quality. I had a very good experience with code revisions. Assertions seem to be demonstrably helpful too.
- dkarl 17y agoIf they got the TDD projects out the door with 60%-90% fewer bugs but only 15%-35% later, it seems like a small adjustment in expectations would get those projects out faster with equal quality.
- seanc 17y agoSo as I was reading the article I clicked on a bunch of the papers, queuing them up for a later purchase decision. But they're all open! Yay Microsoft! So much for my long weekend...