Comments are, to put it mildly, a controversial topic.
There are two very strong opinions in software development, both extremely popular and widespread. The first one states that comments are evil, and you should not use them under any circumstance. The main argument is that instead of using comments, you
Arguments play a very important role in the readability of a function. When implemented properly, they show intent and provide information about the function's behavior. This is one of the reasons why investing time in engineering good arguments can help to improve the quality of your code. Let's see how
The interface segregation principle (ISP) is concerned with the way clients access the functionality developed in another class. It states that clients should not be forced to depend on functionality they don't use.
Following this principle has several upsides. On one hand, it protects your objects from depending on things
In 1987, while delivering a keynote on data abstractions and hierarchies, Barbara Liskov introduced the idea that would eventually become the Liskov substitution principle. The following is a modern (and very formal) description of the principle:
Let Φ(x) be a property provable about objects x of type T. Then
Code reviews are one of those things that you either really love or really hate.
When done well, they can dramatically increase the quality of your code and teach you lots of important practices. Poorly done reviews, on the other hand, can make you dread every time you try to