Technical Breadth for Architects

Key Insight

Software architects require significant technical breadth, unlike developers who need deep technical depth. This distinction is crucial for architects to perceive solutions and possibilities that others might overlook. The concept is illustrated by the 'knowledge pyramid,' which categorizes all knowledge into 'stuff you know,' 'stuff you know you don’t know,' and 'stuff you don’t know you don’t know.' Developers primarily focus on expanding the 'stuff you know' segment, like knowing Java as a Java programmer, to build and maintain expertise, which defines their technical depth. This expansion incidentally grows the 'stuff you know you don’t know' category, such as having heard of Clojure.

As individuals transition from developers to architects, the focus of valuable knowledge shifts profoundly from depth to breadth. Architects gain substantial value from a broad understanding of various technologies and their application to solve specific problems; for example, knowing five potential solutions for a given problem is more beneficial than possessing singular expertise in just one. An architect's technical breadth is conceptualized by how deeply the 'stuff you know you don’t know' section penetrates into the 'stuff you don’t know you don’t know' category of the knowledge pyramid. Consequently, architects must strategically sacrifice some of their hard-won technical expertise in specific areas to dedicate time to broadening their overall portfolio of technological understanding, even if certain areas of deep knowledge may naturally atrophy.

This fundamental difference in knowledge acquisition and focus often presents significant challenges during the career transition from a developer to an architect, frequently leading to two common dysfunctions. Firstly, an architect might unsuccessfully attempt to maintain deep expertise across a wide array of areas, resulting in burnout and limited success in any particular domain. Secondly, it can manifest as 'stale expertise,' where outdated information is mistakenly considered current or cutting-edge, a common issue observed in large companies where long-serving leaders make technology decisions based on obsolete criteria. Architects must, therefore, consciously adapt their approach to knowledge acquisition, prioritizing technical breadth to ensure they possess a comprehensive 'quiver' of diverse solutions for informed decision-making.