Linux Ate My Dog! writes: For better or for worse, the web has transitioned from a system made by software engineers joined by a neglected user interface pro tinkering with page layouts, to one where teams of coders, Interaction Designers, and Graphic Designers work together to create rich interactive experiences. I have transitioned with it, from the software cubicles to the Digital Agency, and working with Graphic Designers I noticed something interesting: they handle critiques of their design much better than programmers do of their code, and I think it is because of what they go through during their training. During crunch time nobody cares what code looks like internally, just that it passes acceptance tests, so we get very ego-invested in how save the world from missing our deadline. While there are strategies to handle ego-investment, and pair-programming does force us to review the internals of code and architecture more these days, is there actual planned systematic review of your code? How do you handle criticism and praise for your lines?