Thank you, Readers, for reporting errors

The first step to getting things fixed is to know they are broken. This is true whether you work for a software company, are coaching a little league team, or write a blog. None of us is all-knowing, and we all make mistakes. I would venture to guess that most of us, if we have made a mistake, especially on a project that we care very much about, would like to fix it.

So thank you, thank you, thank you to those of you who have pointed out errors on my site. I can’t tell you how much I appreciate that my mistakes are not hanging out for all the world to see anymore. That would be embarrassing! What kind of mistakes do I mean? Here are a few of the more recent ones:

  • The Mesh gallery on my recent Making apple pie: a photo essay was broken. My dad reported it to me, as did several readers in the comments. As a result I was able to report feedback to the Mesh team, and they got it fixed up.
  • I misspelled “lobotomy” in every instance in my Half-full post. Thank you to my friend Dee, of, who texted me and said “Hi hon – love the new post!  Heads up, though, it’s lobotomy, not labotomy.” Thank you, Dee ❤️
  • I entered some HTML into the visual editor instead of my text editor on a recent post, and the code appeared on the front end of my site. My coworker Kelly pinged me to let me know it was showing, and also make sure it wasn’t an error with the editor. No, I assured her, it was not the editor. It was a case of PEBCAK.

I know it can be hard to tell someone, hey, you’ve got a big chunk of black bean on your front tooth. But that’s the kind thing to do, right? Better to tell them and be embarrassed for five seconds than to let them walk around ALL DAY with gunk in their smile.

Not that that’s ever happened to me.


It’s that time of year. Time to scope the outside of the house. Find a flat area to build a stand. Time to poke around, asking for whispered tips on whose is best-seasoned — I’ve heard folks are secretive about sources around here.

It’s time to think about firewood.

When we moved from Florida to Minnesota, I made a wish board for everything I wanted to find in a home. On the board, I wrote things like walking distance to the kids’ school, safe neighborhood, a place for a garden, and the thing I wanted most? A fireplace. The house we found had all of those things.

I loved our fireplace. Each fall we bought half a cord of wood. We stacked it under an eave, on a red brick patio, up against the house next to the kitchen door. The eave mostly protected it from getting buried by snow, and in winter I’d build fires in the afternoon when the kids came home from school. We’d drink hot cocoa and listen to wood pop, and we’d pull the bean bag next to the hearth and we’d read books and play Sorry!

I can’t wait to do that again. When we first moved to Virginia, we lived in a townhouse without a fireplace. In fall and winter, on my walks and runs through the hills, I’d smell chimney smoke in the cold air. I’d watch white puffs rise from the valley. I could smell the wood burning, and I imagined rocking chairs, blanket wrapped laps, quiet broken only by snapping, popping, and the soft turning of a novel’s pages. I ached for a fireplace every time I smelled chimney smoke. When it came time to buy a house, due to timing, pricing, and the small size of our town, our options were very limited. I feared we would not find a house with a fireplace.

But we did. And last night, as we worked on our September budget, I was thrilled to add in:

  • Fireplace stand
  • Fireplace tools
  • Firewood

I can’t wait for our first fire.

Photo credit: Ben Dwyer of Full image available here.