✳flâneur — a map of the web's best reading
10 Common Mistakes Developers Make When Reviewing Code | by Tate Galbraith | Level Up Coding
levelup.gitconnected.com · 248 words · saved by 1 readers
Don’t fall into these traps
Member-only story Programming Developer Technology Software Development Coding 10 Common Mistakes Developers Make When Reviewing Code Tate Galbraith 6 min read · Jul 14, 2022 -- 1 Listen Share Press enter or click to view image in full size Photo by Austin Distel on Unsplash Reviewing someone else’s code can feel like you’re calling their precious baby ugly. But that code might be bad, and that baby might actually be hideous. When you look at another developer’s code, you want to provide honesty and actionable feedback. Pull no punches when it comes to code reviews. Be sure to give the author
Explore this link on the map →related reading
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- How to Do Code Reviews Like a Human (Part One) · mtlynch.iomtlynch.io
- How to Make Your Code Reviewer Fall in Love with You · mtlynch.iomtlynch.io
- How to Do Code Reviews Like a Human (Part Two) · mtlynch.iomtlynch.io
- Reading 4: Code Reviewweb.mit.edu
- Things You Should Never Do, Part I – Joel on Softwarejoelonsoftware.com
- Google Testing Blog: Code Health: Too Many Comments on Your Code Reviews?testing.googleblog.com
- I built an AI code review agent in a few hours, here's what I learnedsourcebot.dev
- Nonviolent Code Review - MediaWikimediawiki.org
- New Junior Developers Can’t Actually Code | N’s Blognmn.gl
- The Most Efficient Way to Read Code Written by Someone Else | Towards Data Sciencetowardsdatascience.com
- I Finally Learned How Senior Engineers Read Code (It’s Not What You Think) | by Dua Asif | Activated Thinker | Mediummedium.com