Clean architecture that harms your code
summary
A Ruby developer examines how applying popular practices—TDD, SOLID, DDD, and The Clean Architecture—can lead to over-engineering and practical problems in a team project. Using his own year-and-a-half-long attempt to build an application, he discusses concrete pros and cons, common pitfalls of strict adherence to these practices, and the conclusions he drew.
AI-written summary · about
chapters (8)
- 0:00Introductie en persoonlijke ervaring
- 3:37Clean architecture principes
- 10:28Problemen met strikte lagen
- 20:13Praktijkvoorbeelden en valkuilen
- 27:49Alternatieven en flexibiliteit
- 35:25Teamdynamiek en implementatie
- 41:58Balans tussen puurheid en realiteit
- 48:08Conclusie en Q&A
related talks
56mClean Architecture: Deep Dive
43mAgile clean architecture
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
51mClean Architecture: A Deep Dive
47mStep by Step Toward Clean Architecture
51mClean Architecture: Why? How? For Whom?
19mClean Architecture: A Solution to Improve System Maintainability
41mThe challenge of building maintainable, robust applications