The best insights on software development.
At some point, every growing engineering team gets a scare: the monthly cloud provider bill comes in much higher than anyone expected. In the beginning, the focus is always on
A bug report comes in involving a critical user flow. The frontend team traces the issue to an unexpected API response. The backend team insists their service is working correctly.
You can feel it when part of the system is wrong. The whole team feels it. Builds are slow, tests are unstable, and every new feature in that area becomes
A front-end codebase with a few dozen developers working on it starts to show familiar signs of wear. Pull requests get larger and touch more files than you would expect.
When the engineering team is small, dealing with production incidents usually feels simple. A few people who know the system well jump on a call, figure out what’s wrong, and
Shipping a large change to a production system with a big user base creates a very familiar kind of stress. The business wants to move fast, but engineers know that
FAQ