There's a big "if" of course, don't just throw your tests out of the window. But indeed, they need to bring value... so start by having really good tests.

A good debunk of that claim we sometime see. Of course the tests need to be designed and you need to have good architecture blueprints to follow, otherwise you'll be in trouble... TDD or not.

That's an interesting trick to make sure people reevaluate comments when they remove some code. Doesn't work for every language of course.

OK, the concept if really mind bending. The tech behind it is really interesting.

This is an old one but still a funny way to approach the question of test coverage. Unsurprisingly, the context matters.

Indeed, is it that the language itself has a steep learning curve? Or that the emphasis is on the wrong things in the public discourse? I like the emphasis on the Aliasing Xor Mutability, it looks like a good way to approach the language.