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 birchnature.com, 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.