Surprise: Software architecture is about trade-offs. Independently testable code is great, the complexity often required to achieve it isn’t

@stilkov don’t understand about excess complexity from making code testable. Examples?

@sf105 E.g. having interfaces for every single class, even those that only have a single implementation. More generalized: extra decoupling.

@stilkov agreed. Naive interface per class bad, but rather a sign of weak design skills. Testability isn't the problem. Also ...

@sf105 true. But in any case, testability, while being a desirable property, is just one of them, and comes at a cost. As does everything.

@stilkov not keen to engage latest backlash (says I on twitter). Too many strawman arguments flying about.