Software component names should be whimsical and cryptic
The author seems to be talking about names for two totally different things, lumping them under the term "component."<p>Whimsical project name? No problem.<p>Whimsical type name within a project? Really bad idea.<p>Whimsical variable name? Don't even think about it.<p>The concept the author is missing is "convention." Whimsical project names fall within a well-understood and used convention. The convention for type and variable names, however, is set by the standard library and these are almost always descriptive. Their purpose is, in the best case, to reinforce a ubiquitous language drawn from the domain.