Qualities of a Highly Effective Architect Keynote
summary
Lists twelve concrete habits: mentor others, prefer prototype beats argument (one-hour prototype example changes decisions), evaluate trade-offs with the debate with knives technique, reduce the truck factor so one person’s death doesn’t kill the project, avoid “PowerPoint architects” who stop coding, practice collective ownership (readable code must be cross-reviewed), gain domain expertise, actively unlearn old practices, diversify languages (learn the one that makes you cry), and evolve architecture with stated confidence levels.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:48Architect
- 2:09Who needs an architect
- 3:12Be a mentor
- 6:23Evaluate tradeoffs
- 8:38Debate with knives
- 10:42Guide dont dictate
- 13:22Practice collective ownership
- 14:50The truck factor
- 16:49Let developers figure it out
- 19:25Its safe to be honest
- 24:07Give people an opportunity
- 27:06Gain domain expertise
- 30:04Collaborate
- 31:55Diversify
- 38:57Danger
- 40:11Architecture Committee
- 42:21Architect practices
- 42:34Write code
- 42:59PowerPoint Architects
- 43:23Technical Decisions
- 44:00Deliver the Architecture
- 44:51Confidence
- 45:39Summary
related talks
54mQualities of a Highly Effective Architect
42mQualities of a Highly Effective Architect
59mHow to Think Like an Architect
02mHigh-performance teams
45mTeam and Software: Making an Impact as an Architect
25mLeapfrogging from Good to a Great Architect
59mBecoming an Architect: Nurturing Essential Skills for Success
49mWhy software architects fail: and what to do about it