Great analysis on code review thanks!
Only thing I would add is if you can with a bit of dev-ops automatically run linting, tests AND build a QA env with test/demo datga and push the temporary URL and test results back to the code review platform, it means developers don’t waste time checking it all out locally, they can view the code, see it working, know it passed all the tests.
Removing the subtle barriers/pain points as to why people don’t code review (or just give a thumbs up with no checking) is what to focus on.
After that reducing time for all of the above to happen. Feedback in < 5 mins that tests all passed, QA env is built etc when that gets towards 30mins QA just stops happening as things are being failed by the system but the developer has moved on to another task.
