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
related reading
- Shipping Code Faster - by Ryan Peterman - The Peterman Postdeveloping.dev
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- Mistakes engineers make in large established codebasesseangoedecke.com
- How To Do Lessalexturek.com
- How I ship projects at big tech companiesseangoedecke.com
- The ideal PR is 50 lines longgraphite.dev
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Notes on software qualityanthonyhobday.com
- Advice for new software devs who've read all those other advice essays • Buttondownbuttondown.email
- How To Drive Meetings - by Ryan Petermandeveloping.dev
- Unified Versus Split Diffmatklad.github.io