It’s Not You, It’s Me: Improving the Quality of Deliverables Through an Effective Code Review

Software development is not getting simpler. Nowadays any application seems that needs to be cloud-based, event-driven, and provide high levels of scalability and fault-tolerant. The consequence of this scenario is that the code review stage of your development lifecycle becomes increasingly more challenging due to the broad knowledge scope and more important to catch errors. Unfortunately it is easy to lose track of what is important when submitting and reviewing code. I will discuss some of the common pitfalls I have encountered and where to focus to improve your review process. <h1>It is not a pull request, it is a peer-review</h1> Version control software (<a href="https://en.wikipedia.org/wiki/Version_control" rel="noopener ugc nofollow" target="_blank">VCS</a>) is almost omnipresent in our industry, but some may not even recognize it due to the popularity of git, which almost became its synonym. Github popularized the term pull request, where you have a way to inform other developers that you created a new branch, corresponding to a new version of your source code. Others can then see what are the differences and comment on them, eventually approving or declining the merge of your changes into the mainline. The theory behind this is that by giving chance to others to look at your proposed changes, they can spot errors you missed before they go into production. <a href="https://betterprogramming.pub/its-not-you-it-s-me-improving-the-quality-of-your-deliverables-through-an-effective-review-df0149b8166f">Website</a>