the log

Field notes from the agentic journey.

Written when something is settled enough to be worth writing down. Nuance over specifics; lessons over reportage. Sanitized of client and IP detail by default.

The certs are a footer, not a pivot

Three AI certifications added to the resume. What they mean — and what they don't.

Name the threat, not the layer

Refuse defense layers until you've named the threat. Half don't survive the sentence.

The single question that catches wrong-shape architecture

When an agent proposes a deploy approach, ask one thing first: what does this look like on a typo fix?

If a role doesn't have a name, it's already a security problem

Unnamed agent identities accumulate ad-hoc bypasses. Name them before they accumulate.

Operator-as-merge-gate is not a placeholder — it's the work

The agent doesn't get to propose-and-execute. Two recent failures would have shipped silently otherwise.

governancereview

Why I made a layered code review

Layers of concern are easier for a model to reason about than a flat 'is this code ok'.

There shouldn't be a storm

On rejecting per-change fanout in favor of scheduled reconciliation.

I stopped writing code, mostly

And I'm a better engineer for it.

operatingcareer

Agentic velocity is not prompting

The skill is workflow design. Prompts are the easy part.

Starting the agentic journey

Why I'm doing this. Day one. Kept here as the origin.