The mask in the README
2026.139An attention mask drawn in ASCII, and the architectural trade it names.
architecture
all tags →An attention mask drawn in ASCII, and the architectural trade it names.
If Earth were an operating system, physics would be the kernel.
Connection pool sizes, retry counts, timeouts, commented-out endpoints -- and the archaeology of values that survived production.
Three checks and the developer assumes the fourth is covered. That gap is where the damage hides.
Your code already leaves the machine. The agent just gave it another surface.
What Tesla's 3-6-9 has to say about scaling systems -- and the invariants that hold while the rest moves.
Retries fix distributed systems. Repeating yourself fixes attention asymmetry.
The abstractions rotate every few years. The failure modes don't.
A regulation arrives. The work looks like encryption at first. It is not.
The legacy codebase runs the business. The migration is on every roadmap. Not this one.
The new user service got Go because it fit. A thing built compatible with the old never needs a migration mandate.
What it takes to build a remote engineering center -- and what stays the same when you do it again at a tenth of the scale.
The board put us ahead of every customer ticket - until it stayed green while the data underneath it went wrong.
Autoscale never helped in the time of crisis. What helped was prescaling -- capacity ready before the traffic arrives.
Service discovery, health checks, and dynamic config across a growing fleet of microservices -- and the moment KV store got too popular.
A GraphQL gateway that started as a unified API layer for clients became the place where we could intervene without touching the backends.
I've built a rules engine twice, in two languages, at two scales. The tree is the same.
What a digital wallet looks like underneath -- a balance, a ledger, idempotency keys, and the gap between moving money and moving money correctly.
Picking the first piece to cut from a Perl monolith, rewriting it in Go, and switching over before you lose your nerve.
What a codebase looks like when two people build everything -- 350 commits, and a todo list with two items.