• eletes@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    6 months ago

    Holy fuck whoever was in charge of setting up that disaster recovery needs a million dollar bonus. I get that they’re managing $80B and this should all be standard but people usually don’t listen to IT and take DR seriously. And even if you do set it up, are you going back to check that your backups are functioning properly and have alarms for when it messes up

    • snekmuffin@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Tbf python guidelines encourage it over if/else in cases like this. “Easier to ask for forgiveness than for permission” or something along the lines

      • bjornsno@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        Day 598 of asking for a way to tell which functions throw exceptions in Python so I can know when to wrap in try catch. Seems to me that every other language has this, but when I’ve asked for at least a linter that can tell me I’m calling a function that throws, the general answer has been “why would you want that?”

        How am I supposed to ask for forgiveness if it’s impossible to know that I’m doing something risky in the first place?

        • sqw@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 months ago

          cant practically anything throw an exception given the right (sometimes extremely remotely possible) circumstances?

        • ScreaminOctopus@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 months ago

          Yeah, for this reason I would pretty much never encourage exceptions in Python over some other form of error handling. It’s so frustrating when called code throws some random exceptions that are completely undocumented. This is one of the few things Java got (sort of) right