Mark Richards Interview
summary
Goals include building an architecture manifesto and leveraging the developer to architect resource alongside books on microservices and messaging. The talk pushes concrete changes: reduce obsession with technology and design, increase emphasis on people skills and leadership, require continuous architect guidance through implementation, and run periodic summits to collect lessons learned and reach consensus on practices. The claim is that collective, repeated collaboration produces practical solutions rather than isolated opinions.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:29What would you like to achieve
- 0:59What is your passion
- 1:32Impact of Global Software Architecture Summit
- 1:54Problems with Software Architecture
- 2:36Conclusion
related talks
02mInterview with Mark Richards
59mHow to Think Like an Architect
45mTeam and Software: Making an Impact as an Architect
08mLightning Talk: Breaking the Mold: Unveiling Anti-Architectural Patterns in...
08mLightning talks – 101 Things Software Never Learnt
49mWhy software architects fail: and what to do about it
37mArchitecting for Tomorrow: A Pragmatic Perspective
25mLeapfrogging from Good to a Great Architect
