Earlier quoted context omitted.
I immediately thought that, too. I've worked with junior developers who, instead of learning from their mistakes, were defensive in code reviews and never took time to learn from their mistakes.
I'm 3ish months into my first post-graduation development job. It's really hard to go from school, where results counted, to an internship, where there was far more emphasis on getting shit done than how it was done (enterprise back office systems) to a professional software development job on a fully functional profitable web app. It's not so much that the skillset that's required is different, though that's certain…
When all else - I mean google and more importantly talking with colleagues during breaks about what you're doing - to make you realize this is the point of code reviews. And it's good - after that realization you suddenly have one more known mistake under your belt which you won't make in future.
When I was young I practiced kendo. One of the things I learned then was that when a partner hits you, he's actually helping you realize your technique has a flaw. That's how you grow as a swordsman - and as a developer too.