3 ms·
I know when I'm coding for me I don't because to me, tests don't solve the problem I'm out to solve at the time. I want this thing, over there. A test does not
by salawat 8y ago
I know when I'm coding for me I don't because to me, tests don't solve the problem I'm out to solve at the time. I want this thing, over there. A test does not get it there.
Now, once I'm done with getting that over there, then I look at it and evaluate my level of testing I'm going to commit to it.
Some code, I can keep straightforward and narrative enough where even coming back a year later, I can pick it up and quickly move with it. Part of my secret to doing that is forcing myself to sit down with a saintly non-programmer, and talk them through it.
If I can get them to follow, I've got it nailed down. If I can't, I haven't whittled it down to it's simplest incarnation.
For all the other code... Let the test suites be written!