4 ms·
You do realise even the founder of TDD doesn't back it anymore and code coverage is a very poor metric, your words sound like a senior developer from 2010. If h
by amriksohata 10y ago
You do realise even the founder of TDD doesn't back it anymore and code coverage is a very poor metric, your words sound like a senior developer from 2010. If he's a bad developer the best he can do is read up on SOLID principles and read a book like Clean Code with good examples of how to write code.
- amriksohata 10y agoThat said, from the article it just sounds like he's worked for shitty companies that don't understand the value of not writing code twice
- jghn 10y ago"You do realise even the founder of TDD doesn't back it anymore" I ask this out of genuine curiosity but do you have a cite for this? Being fairly anti-TDD myself it'd be good to keep this factoid in my pocket.
- matthewmacleod 10y agoTDD is still a fine tool and the field hasn't moved on so much in 6 years that it's a stupid suggestion. It's a perfectly viable tool for helping to maintain output quality - like all other tools it might not work for everybody, or it might have to be applied carefully. But I wouldn't advise anyone to cargo cult the apostasy of a single proponent.
- emmelaich 10y agoIf you're referring to https://www.facebook.com/notes/kent-beck/rip-tdd/750840194948847/ https://www.facebook.com/notes/kent-beck/rip-tdd/75084019494... he was being sarcastic. But he also has said it can be over-done. Which is not surprising, because everything that can be done can be over-done.