Code Reviews in Tech: The Missing Guide

Why a guide for code reviews?

Have you ever felt daunted by your code being reviewed? Have you ever felt a lack of confidence in reviewing other people’s code? Has your team ever struggled to get code reviewed in time? If yes, you are not alone. Those are problems we software engineers are facing every day in every company, in big FAANG companies, or in tiny startups.

Code review is a software quality assurance process in which source code is analyzed manually by fellow engineers. Code reviews are something we do every day, however, they are also the most likely processes that hurt morale and relationships and break teams.

How this guide will help you

For many years, I took note of the problems and suggested solutions to teams. In addition, I did many experiments within teams to improve the processes and best practices.

This tiny book outlines intentions and etiquettes that have been tested in my whole engineering career, along with examples. By the time you have finished reading the book, I hope you feel better equipped to meet real-life situations with code reviews at work and take action to solve them.

Contents

• Introduction

• Goals of Code Reviews

• Intentions

• Etiquettes

• Processes

About Author

Grace Huang is an ex-founder with a successful exit. She writes about startups, entrepreneurship, investing, software and hardware engineering, manufacturing, and lifelong learning. 

Check her Linkedin profile (https://www.linkedin.com/in/lghuang/) to learn more. Feel free to ask questions or drop a note on Twitter (https://twitter.com/imgracehuang).

FAQ

What's the refund policy?

If what you see is not what you expected, just reply to the download email within 30 days, and you'll get a full refund. No questions asked.

Can I preview this book?

Yes! You can find a page of the book in the photos above, so you can get a taste of it.