A commune in the ivory tower: A new approach to architecture
summary
Claims a decentralised decision model called the architectural advice process where anyone can decide after actively soliciting experts and affected parties, recorded as architectural decision records and reviewed in a weekly advice forum (typically 30–60 minutes). Uses ADRs in source control or Jira, spikes for experiments, and metrics like decision frequency and rollback rate. Examples: nanoid shortened public IDs, TypeScript Lambdas proved cheaper despite warmup; four common failure patterns and practical fixes are documented from real client rollouts.
AI-written summary · about
chapters (8)
- 0:00New architecture approach
- 4:35Traditional architecture problems
- 8:07Architectural advice process
- 12:03ADRs for decisions
- 18:01Storing ADRs effectively
- 23:56Architectural advice forum
- 29:11Top 4 failures
- 35:46Summary
related talks
38mA Commune in the Ivory Tower: A New Approach to Architecture
31mA Commune in the Ivory Tower? – A new approach to architecture decisions
39mA Commune in the Ivory Tower? - A New Approach to Architecture
39mOne Does Not Simply Make Architecture Decisions Alone: ADRs and Architec
59mNew Approach to Architecture
47mMaking architecture decisions, the Agile Way
46mCreating Effective and Objective Architectural Decision Records (ADRs)
16mEveryone architect!