Code reviews is feedback, but if your friend or partner or colleague would ask you for feedback on some of their work, you would probably not send them a list of 50 things they did wrong. Yet in code reviews, this is perfectly normal.
Could we do better code reviews by just changing the way we give and take feedback? I'll share 10 tips that I try to follow to turn code reviews from a boring exercise or something you dread to a much more pleasant experience.
Tess is a developer/data scientist working at Microsoft. Over the past 20 years she has changed the way we do .net debugging, developed a large number of mobile apps. As of a couple of years ago she moved into the world of data science and machine learning working with a lot of the largest companies in Europe and beyond on really tough ML problems.
She has has spoken at lots and lots of conferences around the world on a wide variety of topics including deep .net debugging, UX, web development and Machine Learning. You can also find her on twitter at @TessFerrandez
