How to Be a Software Architect: Architecture Starts Before Code (EP02)

Most software projects fail not because of bad code, but because of decisions that were never made — or made too late. This video explains why great architecture starts before the first line of code is ever written.

You’ll learn how architects think, what questions they ask early, and how tools like ADRs, tradeoff matrices, and system boundaries help avoid costly mistakes later.

Perfect for developers transitioning to architecture roles, or architects mentoring future technical leaders.

📌 What you’ll learn in this video

🧱 What really separates architecture from code
🧭 How to make strategic decisions using ADRs
🧠 The mindset shift from coder to architect
❓ Key questions to ask before implementation
📐 How to define system boundaries and map interactions
🤝 Who the key stakeholders are and when to involve them
🛠️ Tools like C4 diagrams, EventStorming, and Wardley Maps
⚖️ How to use tradeoff matrices to guide design
🔐 A real-world ADR example for OAuth2 authentication
🚨 Common anti-patterns when starting with code too early

⏱️ Timestamps

00:00 – Introduction & Overview
05:09 – The Invisible Beginning
07:21 – Architecture vs. Code
10:18 – Timeline of a Feature
12:00 – From Coder to Architect: Mindset Shifts
16:30 – Core Questions to Ask Before Coding
21:17 – Stakeholders to Involve Early
22:57 – Defining System Boundaries Visually
25:19 – What is an ADR (Architecture Decision Record) – OAuth2 Example
34:36 – Tools That Support Early Architecture
39:27 – Architecting a System
43:50 – Constraints That Shape Architecture
45:47 – Understanding Tradeoffs and Using a Matrix
47:29 – Example Tradeoff Matrix: Microservices vs others
49:49 – Modular Thinking from Day One
51:26 – Anti-Patterns of Starting With Code
52:14 – Summary