Four NOs of a Serious Code Reviewer от Yegor Bugayenko

Докладчик Yegor Bugayenko
Four NOs of a Serious Code Reviewer
  • talk
  • 60
  • engineering

Code reviews (a.k.a. peer reviews) must be a mandatory practice for every serious software development team. Some do pre-merge code reviews, protecting their master/development branch from accidental mistakes. Others do post-merge regular reviews to discover bugs and inconsistencies after they are introduced by their authors. Some even do both, reviewing before merges and regularly after. However, it's not so simple to do them right. I would even say it's very easy and comfortable to do them wrong. Most code reviews and reviewers I've seen make similar mistakes. That's why I decided to summarize the four basic principles of a good reviewer as I see them.


I've never presented this talk anywhere, but wrote a blog post about this subject:

Constraints and Class Arrangement
Session History
Обновлен 24 нояб., 08:27