Code Review

January 8, 2019

Code Reviewer Spotlight: Eli Perelman


A passion for contributing to open source projects is one of the most common traits we see in PullRequest code reviewers. Eli Perelman has dedicated his programming career to helping other developers through open source. Now, as a PullRequest code reviewer, Eli applies his commitment to improving the experience of other developers to reviewing code for other teams.

This Code Reviewer Spotlight is part of an ongoing series of interviews where we ask our top reviewers the following seven questions so you can get to know them. Below, discover how Eli sees being a reviewer as another a way to improve the experiences of other developers.

Brennan Angel headshot

December 30, 2018

The $85 Billion Cost of Bad Code

A recent study from Stripe and Harris Poll found the average developer spends 42% of their time dealing with technical debt and maintenance issues, of which 3.8 hours are spent just on debugging “bad code,” or poor quality code that’s difficult to maintain. The opportunity cost of bad code comes to $85 billion annually — resources that could otherwise be used to build better software.

Lyal Avery headshot

December 10, 2018

Code Reviewer Spotlight: James Slater

PullRequest reviewer James Slater learned Google’s code review process by doing. Over several months of demonstrating his understanding of the style guide, code clarity, language mastery and best practices, he was finally granted JavaScript Readability at Google — an internal certification that shows you understand Google’s best practices and coding style for a given language.


Completing the demanding readability process showed James’ commitment to improving code quality and mentoring others, and it also highlighted what he liked and disliked about the code review process. Over his engineering career, he found the right balance of positive, constructive guidance, and now provides code review as a service with PullRequest.

Brennan Angel headshot

December 4, 2018

Why Truly Great Product Managers Love Code Review

Many years ago, I started my career in product management with only a basic understanding of what is code review—developers looking through each others’ code for bugs. With upcoming deadlines, KPIs, user (re)engagement, compliance, and revenue goals all competing for my attention, understanding our development team’s code review process wasn’t a priority. After all, we had a great QA team. It took some time for me to understand that code review is so much more than identifying new issues.

Dan Mateer headshot

November 26, 2018

Code Reviewer Spotlight: Tristan Dunn

With experience scaling development teams at companies like Clearbit, Envoy, ROLI, Dribbble, and Google, PullRequest reviewer Tristan Dunn‘s resume spans many different creative industries. Looking across them all and his work with PullRequest, he sees how new hires or new developers provide a fresh perspective through code review, and how sometimes that’s exactly what’s needed to find code smells that teams may have become nose blind to.

Our Code Reviewer Spotlight is an ongoing series of interviews with top reviewers to learn more about the senior developers in our reviewer network:

Brennan Angel headshot