A collection of characters, stories, and other elements
We invited ten developers from leading tech startups around the Bay Area to join us for an “off-the-record” dinner to discuss the practice of code review (and what we want in an ideal code review process). Below is a wrap-up of the salient points from our dinner. Given the off-the-record nature of this discussion, we have removed any mention of proprietary processes, repositories, or code examples.
A typical code review UI (in a GitHub pull request).
Key takeaway: the code review process is still very labor-intensive and performed manually, even though tools for other parts of the development process (like continuous integration) are more automated.
Key takeaway: as engineering teams scale, the code review process gets more involved and less nimble due to the limitations of current code review tools.
Key takeaway: the next evolution of code review tools should include more automated features that work at scale across different teams.
We asked each person to share what their “ideal code review tool” might look like. Here’s what we heard.