How do I take blunt code review feedback without getting defensive?
Fix the easy 90% of the comments silently, batch the genuine disagreements into one short call, and never reply the same day you read them.
Tag
Technical leadership: mentorship, code review and putting team communication in writing. questions under this tag, answered directly.
3 answered questions carry this tag.
Fix the easy 90% of the comments silently, batch the genuine disagreements into one short call, and never reply the same day you read them.
Kill the reflex to grab the keyboard; your metric isn't how fast you ship today but whether the junior needs you a little less each week.
Take an ownerless org-level problem, lay the solution out in a written tech strategy, and show impact through the teams you accelerate, not your commits.