Earlier quoted context omitted.
To add balance to the statement about asking an art student to give an opinion of your work to get your ego stroked, I had a far different experience. I went to art school, and from foundation year (where you learn a smattering of everything: drawing, painting, sculpting, etc.) to senior year (when I focused on film and animation) I constantly had my work reviewed. Sometimes I got effusive praise, and sometimes I lef…
Code review takes too much time. You can take a painting that took 100 hours to make, and start delivering useful criticism after a minute or so. Giving useful feedback on a programming project that took 100 hours will take much, much longer. Also, art is meant to be examined - that is its primary purpose. Source code, not so much.
I don't agree that source code is not meant to be examined ( but maybe we work in totally different fields ). I regularly read source code from my coworkers, and they regularly have to read mine. Often, the developer who wrote the code is not available for questions, or isn't with the company any longer. My own code might as well have been written by another developer if I look at it after about a year. All these issues could be mitigated or muted by another set of eyes, either by sharing the knowledge ( "Why did Bob do this?" might be answered by someone else who'd reviewed the code ) or by asking the questions initially ( "Bob, why did you do it that way?" Bob: "Because of X -- I'll leave a comment in the source ).