Do yourself a favor: slow down & put some thought into naming things. Future-you will reap the benefits. Do yourself a bigger favor: Go back and re-read all 4

Do yourself a favor: slow down & put some thought into naming things. Future-you will reap the benefits. Do yourself a bigger favor: Go back and re-read all 4 paragraphs in the section "Naming Things". This is solid gold and one of the most overlooked aspects of building good code. I have slowed down many times and named things (variables, function names, labels, etc.) exactly the way I wanted. Then came back 2 days later, unable to understand what I had just written. Because the names were still not good enough. Naming things can be an iterative process. And it's not a waste of time. Coming up with just the right name is hard, but it really makes you think about what you're doing, how you're doing it, and why. These are the things we should be spending time on. This reminds me of Harry Beckwith, the marketing consultant from the east coast who called on clients in California. On the plane trip home, he worked on coming up with just the right name for his client. Invariably, he came up with the perfect name over Lake Tahoe. The next day, he reviewed this name and realized that it was a good first try, but still not right. He came up with the term "Lake Tahoe name" to remind himself that he still wasn't done. Don't leave Lake Tahoe names in your code. You're not done yet. [Harry Beckwith reference: http://search.barnesandnoble.com/What-Clients-Love/Harry-Beckwith/e/9780446527552 http://search.barnesandnoble.com/What-Clients-Love/Harry-Bec...]