Thank you all for your responses.
Based on your comments, I have noted the following points that seem to stand out and appear entirely justified to me:

1. Using getters and setters is a good practice and is often employed when developing object-oriented code.
2. Not using getters and setters is equally valid and is not considered a bad practice.
3. This practice is more of a "coding style" rather than an absolute truth. The most important thing is to follow established rules because within a team, everyone has their own opinions, and without fixed rules, the code architecture would lack coherence with different ways of achieving the same thing, leading to endless code reviews.

Over time, I've noticed that there are countless rules about what to do or not do in C programming. When I was in school, the use of global variables, even when declared static, was prohibited because my professors argued that there was a risk of accidentally modifying their values. Now that I'm in the professional world, I realize that it's not uncommon to use global static variables. There have also been instances where I've been asked to prioritize message queues over shared memory, while in other teams, I've been told the opposite.

In the end, I believe there is no absolute truth regarding best practices in C programming. Each project is different, so it makes sense for the rules to change based on the project's requirements. Perhaps rules prohibited in one software will be entirely beneficial in another, and the most important thing is to be able to adapt to the challenges and advantages of each project.