Recent Features
| |||||||||||||
Humphrey: On Code ReviewHumphrey: On Code ReviewPosted Jan 21, 2013 23:53 UTC (Mon) by marcH (subscriber, #57642)In reply to: Humphrey: On Code Review by marduk Parent article: Humphrey: On Code Review
Enforcing any process or tool is pointless as long as the majority fails to understand the value of it. A process should only (try to) organize things people genuinely want to put some effort in.
Finding time for code reviews is hard enough when people agree they are useful; no surprise they're not done properly when people miss the point.
If you work in a company that does not even understand the value of code reviews then you should probably try to find a better job where quality, teamwork and personal development actually matter. Run even faster if a rigid process forces code reviews to happen anyway.
(Log in to post comments)
Humphrey: On Code Review Posted Jan 22, 2013 2:02 UTC (Tue) by rgmoore (subscriber, #75) [Link] Enforcing any process or tool is pointless as long as the majority fails to understand the value of it. A process should only (try to) organize things people genuinely want to put some effort in. I'm not sure if I completely agree. Sometimes people have to experience something to appreciate the benefits, so enforcing it as a matter of policy has to come before general acceptance. That is admittedly a high risk approach. It will only work if the people implementing the new policy understand the benefits and do a good job of enforcing it in a way that will eventually make the benefits clear to everyone else. Simply trying to enforce an idea, even a good idea, without a clear understanding of the way it's supposed to work is asking for failure.
|
|||||||||||||