Blogging like Chris Coyier

Chris Coyier is well-known for blogging a mind-boggling amout of posts on CSS-Tricks (which is now owned by DigitalOcean). But I’m not going to talk about his stuff on CSS-Tricks, but instead about his personal blog chriscoyier.net.

Chris’ blog feels like a stream of consciousness. It’s just what he’s thinking about at the moment, without any deeper meaning or learning. And yet, those thoughts are still interesting and fun to read. Annoyed at System Fonts in macOS? Just blog about it. Orange favicons work great for light and dark themes? Why not write down that thought, then notice that Safari is weird, and end it with “Time for a nap”. It’s refreshing to see someone share their half-baked ideas without feeling the need to make a grand conclusion or provide a takeaway for the reader. You can just end your post if you don’t know what else to write.

It feels like a conversation with a friend. Sometimes you just want to talk about something that’s been on your mind without worrying about whether it’s profound or even fully formed. It’s totally normal in a conversation to suddenly end your thought mid-sentence with a big ol’ shrug. And that’s what his blog feels like to me.

Maybe we sometimes try too hard to offer some kind of education or to present ourselves as experts? At least I sometimes feel that way. But I don’t think that’s necessary. It’s nice to take a break from expert content and just read something that’s relatable and human.

Chris has definitely inspired me to post more half-baked thoughts. And to not think about words and sentences and publishing too much. Just write it down, press the big button, and continue with your day.

Thought Leaders

I have many thoughts about this topic but I’ll try to keep it short: I don’t like this thought leadership in engineering, where it’s mostly about being an influencer and less about having a good influence.

It rubs me the wrong way. You could just say that it annoys me and I should ignore those parts of the internet. But it actually worries me because it feels like small cult-like groups in which engineers won’t grow: They’re caught in an echo chamber, which makes them feel like they’re growing, but instead of growing as a person and engineer, only a single opinion grows within them.

I don’t like many of my development-related blog posts for one reason: I often feel like I spend too much time explaining the problem instead of getting straight to the point.

Understanding the problem is just as important as understanding how to solve it. So I don’t want to skip explaining the problem properly. And I want to include readers who might not be familiar with the topic. But whenever I start writing, I imagine readers rolling their eyes in light of the “obviousness” of it all.

I often think back to “Words To Avoid in Educational Writing” by Chris Coyier. He warns against using certain common words that make readers feel dumb. Just because you find something obvious doesn’t mean they do.

I’m certainly guilty of using those words myself sometimes, but the message stuck with me. That’s why I always try to explain problems thoroughly: because the reader might not know this yet, and it could be valuable knowledge for them, and I want them to feel included.

Still, I can’t shake the insecurity. Whenever I explain a problem, I worry readers will think that I’m a bit of a dum-dum for explaining something “everyone” already knows. Even when editing my posts before publishing them, I spend most of my time refining the problem explanation, trying to make it not too long but still explain everything.

Do I explain problems too much? You can tell me, I can take it!