3 ms·
What about a kind of middle ground, doing a 'spike' when figuring out stuff, what kind of thing you should build, what the design should look like, etc then fol
by krmboya 9y ago
What about a kind of middle ground, doing a 'spike' when figuring out stuff, what kind of thing you should build, what the design should look like, etc then follow up with TDD to stabilize the identified interfaces and produce tests that act as a system health check?
Ok, for consultants, perhaps they end up doing the same kind of things for different clients to the extent that they can just jump in doing things TDD from the very beginning.
- poushkar 9y agoThat's exactly how I work (web development) and I am really happy with it so far. First, I am playing with a throw-away code to understand how I want it to be. Then, I write some tests based on the acquired understanding and then finally working code. I can even copy-paste some parts of the throw-away code if they were correct initially. I see my designs being damaged by tests sometimes, though but in tolerable amounts, and I am happy to compromise.