I understand the sentiment here, and maybe it applies well to open source projects looking for any sort of contribution. But I've also seen plenty of cases where junior developers jump into the deep end and put up a garbage PR, where the senior developers get to spend cycles effectively rewriting the entire thing through opening tons of issues and comments.<p>This may be uncommon, but my employer has also started tracking metrics on pull requests and merge times. There's incentive in some places to only put up code that's reached some level of "ready to merge" as opposed to using a PR as a tool for peer or group programming. You could achieve a similar collab/feedback by pushing to a fork or branch and then linking to it in a discord or IRC server where you can have "real" time discussion around the change.