DEVMARKS

Create your own public collection of bookmarks to share with others by logging in with GitHub.

All Collections

Doing code review · Matt Layman

4 years, 11 months ago

For Delightful Code Reviews, Say Nice Things

How to Do Code Reviews Like a Human (Part One)

5 years, 1 month ago

Code reviews are an opportunity to share knowledge and make informed engineering decisions Arguments about style are a waste of time in reviews. A good style guide defines not only superficial elements like naming conventions or whitespace rules but also how to use the features of the given programming language More ▼

How to Make Your Code Reviewer Fall in Love with You

2 years ago

Notes from the article that I think are worth highlighting: Before sending code to your teammate, read it yourself. Don’t just check for mistakes — imagine reading the code for the first time. What might confuse you? Pay attention to your patterns of error, and think about creating systems to More ▼

Why code review beats testing: evidence from decades of programming research | Kevin Burke

11 years, 2 months ago

The key part of this article is expressed in the Conclusion: If you want to ship high quality code, you should invest in more than one of formal code review, design inspection, testing, and quality assurance. Testing catches fewer bugs per hour than human inspection of code, but it might More ▼

The Standard of Code Review

I’m adding this mostly for completeness sake. The document talks a lot about `CL` and links to other pages that talk about `CL` without EVER explicitly stating what they actually are. Because of that I’m not sure that this is the best article on Code Reviews but 🤷🏼‍♂️

◉ Writing Reviewable Code

The complexity of understanding, testing and reviewing a change often increases faster than its size: ten 200-line changes each doing one thing are often far easier to understand than one 2,000 line change doing ten things. The minimum size of a change should be a complete implementation of the simplest More ▼

ramblings on code review

Highlights from the article: If you let code go unreviewed, you are explicitly prioritizing your productivity over the productivity of the rest of the team. If you have nothing to say, then say that! If your name is on a review, you should at least acknowledge it with something like More ▼

devmarks.io is Bookmarking for Developers. Automatically sync all your developer resources to one place.