That blog is a gem. At least for me as a student. One item that I found particular fascinating is this: in [1] he quotes: Rigorous inspections [code reviews] c

That blog is a gem. At least for me as a student. One item that I found particular fascinating is this: in [1] he quotes: Rigorous inspections [code reviews] can remove up to 90% of errors before the first test case is run (Fact 37) How to implement this in a loosely organized group of 3 to 4 developers that each have other projects on their schedule but work on some common projects? I'm eager to write a long email to them explaining that we should do a "talk about your code hour" but I can also see the problems with such a approach. Shame, Ego, "no time for this shit", poorly spewed out presentations... are there patterns? or are pattern yet another problem layer? (sorry for hijacking this thread) 1: http://blog.davidtate.org/2011/12/5-minute-book-review-facts-and-fallacies-of-software-engineering/ http://blog.davidtate.org/2011/12/5-minute-book-review-facts...