Live data from Hacker News

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

jeffhuang.com

301–310 of 420 posts

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

#301
post #109

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,…

Mine; the filename is today's date:

alias notes='nvim echo ~/notes/notes-$(date +'%Y%m%d').md'

The format being markdown gives a good syntax clue to vim.

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

#302
post #109

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,…

That sounds quite elegant, but seems this is only possible if you work out of a single machine almost always. Perhaps it could be made into a service? As long as explicit effort is taken that there's absolute minimum extra effort as possible!

A repo on github handles TODO.txt files from multiple machines fine, and better than gDrive or Dropbox. VSCode is now my main editor which makes git integration simple. I can also edit the file directly on github, though never do.

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

#304
post #109

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,…

Be careful about making a file like that -- one where you have to write the entire contents back to disk when you update it even though you only modified the last line or so -- too large. You're definitely better off splitting to give you more chances at not losing everything in the event that it gets corrupted. But I guess proper backups would also take care of that.

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

#305
post #58

My favourite "productivity app" is not an app at all. It's a plain old notebook. I write down any notes and actions I need to take, and strike through them once finished. It has a nice benefit that I can scribble notes, draw lines between ideas, sketch out diagrams, etc.

I tried everything and kept coming back to pen and paper. On the right side if the open notebook is an organized todo list. On the left side are notes and diagrams that I come to during the day.

I had a stroke last May and the only long term side effect (thankfully) is that my handwriting needs to be 2x the size to be legible, making my notebook obsolete.

Will try a todo.txt soon. I love simple.

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

#306
Yes, one of my best tools is a single text file, FACTS.DAT, that I use to remember essentially all little facts.

What is amazing is the combination of (i) how simple the file is, (ii) how easy it is to use, (iii) how little work it took to start using it, and (iv) how useful it is.

I maintain the file, add to it, search it, extract from it with my favorite text editor KEdit and some macros I wrote for KEdit. A lot of (i) -- (iv) is due to the good functionality of KEdit. E.g., KEdit has some sweetheart text parsing tools.

KEdit is no joke: It is a PC version of XEDIT written by an IBM guy, on his own time, in Paris and quickly was an important tool inside IBM. The macro language for XEDIT was Rexx, and for KEDIT, Kexx, a version of Rexx.

Kexx is no joke, e.g., offers decimal integer arithmetic of 1000 digits. E.g., recently, as part of developing some notes on calculus for my 9 year old nephew, as at

https://news.ycombinator.com/item?id=22179494

I used that long precision arithmetic and Taylor series to find Euler's constant e, the base of the natural logarithm, to 36 decimal digits:

e = 2.71828182845904523536028747135266250

I have a command line command FACTS that looks for any executing instance of KEdit that has that file open and (i) if there is an instance then makes that instance visible and at the top of the Z-order and (ii) otherwise creates such an instance.

What does the file look like?

A recent entry is

     ========================================================================
     :Created at. 10:12:19 on Saturday, February 8th, 2020.
     :Keys.  Internet DNS sinkhole C2

     C:\Users\user1\data05\topics\tech\communications\internet\domain_name\domain_name.doc
So, the file consists of a sequence of entries where each entry starts with a line of equal signs and has a time-date stamp, some keywords, and the contents of the entry.

For this sample entry, the next time I want to know about sinkholes and C2 I can read the file with its tree name in the contents of that entry -- the tree name is for a file on one of my disks.

How big is the file FACTS.DAT?

I've been using such files for 20+ years. The latest version started on

Friday, September 2nd, 2005

and now has 97,223 lines.

The file has 2,902,471 bytes and from the rotating disk on my little HP laptop loads right away.

The number of days from September 2nd, 2005 and today, February 8th, 2020, should be 5272, courtesy of some little KEdit macro language procedures I wrote for converting to/from dates and days from the start of the Gregorian calendar.

Having KEdit select all the lines full of equal signs and then count those lines I get 5073 entries in the file. So, that is

5073 / 5272 = 0.962

entries per day.

So

97,223 / 5272 = 18

says that my average has been about 18 text lines a day.

The average number of lines per entry is

97,223 / 5073 = 19.2

and the averge number of bytes per entry is

2,902,471 / 5073 = 572.1

Lesson: Can do a lot with a really simple tool.

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

#307
post #109

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,…

Just a thought but would't creating a new file for each year make it more maintainable? I can't imagine searching a 100k line file or scrolling through it.

I find it useful to have everything in a single buffer, it makes searching easier. Otherwise I'd have to start issuing 'grep' commands and worry about which file is which, and get clever about regular expressions when all I want is instant, friction-free access with a handful of keystrokes. Opening a file that big doesn't take long on modern hardware.

Honestly, there's not really anything to "maintain". Just a text file and some timestamps. No magic at all. Simple as dirt. That's the magic :-)

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

#308
I use a "Todo" web app I made with the same toolset I use for my apps.

On a desktop you can drag and drop the order of the todos so when coding I use it to make quick notes of things I run into and prioritize them.

That's really all I use, but I work for and by myself so I don't need much.

https://cherrypc.com/todo/

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

#310
post #5

One step up from this (if you’re a vim user) is vimwiki. But it really doesn’t matter what you use, the real benefit comes from having a process/habit of continuous review.

this. the precise system doesn't seem to matter as much as actually following it for so long.
Post reply on HN