the growing role of software architects
summary
Claim: software architects must stay hands-on and account for operations not just models, with microservices forcing architecture into integration work and continuous delivery making change cheap. Concrete prescriptions include embedding a full-time DevOps member on the team, using consumer-driven contracts to keep services compatible, favoring breadth over extreme depth in technologies, and resisting solo heroic coding by pairing with developers to delegate while transferring knowledge. Interest in Clojure and reactive styles informs current practice.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:04What is a software architect
- 1:26Is the term architect still bad
- 2:58Is it a relatively new development
- 3:33What do developers need to acquire
- 4:47What do architects need to nurture
- 6:03Delegation
- 6:46Software architecture as a skill
- 7:40Software architecture and DevOps
- 9:23Software architecture and device
- 9:51Software architecture in the past
- 10:40Microservices
- 11:55Meme Wrangler
- 13:10Closure
related talks
46mTHE too MANY FACES OF ARCHITECTURE
38mPractices for Effective Continuous Software Architecture
01h 09mAgile Software Architecture
46mArchitecture & DevOps
02mThe evolution of software architecture
45mDemocratising Software Architecture
51mWhy We Need Architects (and Architecture) on Agile Projects
44mWhen your boss decides to have an architecture team…