Even with all the code review tools out there, not every team or company reviews their code before pushing it live.

Code reviews are crucial to ensure code quality and prevent stressful urgent bug fixes. Effective code reviews will make applications easier to maintain, reduce the number of bugs, and spread knowledge among team members. It is important to make sure reviews improve code quality while keeping team morale in mind. Without an effective code review process, you may have to deal with these problems:

• Fixing bugs late at night or on weekends
• Have trouble maintaining or making changes to your project's code
• Have trouble understanding other developer's code
• Your team and project do not improve over time

You Need Code Reviews helps you learn everything you need to avoid those problems. The book covers everything from introducing reviews to teams that haven't done them before to how to perform and respond to peer reviews. You will learn how to be empathetic and deal with the human side of code to make reviews a process your team wants to be part of. Whether your team already does code reviews or is looking to improve the process, you will find useful advice within You Need Code Reviews.

Table Of Content

This is a listing of chapters, sections, and subsections. Leanpub does not provide a way to provide the table of contents in a nested list.

1. Preface
2. Introduction
3. What are code reviews?
4. Why are code reviews necessary?
5. What if we already do automated testing or have QA (Quality Assurance)?
6. Who should do reviews?
7. Introducing Code Review to your Team
8. Convincing your boss
9. Making your team care about reviews
10. What can go wrong with reviews?
11. Establishing standards
12. How to perform a useful review
13. Finding your review style
14. How to word comments
15. What are you looking for in a review?
16. Is the logic correct? Is it doing the right thing?
17. Are there bugs in the code?
18. Is input validated? Are edge cases handled?
19. Are errors handled?
20. Are there any security issues?
21. Are there any performance issues?
22. Are standards and best practices followed?
23. Are design patterns used correctly?
24. Is the code easy to understand? Will it be easy to maintain?
25. How to respond to a review?
26. Responding to comments
27. Making changes
28. I disagree...
29. Using automated tools to review code
30. Linters, style checks, and static code analyzers
31. Automated Tests
32. Continuous Integration Tools
33. Conclusion
34. About the author

This book is currently an early work in progress with an estimated release date of late 2022.