• Ser Salty@feddit.de
    1·
    1 year ago

    If a programmer does 500 lines, how much work will they get done before their heart explodes?

  • dudinax@programming.devEnglish
    1·
    1 year ago

    True, but the 10 line change can me merged two weeks from now and it won’t make any difference. If you let the 500 line merge languish for two days you’ll have screwed up the work of three other programmers.

  • BenLloydPearson@programming.dev
    1·
    1 year ago

    Y’all need to get yourselves some PR review automation in place. Stop wasting time on trivial reviews and requesting changes for common problems so that when you ping a colleague for a code review, they know it’s important rather than a simple request for a thumbs up.

    • TheGreenGolem@lemm.ee
      0·
      1 year ago

      Why. Whyyyyyy people need to comment this always? Why isn’t just the Approve button enough? I so much hate it.

      • qwop@programming.dev
        1·
        1 year ago

        Ah, that’s too boring. I have a range of responses to pick from to keep things interesting:

        • LGTM
        • Nice
        • Looks good
        • Thanks
        • Looks great
        • :thumbsup:
        • Looks good to me
        • :shipit:

        For me, no text means “I haven’t really reviewed this properly so don’t want to write anything that could be used against me if (when?) this breaks something in prod”

      • HorseWife@midwest.social
        0·
        1 year ago

        If you’re in a place with codebase analytics you want to have at least one comment on every MR - otherwise the system will start to think you’re falling behind… I hate codebase analytics.