How does the work of a software architect differ from that of a regular programmer? In this episode, I'll tell you the 10 aspects that I've learned in 20 years of professional experience in software architecture.

I was promoted to software architect when I was just 20 years old, and although I was skilled in some areas of software development, I didn't really know what I was getting myself into. Being a good software architect requires a set of skills that benefit a typical software developer, but are actually essential to software architecture.

Yes, you need to use coding patterns, know how to interview as a software architect, and choose technologies. But there are other things that can hurt your chances of getting a job as a software architect in your current job or your next one if you don't focus on them.

I hope this episode helps you understand that while there is some overlap between the responsibilities of a software architect and a programmer, the less “fun” aspects of the job are actually crucial to being a really good architect.

Get free access to TechRolepedia here:
https://jaymeedwards.com/access-techrolepedia/

Download my free career guide here:
https://jaymeedwards.com/developer-career-guide/

Do you need help with your career? Learn more about career coaching:
https://jaymeedwards.com/services/software-development-coaching/

CHAPTER MARKERS

0:00 Introduction

0:51 10 aspects of working as a software architect
1:03 1. Zoom in / out
2:17 2. Domain sensitive
3:07 3. Understanding compromises
4:02 4. Selfless Decision Maker
5:02 5. Embrace change
5:44 6. Communicative Mastery
6:26 7. Infrastructure conscious
7:40 8. Strategic Coder
8:50 9. Consider scale
10:28 10. Cost sensitive

11:49 Follow Groove

#softwarearchitecture #programming #softwaredevelopment

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.