From Startup to Scale Up: How to Scale Engineering teams
summary
Company runs with thousands of customers and hundreds of developers and enforces concrete practices: two mandatory reviewers per PR plus subject‑matter panels, schema changes run through PT‑online utility to avoid downtime, and a performance lab with production‑like load that catches regressions (example: a Ruby 2→3 upgrade that spiked object allocations and GC cycles). Release cadence uses sandbox deployments, minor releases every two weeks and major every three months, and multiple deployment branches to limit blast radius.
AI-written summary · about
