smells-and-heuristics-tests.markdown

+###### [Home](home) / [Digitec Coding Practices](coding-practices) / [Global Coding Standards](global-coding-standards) / Smells and Heuristics - Tests
+
+---
+
+
+[:arrow_left: Names](smells-and-heuristics-names) | [Conclusion :arrow_right: ](smells-and-heuristics-conclusion)
+
+# Tests
+
+
+#### N1: Choose Descriptive Names
+
+Don't be too quick to choose a name. Make sure the name is descriptive. Remember that meanings tend to drift as software evolves, so frequently reevaluate the appropriateness of the names you choose.
+
+This is not just a "feel-good" recommendation. Names in software are 90 percent of what make software readable. You need to take the time to choose them wisely and keep them relevant. Names are too important to treat carelessly.
+
+Consider the code below. What does it do? If I show you the code with well-chosen names, it will make perfect sense to you, but like this it's just a hodge-podge of symbols and magic numbers.
+
+
+
+
+---
+
+[:arrow_left: Names](smells-and-heuristics-names) | [Conclusion :arrow_right: ](smells-and-heuristics-conclusion)
\ No newline at end of file