79
Can We Stop With the Uptime Percentages?
(blog.jim-nielsen.com)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
Also: uptime percentage must be computed as the intersection of uptime across services, not the union.
Normal people have no understanding of percentages or numbers, I agree saying 12 hours of downtime is more useful, but I’m also tired of trying to contextualize numbers for the numerically illiterate.
"innumerate", same as illiterate, but for numbers. Not sure if it's a common enough word for people to understand what you're talking about, but still there it is
So if "innumerate" and "innumerable" are both words, there must be an "illiterable," meaning "too many words to be expressed."
I was looking for that word but didn’t arrive at it
https://mrshu.github.io/github-statuses/
Don't forget about: https://www.dayswithoutgithubincident.com/
Important because it shows their high score. The best they've done this year is 6 days without an incident. That's their high score.
They're tied for their high score right now which is cool, but it's shameful that the longest they've gone all year without something going down is 6 days.
According to that, actions is down ~1 working day/month. That's sooooooooooo bad.
I thought big tech wanted us to move away from personal devices into the cloud. This isn't the way to do it.