News for hackers. Stuff that matters.

A comment on The Pragmatics of TDD. Parent comment

Re:The Pragmatics of TDD by pnathan on Wednesday March 06, 2013 @03:13PM (#5333516)
I just cranked out a pile of code under pressure with a tight time constraint. I didn't TDD. What I did was codesign my tests and code: I rotated between the test and code so that when I finished a particular function, it was reasonably tested.

While not, NOT a TDD approach, it did lead to a much higher code coverage and added a safety net when I had to change it: I knew I could change the code, and if the result was materially affected, I'd know.

It did slow me down in the initial writing, but in the revisions, it sped me up, IMO.

[ Parent | on HN ]
Re:The Pragmatics of TDD by jfabre on Wednesday March 06, 2013 @04:06PM (#5333926)
I agree with you, but before one can transcend TDD, one has to learn it. The pupil was no longer confused. ;)

Seriously, the current status quo most of us live in right now is zero to very few automated tests. That's what I'm arguing against.

[ Parent | on HN ]
Re:The Pragmatics of TDD by pnathan on Thursday March 07, 2013 @12:46PM (#5338968)
> I agree with you, but before one can transcend TDD, one has to learn it. The pupil was no longer confused. ;)

I do not claim trascendence. It's just what worked for me. I've never done TDD at any time in my life. Note, after reading the arguments for it here, I think I will give it a spin.

[ Parent | on HN ]