The best code review comments outlive the PR they're on
Most teams that say they mentor through code review are actually just enforcing taste, inconsistently, one PR at a time. A comment is mentorship when it changes how the author reasons about the next five decisions, not just the one sitting in front of them.
It's the same skill as architecture, just applied at sentence level. The Technical Leadership Advisory service and the career story on the journey page both come back to the same idea: judgment that transfers, instead of judgment that has to be repeated by hand in every PR.
What strong review guidance actually looks like
Name the principle, not just the fix — pointing out that a change creates a race condition teaches something; telling someone to add a mutex there doesn't.
Separate what's actually broken from what you'd merely prefer. Blocking a PR over a naming convention teaches the wrong lesson.
Use review to clarify who owns what, not only whether the syntax is clean.
Review quality matters even more mid-migration, which is a big part of why it comes up again in How to Modernize a Legacy Monorepo Without Freezing Delivery.
How to mentor without slowing delivery
Save the long explanation for patterns you'll see again. A one-off mistake doesn't need a paragraph.
Write the lesson down once, in a doc or a short design note, instead of retyping it in every PR that touches the same code.
Pair in real time on the changes that are actually risky. Comment volume is not a substitute for sitting next to someone.
Keep expectations visible before the review starts, not discovered during it — a short style guide beats a surprise nitpick.
Where readers can go next
If this resonates, the next useful places on the site are about, services, and What Strong Technical Due Diligence Looks Like for Startups and Hiring Teams.
The actual goal
Mentorship through review is working when the team needs you less, not more. The point was never to centralize judgment in one senior engineer — it's to get good judgment running in more heads than just yours. contact me if that's the gap you're trying to close.
