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