How to Make Your Code Reviewer Fall in Love with You
mtlynch.io · 3,087 words · saved by 1 readers
Best practices for code review when you're the author.
When people talk about code reviews, they focus on the reviewer. But the developer who writes the code is just as important to the review as the person who reads it. There's scarcely any guidance on preparing your code for review, so authors often screw up this process out of sheer ignorance. This article describes best practices for participating in a code review when you're the author. In fact, by the end of this post, you're going to be so good at sending out your code for review that your reviewer will literally fall in love with you . But I don't want my reviewer to fall in love with me…
related reading
- How to Do Code Reviews Like a Human (Part One) · mtlynch.iomtlynch.io
- How to Do Code Reviews Like a Human (Part Two) · mtlynch.iomtlynch.io
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- Mediumlevelup.gitconnected.com
- Cognitive load is what mattersminds.md
- Your job is to deliver code you have proven to worksimonwillison.net
- How to read a codeiamjonas.me
- Agile for developers: Refactoring codeabout.gitlab.com
- Shipping Code Faster - by Ryan Peterman - The Peterman Postdeveloping.dev
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Good code is like a love letter to the next developer who will maintain it.addyo.substack.com
- Why Good Developers Write Bad Unit Tests · mtlynch.iomtlynch.io