Episode 400: Michaela Greiler on Code Reviews

Topics covered
Popular Clips
Episode Highlights
Experience
Michaela Greiler emphasizes the importance of experience and familiarity with codebases in conducting effective code reviews. She notes that reviewers unfamiliar with a particular technology or codebase often struggle to provide valuable feedback, especially when dealing with complex files like YAML. Greiler suggests that new team members, even if they are senior, may take up to six months to offer consistent, valuable feedback due to their lack of familiarity with the codebase 1.
Experience has a lot to do with the way you can give valuable feedback and you can contribute.
---
To mitigate these challenges, she recommends in-person code reviews for new hires to foster a supportive learning environment 2.
Dynamics
Team dynamics and seniority significantly impact the quality of feedback during code reviews. Michaela Greiler highlights the need for a safe space where team members can grow and learn without fear of judgment. She warns against assuming a safe environment exists without continuous effort to maintain it 3.
There must be a constant and continuous effort from the team, from the people, towards working to such a safe space.
---
Felienne Hermans adds that seniority can influence the feedback dynamic, with senior members potentially overshadowing juniors, even in supportive settings 4.
Language
Different programming languages pose unique challenges during code reviews. Michaela Greiler explains that while the mechanics of code reviews are similar across languages, the effectiveness and focus areas can vary significantly. For instance, reviewing C code involves different considerations than Java or C#, due to language-specific features like garbage collection 5.
The code reviews look different for the different programming languages, even though from the outside it looks all the same.
---
She also stresses the importance of traceability in code reviews, advocating for documentation of review outcomes to enhance accountability and clarity 6.
Related Episodes


Episode 93: Lessons Learned From Architecture Reviews with Rebecca Wirfs-Brock
Answers 383 questions

SE-Radio Episode 295: Michael Feathers on Legacy Code
Answers 383 questions

Episode 130: Code Visualization with Michele Lanza
Answers 383 questions

Episode 517: Jordan Adler on Code Generators
Answers 383 questions

Episode 401: Jeremy Miller on Waterfall Versus Agile
Answers 383 questions

Episode 22: Feedback
Answers 383 questions
Episode 422: Michael Geers on Micro Frontends
Answers 383 questions

Episode 134: Release It with Michael Nygard
Answers 383 questions

Episode 101: Andreas Zeller on Debugging
Answers 383 questions

Episode 59: Static Code Analysis
Answers 383 questions

Episode 82: Organization of Large Code Bases with Juergen Hoeller
Answers 383 questions

Episode 96: Interview Krzysztof Czarnecki
Answers 383 questions

Episode 430: Marco Faella on Seriously Good Software
Answers 383 questions

SE-Radio Episode 357: Adam Barr on Code Quality
Answers 383 questions

Episode 17: Feedback and Roadmap
Answers 383 questions














