Blogging for yourself

I don’t know about anyone else (except maybe LornaJane), but when I blog, I generally do it to help future me.

Sometimes I blog about things that I couldn’t find solutions to and had to work out myself (e.g. Node on CentOS 5.7), sometimes about things that I did find help with that I worry might disappear and sometimes even things that are easy to find, but I want a copy myself, just so I know exactly where to look next time I need it.

Sometimes it sucks, not having posts you can send out on twitter or submit to hacker news. I mean, how glamorous is recompiling coreutils? Then suddenly you get a comment from someone thanking you for your work. It helped them fix something they’ve been stuck on for ages. That’s when it’s really worth it.

So, blog for yourself. Blog about the boring stuff, about old outdated tech as well as the cutting edge. Someone will thank you for it, and that someone will probably be you in 6 months.

Michael is a polyglot software engineer, committed to reducing complexity in systems and making them more predictable. Working with a variety of languages and tools, he shares his technical expertise to audiences all around the world at user groups and conferences. You can follow @mheap on Twitter

Thoughts on this post

Russell Allen 2013-03-31

Given that the blog posts I get most response to are about obscure German home-automation technology, I hear you! And the number of times I’ve broken something, “How did I fix it last time? …. Oh yeah I blogged it!”

Leave a comment?

Leave a Reply