How applying concepts from education theory to code reviews can improve knowledge transfer across your engineering teams.
Improving your software development processes through regular code reviews is easier said than done.
Though there are ample merits of good code reviews, a pull request (PR) only ever really receives a passing glance and a thumbs up – or the more traditional, “Looks good to me!”
In cases where teams do rally to perform code reviews, one of two likely scenarios will play out. The first will follow Parkinson’s Law of Triviality, with developers bikeshedding and nitpicking at (what should be) minor changes.