01 / Writing
Long-form notes on engineering decisions, architecture, databases, and the process of building products.
Rails keeps shipping releases and large systems keep running, but the entry point into the profession has narrowed: the market wants middles and seniors, while the places where people become one are far fewer. Why betting on agents does not close that gap.
A production console for Go: a separate process with the same composition root, read-only by default, and a REPL built on Yaegi
In one year, DHH went from fearing that AI would erode his programming skills to giving up coding by hand. Why one engineer's reversal changes which tools others consider acceptable.
A 30-minute reservation expired after only five minutes because the application and PostgreSQL wrote timestamps in different time zones to the same table. How we found it, why staging stayed green, and why the application now verifies the session time zone at startup.
Why a high-priority label loses its meaning when almost every ticket is marked urgent, and how to restore a clear order of work for the team.
Three silent defaults across Gin, GORM, pgx, and Elastic APM: why SQL spans disappeared and why the same context bug also broke request cancellation.
The larger the group, the smaller the average contribution of each person in it.
How to open a transaction at the use-case level, pass it to repositories without coupling business logic to an ORM, and handle nested calls correctly.
Why a shared ErrNotFound conflates distinct failures, where sentinel errors belong, and how to translate GORM or database/sql errors at the repository boundary.
How to enqueue a River job in the same transaction as a business record in PostgreSQL, then run it safely in a separate worker.
A project is a folder, and what the agent receives in it depends on scope, precedence, instruction files, and the directory the session starts in. How to see all four and compare two repositories.
What accumulates in Claude Code, Codex, Cursor, GLM, and OpenCode over a year, and how to audit it: where each file came from, what the scanner finds, what it costs per request, and whether a skill fires at all.
An engineering blog with no CMS and no database: an article is a file in the repository, local and production builds run the same code, and only nginx runs in production.
No writing matches the selected filters.