My 7-Step Cheat Sheet for Choosing Good Names

aming things can be considered a difficult task because the names chosen for variables, classes, functions, and other elements of the code need to be meaningful, accurate, and easy to understand. In order to keep the codebase clean and maintainable, it’s vital to have good, consistent, naming patterns. This can be challenging because, as the system grows, it can be difficult to ensure that new names do not conflict with existing names. In this article, we’ll go through a checklist of considerations when selecting names for our code. The list contains both my personal insights and ideas from established authors such as Uncle Bob and Eric Evans. <h2>1. Intent & Measuring Unit</h2> The name chosen should clearly convey the intended purpose and function of the element, as well as any relevant units of measurement, if applicable. This will help to make the code more understandable and maintainable for both the person writing the code and anyone else who may need to read or modify it in the future. On the other hand, the use of overly short variable names or unreliable abbreviations can greatly impede the readability and comprehension of the code for all parties involved: <a href="https://levelup.gitconnected.com/my-7-step-cheat-sheet-for-choosing-good-names-6137bcdbb2f4">Click Here</a>