Email the Author
You can use this page to email Kevin Hicks about You Need Code Reviews.
About the Book
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.
- Preface
- Introduction
- What are code reviews?
- Why are code reviews necessary?
- What if we already do automated testing or have QA (Quality Assurance)?
- Who should do reviews?
- Introducing Code Review to your Team
- Convincing your boss
- Making your team care about reviews
- What can go wrong with reviews?
- Establishing standards
- How to perform a useful review
- Finding your review style
- How to word comments
- What are you looking for in a review?
- Is the logic correct? Is it doing the right thing?
- Are there bugs in the code?
- Is input validated? Are edge cases handled?
- Are errors handled?
- Are there any security issues?
- Are there any performance issues?
- Are standards and best practices followed?
- Are design patterns used correctly?
- Is the code easy to understand? Will it be easy to maintain?
- How to respond to a review?
- Responding to comments
- Making changes
- I disagree...
- Using automated tools to review code
- Linters, style checks, and static code analyzers
- Automated Tests
- Continuous Integration Tools
- Conclusion
- About the author
This book is currently an early work in progress with an estimated release date of late 2022.
About the Author
Kevin Hicks is a senior software engineer with over ten years of experience developing websites and web applications. Now focusing on mobile and web application development, he works as both a regular full-time employee and a consultant developing sites and applications for a large e-commerce company and clients. Kevin has worked on anything from small mobile games to large e-commerce sites to SaaS (Software as a Service) applications for startups and enterprise clients. Now he is looking to help other people by spreading the knowledge and experience he has gained over the previous years so they can avoid the many mistakes he has made.