<img style="border: none; background:none; width: 0; height: 0;" src="https://welovepg.polymail.io/v2/z/a/NTczNGI1NWMyZDc4/k8dgnfqb7aZxsfA6pf9i--m5CHGPQXFyVT0-LL0vcReg2RBOl7Jd6RLch7SBOeLb4Froz45sJtkm_a3g_zNAZ8-5KPG_ljiiI_AG_42J_PRd7wxyhw7ykFjrHkoC24FfuGflaF_0NJEYjUmN558=.png" alt="" width="0px" height="0px" border="0" />Hi Lrug,<div><br></div><div>Thanks for the opportunity to talk about Code Review at Monday’s meeting. If you want to relive the glory of watching it, I’ve just noticed that the video is online[1] and I’ve also uploaded the slides to speakerdeck[2].</div><div><br></div><div>If anyone does adopt any of the approaches I talked about - particularly around making the motivation explicit and then checking to see if you get those benefits - then I’d love to hear if it works for you. Please get in touch.</div><div><br></div><div>Thanks,</div><div>John</div><div><br></div><div>[1] https://skillsmatter.com/skillscasts/8085-the-art-of-code-review</div><div>[2] https://speakerdeck.com/jcinnamond/the-art-of-code-review<br><br><div id="psignature"><div><br></div><div style="font-size:10px; color: #7E8F9F;"></div></div></div>