Skip to main content
main-content
Top

About this book

The ideal code review process differs from organization to organization, but the needs all boil down to the same foundational factors. A software development team cannot properly grow if its code reviews are not consistent, straightforward, and aspire to hit several company goals at once, such as security, performance, longevity, and more. Implementing Effective Code Reviews is the manual your team has been seeking.

Author Giuliana Carullo uses her expert background to guide you through the basics of building and maintaining clean code, and she is known for distilling complex concepts into entertaining and easy-to-grasp lessons. Healthy code requires incremental improvements, and knowing how to execute this is essential for conducting effective reviews on your team. While complex and fancy code can be interesting to work with, it will not always achieve business goals or solve urgent problems. Good coding practices are at the heart of a high-performing team, and Carullo instills these core values in a simple, straight-forward way in Implementing Effective Code Reviews.

Whether you are a passionate programmer looking to go the extra mile at the office, or an experienced software engineer seeking a guide to how to improve your leadership and code review process, this book covers it all. With each chapter wrapped up in a handy checklist of crucial takeaways, Carullo has created an essential handbook for coders everywhere. There are a lot of myths that dominate the programming landscape, and Implementing Effective Code Reviews grounds the process and gets to the heart of the matter.

What You Will LearnUnderstand how to work with your team to implement effective code reviewsMaster good programming practices that will build healthy codeDiscover how you should tackle different complex areas during code review like, security and performance

Who This Book Is For

Passionate programmers willing to go the extra mile to be better at their jobs, new programmers looking to strengthen their programming skills, and experienced software engineers looking for a quick guide on how to review code

Table of Contents

Frontmatter

Chapter 1. The Art of Programming

Abstract
Software engineering is an old art.
Giuliana Carullo

Chapter 2. Code Structure

Abstract
In the early days of programming, being able to create Turing-complete algorithms was so innovative that people were not that much concerned with structured programming.
Giuliana Carullo

Chapter 3. Data Structures

Abstract
Data structures are often not analyzed as carefully as software architecture, but they definitely have their spot on the stage. Choosing them correctly has a lot of benefits, including
Giuliana Carullo

Chapter 4. Design Smells

Abstract
Not sure if Doyle was thinking about code smells as a crime, but in my opinion it might!
Giuliana Carullo

Chapter 5. Software Architectures

Abstract
In Chapter 2, we started taking a look at some of the possible dos and don'ts around the design phase and introduced why software architectures are important. However, this aspect requires a deeper look. In particular, a strong emphasis on using design patterns properly is needed when dealing with architectures.
Giuliana Carullo

Chapter 6. From Scratch

Abstract
Now that you know what to look for during a review, let’s talk about what to do the moment you start reviewing the code, the architecture, and, equally important, the overall design and understanding of the problem. Looking at the problem and its high-level requirements is important both before starting to write any code and during development time to ensure the code is scaling and growing in the direction it is meant to.
Giuliana Carullo

Chapter 7. Naming and Formatting Conventions

Abstract
In theory, declaring a variable is a child’s play: i_am_a_var = 10
Giuliana Carullo

Chapter 8. Comments

Abstract
I know you probably mumbled several times while coding because you have been asked to write or to update comments. You might think, is it not enough to have some sort of comments inside my code? They must be coherent as well? Mumble, mumble. The answer is yes, we do. Think about it as doing a favor for your future self. Months from now, you may need to revisit the code you wrote today. It might be crystal clear to you right now, but will you remember why you used variable XYZ a week from now? Probably. But how about a few months from now? Unlikely.
Giuliana Carullo

Chapter 9. Concurrency, Parallelism, and Performances

Abstract
Let's be clear: concurrency and parallelism are not exactly the same thing.
Giuliana Carullo

Chapter 10. Security

Abstract
First things first:
Giuliana Carullo

Chapter 11. Code Reviews

Abstract
We covered so far a fairly large spectrum of good practices and checks to perform to ensure quality of our software.
Giuliana Carullo

Backmatter

Additional information

Premium Partner

    Image Credits