Jason Gorman"The problem with test-first is that you end up with lots of tests"
Okay. So how many tests would you end up with if you wrote them *after* the implementation? Fewer?
Hmmm. Interesting.
The problem with test-after is [insert your own punchline here]
Dave W Smith@jasongorman Ask them to complete the thought. Often it's some combination of "... and then the tests run forever and slow us down," and "the tests are brittle, and having to constantly stop and fix them slows us down." There's not great guidance on how to navigate that (or there is, but it's drowned out by guidance that isn't so great).