So, what exactly qualifies as a nit? Software quality is as much about code readability and understandability as it is about delivering bug-free solutions. Code readability is essential to making the solution future-proof because, sooner or later, a colleague will have to modify your code to meet new or revised requirements. Numerous factors contribute to code readability.  

Let’s explore a few common violations:

• declaring variables without using them;
• failing to use the return value of a declared function;
• using nonsensical or confusing variable names within a given context; and
• failing to use keywords from a new language version that make the code safer.

Unfortunately, the subject of compiler warnings is largely neglected in most education programs for professional software developers. However, at OMP, we recognize its importance and prioritize it accordingly. To give you an idea: the C++ compilers we use contain extended lists of possible warnings, and we regularly go through them to decide which ones to activate and which to deactivate. We also review these warnings whenever we upgrade a compiler.

We consider this an act of good housekeeping. While some of our newcomers find it a little disturbing to get so many warnings in the beginning, they soon find that it helps them to deliver better code and avoid unnecessary nitpicking by their colleagues. In the end, compiler warnings become an invaluable resource and a trusted ally.