• YtA4QCam2A9j7EfTgHrH@infosec.pub
    link
    fedilink
    arrow-up
    105
    ·
    edit-2
    8 months ago

    If you can fuck up a database in prod you have a systems problem caused by your boss. Getting fired for that shit would be a blessing because that company sucks ass.

      • YtA4QCam2A9j7EfTgHrH@infosec.pub
        link
        fedilink
        arrow-up
        42
        arrow-down
        2
        ·
        8 months ago

        Never fire someone who fucked up (again; it isn’t their fault anyways). They know more about the system than anyone. They can help fix it.

      • bane_killgrind@lemmy.ml
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        8 months ago

        If you are adding guardrails to production… It’s the same story.

        Boss should purchase enough equipment to have a staging environment. Don’t touch prod, redeploy everything on a secondary, with the new guardrails, read only export from prod, and cutover services to the secondary when complete.

    • daq@lemmy.sdf.org
      link
      fedilink
      arrow-up
      10
      ·
      8 months ago

      Small companies often allow devs access to prod DBs. It doesn’t change the fact that it’s a catastrophically stupid decision, but you often can’t do anything about it.

      And of course, when they inevitably fuck up the blame will be on the IT team for not implementing necessary restrictions.

      Frequent snapshots ftmfw.