3 ms·
> I in no way want to sound like a dk but as an engineer it is your responsibility to practice test driven development but that's not enough. One of the things
by jeswin 11y ago
> I in no way want to sound like a dk but as an engineer it is your responsibility to practice test driven development but that's not enough.
One of the things that put me off when it comes to TDD is that it has always been a bit like religion.
What matters is whether the tests exist, not when they were written. I'd even argue that writing a test first and then being constrained by that box is a bad idea. Write the most elegant code first, and then write tests to cover all paths. You're more likely to know the problem better after the code is written.
- darkr 11y ago> What matters is whether the tests exist, not when they were written Technically true, but with myself at least; when I do TDD, I tend to write more, and better tests. When I write tests after code, especially when working on tight deadlines, there are substantially less tests written, just lots of TODOs that never get done.