In this section, we will explore how to configure some basic tools and automatically run checks on the code, with the goal of leveraging part of the repetitive verification checks.
This is an important point: remember that code is for us, people, to understand, so only we can determine what is good or bad code. We should invest time in code reviews, thinking about what good code is, and how readable and understandable it is. When looking at the code written by a peer, you should ask such questions:
- Is this code easy to understand and follow for a fellow programmer?
- Does it speak in terms of the domain of the problem?
- Would a new person joining the team be able to understand it and work ...
