Situation: During a sprint code review, a teammate submitted a 1,200-line pull request that bypassed our agreed modular design patterns and lacked automated integration test coverage.
Task: I needed to provide clear, actionable feedback to bring the code up to our quality standards without discouraging my peer or making them feel attacked.
Action: Rather than leaving twenty critical comments on GitHub that could feel overwhelming, I sent them a friendly private message and asked if we could jump on a 15-minute pairing call. I opened by acknowledging the complexity of the problem they had solved. I then framed my feedback around our shared team principles and future maintainability rather than personal preference, saying: 'How can we structure this so that if someone else is on-call next month, this code is easy to debug?'. We walked through extracting two helper classes together, and I helped them draft the first integration test case.
Result: My colleague appreciated the pairing approach, happily restructured the PR into two smaller reviewable commits, and later mentioned in our retrospective that the pairing session was one of the best learning experiences of their quarter.