In the earlier days of the ruby community, I feel TDD was seen as gospel. And if you dared say that TDD wasn't the way (which I always felt), you'd feel like you were ostracized (update: just rewording to say, you'd worry that it would hurt you in a job search, not that people were mean to you). So I never spoke up. I feel like I was in the TDD-bad closet.
I absolutely think _tests_ are useful, but have never found any advantages to test-DRIVEN-development (test-first).
But part of that is probably my style of problem solving. I consider it similar to sketching and doodling with code until a solution that "feels right" emerges. TDD severely slows that down, in my experience, with little benefit.
What I've found works really well is independently writing tests afterwards to really test your assumptions.
I absolutely think _tests_ are useful, but have never found any advantages to test-DRIVEN-development (test-first).
But part of that is probably my style of problem solving. I consider it similar to sketching and doodling with code until a solution that "feels right" emerges. TDD severely slows that down, in my experience, with little benefit.
What I've found works really well is independently writing tests afterwards to really test your assumptions.