Being a good code reviewer

One of my internal goals this year was to make a substantial comment on every patchset that came my way.... because the bugs are out there! For this session, we'll talk about how to be a good code reviewer. Topics will include examining memory usage, structure packing, multithreaded impacts, critical section lock scoping, 32bit/64bit impacts, optimal STL usage, unit test coverage, and more. Session will have a C/C++ focus but may not be exclusive to that. Topics will also include several examples that we review together as well as an open discussion period (even bring your most obscure patchset/bugs for us to examine, if you want)