Why everyone 'seems' to 'love' it the same reason functional programming and postgres are darling technologies here on HN. It's more culture than anything else

Why everyone 'seems' to 'love' it the same reason functional programming and postgres are darling technologies here on HN. It's more culture than anything else. People have been testing code for years and years, and people will keep making ways to organize teams, workflows, and every half decade a new Bootcamp, Redmine, Asana and Jira will come out. At the end of the day, you have to have something in place. The bigger your team is the more you need it. TDD is simply one school of thought for how to ship less bugs. Some people do it, most people do not do it strictly. Most of the teams I work with this day and age are no longer very strict on TDD because for their specific products they are shipping it slowed down development enough to notice. But some people love it and some people I think it may make faster. Personally I look at it as a way to solve a problem, likely when assembling a new team. If you don't have issues with speed and quality and coordination then I wouldn't try to add TDD. But if you do it's one of a handful of potential solutions , and depending on your team and product may or may not be a solution.