# King Selby

Da vinícola mais antiga do Japão em atividade na região tradicional de Osaka, este rótulo King Selby é conhecido pela leveza nos taninos e na acidez, ótimo para acompanhar a culinária local. Para está safra 2019 que demarca a uva Cabernet Sauvignon como carro-chefe eu considero muito mais que leve. Seu perene tom de frutas vermelhas e a cor rubi na taça entregam um toque de vinho europeu em um mundo exótico. Poderia ser qualquer país periférico como Turquia. Acaba sendo uma boa surpresa para quem não esperava muita coisa dos vinhos japoneses. Bom para beber sozinho, mesmo, mas não se apaga acompanhado até de um pouco de carne vermelha ou arroz japonês (outra combinação excelente).

# Mission of the architect

Mission of the architect: The job of an architect is to teach and keep coherence across the system. Guide decisions, set constraints, and help teams move forward without blocking them.

Organization before technology: One team, one domain, full ownership.

Gall’s Law: Start small, grow intentionally.

Instead of “how long will this take?”, “Can we make this smaller?”.

The real loop of incremental architectures: Build something small. Ship it. Get feedback. Adjust. Repeat.

Use patterns them when you have a problem, not before.

The Strangler Pattern: when you have a big ball of mud. Build a new module inside the existing system. Safe migration strategy without big-bang rewrites.

Component Architecture: A good component has a few strict qualities: Small classes and single responsibility. High cohesion and a focused interface.Hard boundaries, a single entry point. No spaghetti. Replaceable implementation, so clients do not depend on internals (Liskov matters here).

Event-Driven Architecture: Everyone listens, no one knows each other, and events go through a broker, not direct calls.

Domain Driven Design: Ubiquitous language is not a luxury. It reduces confusion and accelerates change.

When you map events and work, try this mental model:

Orange stickers: events, written in the past tense.

Blue stickers: consequences, the actual work to do.

Yellow stickers: who performs the work, your services.

Red stickers: questions, gaps in your knowledge.

Take this list with you:

Can you make the work smaller?

Do teams own domains end-to-end?

Do you apply patterns when they solve real problems, not by default?

Do components have hard boundaries and respect Liskov?

V2

Gall’s Law: Start small, grow intentionally.

Instead of “how long will this take?”, “Can we make this smaller?”.

Build something small. Ship it. Get feedback. Adjust. Repeat.

Use patterns not before you have a problem.

Build a new module inside the big ball of mud and redirect.

Good component: small classes, single responsibility, high cohesion, focused interface, hard boundaries, single entry point, replaceable implementation (Liskov).

Event-Driven Architecture: Everyone listens, no one knows each other. Broker speaks, not direct calls.

Domain Driven Design: Ubiquitous language educes confusion and accelerates change.

Map events and work by colour: events (past tense), consequences (actual work), who performs the work (services), questions and gaps.

# What Actually Makes You Senior

If you can’t reduce ambiguity, all your other skills are just elegant ways of solving the wrong problem.