News for hackers. Stuff that matters.
Re:Is TDD Worth It? by halostatue on Saturday September 28, 2013 @12:34PM (#6462246)
I interviewed with a company one time that ran with TDD and pairing like a religion.

The guy I was interviewing with didn't like the fact that I thought about how the problem might be shaped (and therefore made assumptions as to what I might want to implement and refine via tests) prior to “writing” that first failing test. It was absolute nonsense and I was rather shocked that the company managed to ship anything, to be honest.

I'm a big fan of tests; I'm a big fan of pairing. They are tools; nothing more.

Re:Is TDD Worth It? by rrouse on Saturday September 28, 2013 @12:51PM (#6462309)
An interview recently felt like that. I was just throwing together little bits of code to make sure I understood the problem clearly, but the interviewer seemed to be a bit agitated that I didn't write a test right away.

I honestly don't work like that. So I'm kinda glad I failed that interview.

Re:Is TDD Worth It? by halostatue on Saturday September 28, 2013 @01:05PM (#6462349)
Yeah. I've recently done a couple of interviews on the other side of the fence (as the interviewer), and I've hit on a problem that can be worked out collaboratively between the interviewee and the interviewer—and how far we go depends on their skill.

It always begins a discussion of the problem and what we want to solve, plus a bit of how—so we can figure out what it is that we're going to be testing for and how to build from that point.