this post was submitted on 12 Jun 2023
15 points (100.0% liked)
Technology
37712 readers
312 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
High-scale software is complex, sometimes there are edge cases where weird unexpected stuff happens. This isn’t a situation they would normally run into.
It absolutely is something they would normally run into. I work on maintaining a massive application; think 60+ teams of 6, each extremely specialized and minimal overlap. Almost 75% of my job is predicting issues and avoiding them. Peer testing draws on this a ton as well. They just continue to plainly show that they don't care. Time and time again, year after year, they continue to have the exact same issues and do fuck all about it.
Why would they normally run into 6000+ subs going private? I'm sure they tested that their code can generally handle some (usually smaller) subs going private, but the number and size of the subs going dark isn't a normal scenario and I doubt anyone would have assumed such a successful and coordinated protest involving some of the biggest subs would even be possible a few months ago.