Earlier quoted context omitted.
I don't consider them to have any tradeoff. So far I am not losing any time applying TDD. And Clean Architecture seems common sense.
TDD tends to result in an encrustation of overly-specific unit tests that can make it harder to rethink a design as you go. It's a valuable technique, but can be counterproductive if over-applied unthinkingly. I've worked in more than one dev team that has imposed TTD-all-the-things policies they've had to retract. Clean architecture as a goal is, of course, uncomplicated. It being a good thing is assumed in the term…
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)