Is TDD dead?

It says that "Nintendo" or "任天堂" the brand name refers to an old Chinese saying "謀事在人，成事在天" which means "Man proposes, God disposes", or "do your best and leave it to the fate". The idea is not far from the stoic ones - try your best and stop worrying. It's like an idea from this classic debate on TDD [0]: Unit tests make you confident. You write it, you forget it. It makes you sleep at night. In my first few years of my career, I was constantly and unconsciously thinking about the code, the business requirement, the team, even outside the working hours. That stressed and drained me a lot. In the end I realized I shouldn't have done that. If I am to worry about those things, I just book myself a calendar and go over those things within the time-box. If I need more time, I book another time block for the next day - as simple as that. Now write that "unit test", forget it, and sleep well at night. If you really need to worry about them, you should have a "quarterly/monthly worrying day" to reflect about your life, your career, strategies and all that. Outside that day, you just live your happy life. [0] ▶ this video

Hot take. Unit testing is not overrated, if you feel this way you likely just suck at optimising your suite for high RoI tests or chase some stupid metric like code coverage getting mad when you find out you wasted a bunch of time writing worthless tests. ▶ this video

I'm not sure I buy this. Quote from Martin Fowler: ▶ this video > I share with with David and Kent, there are problems where TDD doesn't work terribly well, and sadly most of the programming I do these days is not conducive to TDD and I miss it because actually I really like the TDD flow that really works for me just as it works the Kent.

I can't recommend the discussion between Kent Beck, David Hansson and Martin Fowler enough. They look at how and where it should be used and in particular discuss their approach to mocking which I feel is an often misunderstood tool. Part 1 - ▶ this video Part 2 - link Part 3 - link Part 4/5 - link

> Because DHH is just one person. And he only has DHH's experiences. Yep. Uncle Bob is one person, too. tl;dr Think for yourself and don't listen to somebody just because they hurt your feelings. > To pick a topical example: Is TDD hard in Rails apps because TDD is dead or because Rails makes TDD hard? This is a misrepresentation of what DHH has said [1], which is that strict adherence to TDD can make your designs worse: > Over the years, the test-first rhetoric got louder and angrier, though. More mean-spirited. And at times I got sucked into that fundamentalist vortex, feeling bad about not following the true gospel. Then I'd try test-first for a few weeks, only to drop it again when it started hurting my designs. > Used as a hammer to beat down the nonbelievers, declare them unprofessional and unfit for writing software. A litmus test. If you watch the conversations between DHH, Martin Fowler, and Kent Beck, it seems to me that they all agree: testing is good, test-driven design can be bad, and mocking everything is bad [2][3]. I took some time last week to re-read Uncle Bob's book, Agile Software Development, Principles, Patterns, and Practices [4], and Kent Beck's book on TDD [5]. There was a huge difference: Uncle Bob focuses on test-driven design , while Kent Beck focuses on test-driven development . Uncle Bob claims that test-driven development (especially through mocks) universally improves your design, because it reduces coupling and enables refactoring. Kent Beck t