Before you learn how to design systems, it helps to understand what the person designing them actually does. The title software architect means different things in different companies, and it is often confused with senior developer or tech lead. This module clears that up and shows where the role fits in a team and in an organisation.
You'll start with what architects do day to day: making high-level design decisions, weighing trade-offs, and guiding the teams that build the system. Then you'll look at how the role differs from a senior developer, and at the habits that make someone think like an architect, whether or not they hold the title.
This is the first module in the course. Once you've finished it, move on to Requirements & Quality Attributes to learn how an architect turns business needs into measurable goals.
An introduction to the role: a software architect creates the blueprint for a product, and this lesson covers what that job involves beyond writing code.
A look at what architects really do beyond drawing diagrams and picking tech stacks, including making decisions and the impact those decisions have on a project.
Ten key areas where an architect thinks differently from a developer, to help you understand how architects look at a system and how the two roles differ.
A keynote on architectural thinking: understanding business drivers, widening your technical knowledge, and analysing trade-offs, whether or not you hold the title.