Architecture Isn’t Kubernetes
summary
Argues that architecture is designing relationships and mental models not just Kubernetes, listing five concrete practices — expand your thinking toolset, practice metacognition, be excellent at systemic reasoning — plus a bonus: be very good at building tech. Gives examples: cloud native and Kubernetes debates, microservices that stayed tightly coupled, mistaken appeals to past failures, and a team choosing Flutter/Dart. Shows how shifting paradigms (CRUD → events), tracing organizational beliefs, and fixing reasoning bugs change outcomes more than swapping tools.
AI-written summary · about
chapters (10)
- 0:00Intro
- 5:065 practices of a modern architect
- 6:35No. 1: Expand your thinking toolset
- 11:43No. 2: Practice metacognition
- 17:17No. 3: Be excellent at systemic reasoning
- 26:06No. 4: Focus on relationships
- 29:52No. 5: Shift the paradigm …when necessary
- 38:26Bonus: Be really good at building tech
- 39:30Summary
- 40:41Outro
related talks
58mArchitecture isn't Kubernetes
49mArchitecture is Designing Knowledge Flow
40mThe (too) many faces of architecture
01h 02mThinking Like an Architect
41mArchitecture and Agility: A Shared Skillset!
45mArchitecture: The Stuff That's Hard to Change
33mSet Design: Putting the "Art" in "Architecture"
44mWhen your boss decides to have an architecture team…