Field notes from an engineering team shipping mission-critical software.
Shared schema, schema-per-tenant, or database-per-tenant? A practical decision framework from ten enterprise builds, plus the row-level security patterns that hold up under load.
Fifteen years of enrollment data, four departments that each believed their process was the standard, and a hard cutover date tied to the academic calendar. Here is how the migration actually ran.
Event sourcing is oversold as an architecture and undersold as a bookkeeping technique. In ERP systems, where every number must be explainable, the ledger model earns its complexity.
A month-by-month account of taking an engineering organization from zero formal controls to a clean Type II report, including what we would cut if we did it again.
Two-week sprints optimize for motion. Twelve-week cycles optimize for finished work. Here is the cadence we use on enterprise builds and why clients stopped asking for status reports.
Most plant-floor dashboards are designed for the person who commissioned them, not the person standing in front of them wearing gloves. Six rules from screens that survived the shop floor.
Roles on the user table, permission checks in the UI, and an is_admin boolean are the three mistakes we find in almost every system we inherit. Here is the model that scales instead.
The spreadsheet a business runs on is the most accurate specification you will ever be handed. Read it properly before you replace it.
Eighty-two locations, three point-of-sale systems, and no single view of inventory. The rollout plan that got every store onto one platform in a quarter without closing a till.