How does being a software architect differ from a typical programmer? In this episode, I share the 10 aspects I've approached software architecture from that I learned over 20 years of doing it.
I was promoted to be a software architect at just 20 years old, and while I was qualified with some aspects of software engineering - I didn't really know what I was getting myself into. Being a great software architect takes a variety of skills that a typical software developer will also benefit from, but are actually essential to software architecture.
Yes, using coding patterns, knowing how to interview as a software architect, and making technology selections are required. But there are also other things that if you don't focus on, can hamper your ability to pursue a software architect role either at your current job, or the next one.
I hope this episode helps you understand that while there is some overlap between a software architect and a programmer, the less "fun" aspects of the job are actually essential to being a really great one.
Get free access to TechRolepedia here:
[ Ссылка ]
Download my free Career Guide here:
[ Ссылка ]
Need help with your career? Learn about career coaching:
[ Ссылка ]
CHAPTER MARKERS
0:00 Introduction
0:51 10 Aspects of Being a Software Architect
1:03 1. Zoom In / Zoom Out
2:17 2. Domain Sensitive
3:07 3. Understand Tradeoffs
4:02 4. Selfless Decision Maker
5:02 5. Embrace Change
5:44 6. Communicative Mastery
6:26 7. Infrastructure Aware
7:40 8. Strategic Coder
8:50 9. Consider Scale
10:28 10. Cost Sensitive
11:49 Episode Groove
#softwarearchitecture #programming #softwaredevelopment
