Older articles.

What carries an expiry date, how to build the list in a day, why end of life minus lead time is the only number that counts, and the sentence that gets the budget.

Read the article

Five sentences to diagnose it, why the cuts follow the nouns, what helps immediately without a rebuild, and why merging back is not a step backwards.

Read the article

See first, then the keys, then the permissions: credential report and last-accessed data, OIDC instead of key pairs, one boundary instead of many rules.

Read the article

Not the dump but the shaped slice: pick an anchor, find the silent references, mask deterministically, and close the outbound paths in the environment.

Read the article

What an agent is good for in legacy code, where it predictably fails, and the precondition without which it multiplies risk rather than speed.

Read the article

Traces first, one path instead of all: the PHP export quirk, the context in Go, the seam across the queue, and what drives the invoice.

Read the article

Three kinds of cache, why an expiry time usually wins, what goes wrong with cached permissions, and how the debt gets paid back.

Read the article

Partial updates instead of a framework switch: the three problems that actually annoy users, twenty lines of JavaScript, and where this route ends.

Read the article

A shape that fits a quarter: six blocks, a result after each, a decision at the end, and the place where every plan tears.

Read the article