Surprise: Software architecture is about trade-offs. Independently testable code is great, the complexity often required to achieve it isn’t
Apr 27, 2014 · 9:00 AM UTC
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 your tweet is so convoluted I don't even know where to start rebuking it. Although I have a feeling your intentions were good!:)
1
@Cranialstrain @ufried @simonbrown @stilkov the "dev" read about TDD, the "architect" read about XP & where TDD fits in the bigger picture.
@Cranialstrain @ufried @simonbrown @stilkov but they are there, person A wrote good code, person B realises good code was able to be written
@stilkov this is why we should perhaps look to do more component/service testing than unit testing...
1
1
@Cranialstrain @ufried @stilkov yeah, I've also had people suggest that TDD is a substitute for software architecture