Earlier quoted context omitted.
Conversely, We write code once, but read it many times, so longer names seems like a poor efficiency choice.
> We write code once, but read it many times, so longer names seems like a poor efficiency choice. How can you tell what's the type of an ambiguous name if you have no indication of which namespaces are within scope? I mean, think about it. If your concern is readability, doesn't this mean it's important to know what code you're looking at?
Shorter files, shorter names. You can read the namespace once at the top instead of 50 times throughout
This drastically reduces the amount of time it takes to read code.