Skip to main content

Software Architecture Mastery

A learning path for Software Engineers who want to think like Software Architects.

The goal is not to teach patterns, frameworks, or cloud services. It is to develop architectural reasoning: understand the problem, identify constraints, evaluate alternatives, reason about trade-offs, decide, communicate, and evolve.

Under construction

This site is in Phase F0 — technical foundation. The structure, the bilingual build, and the validators are in place; the content of the seven levels has not been written yet.

The full plan lives in the project specification.

The seven levels​

LEVEL 01 — Foundation
        ↓
LEVEL 02 — Software Design
        ↓
LEVEL 03 — System Design
        ↓
LEVEL 04 — Distributed Systems
        ↓
LEVEL 05 — Architecture
        ↓
LEVEL 06 — Enterprise Architecture
        ↓
LEVEL 07 — Architecture Leadership

The corresponding progression of capability:

code → design → systems → distributed systems → architecture → enterprise → strategy

Acceptance test​

The material is doing its job when, handed "Design the architecture for a high-volume payment platform", you do not start drawing boxes — you start asking what the business problem is, which quality attributes matter, and what constraints exist.