News for hackers. Stuff that matters.
Re:What I Wish I Had Known Before Scaling Uber [video] by cortesoft on Wednesday September 28, 2016 @10:56AM (#12598120)
The breakage rate per new feature is fairly constant; if you release 7 new features once a week or 1 new feature once a day, you will have the same number of issues. The question then is; is it easier to deal with all the issues at once, or a smaller number of issues every day?
Re:What I Wish I Had Known Before Scaling Uber [video] by danek on Wednesday September 28, 2016 @11:48AM (#12598618)
In addition to that, I would also worry about interactions between issues. I tend to lean towards spreading out the issues over time to make the eventual diagnosis easier.

Occasionally we'll have a problem where we cannot deploy to production for several days (normally it's once a day). A massive inventory of ready-to-deploy features builds up. When we do finally deploy, this deluge of features and fixes creates new issues that force a rollback, delaying the deploy even longer...

Re:What I Wish I Had Known Before Scaling Uber [video] by cortesoft on Wednesday September 28, 2016 @04:21PM (#12601008)
Absolutely. Confounding issues are the biggest problem, even more so than sheer volume in a small time frame.
Re:What I Wish I Had Known Before Scaling Uber [video] by pc86 on Wednesday September 28, 2016 @01:35PM (#12599602)
Sounds like a testing/UAT issue.