“Where was this book when I started my first architect job?”
Be a complete software architect.
Technology is only a small part of the software architect's job ... what about all the rest?
The Software Architect Field Guide is a book to help you work with people, solve problems, and gain the skills you need to be successful.
Many people think that a software architect is just the next step after lead engineer, a primarily technical position with better pay and more authority.
And while it's true that the pay is good and architects do have more influence, new architects are often surprised to learn that technology is only a small part of their responsibilities. In fact, architects spend more time working with people than anything else.
In The Software Architect Field Guide, you'll learn all these and more:
- Understand the nature of problems
- Draw meaningful diagrams
- Create stories that rally teams around a vision
- Make real progress in meetings
- Navigate team dynamics
By the end of the book, you'll have the knowledge and tools you need to prepare you for a future as an architect, become a better architect, or even work with architects in your organization.
Table of contents
The Software Architect Field Guide is comprised of 250+ pages designed to give you the knowledge and skills you need.
Take a peek at what's inside.
Introduction
The Big Picture
Some quotes from the book ...
Here's some selections to give you an idea of the book's general concepts and approach.
When you made the jump from developer to architect you didn't just become a developer with a lot more power, but rather, you started a journey to become something entirely different.
The Big PicturePeople, problems, and skillsFact is, we’re not always cool, collected, and calm. Sometimes we’re a little shaken or even a lot rattled. Sure, some of us can hide it better than others, but let’s be clear: stressful situations produce stress responses. The more we understand about these situations – and our responses to them – the more we can adjust for better outcomes.
Problem PostureHow to face problems... you won’t always be there to explain your diagram, and people that you might never meet will make decisions based upon nothing more than the diagram itself and what little information they received from the person who delivered it to them.
DrawingOn the importance of diagramsWhen you made the jump from developer to architect you didn't just become a developer with a lot more power, but rather, you started a journey to become something entirely different.
The Big PicturePeople, problems, and skillsThinking of problems as a package containing an issue, affected people, and the resulting threats will help the architect understand why people behave certain ways when faced with problems.
ProblemsUnderstanding context
Fact is, we’re not always cool, collected, and calm. Sometimes we’re a little shaken or even a lot rattled. Sure, some of us can hide it better than others, but let’s be clear: stressful situations produce stress responses. The more we understand about these situations – and our responses to them – the more we can adjust for better outcomes.
Problem PostureHow to face problemsWhatever the provenance, the most effective diagrams aren’t the ones that adhere to a particular diagram convention; the most effective diagrams are the ones that visually communicate with viewers.
DrawingConnecting with viewers
... you won’t always be there to explain your diagram, and people that you might never meet will make decisions based upon nothing more than the diagram itself and what little information they received from the person who delivered it to them.
DrawingOn the importance of diagramsAnd so, would you rather have a one-hour meeting where contributors have a chance to be fully heard, or weeks of meetings where the same topics get discussed over and over because you’ve been talking when you should have been listening?
SolutionsHearing others out
Resources
Diagram resources you can use to get started quickly.
All the diagram elements and styles described in the book, in their original Draw.io format, and ready to use as a model for your own work.
Layout & Colors
Design and organize your visuals to draw attention to key elements.
Text
Strategically arrange text to help the reader interpret the diagram.
Depth & Layering
Add badges and labels to express layers of meaning while preserving space.
Get the free sample chapter
Enter your email address and I'll send you a sample from the book containing one of my favorite chapters. Plus, you'll be notified when the book is available for purchase.
Questions
When will the book be finished?
The first draft of the book is complete and was even released last year for a brief time. Since then, I've focused on refining the content and improving the layout. By the way, if you purchased the book last year, the updated version will be available for free.
How will pricing work?
There will be two options for purchase: the book, and the book plus diagram resources.
What if I have more questions?
Just send an email to [email protected] and you'll get the help you need.
Author
Russ Hawkins – Hey there, I'm the author behind The Software Architect Field Guide.
Over the years, I've worked as an intern, developer, lead, and architect. This book comes from first-hand knowledge gained over a long career working with smart people. I'm indebted to these folks and thankful for the chances to learn, grow, and have some fun building software solutions.