Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Honesty, Kindness, Inspiration: Pick Three by Jacob Stoebel The attitude among many developers seems to be that code reviews can be either honest or nice but not both. I see this as a false dichotomy; while code reviews should be both honest and kind, they should be focused on inspiring creators to go back to their work, excited to make it better. This talk will introduce the Liz Lerman Critical Response process, a framework for giving feedback on anything creative. You'll leave this talk with tips on how to improve your code reviews by putting the creator in the driver's seat and inspiring everyone on the team to make the product even better.
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
# Summary of "Code Reviews: Honesty, Kindness, Inspiration: Pick Three" The video is a talk by Jacob Stoebel at RubyConf 2017, addressing the dynamics of code reviews within the development community. The central theme revolves around the common perception that code reviews can be either honest or kind, but not both. Stoebel challenges this notion and argues that code reviews should not be a matter of choosing between honesty and kindness. Instead, they should aim to inspire developers and encourage them to enhance their work enthusiastically. ## Key Points: - **False Dichotomy:** Many developers believe that feedback can only be honest or nice, leading to discomfort and ineffectiveness in code reviews. - **Importance of Balance:** Effective code reviews should be both kind and honest, providing constructive feedback that uplifts the developer without compromising the utility of the feedback. - **Inspiration:** The focus should be on inspiring developers, allowing them to leave code reviews feeling motivated to improve their work, rather than discouraged. - **Liz Lerman Critical Response Process:** The talk introduces this feedback framework, which is designed to guide how feedback is delivered in a creative context, ultimately aiming to empower the creator. ### Examples & Anecdotes: - Stoebel shares a tweet from a joke account that encapsulates the problematic belief about feedback. It states, "Code review can be honest or nice; pick one," highlighting that many believe there cannot be both from feedback. - He reflects upon the reactions to this tweet, indicating a collective concern regarding the limited perspectives on giving and receiving feedback in the development community. ## Conclusions & Takeaways: - Code reviews should foster an environment where developers feel encouraged and excited to improve their work. - Clarity in communication and a structured format like the Liz Lerman Critical Response process can help achieve a balance between honesty and kindness in giving feedback. - By redefining the standards for code reviews, teams can create more supportive and productive development environments conducive to creativity and innovation.
Suggest modifications
Cancel
