An Initial Thought

Just a brief consideration of initials...

It seems obvious that parents need to at least pay some mind to the initials their child is going to end up with. Although unfortunate initials can be embarrassing, they are certainly not insurmountable. In other words, initials should not make or break a name, in my opinion. This is especially true for a baby girl, who likely will get married and change her initials anyway. Still, when it's avoidable, parents can do their kids a favor and thoughtfully provide name-orders that do not spell/represent something offensive.

"Good" Initials
Most people are fairly indifferent to their initials, in my experience. This is probably a good thing. On occasion though, I'll meet someone who loves their initials. For example, I grew up with a boy named "Andrew Benjamin C." He was thrilled to be an "ABC." Good initials do not elude to anything too specific; they are mildly amusing or clever without adding to the significance of the name itself. An exception to this is if the parents intentionally choose initials with meaning, such as naming a daughter "Sierra Alexandra Moore" after dear old great uncle Sam.

"Bad" Initials
Obviously, there are combinations of names that really should not be combined if possible. Any set of names that spell out particular three letter words, for instance, are bad ideas. Common abbreviations can be bad ideas too, like "SOS" or "TAX." With initials, the goal is not so much to come up with initials that make a child happy as much as to avoid initials that make them cringe. Much of this is personal preference; add some common sense and you're good to go!

Quirky Names with Normal Nicknames

