Re:Tips for beginning systems and software engineers
by cm3 on Thursday May 19, 2016 @06:17AM
(#11729133)
TDD can be tedious at times, but if you do it, you quickly reap the benefits. It makes testing easier, it reassures you that you didn't break everything completely with a random change, and it keeps your API in check. And it makes more of the process reproducable.
[ Parent
| on HN ]
Re:Tips for beginning systems and software engineers
by mbrock on Thursday May 19, 2016 @06:48AM
(#11729233)
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.
Re:Tips for beginning systems and software engineers
by cm3 on Thursday May 19, 2016 @07:07AM
(#11729300)
Right, 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.