Software Architecture

Most systems do not die from bad code — they die from architectural decisions that nobody named and nobody defended. This training teaches you to make those decisions deliberately: to recognise the quality attributes that genuinely matter, to set boundaries that survive changing requirements, and to fit patterns to the problem — independent of the technology stack.

Who it is for

Training for people who want to move from “writing code” to deliberately designing systems. It is most useful when a team is evolving a product whose architecture has started to slow delivery, where every change carries a growing risk of regression.

How we run it

A workshop built on design exercises and discussion of real trade-offs, not slides full of definitions. You work on a sample domain that we grow across the whole course — from model and boundaries, through pattern selection, to a decision record (ADR) and a test strategy. You justify every decision and weigh it against the alternatives.

What you take away

• The ability to read architecture through quality attributes and trade-offs, rather than “because that is how it is done”
• Module boundaries set so that a change in one part does not cascade across the whole system
• Domain-Driven Design and ports-and-adapters applied where they genuinely pay off — and dropped where they do not
• An Architecture Decision Record (ADR) practice that stays useful years later
• The ability to refactor architecture incrementally, without a risky ground-up rewrite