Why Reading Architecture Books Doesn't Improve Your Architecture (opens in new tab)
The problem You've read the books. Probably more than one. Clean Architecture, DDD, Designing Data-Intensive Applications. You know what a hexagon is supposed to mean. You can spot a Repository pattern in the wild. And yet here you are, six months into a project you started from scratch, and the architecture is already a mess. The boundaries you drew on day one are gone. The "service layer" became a 3000-line file that everything imports. Tests take forever. Adding a feature touches five modu...
Read the original article