SOLID Code for SOLID Reasons
The post argues that good code should be written for maintainability, with testability as a secondary benefit. It connects SOLID, bounded contexts, and anti-corruption layers to TDD and criticizes using moles or shims to justify weak design.
