Field notes on engineering, architecture and rolling out enterprise software. Written by the people writing the code.
The temptation to architect for hypothetical scale is the most expensive mistake we see in early-stage products. A short defence of Postgres, monoliths and shipping the simple version first.
A cutover playbook for getting from a 12-year-old custom ERP to Odoo Enterprise — without a single day of downtime.
Six concrete patterns that consistently pull response times down — and three "automation theatre" anti-patterns to avoid.
Sync conflicts, optimistic UIs, and the difference between "works offline" and "actually works offline."
Schema-per-tenant, row-level isolation, or a separate database — the trade-offs you'll be living with for the next five years.
Why the studio model produces better software than the agency model — and what we changed structurally to make it stick.
A practical heuristic for figuring out where tests pay back, where they cost more than they save, and how to tell the difference.