Lately, I’ve noticed that I have less and less free time. That got me thinking of all the tasks on my to-do list and how they fall into two categories: the ones I have to do and the ones I want to do.
Some systems have accumulated so many hacks, workarounds and cruft that improving the codebase has more in common with a Herculean task than anything else. I see two possible ways to go about this task.
A good name can be the difference between explaining what a particular part of code does and confuse you. Names also tell you a lot about the quality of the codebase.