October 2017
Beginner
360 pages
7h 58m
English
Teams who embrace the idea of software architect as a way of thinking instead of as a role on the team produce better software. When the majority of the team is an architect, the team can explore more design decisions faster. Software quality increases since more eyes can critically evaluate design decisions. Documentation is leaner and conveys more knowledge with less effort.
When everyone on the team can design architecture, everyone feels a greater sense of shared ownership over the design. The software becomes our system, not the system. Change becomes easier to manage since everyone understands the intent behind the design and feels a sense of responsibility for maintaining design integrity. Development velocity ...