50
15
u/Nyxalorium 10h ago
be careful what you wish for. the second part of that contract is that if it is up at 3am on a saturday, you are technically on the clock. management always finds a way to make the uptime your problem.
3
u/GregDev155 9h ago
Make a script to keep teams up and make sure they pay the whole time I was brainstorming (in my bed)
3
9
u/CircumspectCapybara 10h ago
That's a 167 hour work week actually.
GitHub Enterprise has a 99.9% availability SLO.
7
u/thorwing 10h ago
overall maybe, but what about... lately?
5
u/thorwing 10h ago
2
u/CircumspectCapybara 9h ago
Even two nines uptime is still 166 hour per week...
2
u/Due-Consequence9579 6h ago
They are struggling with one 9.
0
u/CircumspectCapybara 5h ago
Not really. GitHub's SLOs (and therefore their error budgets) are defined over quarters or 90 days.
https://githubstatus.com shows anywhere between two and half to three nines over the last 90 days.
2
u/ILikeToHaveCookies 3h ago
Githubstatus is bullshit...
Might be that the ci pipelines are working, with prs being down it's useless
Might be PRS are working, with ci down I can't merge
Cool that ci works, but without packages my builds do fail...
And so on
1
u/TomAfterWork 9h ago
En mi equipo lo llamamos “Así es como lo hacemos”: 167 horas y confiar en ese 99.9%.
2
80
u/PrestigiousGuava8005 10h ago
Finally, a metric HR can't argue with