Moved, not settled
2026.216Go spent eight months on dependency cooldown, then closed it by moving it to the proxy. Nobody had to decide whether it works.
Go
tag:
go
all tags →2026
The mechanism is real and it isn't sufficient
2026.175Explanatory power is not predictive power. The Go scheduler knows this. Your postmortems don't.
2025
autobreaker: adaptive circuit breaking
2025.319Why static failure counts break at both ends of the traffic spectrum, and a lock-free Go circuit breaker that uses percentage-based thresholds to adapt automatically.
Replacing OCR with Gemini
2025.191Prompt engineering as product specification, confidence as contract -- what changes when document processing becomes understanding, not extraction.
Fixing OCR addresses
2025.186How 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.
2024
Circuit breaking in Go
2024.272The three-state machine that keeps a failing dependency from taking down everything else -- with sony/gobreaker, a custom atomic implementation, and retry composition.
Scout, plan, wait
2024.233The legacy codebase runs the business. The migration is on every roadmap. Not this one.
Redis caching patterns
2024.172Cache-aside, write-through, write-behind -- and the three problems that make caching hard: stampedes, coordinated expiry, and invalidation.
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.
2019
The loyalty engine
2019.201Points are integers. The hard part is time, and users who think faster than your rules.
2018
The compiler as first reviewer
2018.199How a growing team adopted Go -- not through boot camps, but through code review, shadowing, and a compiler that wouldn't let anyone be sloppy.
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 promocode engine
2017.201A rules engine that answers yes or no during checkout, with condition trees built by people who don't code.
Training a team on a language nobody knows
2017.105Pair-writing a real service, asking questions instead of correcting syntax, and waiting for the style guide until after the team has scars.
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.
2016
Switching to Go
2016.342Migrating a payment processing API from Node.js to Go -- what changed, what improved, and what we gave up.