this post was submitted on 10 Sep 2026
79 points (92.5% liked)

Programming

28435 readers
234 users here now

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

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
79
Can We Stop With the Uptime Percentages? (blog.jim-nielsen.com)
submitted 2 days ago by codeinabox@programming.dev to c/programming@programming.dev
24 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] stickyprimer@lemmy.world 9 points 1 day ago* (last edited 1 day ago)

Rather than guess at which percentage representation is more intuitive to people, the blog post suggests something more concrete:

instead of: GitHub Actions: 98.31% uptime.

We say something like: GitHub Actions: 12 hours affected in the last 30 days (98.31% uptime).

I’ve been presenting numbers to people for a long time and I know they flip back and forth between “these percentages are abstract - what’s the actual total number?” and “how do I put these totals in perspective? What percentage is it?” The blog post suggests offering both, which is the right choice.