If “code review” means the 2 seconds you glance at a PR before you click “merge”, there is likely some room for improvement. But experienced reviewers too might benefit from some new angles on the subject. Even if you don’t usually work with a review system, these pointers can improve your code. In this talk, i discuss some very simple pointers that will make a code review extra useful, illustrated with practical examples. “Useful for what”, you might ask, well, we’ll also discuss that.
About Kees Hink
I’m a Python web developer. After starting out with the Plone CMS (came for the project, stayed for the community) in 2008 at Goldmund, Wyldebeast and Wunderliebe, i’ve spent the last eight years with Four Digits in Arnhem, working mostly with Django.
