3 ms·
I'd translate this as "don't use tests for proof-of-concept code". At least not when success is easily observable.
by bencollier49 11y ago
I'd translate this as "don't use tests for proof-of-concept code". At least not when success is easily observable.
- jacques_chester 11y agoIn XP settings this is called "spiking" and is recognised as an entirely legitimate tactic. The point of spiking is that you don't know enough to TDD. You are outside the sweetspot where TDD is tractable. The key to spiking is that once you come with a plausible approach, or have a conceptual breakthrough, you stop, backtrack and then switch back to TDD. Like everything else in mature software engineering, agile or classical, it requires sustained discipline.
- bencollier49 11y agoInteresting. I've found myself drawn into XP-style delivery repeatedly, probably because I tend to work closely with clients who have rapidly shifting or unknown requirements.
- jacques_chester 11y agoWe have a London office. Email me and I can probably ask if they'll let you visit. (They'll try to recruit you, but TANSTAAFL).