Here we are with the first installment of what I imagine, for now, will be a two- or three-part series in which I ponder why I do the things I do. (A bit of self-reflection is good, right?)

First is blogging itself.

This came to mind recently when I realized that I’ll have been writing this blog for three years soon. Wow, three years already… Congrats, self!

But… why do I continue?

It’s kind of a paradox that part of the reason I do this is to provide helpful information for other software engineers (such as jumping to specific lines in VS Code), yet I don’t advertise or tell anyone about this blog. It has neither analytics nor a comment system, and as far as I’m aware, it currently boasts zero readers.

Has anyone ever actually read any of my posts? Right now, your guess is, quite literally, as good as mine.

(The only person that I know even knows of this blog is a former coworker who only learned about it inadvertently when they asked if I have a personal GitHub account when they left my team and found it through there.)

And to be clear, that’s in no way a complaint. I’m fine with—and even prefer—flying fully under the radar.

But again, why do I continue this blog?

I don’t have a great answer, honestly.

I think it’s a mix of a desire to log some parts of my personal engineering journey; share interesting and helpful learnings; and more recently, perhaps a desire to contribute human-generated content to the increasingly AI-subsumed internet. (I’m so glad I got to experience the internet of old…) Also, having a greater online professional presence might be beneficial career-wise, but that likely hinges on having quality content. (Ruh-roh!)

However, I do think there is value in writing itself. This has been my belief in particular since reading the Japanese book “The Power Of Output: How To Change Learning To Outcome” (Japanese title: 学びを結果に変えるアウトプット大全) by Dr. Shion Kabasawa (樺沢紫苑先生) a few years ago. (Note: I haven’t read and thus can’t vouch for the English translation, but I imagine it’s fine.) Writing and speaking engage the brain in a way that reading and listening alone don’t. Since the pandemic and starting working remotely, I haven’t been speaking to people as much as I did before, so writing helps cover that decrease somewhat, I think. (I should reread that book…)

But, honestly, blogging is also kind of fun.

I think the lack of analytics and comments helps keep it fun for me. I don’t want to have to even think about things like how my “engagement” is down 15% since last month, etc. And I know myself well enough to know that I would look at those numbers and care just enough to where it affects my motivation and/or the content I choose to post about.

Of course, this means that I also don’t get the occasional comment that such-and-such post was helpful, which is kind of unfortunate, as it feels nice to get a little acknowledgement when you’ve helped someone. But I can just presume that someone has stumbled upon, or will do so, an article of mine via a search engine and found it helpful. That’s enough satisfaction for me.

Also, looking back at my own older posts can be interesting. It’s always nice to remember small accomplishments like completing the Ruby koans (which I’d completely forgotten about!) or creating my first NuGet package for .NET, for example. Maybe that’s another plus: having a blog motivates me to do things.

In any case, I intend to keep blogging as I have. If you’re a human reading this or any other of my posts, thank you for taking the time to do!


<
Previous Post
Auto-wrap Git commit messages in Vim
>
Blog Archive
Archive of all previous blog posts