Naming conventions can help you understand the system. Since most application source code is typically developed in several components by multiple developers over time, the probability is that the same item will be called different things by different developers unless you impose and enforce some rules. Now think about reading a story where the names of the characters change from one chapter to the next. But if naming conventions are followed uniformly, the code vocabulary will be spelled consistently, and it will be understandable from one developer to the next. This helps developers who need to understand someone else's work in order to add enhancements or fix problems.
Consistent names give the story coherence.
Now, the developer who wrote this was probably quite pleased with the economy of characters permitted by using an array of customer-record data fields and message texts. Obviously, names make a difference. The extra keystrokes needed to spell things out take less time than the extra time to decode inscrutable abbreviations. Change Naming conventions can help you make changes more efficiently and thoroughly. If each data element has the same name regardless of the code module where it is used, you can automatically locate all references throughout all components and make global changes.