I am dev manager, managing 8 developers. I am facing a problem that the code review becomes more and more a formality even though we all know the code review is important. We do have code review process but when people don't want to do it they can find the way to circumvent it.
I hate to be bossy around, telling my guys "please let's review this together or please take it seriously" all the time. So what are some specific procedures I can take to let them do code review more seriously? Currently I only have two: (a) assign a different guy to fix the bug caused by someone else's code. To fix it he/she has to read and understand others' code first. (b) do code review with them from time to time. But doing that has its own problem too.
I suspect people may suggest me to look into the root cause, find out why they don't want to do it wholeheartedly and fix that instead. But for this specific question I want to focus on what methods I can use (because discussing the root cause may sidetrack my question)
A comment said "The fact you expect strangers from the internet to give you a better reply than your team...". That is NOT what I expect but I guess it said a doubt people may have so I am trying to clarify that: I would be surprised if people tell me that "NO, that never happens in my team, I don't have this problem, or my guys love to do code review". So I was asking some general advices you may have tried to deal with that.
Another comments said "If they knew code review was important they'd be doing it." My counter-argument is even simpler, I know a healthy diet is important but I still indulge myself in junk food! I don't want to delve in the "root causes", which can be another question. Here I simply ask what methods have you ever tried, and if that evolves the root cause in your case I am all ears but if you say "I don't have this problem, my guys just love code review" then this question is not for you.
--- update ----
I search the SE site and find at least two questions were somewhat related to mine,