architect's Guide to Managing a Code Base
summary
Argues architects must balance coding and orchestration, advocating hands-on checks like cyclomatic complexity and preferring composition over deep inheritance, with concrete review catches such as a stray system.exit that crashed production. Recommends tools: Azul Code Inventory run in production to map unused methods (customers find ~33–40% dead code), feeding results into open rewrite for safe removals, and using Sonar for static metrics. Advises unit test coverage around 70–80% as the practical sweet spot.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:52Software architect vs developer roles
- 6:25Coding involvement for architects
- 11:20Architecture patterns and code quality
- 17:23Code reviews and performance focus
- 21:35Technology and library selection
- 24:01Tools for code quality and complexity
- 30:15Unit testing and coverage strategies
- 36:15Java-specific architecture tools
- 39:48Code inventory and dead code removal
- 40:51Summary and Q&A
related talks
01h 07mArchitect's Guide to Managing a Code Base
20mSupporting your architecture with code coverage and static analysis rules
33mBuilding Code Quality
50mCoevolution of Architecture & Code - Closing The Gap
59mTechniques for writing high-quality code
42mThe art of clean code
43mCode quality as an engine of your IT business
07msoftware architecture vs code