Code reviews are an important software engineering practice. The main benefits of code reviews are increased software quality and that knowledge about the code base is shared among team members.
Code reviews can either be your team’s superpower, or an expensive bottleneck. In my code review workshops, I let teams in on the secrets to fast and effective code reviews. In those hands-on and interactive workshops, I share all my knowledge from over ten years of researching software engineering practices and working with product teams such as Windows, Office, Visual Studio and Exchange to boost their engineering habits.
Code review experience
I have researched and improved code reviewing techniques for several years. I worked at the Tools for Software Engineering team at Microsoft. There, my main focus was to analyse and improve the tools and practices for the internal engineering teams. Microsoft’s internal engineering comprises several ten thousand people that used the code review tooling by our team. The analysis I performed and the changes and improvements were driven by data analysis and empirical studies.
Code review tooling
I worked on the team that was responsible for the internal code review tool, called CodeFlow. There, I helped build and deploy a code review analytics platform. But mainly, I helped teams get the most out of their code reviewing practices by distilling code review best practices and code review anti-patterns. For that, I analyze thousands of code reviews and interviewed and surveyed thousands of engineers. Those insights drove the development and enhancement of the code review tool as well as the code review processes.
I was very fortunate to work with some of the main experts on code reviews and empirical software engineering. Chris Bird, who is a stand-out expert when it comes to code reviewing, is also a wonderful mentor. Another wonderful person I work with is Margareth Anne Storey. She is an eminent authority when it comes to helping people to explore, understand, and share complex information and knowledge.
Finally, I want to give my gratitude to my Jacek Czerwonka for his mentorship. He truly knows how to position research in an industrial setting in a way that drives innovation.