I definitely side with the people who said that what you are describing is bad TDD This is the result of people believing « unit test » means I should only tes

I definitely side with the people who said that what you are describing is bad TDD This is the result of people believing « unit test » means I should only test one « unit » (usually a function) When you start testing a behaviour which can span multiple scopes, your tests don’t suffer from the same problems. As for Clean Architecture, the overhead is quite minimal, and being able to hide complex stuff behind an interface means you will actually save a lot of time (like not having any database for several weeks, which helps iterating a lot quicker) I have had the chance to see strong craft practitioner, it convinced me that they are indeed faster than the majority of developers (and ship more often)