Hacker News Reader

I generally like the idea of keeping PRs small, but it can be difficult to do so, because I'm spending too much time waiting on code reviews.

Stack!

++ to stacking - google has lots of folk's writing on this, ie: https://benjamincongdon.me/blog/2022/07/17/In-Praise-of-Stac...

The general idea is that you have a chance to parallelize waiting for review with you writing more code, leading to high-velocity small PRs and never being blocked.

This works fine if you're stacking/using TBD

My team does long-lived feature branches so tbh it's pretty hard to keep PRs small

Wait until you see what the research shows about PR descriptions

It saddens me so much lol. Im determined to find evidence for writing good descriptions, but hey, all the more interesting if I cant

where can i see the average size of changes in my repository?

The ideal PR is 50 lines long