= 27d567bc2d48d9f40e9ccc20ea370b15)
matt comments on Coding Rationally - Test Driven Development - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (82)
Jonathan - one of the reasons to write unit tests is so that programmers other than you can see what your code is designed to do (for occasional values of "programmers other than you" that includes you when you're not at your best). Inheriting someone else's bad tested code is much less painful than inheriting someone else's bad untested code.
(And I humbly observe that a larger proportion of the untested (or sparsely tested) code I've inherited has been bad than the tested code that I've inherited.)
I agree that automated tests are more important in multi-person projects. I do value whatever tests exist in projects I've worked on (including my own solo stuff); I just don't always choose to spend the effort creating them.