http://misko.hevery.com/code-reviewers-guide/ http://misko.hevery.com/code-reviewers-guide/ This is the highest value to time spent read that you will ever exp

http://misko.hevery.com/code-reviewers-guide/ http://misko.hevery.com/code-reviewers-guide/ This is the highest value to time spent read that you will ever experience for programming. If you read through the rest of the guy's justification for these points (by clicking the headings and then if you want more trawling through older blog posts) you will start to see the matrix. You might have taken a class that said "high coupling in your software is bad," but it's an entirely different experience to see the common patterns that result in high coupling (or the violation of scopes via accessing global state etc) and pragmatic ways to re-write them. Making programs a recursive 2 steps per object life time (lifetime of server, lifetime of request, etc): 1. Draw the object graph by instantiating objects of the current lifetime and giving them references to eachother 2. Call run(), which executes the object graph Felt like an epiphany to me.