So, kind of "one big text file", but with a small script to enhance that for timekeeping purposes.
Not-so-fun related fact: About a month ago, I had hardware failure and needed to replace my work laptop. My script didn't get backed up, as it wasn't in one of the directories that I copied over before replacing the machine. So I rewrote it and... now there's a bug that screws up the time calculation if the day isn't 8 hours. Haven't figured out why... Gotta love automation!
echo "Fixing ssh key permissions for ansible. --my.name JIRA-1000101" | logger
Logger sends the text to syslog. If someone detected a system change they will eventually also see my message and can review the JIRA that hopefully answers any questions they might have as well as showing my work and approval process. That has saved me from many emails and meetings and saved me a lot of time.One could run a syslog server on their home/vpn-mesh and/or use rsyslog with TLS and send messages from any terminal to the syslog server. I have also found this to be a useful way to distribute commands and log feedback for home automation. Not command injection but automation that looks for keywords and takes actions.
Managed as a private git repo. Because I use multiple machines, git helps me with easy backups, merging, and version control.
I just use my OS's default plain text editor for writing.
I prefer markdown instead of plain text because it allows me to link to images. Images are stored in yyyy-mm-dd/ directories.
All these decisions were motivated by my long-term goal to make my journal easy to own, read, process, and pass down two or three decades down the line.
That goal pretty much rules out any kind of third-party service or specialized journaling application. git is the exception but I always have an accessible version even if git disappears.
At work I’ve tried various options, mostly with text files or markdown. Currently, I wrote something in bash to quickly log stuff to a text file and parse the file to get a log from a certain day, so I can fill out some time tracking stuff each week.
I have found MD to be the proper mix between formatting and plain text, just enough formatting to enhance readability but not enough to require a mandatory parsing tool. Overall I just consider it essential that at anytime I can take my 4+ years Of daily documents and interact with them in however I want.
I used to log activities in Word2000 back when I was a sysadmin (aka DevOps)
Publicly, I blog at mikewarot I hope to replace it all with a Memex eventually... once I figure out what that really means (I've been doing a lot of reading and watching videos about the origins of the idea)
A few years ago I used DayOne for a while but I ended importing everything to Evernote, as having everything in the same place is valuable.
I haven’t decided which I prefer yet.
But now that I think about it, I only use DayOne on mobile so I suppose it’s actually just my mobile solution.