• Geyser@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    6
    ·
    4 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
      32
      arrow-down
      1
      ·
      4 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.

    • aodhsishaj@lemmy.world
      link
      fedilink
      English
      arrow-up
      22
      ·
      4 months ago

      How could one Dev commit to prod without other Devs reviewing the MR? IF you’re not protecting your prod branch that’s a cultural issue. I don’t know where you’ve worked in the past, or where you’re working now, but once it’s N+1 engineers in a code base there needs to be code reviews.