Mentoring Junior Developers Through Code Reviews

I am a Sr. Software Engineer at Oracle with over 6 years of experience. Great seniors at Amazon and Microsoft have mentored me. I am now mentoring some really smart junior engineers. One thing I wish both sides of the table understood to make the process a bit easier would be this: Senior developers should act more like mentors and less like managers. Junior developers should act more like owners and less like task-takers. What does this look like in practice? For senior engineers: 1) Share context, not just tickets. Explain the tradeoffs and the reasons behind decisions. 2) Review their thinking approach, not just to approve or reject. Leave at least one learning point in every session. 3) Give space for juniors to think aloud. Help them debug their approach before you hand them your own. 4) Protect them from random chaos when you can. Take the heat upward, pass clarity downward. For junior engineers: 1) Do not show up to a senior with an empty page. Try something first, even if it is wrong. 2) Ask for feedback on your thinking, not only your code. 3) Own the problem from start to finish. Logs, tests, edge cases, rollout, follow-up. 4) Take notes and close the loop. If a senior explains something once, capture it so you can use it again. The best teams I have worked with did not feel like “senior vs junior.” They felt like a group of people at different experience levels, all caring about the same product. If you are a senior, you are already a role model, whether you want it or not. If you are a junior, you are already part of how the culture feels. Act like mentors. Act like owners. The product gets better this way, but the people get better too.

Stop leaving "corrective" PR comments. You're just creating code monkeys. 🙊 There, I said it. Early in my career, a senior dev left a comment on my code: "Incorrect. Use a different pattern." I felt stupid, and I learned nothing about the why. I just did what I was told. That experience taught me that the goal of a code review isn't just to fix the code. It's to build a better engineer. Something I learned while being a Teaching Assistant for a Software Engineering class but never got to apply in the real world. I could map the learnings 1-1. My philosophy now: A great PR review closes two things: 👇 1. The technical ticket. 2. An invisible ticket in the other developer's confidence. Here's my 3-part framework for reviews that actually coach: 1. Start with a Question, Not a Command: Instead of "Change this," try "What are your thoughts on how this might scale under heavy load?" It invites a discussion. 2. Explain the 'Why' Behind the 'What': Don't just suggest a change. Link to the documentation, a blog post, or an internal principle that explains the reasoning. 3. Compliment the Good Stuff: Find something to praise. "Love how you simplified this logic here." It creates psychological safety and makes the constructive feedback easier to hear. Let's stop correcting and start coaching. 🚀 #Leadership #SoftwareDevelopment #WorkplaceCulture #Mentorship #CodeReview

"Hey… I rewrote the commit message, but I wasn't sure how to respond to the 'this makes no sense' comment." It wasn't my comment. But I knew exactly whose it was. And I knew how much it affected her willingness to submit the next PR. Here's the thing: Most engineers aren't avoiding code reviews because they don't care about quality. They're avoiding you. Or more specifically, how you make them feel. There's a massive difference between: • "Why would you do it this way?" vs • "Let's talk through what this is solving—there might be a clearer way." Critique should make someone's code feel challenged. Not their confidence. If your code reviews sound like rants, nags, or insults, dont be surprised when junior devs: • Delay shipping. • Ask fewer questions. • Avoid your name in the reviewer list. Want people to write better code? Try writing better comments. Here are some examples that actually work: • "This is clean—love the naming here." • "Could we simplify this even more?" • "Appreciate the test coverage here—nice work!" • "What do you think about extracting this into a helper function?" • "Good catch on handling that edge case." Code quality matters. But morale does too. The best engineers I know give feedback that makes people excited to improve, not afraid to try. Your code reviews aren't just about the code. They're about the person writing it. Encouragement isn't fluff. It's fuel.

The best code review I ever received had zero technical feedback. Instead, my senior colleague wrote: "The code works perfectly, but someone reading this in 6 months won't understand the reasoning behind your approach. What context are we missing?" No nitpicks about variable names. No debates about algorithms. Just one simple question that changed how I think about code forever. That review taught me: → Code is written once, but read hundreds of times → Your biggest audience isn't your team today—it's your team in 6 months → Clarity beats cleverness every single time → The best code tells a story, not just executes logic Now when I review code, I ask different questions: "What story is this code telling?" "Will someone understand the 'why' behind these decisions?" "Are we solving for today's problem or tomorrow's maintenance?" The most impactful code reviews aren't about finding bugs—they're about building empathy for the humans who will inherit your work. What's the best non-technical feedback you've received on your code? #CodeReview #SoftwareEngineering #TechLeadership #CleanCode