Keeping a plaintext “did” file
theptrk.com
Keeping a plaintext “did” file
1–10 of 202 posts
Re: Keeping a plaintext “did” file
#2Yeah, it's easy to forget. CHANGELOG is the historical equivalent, but that seems to be dead.
Re: Keeping a plaintext “did” file
#3If the file does not exist, then
vim +'normal Go' +'r!date' ~/did.txt
Re: Keeping a plaintext “did” file
#4If the file does not exist, then vim +'normal Go' +'r!date' ~/did.txt creates a file with the first two lines being blank.
hm, good thinking, I guess I should run `touch` to create the empty file first.
Re: Keeping a plaintext “did” file
#5This reminds me of the `plan` files used by John Carmack and and ID software. It's a good way to look back at things and remember how far you've gone and give some perspective on how some big problems at the time were not so big today...
Re: Keeping a plaintext “did” file
#6I use the following to maintain a journal: http://jrnl.sh/
Re: Keeping a plaintext “did” file
#7Isn't this effectively what code commits are for? If you've done something worth noting, it should probably be in a commit anyway.
Re: Keeping a plaintext “did” file
#8Isn't this effectively what code commits are for? If you've done something worth noting, it should probably be in a commit anyway.
Do you mean that all is worth is code ? I code as a living but wouldn't say that all I do is coding or in a text file. By example talking with X is worth noting or setting up a complex embedded device with all its tooling is definitely worth noting.
Re: Keeping a plaintext “did” file
#9join the (very recent) crowd: https://news.ycombinator.com/item?id=17532094
Re: Keeping a plaintext “did” file
#10I have a windows notepad file for the same reason. F5 prints the date/time stamp.