Live data from Hacker News

Keeping a plaintext “did” file

theptrk.com

131–140 of 202 posts

Re: Keeping a plaintext “did” file

#131
post #61

Earlier quoted context omitted.

If you're on Android, you can do this today with Termux. I believe you can also set up shortcuts (so you could have a home screen widget to open your TXT file).

That would hand over full control to the author of Termux. According to the play store it is a guy called Fredrik Fornwall. I never heard of him. So I would not trust him with my digital life.

Seems to be open source -- https://github.com/termux/termux-app.

Re: Keeping a plaintext “did” file

#132

Earlier quoted context omitted.

I've gotten into the habit of defensively tracking every interruption - if somebody stops by my desk or slacks me or asks me to come by and look at something, I keep a text file of exactly when and how long. Then, if anybody ever asks why such-and-such is taking so long, I have a detailed record of _exactly_ why.

What do you do when somebody interupts you on the way back from your interruption? Do you just log it as "interruption"?

I'm non-reentrant. In that case, I kernel panic.

Re: Keeping a plaintext “did” file

#133
post #75

Earlier quoted context omitted.

Actually the fact that I finally had an outlet for my frustrations was very cathartic. It was a lot like writing sad poetry over lost love.

Or the epilogue to my life spent indoors fixing bad code.

That may be the most depressingly truthful description of software development I've ever run across.

Re: Keeping a plaintext “did” file

#134

Keeping a "did" file is also immensely valuable to demonstrating your performance and achievements to your employer. Think about all the positive things you've done for work over the past year. It's hard to account for them all mentally, and even harder for your boss to remember.

I think this is important. One of the most career oriented people I know, call him a mentor of mine, kept entire binders full of everything he did. Every accomplishment. He prepared for performance reviews like he was going to war.

As a manager I suggested to my reports that this in addition to proving your work, it also helps as a way to understand whether you are stagnating at work, or continuing to learn and evolve.

Re: Keeping a plaintext “did” file

#135
post #121

Earlier quoted context omitted.

Yep. I'm amazed by how many different hacks, tools, and one-offs get proposed in threads like this when an amazing plain-text note/organization/GTD/life management ecosystem already exists and is supported by endless configurability. Of course, we're talking about org-mode. (Religious org-mode user for approximately four years.)

I'm perpetually saddened because I work in aerospace where the IT policies are quite restrictive due to security clearances and whatnot, so I'm stuck on windows and can't install emacs :( Every few months I toy with the idea of implementing a poor man's org-mode in VBA.

That's tough, especially because emacs + org-mode is most usable when combined with a few melpa packages. Even if you could get emacs installed, you'd (probably) want melpa packages to make it more usable.

Re: Keeping a plaintext “did” file

#136
post #121

Earlier quoted context omitted.

Yep. I'm amazed by how many different hacks, tools, and one-offs get proposed in threads like this when an amazing plain-text note/organization/GTD/life management ecosystem already exists and is supported by endless configurability. Of course, we're talking about org-mode. (Religious org-mode user for approximately four years.)

I'm perpetually saddened because I work in aerospace where the IT policies are quite restrictive due to security clearances and whatnot, so I'm stuck on windows and can't install emacs :( Every few months I toy with the idea of implementing a poor man's org-mode in VBA.

Emacs doesn't have to be installed on Windows, strictly speaking... you can run it out of a subdirectory without using an installer. IIRC the Windows installer just sets up some registry keys that make life a bit more convenient, but they aren't blockers to actually running the application.

Re: Keeping a plaintext “did” file

#137
For a decade or so, I've been using `vim -o ~/{todo,progress,done}`

That gives me vim with three splits. Every day I add a new heading with the current date in the bottom split, then in the top one I list the things I plan to do that day. As new urgent work comes in throughout the day, I add it to the top split too. When I start working on something, I move it to the middle split. If I have to shift between tasks, I'll keep their entries in the middle split up to data with what i've done, next steps, etc. When I finish something, I move it from the middle split to the bottom split.

You can see a sample at https://imgur.com/a/jNa5Qp3

This helps me

* plan how much I can accomplish in a day

* limit the number of things I'm doing at once

* remember context when i do have to multitask

* explain to others (e.g. my manager) what i've been working on

Re: Keeping a plaintext “did” file

#138

Back in the late 1990s and early 2000s I experimented with a number of complex rich text, database, and proprietary formats for my notes files. It was a disaster in terms of long term accessibility. Since ~2004 or so I've used exclusively a single plain text file with embedded filepaths if media references were required. This has worked far better and now offers a remarkable resource for both nostalgia and getting st…

You might be interested in the vimwiki plugin. The diary feature automatically creates pages per day named with a datestamp. Grep to search.

Re: Keeping a plaintext “did” file

#139
post #26

Similar but not the same: most days day at work I create one or more txt files in notepad (kate to be exact) where I paste every temporary info while I work on some task. Basically everything that doesn't go to git, and you have to keep somewhere while you're working on it: - nonobvious terminal commands or small scripts I had to write - fixes for enviromental/configuration problems - fragments of stacktraces - fragm…

This is very similar to what I do as a sys eng. I call them weekly's, store them as [date].txt and use notepad++ to compose. I separate stuff with #########[brief desc/todo] and save the all the random tidbits, logs, dumps, presentation outlines, requests, urls, etc.

I have a script that copies them up to my backup drive and Windows full-text indexing is enabled on the folder, so it is easy to search all the content from the start menu. It helps me because my memory is not the best...your point on the deja vu is right on.

The stuff that ends up being really helpful, such as some long bash command, PS for querying AD, complex DB queries, etc. get promoted to helpful_notes.txt.

Re: Keeping a plaintext “did” file

#140
post #138

Back in the late 1990s and early 2000s I experimented with a number of complex rich text, database, and proprietary formats for my notes files. It was a disaster in terms of long term accessibility. Since ~2004 or so I've used exclusively a single plain text file with embedded filepaths if media references were required. This has worked far better and now offers a remarkable resource for both nostalgia and getting st…

You might be interested in the vimwiki plugin. The diary feature automatically creates pages per day named with a datestamp. Grep to search.

+1 for vimwiki; all plain text, with some light organization sprinkled on top. I've gone the OneNote/Evernote/GoodNotes route and keep coming back to vimwiki. If I could find a non-kludgy way to get it on iOS, my grail will have been found.

You don't even need grep, as vimwiki has built-in search:

":VWS /pattern/

    Search for /pattern/ in all files of current wiki.

    To display all matches use |:lopen| command.

    To display next match use |:lnext| command.

    To display previous match use |:lprevious| command."
Post reply on HN