✳flâneur — a map of the web's best reading
Why Write Small Diffs - by Ryan Peterman
developing.dev · 478 words · saved by 1 readers
5 Reasons
Why Write Small Diffs 5 Reasons Ryan Peterman Feb 09, 2024 74 12 Share 👋 Hi, this is Ryan with this week’s newsletter. I write about software engineering, big tech/startups, and career growth. Thank you for your readership, we hit 48,000 readers this week 🙏 🎉 This week, I wrote about why small diffs are best. If you find the post helpful, please share it with your friends and coworkers. Enjoy! Note: “diffs” == “code changes” == “PRs” After writing over 1000 diffs, I prefer smaller ones. Often there’s wisdom in what you naturally tend towards over time. This preference developed after lots o
Explore this link on the map →related reading
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- The ideal PR is 50 lines longgraphite.dev
- Unified Versus Split Diffmatklad.github.io
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- rams - Expert Design Reviews on Every PRrams.ai
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- Compare · Surfer-Org/Old-Protocol · GitHubgithub.com
- The Myers diff algorithm: part 1 – The If Worksblog.jcoglan.com
- Introducing FrontierCode | Cognitioncognition.ai
- How to Make Your Code Reviewer Fall in Love with You · mtlynch.iomtlynch.io
- The comprehensive guide to writing the best PR title of all timegraphite.dev
- GitHub - conventional-changelog/conventional-changelog: Generate changelogs and release notes from a project's commit messages and metadata. · GitHubgithub.com