If you are newer to programming or work for companies that don’t do reviews, you may be wondering why code reviews are so critical.
This question is more likely if you already have automated testing or a QA (Quality Assurance) team. Code reviews are necessary as they offer multiple benefits that help improve your code and your team. These benefits include:
Helping reduce bugs and logic errors
Providing an opportunity for training
Spreading knowledge across areas and teams
Revealing new ideas and techniques
Let’s take a closer look at each of these.
Code reviews help reduce bugs and logic errors.
Sometimes the best place to write code for your project is outside it.
This may sound like a lie. How could writing code outside of a project be the best place for the project's code? How can it even help the project at all?
Working within a project, especially a large and complex one, other code can get in the way of what you are writing.
By removing the distraction of unrelated code, you can focus on your task.
When experimenting with designs or figuring out a tricky issue, it's quicker and easier to focus on the smallest amount of code needed. You don't have...
Working with code you’re unclear about is like wading through a swamp. You should attempt to get yourself on solid ground as quickly as possible
– Jon Skeet
One of the most frustrating things about bugs with computer software is you get a bug report, someone is breathing down your neck to get it fixed, customers are upset, and everyone thinks it should be easy to find and fix.
We’re lucky if the problem is precisely where the error says or the user’s bug report has enough details. Often we are stuck having to dig into the code while trying things ourselves to...
As you continue building out Laravel apps, you will notice spots that you need to perform the same queries. If your project is like most projects I've worked on, you will start with just repeating the query code in many places.
This works great until you need to change the query. Because the query is repeated throughout your code, you now need to change it everywhere. And you might forget to change it somewhere 🤦🏻. This is an enormous maintenance headache. I can't even count how many bugs I've encountered (and written myself) from forgetting to update code in multiple places.
I'm like most builders and creators. I believe my work needs to be perfect to put it out there. We all talk about minimum viable products and releasing early and often. But actually doing it is another story.
When I see all the minor mistakes in my work it makes it hard to release. This really only matters to us builders, though. Because we are in the industry and know how things could be better, it's hard to be okay with mistakes or non-perfect solutions.
The ironic thing is users just don't care about it being perfect.
Users don't care that it looks...
I am senior software engineer that focuses primarily on web and mobile applications. I work both as a regular full time employee and a consultant developing apps and websites for clients. This is my personal blog where I write tutorials, tips and tricks, and my opinions on various software languages, technologies and tools.