Writers of software and writers of documentation practice a shared art: we bestow abstractions with names. We know weve succeeded when our names illuminate concepts, elicit a-ha moments, and empower users to put our product to work. We know we've failed when the names we've chosen confuse, frustrate, misguide, or offend. Naming things well matters. Too often, though, good names are hard to come by, and bad names are hard to change.