• William@lemmy.world
    link
    fedilink
    arrow-up
    21
    ·
    1 year ago

    Even if you release multiple times every day, refusing to release on Friday still makes sense. It’s not about expecting bugs, it’s about guaranteeing that your devs’ time is their own. If you aren’t okay with paying your devs for time they spend dealing with their own problems at home (without charging them their PTO time for it!) then you shouldn’t be okay with making them work on weekends, no matter how rare it is.

    • rglullisOPA
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      6
      ·
      1 year ago

      The author ended up creating a strawman. Allen’s argument was pretty clear: if your deltas are small and your deploy system is fully automated, then no one should be afraid of the risk of deploying.

      Given that, if I deploy on a Monday morning and there is a bug on the new release, you revert, reproduce the issue in staging and push only new code when it is fixed. Same thing if I were deploying on a Thursday afternoon or a Friday at 7PM.

      • MajorHavoc@lemmy.world
        link
        fedilink
        arrow-up
        9
        ·
        1 year ago

        Only inexperienced developers* are unafraid of deploying right before leaving the office.

        There’s an entire untapped universe of possible new ways that things can go horribly wrong.

        *Experienced developers who hate their boss and their colleagues, too, technically.

        • rglullisOPA
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          4
          ·
          1 year ago

          possible new ways

          Name two, please.

            • rglullisOPA
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              4
              ·
              1 year ago

              How is that not easily reversible?

              • MajorHavoc@lemmy.world
                link
                fedilink
                arrow-up
                4
                ·
                1 year ago

                It’s not about how hard the problem is to reverse, it’s about respecting the team enough not to call them on Saturday.

                • rglullisOPA
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  arrow-down
                  4
                  ·
                  edit-2
                  1 year ago

                  Again: if the changes are small enough and you have automated checks in place, they should not require manual intervention.

                  Plus, what happens if a deploy on Thursday has a bug which only is manifested on a Saturday?

  • mattreb@feddit.it
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    In one of my jobs, they were automatically locking any push 2 hours before the shift ended.

  • MajorHavoc@lemmy.world
    link
    fedilink
    arrow-up
    11
    arrow-down
    2
    ·
    edit-2
    1 year ago

    If something goes wrong, devs have to give up their weekend to fix the issues, leading to burnout and dissatisfaction.

    Correct in spirit, but the words “burnout” and “dissatisfaction” are weasle words that spinless middle managers use.

    The correct terms are “abruptly quiting without notice leaving the company fucked and our stock worthless”.

    A minor point, but worth clarifying.