The fastest period of growth in my career started the year I stopped reading code review comments as a verdict. A line left on a PR is not a judgement of my worth as an engineer. It is a signal: about my code, about the reviewer's mental model, about the gap between the thing I wrote and the thing the system needs.
That sounds obvious when written down. It did not feel obvious when someone left twelve comments on a PR I thought was clean.
The reframe.
Treating each comment as data instead of as a grade changes the shape of the whole conversation. When I stopped defending, I started listening. When I started listening, I started understanding, not always agreeing, sometimes I push back and I am right to, but understanding what the comment is actually pointing at.
The second-order effect was that my own review comments got better. When I was not worried about how mine would land, I could focus on what I was actually trying to communicate. I got clearer. I got kinder. The reviews I leave now are the ones I would have wanted to receive.
The compounding.
Constructive feedback is the cheapest mentorship available. You do not need a formal arrangement or a structured programme. You need a team that gives a damn and enough self-possession to let the signal in. A single well-aimed review comment (the kind that points at a design flaw you would have carried forward for years) is worth more than months of self-study. You cannot find the blind spot you cannot see.
What I try to do now.
I try to leave one comment on every PR that is not about correctness but about craft: a question, an alternative, a pattern I have found useful. Not a prescription. An invitation. And when I receive a comment I do not immediately agree with, I sit with it before responding. Usually it opens something up. The ratio has shifted, and the work is better for it.