Architecture is a judgement discipline. It resists the lecture-and-exam format because the hard part is not knowing the patterns — it is knowing when a pattern is wrong for the situation in front of you.
Vocabulary is not competence
A learner can recite hexagonal architecture, CQRS and event sourcing after a weekend. None of that predicts whether they can look at a messy real system and choose the boundary that will still make sense in eighteen months. We separate the two explicitly: naming things is week one; deciding between things is the rest of the course.
Structure of the programme
- Foundations — the notation and the concepts, taught to fluency, not familiarity.
- Constraints — how quality attributes and business goals compress the design space.
- Trade-offs — real engagements, deliberately under-specified, argued in the open.
- Execution — turning a defended design into something that generates and validates.
Learning by defending decisions
Every module ends with a decision the learner has to defend against a reviewer who is allowed to disagree. The point is not to reach the 'correct' answer — there rarely is one — but to make the reasoning explicit enough that it can be challenged. That is the actual skill.
We do not grade the diagram. We grade the argument for the diagram.
Why it ladders into the network
Graduates move naturally into executable architecture because the habits are the same: state intent precisely, expose it to challenge, keep it authoritative. The tooling across the ADAAS network rewards exactly those habits.
Teach judgement first; the tools amplify whatever judgement is already there.