Case study · 2020–now
A migration linter for Postgres
This case study is sample content. Replace it with verified work before production deployment.
The first version parsed migration files and explained which statements could take strong locks. It deliberately used the same language as the Postgres documentation, with a short operational translation beside it.
Rules included enough context to avoid becoming background noise: estimated table size, server version, transaction boundaries, and whether a safer expansion-and-contraction path existed.
One binary, stable output, and exit codes designed for CI made adoption easy. The project earned trust because teams could see the reasoning and suppress a rule locally with a written explanation.
A durable decision leaves enough context for the next person to understand the tradeoff, not merely the outcome.
