Beyond Technology – the 10 Ks in Software Architecture
summary
Discusses what it truly means to be a software architect beyond just following new technologies, buzzwords, or designing technically perfect systems. Uses concrete project experience to show challenges that technology alone doesn’t solve—issues like communication, compromise, cultural aspects, and defining/enforcing principles and best practices in real organizations.
AI-written summary · about
chapters (9)
- 0:00Start
- 5:54Communication
- 10:58Collaboration
- 16:00Coordination
- 18:46Culture
- 23:38Commitment
- 27:37Confidence
- 34:29Creativity
- 42:58Change
related talks
45mTeam and Software: Making an Impact as an Architect
46mTHE too MANY FACES OF ARCHITECTURE
01h 02mHow Do I Become a Successful Software Architect?
49mWhy software architects fail: and what to do about it
41mArchitecture Isn’t Kubernetes
52mEtiquette for Software Architects
43mSoftware Architecture, Design Thinking & Knowledge Flow
45mFive things every developer should know about software architecture