On Sun, Feb 23, 2014 at 2:51 PM, Philip Schwarz < [email protected]> wrote:
> > In "TDD Triage" [1] Robert Martin has a section called "Well, if you are > going to write some tests afterwards, why not write all tests afterwards?". > This is a fallacy called "slippery slope" which I have no interest going down on. And again, given Uncle Bob's financial interest in the success of agile, I take everything he says with a grain of salt, and from a more general point of view, I find his writings very far removed from the day-to-day reality of industrial software, especially in all the dogmatic approaches that he recommends. If there's anything I've learned about software development in about 40 years of practice, it's that it's constantly changing and that there are no absolute rules. > So, *all else being equal*, test-first is clearly better than test-after." > "Clearly", really? Not even a shred of a doubt there? There is never a time where test first might be worse than testing after? See what I mean when I was talking about dogma? -- Cédric -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/groups/opt_out.
