Etiquette for Software Architects
summary
Practical advice for software architects and responsible development teams on spotting risks and opportunities early and taking appropriate actions. Presents common good and bad behavioral patterns and concrete, technology-neutral practices to achieve better software architectures and more productive team collaboration.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:07determine quality
- 19:20Example: External Interfaces.
- 39:46Architects speak to stakeholders in their own languages.
- 43:07conceptual integrity
related talks
46mTHE too MANY FACES OF ARCHITECTURE
49mWhy software architects fail: and what to do about it
45mFive things every developer should know about software architecture
45mFive things every developer should know about software architecture
45mTeam and Software: Making an Impact as an Architect
59mHow to Think Like an Architect
46mHow does the architect know?
14mthe growing role of software architects