• ViatorOmnium@piefed.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 days ago

    I wouldn’t say PR size is a bad metric, you usually just need yo read it the opposite of how sloppers do it, i.e. the most productive PRs are short and focused.

    • Slotos@feddit.nl
      link
      fedilink
      arrow-up
      0
      ·
      4 days ago

      I’m working with a legacy codebase for the last few months, where a simple PR often ends up crossing a 1000 lines count due to testing and commenting, and I can’t stop apologizing for those.

      Yet there are people out there bragging about 10x changesets.

      • ViatorOmnium@piefed.social
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 days ago

        I’m not saying it’s a good individual metric. In fact, applying individual metrics to developers (or most workers really), will only land you in Goodhart’s hell.

        But as part of holistic operational health tracking, it’s a useful team level metric, as there is ample evidence that shorter PRs tend to result in less operational issues. And, of course, this is only valid if you don’t try to tie financial rewards to it, otherwise people will forget that PR size is a proxy measure for how easy changes are to review and rollback.