10 things I learned after doing 2400 code reviews in 6 months
Patroklos Papapetrou is a chief software architect, addicted to software quality and an agile team leader with almost 20 years of experience in software development. He believes and invests in people and team spirit seeking quality excellence. He’s one of the authors of SonarQube in action book and he recently founded his own consulting and training company. He’s an occasional speaker giving talks about clean code, code quality, software gardening and other cool stuff he wants to share with fellow developers
I work remotely as part of a distributed company and I have the chance in my current job to review almost all pull requests submitted by several developers. During the last six months I learned a lot both as a reviewer and a developer and this what I want to share!
I will discuss about things I learned to improve myself as a reviewer, and I will present automation and tools integration ideas to facilitate the code review process. I will also explain the most common coding mistakes I have noticed, developer patterns , human habits and how all this made me a not only a better code reviewer but also a better developer. It’s going to be a fun talk with some real code review examples that I hope people will enjoy. After all code reviews should be fun and not a necessary evil.