Generally, parents choose a "normal" name and a unique nickname for their kids (if they're going the nickname route), as opposed to the other way around. For instance, "James" may be called "Jamie," or "JJ," and "Margaret" may be "Greta" or "Marti." However, an interesting twist on nicknaming is to select a more unusual first name and have a typical nickname. Some examples":

Boys:
- "Hal"- short for "Hallelujah"
- "Zeke"- short for "Ezekiel"
- "Mel"- short for "Melchizedek"

Girls:
- "Rhoda"- short for "Rhododendron"
- "Zoe"- short for "Arizona" (I actually know one!)
- "Maggie"- short for "Magdalena"

First/Last Considerations

It seems obvious that parents must pay attention to their last name before deciding on a first name for their kids, but to what extent should a surname make a difference?

Certainly it's important to avoid accidental rhyming names, like "John Swan." This goes for potential nicknames as well, like "Richard Fitch," who could very well end up a "Rich Fitch."

Less obvious than rhymes are run-on consonants, and even run-on vowels. For example, I cannot name a child a name that ends with "B," like "Abe" or "Gabe," since the ending "b" sounds runs in to the beginning "b" sound of our last name and gets lost. This means, of course, that the nice-sounding "Abraham" and "Gabriel" are not good possibilities for us. A friend of mine as a brother named "Bryant Todd." One of those poor "ts" gets completely lost! If your last name begins with a vowel, like "O'Brien," you'd be better off avoiding first names that end with a long "o" sound, like "Milo" and "Cairo."

Along with ending sounds, it's wise to consider syllables. I don't really believe that there are any fast rules for syllables (such as, a 1-syllable last name needs a 2-syllable first name)- there are always exceptions that work. Take my 2-syllable last name, for instance: my husband, myself, and my sister-in-law all share the name. One of us has a 1-syllable first, one has a 2-syllable first, and one has a 3-syllable first. They all work fine. Or what about a 1-syllable last name, like "Fox?" It could be argued that such a name should never be paired with a 1-syllable first name (Bob Fox), for example, but many of them are perfectly okay, like "Meg Fox" and "Sam Fox." "Blake Fox" doesn't work, though. So, pay no heed to rules, but try each name combination out- some will work, so just won't sound right. I like the name "Reuben," but it sounds wrong with "Bowen." It has more to do with the ending syllable sounds on both names, but clearly it doesn't have the right ring. Another 2-syllable Old Testament name, "Asher," sounds fine though. It's necessary to note not just the ending of the first name with the beginning of the last, but also the ending of the first with the ending of the last. In the "Reuben" example, "en" and "en" at the end of each does not sound right. Also, similar consonants may be a problem, like in "Violet Schmidt" and "Elena Mirna." Although, "Violet White" and "Elena Dinah" are not so awkward.

To summarize, don't be afraid to play around with any "rules" regarding first and last name combos, but don't throw all caution to the wind either. Try your first name (and any likely nicknames) out a few times, and run it by a trusted, unbiased friend if you dare.

T!

The letter is "t" and the gender is guys!
Here are my favorite masculine "t" names of the moment:

- Tobias (I love "Toby" for a nickname, even if it is a "dog" name! And "Tobias" is so distinguished!)
- Tate (Uncommon but not weird, simple and strong)
- Thatcher (Going along with the surname trend...)
- Thaddeus (Both "Tad" and "Thad" are nice nicknames)
- Trace (One of our favorite "Louis L'Amour-esque" names)
- Tanian (Short from "Dartanian-" I'd never be likely to use it myself, but I remember a baseball player named "Tanian" after the muskateer, and he totally pulled it off. It's been dear to me ever since.)

I'm probably forgetting some..."t" names tend to be more unusual, unless you stick with something really common like "Thomas." What are your favorite masculine "t" names?

"K"

First off, my sister was gracious enough to comment on my post Premeditated Naming, so if you're interested in hearing how she ended up choosing a name, check out the comments.

Today: the gender is female and the letter is K. And C. and Q. Really anything that makes a "k" sound. Here are a few of my favorite "k" names for girls:

- Cora/Coral and many of its variations (I know a "Corabelle" and a "Coralee" and think they're so lovely)
- Kate (a true classic)
- Quinn (unique but simple and feminine)
- Kayla/Kaylee (they're too common for today, but maybe in a decade or two...they're such sweet names)
- Callie (I just love this name, and I really can't put my reasoning into words. It's just a terrific name!)
- Kendra (I've gotten flak for liking this name, which some classify as either "gangster" or "loose," but I stand by my longtime love of the name anyway )

I favor well-established "k" names, especially since there are so many made up ones these days. What are some of your favorite female "k" names?

Rainy Day Names

It is monsooning here in Flagstaff, and what better way to spend a rainy, thundery afternoon than musing about weather names?

Since I am a HUGE fan of rain in general, perhaps it is no surprise that I love the name "Raine." Now, I know that I am totally breaking one of my rules by adding an "e" to the end of the name, but I really think it makes it seem more complete, and less forecasty. I also like "Rainey;" it's sort of like an alternative to "Laney," which I also like, by the way. "Raine" makes a delightful middle name, if you or your husband are not quite enough committed to it to use it for a first name. "Zinnia Raine" is one of my favorite girl names (it's hippie enough for Flagstaff or Seattle), but since the spousey isn't a fan, one of you can use it! Zinnias are big, gorgeous, poofy flowers, by the way.

Other nice weather names? Well, "Sunny" is a little dated, though it's cheerful and sweet. More modern takes are "Sunshine" and anything with "Sol" in it, like "Solara." "Stormy" and "Gusty" are unusual, but you'd better hope your daughter isn't that tumultuous! "Snow," and it's Spanish equivalent "Nieve" are not too uncommon Blake informed me of a celebrity baby horrifically named "Reignbeau," and I'm sure there are a few little "Lightnings" out there.

Whatever your weather is right now, enjoy your afternoon! Happy naming!

On Place Names

I like the idea of naming a child after a place of significance. This is an area for particular care, however...

Blake and I spent part of our first date sitting on a bench in West Seattle, enjoying the city skyline at night across Elliott Bay. I've always been fond of the name "Elliott" for a boy, and I like the fact that the name has significance for Blake and me. Plus- two sets of double letters!! But...it's not too likely that little "Elliott" would appreciate the romance behind his name. Maybe it would be different were it a daughter, but it seems cruel to burden a boy with a name with sappy connotations. Plus, "Elliott" has no good male nicknames. And I'm concerned it may go the way of "Ashley," "Lindsey," and "Taylor" and become more of a girl name.

If there's a place that is deeply special to you (and always will be), choosing a name reminiscent of the place can be extremely meaningful. For example, if your beloved grandparents were from Italy, perhaps naming a child "Romey" or "Venice" would be a fond reminder of them. I'd stay away from "Pompeii" though, since more cataclysmic images tend to come to mind than warm thoughts of the motherland. Along with that, it's best to discard places that people tend to make fun of, like "Detroit."

As long as the location in consideration doesn't have romantic associations for the parents that would potentially horrify/humiliate their offspring, and as long as there is SOME significance to the name (I think it's silly to name a kid "Brooklyn" or "Dakota" or "London" just because they're popular options), go for a place name! Some ideas:

- Biblical place names: one of my favorite girl names (I'm hesitant to write it since it will likely be the name of our next daughter) is a Biblical place name. Also, "Belen" (Bethleham in Spanish), Magdalena, Eden, Berea (my friend Aimee chose this lovely, unique name!), and Israel.

- Bodies of water, mountains, and landmarks: I grew up near Lake Meridian, and I always thought "Meridia" would make a nice name. Or I could use "Lillian," since the first lake I ever backpacked to was Lake Lillian. "Rainier" is a name I'll always love, since Mt. Rainier is the quintessential mountain, and is so emblematic of my western Washington roots. Other mountains? McKinley, Shasta, or Baker, perhaps? As far as landmark names go, why not Zion (could be a biblical name or a nod to the national park)?

- City/Country names: Well, my hometown is "Kent." It's sort of in the hood though, not really a place to pay homage to. Common choices include: "Paris," "Kenya," the previously mentioned "London," "Dakota," and "Brooklyn," and "India." Again, I beseech you to only pick a city/country name for your baby if you have some sort of connection to the place, not just because you like the way it sounds. At the same time, you don't want a name that you have too much connection to (naming our next child "Flagstaff" would be pretty ridiculous).

In summary, a place name can be a terrific, unique, and meaningful moniker for your child. Just consider any weird connotations the name may evoke, and analyze your motive in using the name. After all, you want your child to love his name, and hopefully the place it honors as well. 

Musings

The last couple weeks I've been caught up in a name that's a little unusual for me- kind of trendy, kind of gangster, but entirely lovely: "Mahalia." Mahalia is Hebrew (hence the trendiness- Hebrew names are quite popular right now) and means "Tenderness," which is very sweet. I can't imagine using the name myself, but someone should, because it would make me happy. If you happen to already have a daughter named, say, Kale'a, for example (ahem, Laura), "Mahalia" would make a very appropriate sibling name!

Other names on my radar:
"Laurel-" A lovely, feminine name suggested by a friend as an alternative to the very popular "Lauren."
"Gage/Gauge-" I have a weakness for manly, old west names. Blake trained in Phoenix last week with a Gage from Texas (figures)- named for the shotgun, of course!
"William-" It's my granddad's birthday today. He's a "Bill," and though I'm more partial to "Will" as a nickname for "William," it's a name you can't go wrong with. Unless your last name is Williams or something. Or the baby is a girl.

Premeditated Naming

Blake and I are very much of the "have the name ready long before the baby arrives" mindset. It never even really occurred to me that "Aurora" might not be an "Aurora." Of course she would! If she wasn't, than she could become one. In fact, we have our son's name all set, just waiting for his October arrival. What if he doesn't look like a __________? Whatever, he'll be all nice and pink and wrinkly, and ___________ will suit him just fine.

However, I realize many people take a different, more diplomatic approach at the hospital/birthing center/home: have some names in mind, but go in with no expectations. For instance, my sister (who's baby girl is due any day) and her husband have three full names selected. They plan on seeing their daughter before deciding on one. Lindsay hopes they'll take one look and just know, but she's practical enough to know this does not always happen. Their strategy? They have one name they classify as very "delicate and beautiful, quite feminine," which they'll use if she has very fine, pretty features. The next name is reserved for a "cute, chubby, smooshy" baby. And the last? Well, they just decided on the last a week or two ago, mainly because Lindsay strongly felt they should go in with three names, not two. The last is their least favorite, they admit, but they like the meaning of it the best. Supposedly if the other two names seem not to fit, this last will work for a wide variety of babies. I'm most partial to their smooshy name myself, but all three are lovely, and I can't wait to find out who she is!

I also know of several people who did indeed go to the hospital etc. with a name all good and chosen, only to cast eyes upon their offspring and know instantly that the name would never do.

Another option is having no idea whatsoever what to name the baby, until two days after its birth you have to sign the birth certificate before leaving the hospital, so you grudgingly agree to your husband's favorite name, only to regret it for the next two weeks before finally accepting it (I'm not naming names here...).

Ultimately this leads to the much-pondered question, "does the name grow to suit the person or the person suit the name?" That is a discussion for another day.

Certainly there is no right or wrong method here, and I'm curious as to your thoughts: Be set on a name prior to the birth, have several options, or wing it?

Naming Subsequent Babies: Part 3

Here are some final (for now) thoughts on naming subsequent babies. I'll add more to this series on occasion, but must move on!

---One way to end up with names that "go" together is to select names from the same era. This allows for a pretty broad range of names, while still providing some continuity. By "era," I don't necessarily mean a specific year or two, more than names that give the same vibe. For instance, I have a friend with two little girls, the first named "Claire" and the second named "Audrey." Both names have a kind of retro, sweet sound to them. The parents are expecting their third child, and they'll likely want to stay away from modern, trendy names that lack the whimsy of their first two names. Names that evoke the same vibe? Perhaps: Phoebe, Gemma, Lucy, Pearl, Sadie. For a boy, they'd want to keep the retro-sense, but avoid the sweetness. Something well established, recognizable but not too common would fit the bill: Todd, Victor, Simon, Quinton, Lucas, Thaddeus, or Winston would be some examples.

---Chatting with a friend yesterday, we discussed a less-themey take on a theme: keep a consistent sound to begin the names, but not necessarily with the same letters. This friend has two sons (Kiefer and Cooper). Were they to have a third child, a fun way to keep the "k" sound would be going with a "qu" name: "Quinton" or "Quincey" for a boy, or perhaps "Quinn" for a little girl.

---One friend commented on an earlier post that the only thing connecting their potential baby names is that they are all unusual. Really, this is an entirely acceptable approach to naming, and obscurity is as a good a connection as anything. As long as Siren, River Rock, and Caesar don't have a little brother named "John," people are unlikely to grumble that their names don't go together (though they're likely to find other reasons to grumble).

---Finally, spend some time rattling off names to see how they flow together. If your oldest child is "Shane" and you're planning on naming your new baby "Erin" or "Aaron," practice saying, "My kids, Shane and Erin." To me, "Shane and Erin" doesn't flow well- it's too full of "n's" and is awkwardly rhythmically. A better sounding combination would be "Shane and Olivia," or "Shane and Dierdre." That doesn't mean Shane shouldn't have a little sister Erin, it's just a word of caution.

Since for the next four months I'm still the mom of just one little one, what are your experiences with naming siblings? What factors did you consider or disregard? Any regrets?