Knowledge base

How to record and communicate technical decisions so they survive the future: Architecture Decision Records, RFCs, the C4 model, and sequence diagrams.

The meta-skills that do more work than any single pattern: reversible vs irreversible decisions, Conway's Law, and matching complexity to the actual problem.

SOLID principles applied with restraint, design patterns without cargo-culting, the timing of abstraction, and designing the contracts where teams integrate.

Scalability, reliability, security, observability, and performance — the qualities that separate a design that demos well from one that survives production.

A short intro post — confirms the blog pipeline is live and explains how to write the next one.

Where systems get genuinely hard: data ownership, consistency models, the CAP theorem, choosing the right kind of database, and the shared-database trap.

The single fundamental beneath every architecture decision — what changes together, and how to keep it together — plus the domain-driven design vocabulary for drawing boundaries well.

Monoliths, modular monoliths, microservices, event-driven systems, and serverless — what each buys you, what each costs, and how to choose.

What changes about how you think technically when you go from writing code to leading the people who write it.