¯\_(ツ)_/¯

It's just a logical fallacy you fall into when you write tests. Once you layout a design and write the tests you start having to bounce back and forth because believe it or not, tests can have bugs too.

I'm not sure I agree with that. Tests in any kind of development environment can have bugs, and if you don't realize it you'd still be changing the underlying code to reflect what you believe is to be a valid test. You'd still have to fix your tests and underlying code regardless. It's test driven development, not test driven design. It seems like you guys are saying TDD is "design by creatings tests" rather than "design and build with tests". I've never used it so I don't know how it works in large teams, just seems like what you guys are describing is a poor implementation of it. Who knows, maybe most people just suck at TDD and as a result it as a stigma.

/r/ProgrammerHumor Thread Parent Link - i.imgur.com