Introduction: What You’ll Learn
This simulation explores how to mentor and coach a peer after they receive challenging feedback in a code review. You'll learn how to help them regain confidence, focus on constructive improvement, and foster a positive learning environment.
You’ll practice:
- Providing empathetic support and encouragement
- Helping identify actionable improvements
- Guiding reflection on feedback constructively
- Enhancing a peer's development and confidence
Step-by-Step Simulation
Scene 1: Setting the Stage
Mentor: "Hey Jamie, I saw the comments from your recent code review. Want to grab a coffee and chat about it? I’m here to help you work through the feedback and see how we can make it a positive experience."
Jamie: "Thanks. Yeah, that review hit me hard. I thought my code was on point, but the feedback was a bit overwhelming."
Mentor: "I totally get that. Feedback can feel harsh sometimes, but it’s really about helping you grow. Let’s dig into it together and see where we can make some improvements."
Scene 2: Analyzing the Feedback
Mentor: "So, what were the main points from the review that stood out to you?"
Jamie: "They mentioned my variable names weren’t clear and my logic was hard to follow. It felt like I couldn’t do anything right."
Mentor: "I’ve been there too. Naming things is surprisingly tricky, but it’s something you can improve with practice. Let’s also look at simplifying your logic—sometimes a fresh perspective helps."
Jamie: "I guess I could have used more descriptive names."
Mentor: "That’s a good start. And about the logic—were there specific parts that were flagged?"
Jamie: "There were some nested conditions that got complicated."
Mentor: "Let’s walk through those together and see how we can clean them up."
Scene 3: Focusing on Strengths and Growth
Mentor: "Remember, reviews aren't just about what needs fixing; they're also about recognizing what you did well. What parts of your work do you feel proud of?"
Jamie: "I managed to implement the feature quickly and made sure to cover edge cases in my tests."
Mentor: "That’s awesome! Speed and thorough testing are big wins. Let’s build on those strengths while refining your naming and logic."
Jamie: "Thanks. I was feeling pretty down, but this helps."
Mentor: "Every developer goes through this. It’s part of the journey to becoming better."
Scene 4: Setting Goals and Moving Forward
Mentor: "Let’s set some goals. How about we refactor the logic together and review the variable names? Then you can give it another go before resubmitting."
Jamie: "That sounds like a good plan. I want to get this right."
Mentor: "You will. Let’s also set a follow-up next week to check in on your progress. Remember, I’m here to help."
Jamie: "Thanks for the support. I’m feeling more optimistic now."
Mentor: "Anytime. Let’s turn this feedback into a stepping stone for even greater things."
Mini Roleplay Challenges
Challenge 1: Jamie gets defensive about the feedback.
- Best Response: “I know it can feel personal, but it’s about making the code better. Let’s see how we can use this feedback to strengthen your skills.”
Challenge 2: Jamie is reluctant to ask for help.
- Best Response: “I’m here to support you, and asking for help is a great way to learn. Let’s tackle this together.”
Challenge 3: Jamie feels demotivated and wants to give up.
- Best Response: “I know it’s tough right now, but you’ve handled challenges like this before. Let’s focus on one step at a time.”
Optional Curveball Mode
- Jamie struggles with a similar issue in the next review.
- Jamie doesn’t want to discuss the feedback.
- Jamie feels isolated and unsupported by the team.
Practice handling each one with empathy and constructive guidance.
Reflection Checklist
Mentorship Approach
- Did I create a safe space for Jamie to express their thoughts?
- Did I focus on strengths as well as areas for improvement?
- Did I provide actionable next steps?
Support & Encouragement
- Did I help Jamie see the feedback as an opportunity for growth?
- Did I offer my assistance in a supportive manner?
- Did I reinforce their value and potential as a developer?
Common Mistakes to Avoid
- Focusing only on negatives without highlighting strengths
- Overloading with too much advice instead of actionable steps
- Rushing the conversation without listening fully
- Making the peer feel more overwhelmed or inadequate