3 ms·
thats not the kind of progression you like to see - that is, error rates increasing over time instead of decreasing.
by ejb999 5y ago
thats not the kind of progression you like to see - that is, error rates increasing over time instead of decreasing.
- TheRealPomax 5y agoOnly if you believe those numbers mean anything. What are the errors for? Github has been adding lots of features and subproducts over the years, becoming a bigger and bigger platform as a result. What you want is the error-per-component, which may very well have actually gone down, with error spikes coming from "when github adds a completely new feature and it goes through a slew of incidents in its first year". The bigger the feature, the more incidents. Without more detailed numbers, there's literally no conclusion to draw here.
- ejb999 5y agoEvery place I have ever worked reported incidents going down would be good, not up.
- TheRealPomax 5y agoEvery place I ever worked at understood that if you x3 the codebase/infra/interaction surface/etc, you can expect x3 errors. If the total number of errors don't go up as you grow you're doing amazing, and if they go down even though you're landing more and more code for more and more features and subproducts, you have a genuine miracle.
- AlexandrB 5y agoThese features can't be rolled out incrementally to users? In this day and age it seems weird for a web app to do a global go-live with something before testing it with a smaller group first.
- TheRealPomax 5y agoA "smaller group" on github's scale is still large enough to take down an entire sub product like actions, hooks, codegroups, etc.
- quercetumMons 5y agoReasonable if growth/load is growing, too.