The move from C/AL to AL brought many new development paradigms to our industry. Source Control, Extensions, Cloud-first approach, just to name a few. One of them is also the Code Review which is a huge addition to code quality. The change happened a few years ago and partners adopted many different approaches to Code Reviews. But Code Reviews aren’t new, many mature industries have been using them for decades, and now AI is supposed to help with that as well. I believe now is a good time to stop for a moment, review our code review processes, and talk about best practices. How to ensure code reviews are not overwhelming? What are communication best practices, so the comments are well received? How to prevent “rubber stamping” pull requests? What tools can make them more manageable? How can the GitHub Copilot help with all of that? Join the session to see how we can take the effectiveness of code reviews to another level.