My productivity app for the past 12 years has been a single .txt file

I use a single text file, have done this for decades. I dump everything into it and don't worry too much about structure, it's an incredible resource for "remembering" minutia, things like "what was that server that i thought might have had some issues last August?" Just a quick control-S and I'm there. My current 7+ year old notes file has about 100K lines in it right now. I can tell you what I was doing last year, or the…

The key to this solution isn’t really the .txt file or the formatting. It’s the ritual. Any productivity system can be made to work once it becomes a habit and therefore your default action. I think .txt files or Org mode are attractive to devs because they feel like something we’d be doing anyway during our day. the same system will work with a paper journal or even a fresh piece of paper every morning if, and only if, it…

At my first job out of college in 1985 I worked for a unknown, unsuccessful mainframe company. I started a TODO.TXT file when I arrived; when I left a year later I put my TODO.TXT (along with ADDRESS.TXT, DATES.TXT) on a 5.25" floppy and took it with me to the next company, and the next, and the next. I didn't buy my own computer until 1997, and those files finally made it to a machine I own and control. Those…

I've been noticing lately, at least for myself, that useful technology stopped happening like 10-20 years ago. If all you could use was tech from 2000 and before you would have a pretty stable stack that just worked (without a monthly subscription.) There is also this article today: https://jon.recoil.org/blog/2025/12/an-svg-is-all-you-need.h... about how great good ol' svg is. And then every recurring article about using RSS instead of all the other siloed products. textfiles, makefiles, perl, php, rss, text…