The Failures of “Intro to TDD”

Re:The Failures of “Intro to TDD” by rubiquity on Thursday June 18, 2015 @10:00AM (#9738517)

Any discussion about TDD requires a link to Rich Hickey's Hammock-Driven Development talk: https://www.youtube.com/watch?v=f84n5oFoZBct

The important thing that TDD or any other software design methodology is trying to accomplish is getting you to think about the design of your programs. However you want to accomplish that is fine as long as you take some time before you open your editor and think before you start writing code. It doesn't necessarily have to be TDD.

[ Parent | on HN ]

Re:The Failures of “Intro to TDD” by marcosdumay on Thursday June 18, 2015 @12:02PM (#9739452)

Funny thing.

I think that thinking about the design of my programs is easier once I have some amount of working code.

There's a minimum organization needed for starting to code, but every time I decide to think any further when solving a problem I'm not used to (optimally that would be always), I end up optimizing for the wrong problems and have to restructure it all later anyway.

[ Parent | on HN ]

Re:The Failures of “Intro to TDD” by rubiquity on Thursday June 18, 2015 @12:26PM (#9739671)

That's a great point! I've certainly had times where spiking a bit of code and then thinking was valuable. There are no maxims in program design so I'm glad you took the time and thought about that :)

[ Parent | on HN ]