←back to thread

17 points gashmol | 1 comments | | HN request time: 0.203s | source

I've used several tools over the years but no one fits my needs well enough. I wonder if I miss some magic tool. Which tool work best for a single person operation?
Show context
nuc1e0n ◴[] No.41897597[source]
Git for source code control. A notepad and pencil for listing out the TODOs. I write "Done" next to a bullet point when it's done. I might rewrite the list occasionally without the done items for clarity or write numbers next to the bullet points to prioritise them. I think if you can't write out a task description as a short sentence then it's either not well understood enough or too broad in scope to accomplish easily. In the latter case it needs breaking out into a set of smaller tasks.

I don't use any framework for unit tests. Only a short program for each test that returns 0 on success or some other number for failure and prints a message to stderr about what the problem is. These get run in a loop from a shell script.

replies(1): >>41897828 #
hyperbrainer ◴[] No.41897828[source]
The same as you, but for TODOs, I have a simple macro on my neovim setup because then I can keep the todos with my version control(it is a single text file, newline separated) and see what changed and why I added something. Really helpful if I come back to something after some time.
replies(1): >>41897969 #
jvanderbot ◴[] No.41897969[source]
I do something similar. Simple highlights on to-do items helps a lot.

And using bullet journal style to-do markers help organization.

- [ ] todo

- [x] done

- [-] failed

- [v] dropped

- [>] migrated

- [^] scheduled

- [<] delegated

Easy to set up vim highlighting on those patterns.

I have some examples here:

https://jodavaho.io/posts/bullet-journalling.html

And a bash setup here

https://github.com/jodavaho/bashlog

replies(1): >>41898075 #
1. nuc1e0n ◴[] No.41898075[source]
I wasn't aware what I've been doing is named bullet journaling by some, but thanks for this info.