I have several writing outlets, and each one has its own benefits and disadvantages.

There’s this blog, where I slowly become more comfortable writing about more personal things. It’s a good outlet because writing to someone else (you—and thank you, by the way) affects not just what I write but also how I write. Things tend to be clearer and to the point. Usually.

There’s my handwritten journal(s), where I write my feelings and conclusions about certain things as well as notes that I want to keep private. This is a good place to let out thoughts because it allows me the freedom to write whatever I want without explaining myself. At the same time, it limits how much I can write and for how long, as writing by hand is much slower and also starts hurting my hand after a while (I think it’s the pen). It’s also not a good place to find specific information, like names and addresses, which leads me to my new-old addition, the events.org file.

my events file is written in Emacs org-mode. Without getting technical as I usually do when I talk about org-mode, this file contains exactly what the handwritten journal does not: precise locations (with map snippets and links to coordinates), names of people, and exact times. For example, the events file would mention I was out with friends (their names would be captured as tags in the entry) last weekend at a certain pub (map snipper to show it) at a certain date and time. Then, in my handwritten journal, I would expand on our conversation and my opinions if I have more to add.

That last bit above, “if I have more to add,” is different from how I used to capture events in the past completely in Emacs org-mode. I would write down every day in my old journal.org file, making it a habit to try and write every morning or every night, sometimes more in between. I was writing a lot in my journal.org file, leaving little time and energy to write on my blog, let alone a handwritten journal. Too much was invested in one place.

I write on my blog much more often than I write in my written journal. Even if I don’t write a full-length post, I will comment about something I read or a quick photo with an explanation. The more I write these little “nuggets,” the easier and more streamlined writing those become. The “nuggets” workflow is completely mobile with the micro.blog app; most of my photos are taken on the iPhone anyway, and I can edit them with Lightroom or Snapspeed on my phone. I also have Grammarly turned on as a keyboard for proofreading. With these short posts, I skip writing in org-mode anyway.

As you can see, there’s a sort of a cycle going on here. My Events file would describe events along with meta information, while notes about these events would go to my blog and/or my written journal for private comments later when I mentally digest things. There’s another thing I started doing because of the influence of my events file: I started taking more pictures of every place I go to, even if it’s as boring as the sidewalk next to a place.

Photos on the iPhone (or an Android) contain important information I could use later. The time the photo was taken would tell me when the event started. The coordinates, which are captured automatically, will tell me where it was if I don’t remember the name (or if it’s just a spot somewhere without a name) later when I want to find it on a map1. A photo can also include other information, like a menu of a nice restaurant, or it can be aesthetically pleasing, like the view from a nice spot overlooking a river. Such photos can decorate the entry in the events file, be printed and included in the journal, or be posted here with an explanation. Photos are really great for all of the outlets I mentioned.

1 - I used to use Swarm for this, and I even have a feature on this blog which posts locations from it automatically, but I stopped. For one, Swarm is a private company and my location data belongs to them before it belongs to me. For another, getting this information out and use it is tricky.