4 ms·
TDD is a kind of semi-formal specific process with a whole legacy of consultant workshops and all of that stuff. So I think it's great to mostly ignore that, s
by mbrock 10y ago
TDD is a kind of semi-formal specific process with a whole legacy of consultant workshops and all of that stuff.
So I think it's great to mostly ignore that, since it's contentious, and focus on that core question: how do I know that the system works correctly?
This also makes it obvious why type systems are a glorious ally, in addition to test suites and proofs.
And it's a core question because if I don't have grounded confidence in the system's correctness, then that's likely to be anxiety-inducing, irresponsible, and sometimes dangerous.
- cm3 10y agoRight, and I didn't learn TDD formally. Sorry for using it freely. I write tests in tandem with the implementation and do not write tests and only then the implementation.