A gentle, thorough guide to one of the most useful ideas in software design: the box-of-clip-together-blocks vs. pre-molded-figure analogy, what inheritance really gives you (code reuse, polymorphism, specialization), what composition really is (holding and delegating), the two flavors composition/aggregation, the is-a vs has-a sentence test with the classic Penguin/FlyingBird and…
A software architect draws the map. But a map drawn by someone who never walks the streets tends to be wrong in ways nobody notices until it is too late. This thirteen-chapter guide unpacks what “staying hands-on” really means, what happens when architects stop coding entirely (the ivory-tower drift), the…
Not every team has to invent the wheel from scratch. Somewhere, someone has already solved a very similar problem — and written down how they did it. That written-down wisdom is called a reference architecture. This guide unpacks what it really is, how it differs from a solution architecture, what’s…
Drawing a good architecture is one thing. Making sure that dozens of teams, over many years, actually stick to it — that’s a completely different challenge. This guide unpacks architectural governance — what it really is, how it differs from architecture design, its four pillars (principles, standards, review and approval,…
The code can tell you what a system does. It almost never tells you why it was built that way, or what would break if you changed it. That missing “why” is exactly what architecture documentation is for. This guide unpacks what it really is, why it exists, why code…
A short note, written the moment a big decision is made, explaining what was decided and why. That’s the whole idea behind an Architecture Decision Record. This guide unpacks the classic five-part template (title, status, context, decision, consequences), the ADR lifecycle (proposed → accepted → superseded → deprecated), a worked…
Long before a single line of code gets written, architects need a way to draw their ideas so other people can actually understand them. UML is the shared drawing language that lets an idea in one person’s head become a picture everyone else can read. This guide covers what UML…
Some questions aren’t about what a system is made of — they’re about what happens, in what order, when someone actually presses “buy now.” This guide unpacks sequence diagrams — the three core building blocks (lifelines, activation bars, messages), the different arrow styles and what they mean, combined fragments for…
Some systems are too big to draw one class at a time. A component diagram steps back, groups related code into sensible chunks, and shows how those chunks plug into each other. This guide unpacks the notation (lollipops, sockets, connectors, dependencies), how to read and draw one, how it compares…
Most people picture an architect drawing diagrams once, at the very start, and disappearing. In reality, a good architect’s fingerprints are on almost every stage of a project — from the first client conversation to years after launch. This guide walks phase by phase through the SDLC, showing what an…