I like TDD. It’s just a tool on our tech belt. If done right (takes practice and open mind tbh) the major benefit is you have code that is single responsibility

I like TDD. It’s just a tool on our tech belt. If done right (takes practice and open mind tbh) the major benefit is you have code that is single responsibility and easy to understand, isolate, or modify. We have so many things on our tech belt, like clean architecture or x pattern. This is just another tool, and I think it helps especially in building complex software. Just be practical and don’t try to be “the 100%er” who is super rigid about things. Go into everything with a 80/20 mindset. If this is something mission critical and needs to be as dependable as possible, then use the tools best suited for it. If you’re literally putting buttons on the screen which Product is going to scrap in two weeks, maybe use TDD for the code responsible for dynamically switching code based on Product mindset that week.