Moi? I think TDD rocks! If forced to choose, I'd pick pairing/code review in preference to TDD; but I wouldn't like to be forced to choose.
As for TDD itself... I like to capture facts in the type system where I can, so that the code doesn't even compile if something is wrong. After that I like the QuickCheck / ScalaCheck approach where values are generated and passed to your functions to validate invariants. After *that*... It's down to good-old unit tests On 21 February 2014 21:08, Rakesh <[email protected]> wrote: > Hi, > > **usual disclaimer about not looking to start a flame war** > > A friend of mine recently interviewed at a company for a position as an > iOS dev. > > The topic of TDD came up and my friend stated that she was a big fan. > > The interviewer on the other hand, said he wasn't and that the 'jury was > still out'. > > I'm curious, who is the 'jury'? > > As for myself, if i can join a team doing tdd or be in a position where i > can, i'm happy. > > This group is stocked with experienced devs so i'm not looking to convert > anyone, but surely by now, the nay sayers are in the decline? > > Thoughts? > > Rakesh > > Ps kevin, REALLY interested in your opinion. > -- 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.
