The mask in the README
2026.139An attention mask drawn in ASCII, and the architectural trade it names.
An attention mask drawn in ASCII, and the architectural trade it names.
What Tesla's 3-6-9 has to say about scaling systems -- and the invariants that hold while the rest moves.
The abstractions rotate every few years. The failure modes don't.
Trading a traditional OCR pipeline for Gemini's vision model -- prompt engineering as product specification, multi-factor confidence scoring, and what changes when you treat document processing as understanding rather than extraction.
How a cascade of exact, prefix, and fuzzy strategies resolves broken OCR output into valid addresses -- with confidence scoring so downstream systems know what to trust.
A regulation arrives. The work looks like encryption at first. It is not.
The three-state machine that keeps a failing dependency from taking down everything else -- with sony/gobreaker, a custom atomic implementation, and retry composition.
Cache-aside, write-through, write-behind -- and the three problems that make caching hard: stampedes, coordinated expiry, and invalidation.
Streaming replication, automated failover, and the operational lessons that aren't in the PostgreSQL docs -- split-brain, silent lag, and why DR drills matter more than DR plans.
The board put us ahead of every customer ticket - until it stayed green while the data underneath it went wrong.
Service discovery, health checks, and dynamic config across a growing fleet of microservices -- and the moment KV store got too popular.
Transaction pooling, one SET that didn't stick, and a standup that moved on.
A GraphQL gateway that started as a unified API layer for clients became the place where we could intervene without touching the backends.
Picking the first piece to cut from a Perl monolith, rewriting it in Go, and switching over before you lose your nerve.
Adding businesses to a social platform built on Neo4j -- and realizing both sides of the marketplace use the same graph patterns.
Replacing an e-commerce frontend without turning off the old one -- carving over layer by layer while the store takes orders.
Building catalog search with flattened MongoDB documents and application-side scoring when the proper tools don't exist yet.