TDD
There are 4 entries for the tag
TDD
This content comes solely from my experience, study, and a lot of trial and error (mostly error). I make no claims stating that which works for me will work for you. As with all things, your mileage may vary, and you will need to apply all knowledge through the filter of your context in order to strain out the good parts for you. Also, feel free to call BS on anything I say. I write this as much for me to learn as for you.
This is part 5 of the How We Do Things series.
In the last installment I talked...
This content comes solely from my experience, study, and a lot of trial and error (mostly error). I make no claims stating that which works for me will work for you. As with all things, your mileage may vary, and you will need to apply all knowledge through the filter of your context in order to strain out the good parts for you. Also, feel free to call BS on anything I say. I write this as much for me to learn as for you.
This is part 4 of the How We Do Things series.
Today we're going to talk about...
I suppose it's time for the obligatory weigh-in on the latest bit o' reckless software advice from Joel Spolsky on the merits of the "Duct Tape Programmer".
I think being a duct tape programmer is a bit like being an alcoholic. Once you become one, you are one, and when you want to stop, you have to constantly be vigilant against backsliding. Oh, and the first step is admitting you have a problem.
Hi, I'm Scott, and I'm a recovering duct tape programmer.
I don't want to get too deep in the weeds on Joel's article, because the simple fact is that it...
To the unintiated, the title is: The Safety Net - Test-Driven Development In Real Life For the Win. Warning - This post contains some of my thoughts about *practical* TDD and the reasons for it. This may not all encompass "dogmatic" TDD practice. To me, TDD is all-important first as a safety net. Before you find TDD soluble enough to understand how it helps you drive design, you have to understand that you're putting it there to save your code from you, your QA group, and most of all, changes. When I think about TDD, I think about it as...