geepawhill.org/the-gold-of-mi…
how can such a low-seeming value really be gold?
let's work it out, eh?
we see this over and over again. in fact, noobs overemphasizing artifact over process-through-artifact is one of the reasons TDD is so hard to get in to one's head.
what have we got?
and we're done, we're not changing any code, so they don't give us a safety net, cuz there's nothing at risk.
if we're already completely done with the product, they're just so much used kleenex cluttering up our repo.
we've dispensed with the microtests. also the repo. also the compiler. and the programming language. and the manuals. and stack overflow.
*but* . . .
i promise i'll be back, and we really will go straight to a list of the value provided, all of which occurs when we're not done, and much of it occurs not from the microtests themselves but from the act of working with them.
:)
have a strange mid-evening!