Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don’t let code become stale.

  • zalgotext@sh.itjust.works
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    Get the value to production

    Ugh, not this SAFe Agile ™ cultist bullshit. The “value” is working, bug free code, which you get when you put it through review and QA before it gets to production.

    • Mossheart@lemmy.ca
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      There is no value in spaghetti piled on top of rotten spaghetti. Tech iCal debt is real and if you’re just shippin it and plan to fix it later, y’all gonna have a bad time. Nothing more permanent than a temporary workaround.

    • Deifyed@lemmy.ml
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      There’s often features and bug fixes worth more than the ones introduced in the PR. I’ve yet to see bug free code just because it’s went through review and QA.

      • zalgotext@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Surely you’ve seen bugs caught because code went through review and QA though. Those are bugs that would go into production if following the “advice” in this post.

        • Deifyed@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I’m saying identify the bugs through review, and fix them. Just do it in a new PR unless they are critical