legibility
Step-by-step explanation:
People are able to understand what aspects of their programs are and they can learn how to do good programming. Comments are especially useful when translating code for comprehension. This functions also for people who did not write the text, but try to read and understand this. When someone calls their variables stuff like "soup," "pumpkinpie," so he knows what their usage is all about. It is easy to read by offering variable names like "velocity," "average height" and "total score."
This deals for functions / methods as well. In what is done a feature known as getIdFromName is simple.
Not just that, it allows programming activities to determine what is really important. When someone has practiced good programming principles, they will mark constants in ALL CAPS by typing them. So something is a fixed feature, easily observed. Strategies and artifacts are often called like this, with each word capitalized on its first letter and then on its first letter. A name like this with a first major letter typically is given to the grades.
If you are aware of these principles, at least, you may tell what you should be working with because reading code by just how it is called. This wouldn't be the situation and the computing world would be a messy place without programming principles.
It's not all adhering to these, I presume. Most annoyingly, often people don't follow better programming and also don't reflect on its own software, so it takes hours to figure out just what it is.
That is why it is important to have expectations.