Step 2 — Understanding what makes code good at the small scale — before you design systems, you need to see what quality looks like up close.
Clean Code / Code SmellsStep 3 — The empirical laws every engineer should know. From coding and estimation to communication and management — broad but essential context.
The Empirical Laws of Software EngineeringStep 1 — Read this first. It explains how to use this collection and the architectural mindset you need to develop.
Start Here — How to Use This CollectionStep 4 — Your ongoing reference. Every time you hit an unfamiliar term in this collection, come back here. Definitions, context, and the trade-offs behind each concept.
Architecture Glossary — Key Terms Every Architect Should KnowStep 5 — The single most important mental model in architecture. Read this before moving to the Architecture track.
How to Think in Trade-offs