Software Architecture with BowTiedCelt

Software Architecture with BowTiedCelt

Share this post

Software Architecture with BowTiedCelt
Software Architecture with BowTiedCelt
The Power of Breadth: Why Software Architects Need a Wide-Ranging Technical Knowledge Base
Copy link
Facebook
Email
Notes
More

The Power of Breadth: Why Software Architects Need a Wide-Ranging Technical Knowledge Base

2: Think like an architect

BowTiedCelt's avatar
BowTiedCelt
Jun 03, 2023
∙ Paid
3

Share this post

Software Architecture with BowTiedCelt
Software Architecture with BowTiedCelt
The Power of Breadth: Why Software Architects Need a Wide-Ranging Technical Knowledge Base
Copy link
Facebook
Email
Notes
More
1
Share

Jack of all trades or master of one. This is the common tradeoff you hear for software engineering. For software architecture the answer leans more towards jack of all trades.

This post will be the second in a series about the Software Architect’s toolbox, or how to be a software architect. Being a software architect is different than being a developer on a software engineering team. It requires different thinking and skills to be effective. Although, the skillsets are adjacent, there still different.

Make sure you give my last post on Software Architecture a read:

What is Software Architecture?

BowTiedCelt
·
April 13, 2023
What is Software Architecture?

Generally, as you become more senior in software engineering you begin to write less code and focus more on design, high level implementation, and the technical direction of your org. Generally, this is true. However some people do remain high output coders into their staff career. This can all be very individualized. Most people though tend to focus on the abstract and lucrative field Software Architecture, your’s truly included in the lucrative part.

Read full story

Table of Contents:

  1. Introduction

  2. Breadth of Knowledge: What It Means and Why It's Important

  3. Depth of Knowledge: Its Role and Limitations

  4. Striking a Balance: The Importance of Both Breadth and Depth

  5. Recommendations for Software Architects

  6. Conclusion

The Power of Breadth: Why Software Architects Need a Wide-Ranging Technical Knowledge Base

Introduction

In the world of technology, the term 'software architecture' can carry different meanings for different people. My perspective aligns with the common understanding: software architects are professionals concerned with system-level design, focusing on the structure and blueprint of software. They often find themselves less involved in the implementation phase, and more invested in the overarching design.

Much like traversing a tree data structure, there are two types of knowledge in this domain: breadth and depth. Breadth represents a wide-ranging knowledge base, encompassing numerous areas. It's typically high-level knowledge, as it casts a wide net over a diverse set of subjects. On the other hand, depth signifies a profound understanding of a specific area or tool, akin to casting a smaller but much denser net. Individuals with depth knowledge typically have a deep familiarity with a few tools or areas, right down to the nuts and bolts. Meanwhile, those with breadth knowledge possess a high-level understanding of a multitude of tools or areas.

Keep reading with a 7-day free trial

Subscribe to Software Architecture with BowTiedCelt to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 BowTiedCelt
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share

Copy link
Facebook
Email
Notes
More