The document discusses the concept of accidental versus deliberate architecture in software design, emphasizing the need for intentional decision-making to avoid legacy issues. It highlights Bob Martin's clean architecture principles, aiming to reduce human resources in system maintenance while achieving efficiency. The text also features insights from James Thompson regarding the importance of thoughtful architectural planning.

1. Beyond
Accidental Architecture

2. Accidental Architecture

4. Accidental Architecture

5. Value Judgements

6. Warning Signs
Changes becoming
Slower,
Further Reaching,
and Less Confident
God Objects
Labelling as “Legacy”

7. Deliberate Architecture

8. Avoiding a Facade
Intentional Effort from
Individuals
Teams
Organization

9. Bob Martin’s Clean Architecture
The goal of software architecture is to
minimize the human resources required to
build and maintain the required system.
The only way to go fast, is to go well.

10. Deliberate Architecture

14. Deliberate Architecture

15. Questions

16. James Thompson
Staff Software Engineer @ Nav
@plainprogrammer
theplainprogrammer.com