Non-Post and Baby Names

(Thanks for the idea, Bubandpie!)

It is raining here, Eli has some sort of stomach virus, and every single thing I look at in our house is a nagging reminder of something I should be doing. I doubt that the arrival of my Harry Potter book is going to help.

We've had all summer to read the twenty books for the summer reading program, and now there is just one week left. I don't think that reading eight books to your kindergartner in one sitting so that she can get some prizes is what the librarians had in mind.

The RSVP date for my sister's wedding has come and gone, and approximately half of the invitees haven't responded. What is that?

Sara is entering her office's bake-off with this recipe today. Hope she wins big!

Katherine is sitting at our dining table painting in a paint-with-water book of animals right now, and she just asked. "What's that critter?" You can take the girl out of Kentucky.... (It was a skunk, by the way.)

Let's talk about baby names some more. Swistle took my question and turned it into a post that received 59 comments! She can totally spin blogging gold out of straw.

As I mentioned, we always have an easy time with girl names. We already have a girl name for this baby, which probably guarantees that it's a boy. I am circling back around to a boy name I have loved since before Katherine was born. (We weren't able to find out if she was a girl or boy.) It is a family name, not commonly used, and one of a very small number of names that Scott and I agree upon. However. Here in our small town, it is also the name of the son of a prominent citizen. This boy is well-known and not... well-liked. Granted, there will be about a 10-year age difference between him and our possibly-male, hypothetically-named child, but, will people hear the name and have a negative association? Will they wonder why we chose the same name? What do you think?