Mobile Design Pattern Gallery, 2nd Edition

Foreword

To name something is to begin to understand it.

My five-year-old son, like many children, enjoys looking at clouds. Recently, he clued into the fact that different kinds of clouds have different names. And so, being of good geek stock, he proceeded to memorize them—cirrus, cumulus, stratus, cirrostratus, cumulonimbus, altostratus, lenticular—all of the ones I knew, and then some. I’d certainly never heard of “cumulus congestus” before.

Now, when he looks at the sky, he can tell me which clouds are which. More than that, he notices more than he did before, and with greater nuance. He has learned to visually discriminate among cloud types based on texture, color, height, movement, and who knows what else. (They’re not always easy to tell apart, of course, but that doesn’t bother him.) He can predict, with some accuracy, which ones might drop rain on us and which won’t.

And in his limited preschooler fashion, he uses his cloud knowledge to analyze the big picture. “Cirrostratus clouds might mean a warm front,” he points out. Or, “Cumulus congestus might turn into cumulonimbus! Then we could get a storm.”

Above all, he enjoys knowing these names. Little kids seem to get a kick out of naming the things they love, whether they’re clouds, dinosaurs, bugs, cars, dolls, or movie characters. Certainly their imaginations aren’t limited by that left-brain knowledge, despite our grown-up romantic biases—my son still sees palaces and ducks and cauliflowers in the clouds, even as he names ...