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

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

    I kind of with the sentiment. Review pre merge though, but only block the merge if there are serious faults. Otherwise, merge the code and have the author address issues after the merge. Get the value to production

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

      have the author address issues after the merge.

      Hahahahahahaha. Sorry, you’ve merged, next ticket, PM needs shiny results for execs this QBR!

      This is how bug backlogs grow.

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

        Yeah, I see your point. Maybe my employers are different, it’s never been an issue explaining why the ticket isn’t closed just because the PR is merged

    • Doveux@pawb.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I’m with you. I’ve worked on a few teams, one of the first was a company where two teams were contributing code changes to the same product. The other team “owned” it and as a result it took ages, sometimes months, to get code changes merged. It meant more time was spent just rebasing (because merging wasn’t “clean”) than working on the actual feature.

      My current role, we just do TDD, pair programming, and trunk-based development. We have a release process that involves manual testing before live deployment. Features that aren’t ready for live are turned off by feature flags. It’s quick and efficient.

      Fundamentally I think the issue is the right tool for the job. Code doesn’t need to be managed the same way in a company as it does in an open-source project.

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

        Sorry about the confusion. It’s not sarcasm. I’m just sick and tired of people blocking my PR because of an argument about wether the function should be called X or Y or Z or D

        • jjjalljs@ttrpg.network
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Ah. Yeah those kind of nitpicks are annoying. We try to specify when comments are blocking or non blocking on reviews.

          But I definitely block a lot of reviews over no tests, bad tests, no error handling, failed linting. And the occasional “this doesn’t do what the ticket asked for”