Tue 06 Jul 2021

How disable comments make static analysis tools worse

Seeing disable comments in code has always made me feel uneasy. Whenever I encounter one, a bunch of questions pop into my head. What kind of error did the static analysis tool report? Was it something that didn’t apply? Why did the developer choose to ignore it? Were they being lazy? Did they understand the error? What is the risk of keeping it ignored? If it’s being ignored, why is the rule even enforced?

Source: How disable comments make static analysis tools worse, an article by Jeroen Engels.

git update: the odyssey for a sensible git pull

While git pull kind of works, over the years a slew of people have pointed out many flaws, and proposed several fixes. Some have even suggested that newcomers should be discouraged from using the command (as they often use it wrongly), and others to remove it entirely.

I spent several days digging through the entire history of the Git mailing list in order to document all the discussions related to git pull and its default mode. It’s a long story, so grab some coffee (a whole pot of it).

Source: git update: the odyssey for a sensible git pull, an article by Felipe Contreras.

Well Written Pull Requests

Writing better pull requests is one of the best improvements you can make as a software engineer. Well written pull requests create a smoother review process, help get your PRs merged faster and increase the level of trust and respect you earn from your team. This guide will present several easy to implement ideas that will help you write better pull requests.

Source: Well Written Pull Requests, an article by Matt McCormick.