Timeline for If TDD is about design why do I need it?
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2011 at 16:29 | comment | added | Steve Jackson | +1 TDD is feedback. As most measures of feedback go, it's fairly objective and completely automated, so it can be shared by team members of all skill levels. Before TDD, good code was something you "felt", or was confirmed sometime after the users got the software. The shorter the loop, the more confident you feel. Unfortunately TDD is prone to overconfidence as "feeling" a good design, but it's far easier to self-correct. | |
| Aug 23, 2011 at 13:43 | history | answered | Wayne Molina | CC BY-SA 3.0 |