Congratulations, You're an Architect
summary
Argues that architecture is mostly attitudes and behaviors not patterns, and gives concrete practices: paraphrase to check assumptions and treat conversations as negotiation tied to business outcomes like ROI, time-to-market and cost of ownership. Recommends building credibility with small, trackable wins, record minutes and actions after meetings, use task reminders (Outlook/Trello) to start work earlier, and sit with the dev team and code to validate patterns. Encourages asking “stupid” questions to expose assumptions and stay accountable.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:31Dont get fixated on the job title
- 0:57The role of an architect
- 1:27Attitudes and behaviors
- 2:14Communication
- 4:12Transparency
- 5:02Creator
- 5:56Leadership
- 7:11Accountability
- 9:25Ask dumb questions
related talks
45mArchitecture: The Stuff That's Hard to Change
01h 02mThinking Like an Architect
25mLeapfrogging from Good to a Great Architect
49mCultivating Architecture
59mBecoming an Architect: Nurturing Essential Skills for Success
42mQualities of a Highly Effective Architect
45mTeam and Software: Making an Impact as an Architect
01h 02mWhy We Need Architects (and Architecture) on Agile Projects