I think code review should be the responsibility of whole team. The more you share the code with other the more and more idea will came out. And the review may look into the code in some interesting viewpoint. Also the reviewer could just learn a new way to do something. So, this is a win-win situation both for the coder & reviewer as well as for the team. Because the code will be less prone to error once it has been reviewed by others.

Arcond wrote: My real questions are, does it matter much any more? Not really. utf8-cpp

I wish it was, alas no. Embarcadero have in fact recently released RAD Studio 2010. Their bastardised rip-off of VS which never seems to work. He who makes a beast out of himself gets rid of the pain of being a man.

Well, I am the architect where I work. I am pretty much THE senior developer, designing high level application architecture, planning domain objects, making platform choices (i.e. Making the decision to move to ADO.NET Entity Framework when its released), learning new architectural possabilities, overseeing architectural changes to existing code, implementing database schemas and schema changes, optimizing SQL Server queries and tuning indexes, planning hardware upgrades and some network infrastructure for the entire system (database, application, and web servers), etc. I also code plenty, writing business objects, WCF services, ASP.NET pages and controls, etc. On top of all that, I also mentor the other developers, teach CSS and web standards conformance to developers and graphic designers, and when I manage to find some free time, I learn new technologies (currently investigating advanced WCF topics and learning Entity Framework for its eventual injection into our common architecture, replacing our existing DAL). Yes, Architects DO work. ;)