3 ms·
After many years of using different tools to keep track of tasks, I ended up with a very simple system: a markdown journal for what I do every day. Whenever I
by allenu 5y ago
After many years of using different tools to keep track of tasks, I ended up with a very simple system: a markdown journal for what I do every day.
Whenever I have a task that I need to complete that day, I add an entry in the current day's log. If I get it done, I 'x' it. If not, I carry it over to the next day. Of course, for work projects we have Jira to track work as well, but my task list is for things like "set up meeting with so and so" or "get screenshots to so and so" or "start working on ticket 1234". Any meeting notes or random things I think might be worth recording, I put in the log for the day.
For my personal projects, I keep a LOG.md file in the repo for the project and usually a separate TODOs.md since I don't use Jira or anything like that. As new work comes up, I add it to the TODOs file. I also nest tasks just using tabs. It's super simple, but it gets the job done.
I've learned that I don't like relying on outside software for keeping track of tasks. It's just faster for me to type away using vim in a text file. It gets synced with the repo and I don't need to worry about signing in to some cloud software or worrying about them adding/removing/changing features on me (or going under).