TDD (I lump together lots of extended practices here) is hard. It's hard to learn from a book or blog post. It's often hard to solve the many problems of "how

TDD (I lump together lots of extended practices here) is hard. It's hard to learn from a book or blog post. It's often hard to solve the many problems of "how do we test <behaviour X>?". It's hard to know when to stop spiking and start test-driving. It's hard to stick to it when you solo and you think "oh I can just skip a few steps here and come back afterwards". It's hard to learn mockist style and statist style. Hard to go all-in on one style, then all-in on the other style, and then afterwards often hard to strike the right balance between them. It's hard to deal with the vast universe of technologies which, having not been developed in a TDD fashion, are hard to test. It's also hard being told your years of practicing amongst practitioners aren't real experiences. That you didn't see the remarkable speed and confidence it granted on massive codebases with hundreds of engineers in dozens of teams working for multiple companies on several continents for years on end.