3 ms·
Not much to add to that, it's pretty much exactly the way I feel things ought to be. I.e. be sensible and use your head: if you've got things figured out, spen
by davidw 17y ago
Not much to add to that, it's pretty much exactly the way I feel things ought to be. I.e. be sensible and use your head: if you've got things figured out, spend some time putting together some good tests, they'll save you in the long run. If, on the other hand, you're still exploring, writing code and tests is likely to be a waste of time if you end up throwing things out a few times.
- hello_moto 17y agoAs long as your code can be unit tested, it's okay to test it later. But what if the "exploratory" code becomes hard or almost impossible to test (due to dependency et al.)? Refactor it? but you have no test that acts as a safety net during the refactoring period.