Architecture: The Stuff That's Hard to Change
summary
Argues architecture is the stuff expensive or risky to change, cites Fred Brooks’ 8‑bit byte decision still holding 56 years later and Margaret Hamilton’s Apollo work, shows tooling like Visio diagrams and web sequence diagrams, inspects live systems (Redis clusters, RabbitMQ, Mandrill MailChimp SMTP relay) and finds nine separate email systems to consolidate, recommends building dashboards, fake JSON stubs and spec tests to validate designs, describes a CRM integration that removes weekly spreadsheet mailing work and actually succeeds.
AI-written summary · about
chapters (11)
- 0:00Start
- 10:51MARY SHAW DAVID GARLAN
- 17:27Communicate Decisions
- 17:54What Have You Got? Understand your existing Technology
- 22:09What Do You Need? Asking the Right Questions
- 23:32What Can You Build? Understand your Capabilities
- 25:56What Can You Buy? Look for platform-as-a-service and software-as-a-service solutions
- 26:53What Can You Lose? Look for Redundancies and Duplication
- 27:54DECIDE WHAT TO DO (The easy part)
- 28:29COMMUNICATING DECISIONS
- 36:07REINFORCING DECISIONS
related talks
45mArchitecture: The Stuff That's Hard to Change
33mSet Design: Putting the "Art" in "Architecture"
01h 02mThinking Like an Architect
40mThe (too) many faces of architecture
45mSoftware Architecture for Humans!
24mThe too many faces of Architecture
57mDomain Architecture Isomorphism and the Inverse Conway Maneuver
41mArchitecture Isn’t Kubernetes