Surprise: Software architecture is about trade-offs. Independently testable code is great, the complexity often required to achieve it isn’t
4
30
23
@stilkov don’t understand about excess complexity from making code testable. Examples?
2
@sf105 E.g. having interfaces for every single class, even those that only have a single implementation. More generalized: extra decoupling.
5
@stilkov Testable code does not require an interface for every class. I can equally argue tests help keep code focussed @sf105
1
1
Replying to @SteveSmith_Tech
@AgileSteveSmith @sf105 I agree and I’m not saying it’s necessary. It’s being done all the time, though.

Apr 27, 2014 · 12:51 PM UTC

1
Replying to @stilkov
@stilkov Uninformed decisions are easier than informed decisions, sadly @sf105