• Geyser@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    6
    ·
    5 months ago

    Was there a process in place to prevent the deployment that caused this?

    No: blame the higher up

    Yes: blame the dev that didn’t follow process

    Of course there are other intricacies, like if they did follow a process and perform testing, and this still occurred, but in general…

    • j4k3@lemmy.world
      link
      fedilink
      English
      arrow-up
      33
      arrow-down
      1
      ·
      5 months ago

      If they didn’t follow a procedure, it is still a culture/management issue that should follow the distribution of wealth 1:1 in the company.

        • erwan@lemmy.ml
          link
          fedilink
          English
          arrow-up
          11
          ·
          5 months ago

          I hate to break it to you, but companies with actual safe rails to deploying to production do exist.

          And when things go wrong, it’s never the responsibility on a single dev. It’s also the dev who reviewed the PR. It’s also the dev who buddy approved the deploy. It’s the whole department that didn’t have enough coverage in CI.