[codeonfire]

Unit tests, code reviews, pair programming, procedures, etc are all tools. Their use depends on the circumstances. In some cases unit tests are the absolute wrong thing to do. For instance what if you have been given two days to prepare a client demo on which a large contract rests. Unfortunately, a great many people have found that they can exist in the corporate world simply by complaining about things and never really doing anything. Either that or they don't know what their doing. These are the people who try to enforce rules like 'every commit has to be code reviewed' or 'every single line has to be unit tested.' Usually its at a small, new company where the guy put in charge is still beginner-intermediate level. In these situations there is usually cargo cult behavior going on and a desire to look like experienced devs by making stupid rules for everyone else.