DescriptivelyNamedFoo = new DescriptivelyNamedFoo();
In a language with even limited type inference, e.g. C#, this repetition is gone.I simply don't accept your priors.
Or the situation with the file names, as someone else mentioned at more length.
I've come across that rule (Gerrand's rule?) which sums up my personal experience pretty well:
> The greater the distance between a name's declaration and its uses, the longer the name should be.
I often notice that I can remove a comment line after renaming a few identifiers in the code below it, because the code starts to read self-explanatory enough.
I've found that people who believe too much in the ability for identifiers to tell the story of the code factor too much stuff into separate non-reused functions. The result being that you can't take the name at face value; you need to push the current context onto your mental stack, drill into the identifier being called, and if necessary continue drilling, until the unstated side-effects and extra bits and bobs that always accrete in continuously maintained code become clear. This code is ironically harder to read than inlined code.
Careful with that. I'm of the mind that the code author is incapable of describing how readable any codebase is. It's too easy to mistake your innate understanding of your own creation for readability.
You only need to type unsafe_file_name_from_user once. After that, even the simplest, language-agnostics autocompletion of identifiers from the current buffer goes a.long way. A proper IDE makes it even simpler.