"They" are on it 24/7

Notice all the information you get so you can resolve the issue...
- The infantilization of error messages annoys me to no end. Sure Error: exception FF02345A0 in module flarghbhgy.py is not immediately helpful, but at least it allows me to search for a solution or a cause. Recently though, a frighteningly large portion of software developers decided for some reason that Oopsie poopsie, someone made a boo boo is a better error message, especially if it's accompanied by a cute whimsical image of a kitten or some shit...
  
  OOPSIE WOOPSIE!! Uwu We made a fucky wucky!! A wittle fucko boingo! The code monkeys at our headquarters are working VEWY HAWD to fix this!
  
  "This shouldn't happen"
  
  A lot of this came out of https://en.wikipedia.org/wiki/Don%27t_Make_Me_Think which a lot of dumb UX people took to the worst extreme to be like “dumb idiot user should only get one button ever”
  
  I don't mind a whoops somebody fucked right up error message if you let me click a button for more details. Or at the very least, give me a reference number I can tell somebody about. Some "software companies" don't even properly log things on their end so nobody can solve shit.
  
  sometimes they don't even store logs so you can't do shit even if you were focused on just fixing this shit

I use Teams for work and I actually think it could be classified as malware

The other one instantly visible here: nondescript error messages that make it impossible to fix. 'Something went wrong'.
- And then the troubleshooting steps are like reset the app, reset your account and if that doesn't fix it reinstall Windows. If it still won't work, buy a new computer.
  It's terrible, just give me the info I need to figure out the root cause. It's probably very easy to fix. Instead of the ol' nuke it from orbit approach.
  And it's not just on the side of consumers either. More and more people are using docker to run shit and just reset or reinstall whenever an issue pops up. Sure that's often faster and it might work, but it won't prevent the issue from returning and you won't have learned anything. I learned the most from fixing broken shit. It requires you to figure out how it should work and what's preventing it from working like that. We are making ourselves dumber this way.
  
  More and more people are using docker to run shit
  Docker is not made that way so people can get out of fixing shit that breaks constantly. The point is more to get rid of once-in-a-lifetime errors for which a reinstall or restart would be faster for anyway, but the main reason is that you get to sleep because if something fucky happens at 3AM, it's more likely the system will just right itself.
  I certainly wouldn't call debugging a blinking container easier than just fixing shit on the server. In a container though, I can be sure the issue is fixed and it's not just another bandaid on a growing pile that is going to explode as soon as the guy building the pile retires.

I blame reticulating splines.

Anyone else having Teams just disappear without notice? It happens across my office
- Afaik it silently crashes and restarts itself minimized to tray every so often
  
  Seppuku