✳flâneur — a map of the web's best reading
The ideal PR is 50 lines long | Graphite
graphite.dev · 1,232 words · saved by 1 readers
Graphite is modern code review for fast-moving teams - we help engineers write and review smaller pull requests, stay unblocked, and ship faster.
Most engineers intuitively know that smaller code changes are better than big ones. The logical arguments flow easy - small pull requests are easier to review, less likely to have bugs, and are faster from inception to deploy. There are a few papers around this that I love - see the references section at the end of this post for further reading. But how small is small? Can PRs be too small? And if a PR is better than a big PR, how much better? The claim: the ideal PR is 50 lines long After pulling the numbers, the ideal code change is 50 lines long. 50-line code changes are reviewed and merged
Explore this link on the map →related reading
- The comprehensive guide to writing the best PR title of all timegraphite.dev
- Why Write Small Diffs - by Ryan Petermandeveloping.dev
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- meks.questmeks.quest
- AI code reviews for complex codebases | cubic | Try free nowcubic.dev
- rams - Expert Design Reviews on Every PRrams.ai
- llm-wiki · GitHubgist.github.com
- Introducing FrontierCode | Cognitioncognition.ai
- Google Testing Blog: Code Health: Too Many Comments on Your Code Reviews?testing.googleblog.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Compare · Surfer-Org/Old-Protocol · GitHubgithub.com
- How to Do Code Reviews Like a Human (Part One) · mtlynch.iomtlynch.io