Software Architecture: From Developer to Architect
47mBeginner2021-01-29
Authors

Lee Atchison
Cloud Strategist, Thought Leader, Industry Cloud Expert
Course details
How is a software architect different from a developer? What exactly do architects usually do, and what additional skills would you need to become one? Instructor Lee Atchison answers these questions and more as he introduces you to thinking like an architect. Whereas a developer focuses on details, an architect’s role requires letting go of the details in order to guide the process. A good architect evaluates proposed designs and methodologies and provides feedback to keep the big picture and all outside needs in mind. Lee walks you through a day in the life of the architect, which lets you see the roles that architects may fill for themselves and others. The modern architect needs to keep several principles in mind, and Lee discusses each one. He covers additional skills you need to develop to become a successful software architect, then concludes by walking you through how to discuss with your current manager your goal of becoming an architect.
Skills covered
Software ArchitectureFoundationsSoftware Development
Concepts
0. Introduction
- 01 - Wisdom in software engineering
1. Developer vs. Architect
- 02 - Big picture vs. little picture
- 03 - Teacher rather than dictator
- 04 - Evaluator and feedback
2. Day in the Life of an Architect
- 05 - Learn and experiment - Self
- 06 - Train and coach - Others
- 07 - Review plans and guide decisions - Systems
3. The Modern Architect
- 08 - Agile architecture processes
- 09 - Growing the team and team skills
- 10 - Dev and ops - Both work together
- 11 - Scale and availability - Beyond just making an app
4. Additional Skills Needed
- 12 - People skills
- 13 - Talk to your manager