software architecture vs code
summary
Argues that architecture must be visible in code and offers concrete practices to achieve it: use an architecturally evident coding style, enforce naming and packaging conventions and annotations so code reflects architectural intent, put at least one architect on the team who still writes code, and teach developers to step back and see the big picture. Claims these steps make systems easier to understand and maintain and cites microservices, Docker and Pivotal as relevant examples.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:44Architectural Evident Coding Style
- 2:25Benefits
- 3:17Architects and Developers Can Do To Maintain a Close Connection between the Architecture and that Code
- 4:05Mindsets
- 5:33Advocating for Software Architecture as a Skill
related talks
46mSoftware Architecture vs Code
42mSoftware Architecture vs Code
50mCoevolution of Architecture & Code - Closing The Gap
45mSoftware Architecture for Humans!
51mSoftware Architecture for Humans!
46mTHE too MANY FACES OF ARCHITECTURE
45mFive things every developer should know about software architecture
45mFive things every developer should know about software architecture
