Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RailsConf 2017: Goldilocks And The Three Code Reviews by Vaidehi Joshi Once upon a time, Goldilocks had a couple extra minutes to spare before morning standup. She logged into Github and saw that there were three pull requests waiting for her to review. We've probably all heard that peer code reviews can do wonders to a codebase. But not all type of code reviews are effective. Some of them seem to go on and on forever, while others pick at syntax and formatting but miss bugs. This talk explores what makes a strong code review and what makes a painful one. Join Goldilocks as she seeks to find a code review process that's neither too long nor too short, but just right!
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In her talk "Goldilocks And The Three Code Reviews" at RailsConf 2017, Vaidehi Joshi explores the timing and effectiveness of code reviews in software development. Drawing parallels with the fairy tale of Goldilocks, she seeks to find a code review process that is 'just right'—not too long, not too short, but effective. The presentation highlights the evolution and history of code reviews, their importance in fostering quality code, and the various methods that can enhance the review process. ### Key Points: - **Fairy Tale Retelling:** Joshi introduces a modern rendition of Goldilocks as a Rails developer who navigates through different job experiences with varying code review processes. - **Importance of Code Reviews:** She emphasizes that structured and thoughtful code reviews are crucial for improving code quality and helping developers grow. - **Types of Code Reviews:** The talk outlines three types of code reviews: - **Inspections:** In-depth focus on defect detection, requiring clear roles and checklists. - **Short Reviews:** Brief reviews that can significantly reduce error rates in code submissions. - **Walkthroughs:** Exchange-oriented meetings designed for learning and questioning between developers. - **Research Findings:** Joshi presents findings from a survey she conducted, revealing the effectiveness of code reviews and highlighting that the quality of a team’s code review process is essential for developer satisfaction. - **Principal Takeaways:** Through the analysis of the survey results, Joshi concludes with several recommendations: - Review everyone equally—emphasizing collaboration and the importance of feedback for all team members. - Provide concise context in reviews to facilitate better understanding and communication. - Utilize tools like linters to streamline the process and focus reviews on substantial content rather than syntax. - Maintain an iterative process for continuously improving the code review system. In a closing reflection, Joshi encourages teams to engage in conversations about their code review practices to ensure they are effective and valuable. She reinforces that while theory is vital, the practice of code reviews ultimately hinges on how well teams conduct them. Engaging openly in dialogue around these processes can lead to richer collaboration and better outcomes in software development.
Suggest modifications
Cancel
