Write less to write more
15 Nov 2022I maintain a blog at https://zeux.io/ - which I started all the way back in 2007, at the beginning of my professional career. You would be forgiven to not know it exists - after all, in recent years I seem to average a couple posts a year.
I’d like to think that I’m a decent writer, at least as far as technical topics are concerned. People who’ve worked with me have seen long emails, Confluence docs and Perforce/Git commit messages - the way I write those is usually in one go, start to finish, and then either send immediately or skim once to correct mistakes. Why, then, do I not write blog posts that often these days?
Even though writing seems easy these days, writing blog posts still takes seemingly forever. I don’t track the time explicitly but it seems to take me about 6 hours to make a post. Writing is one part - at 3-4 thousand words and something like 60 WPM, it takes an hour just to type. But the bulk of the work goes into making sure my numbers are accurate, re-running / re-profiling programs, formatting code carefully for reading convenience, finding or generating diagrams and charts, and editing after the post has been written.
On the other side of the spectrum is Twitter. 240 characters per post is just too little, and thread-based posting is awkward, with limitations on code/layout. This makes it difficult to share meaningful thoughts, and trying to fit messages into a small series of tweets is a struggle. Cut too little, and you get a rambly thread with poor layout. Cut too much, and you remove nuance that results in a poor message at best, and starts a flame war in comments at worst. EDIT: And what if you made a mistake or forgot to add something?
Cohost seemingly makes these problems disappear, at least now while the platform is small1. No explicit size limit makes me feel like I can properly format my thoughts, the lack of explicit focus on virality and engagement makes me worry about mistakes less, and everything about the site somehow feels like a cozy cafe you stumble upon at the end of long walk and spend an hour in, just to come back again and again and again in the future.
I’m sure I’m going to write more blog posts at some point, and whether tweets or toots or something else survives is a convenient medium to share links to cohosts (is that a word?) or blog posts if nothing else, but, at least for now, Cohost is quickly becoming my medium of choice. Expect me to write about technology here, as well as about life in general. Most of what I share here will probably be written in the style that works best for me - written in one go, with minimal edits or preparation, with occasional image or code snippet that’s easy for me to grab.
One aspect I’m still struggling with is figuring out the reading aspect. I’ve long relied on RSS feeds, and that’s going to continue, but Twitter was also a source of extra reading material from people I followed. It’s not clear how this needs to shift now - do I follow people on Cohost? Does Mastodon replace that, and who do I follow there? Does Twitter survive and rebound? Time will tell.
-
This post was originally published on Cohost; the platform was shut down as it was not financially sustainable, so it lives here now. ↩
| « ARM: Pragmatism, not purity | On greedy algorithms » |