For me it is LARPing, people pretending that code they write is so complicated and so important they need 100% test coverage and nuclear reactor will melt down somewhere if they don’t do their job on the highest level.
I write testable code without TDD and if something breaks we write test to cover that case so it doesn’t happen again.
How do you refactor code, if you have a poor test coverage? Also for me actually the most importan benefit is the instant feedback I get, when I write the unit tests before the implemenation. I can move faster with more confidents.
Probably by working in an environment where that confidence is conveniently provided by static type analysis. If the parts are sufficiently reshaped to fit together again you just know that it will work. And chances are that feedback is an order or two of magnitude more instantaneous.
I write testable code without TDD and if something breaks we write test to cover that case so it doesn’t happen again.