My takeaway from this story is slightly different - we need better tools. Especially better refactoring tools. IMO, using larger names is only a symptom of the

My takeaway from this story is slightly different - we need better tools. Especially better refactoring tools. IMO, using larger names is only a symptom of the main problem - the fact that we're still using plain old text search and replace. We're relying on it way too much. And its not a very precise, very fine tool. Code organization solutions don't seem to fully solve this either. 1) Whoops, we need to change this style everywhere: "Lets just use classes, then when we want to change the style of our buttons we can change it at a single place (the class)" 2) Whoops, we need to change the class name "Lets just use templates containing the class name, then when we want to change the class name we simply change it in the template" 3) Whoops, we need to change the template... and so on. I think there is a clear need for better code maintenance tools, for all languages. Especially the search (and replace) problem. Perhaps search tools that are based on the language parsers would help.