Obsidian with the Todo plugin and tags.
I am also a part of the cult slowly building a personal database in obsidian to use as postmortal-simulation training fodder later.
Ask HN: How do you keep track of your to-dos? longer-term projects?
11–20 of 37 posts
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#12A .txt file with a "char-checkable" list
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#13At the moment, I use Todoist as a front end and have a bunch of automations that run via the API.
Could you elaborate on this?
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#14Joplin on my phone and linux pc's and a free nextcloud hoster for synching it with e2e encryption.
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#15Todos: pad kept near dominant hand. Blue pen to add, Red pen to cross out.
Long Term: Markerboard in office
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#16taskwarrior + taskwarrior-tui
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#17At work I use a personal kanban task organizer to prioritize my tasks. The tasks for today are also visible in Outlook. It is a desktop app that I wrote for my needs.
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#18For my long term side project I just dump ideas into a barely organised backlog.md [^1]. After finishing a feature or taking a few months away, I normally dive back in by browsing this and choosing the next milestone.
It's worked well for a couple of years, and helps me keep the long term goals in mind.
[^1] https://github.com/DomWilliams0/name-needed/blob/develop/.pl...
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#19trello
Re: Ask HN: How do you keep track of your to-dos? longer-term projects?
#20Text file or org mode. For something really big I guess I'd consider an issue tracker, but I've never had to do that for any personal project. I've been at companies obsessed with using technology for this and it's always been a waste of time, especially when they churn to a new system without fully migrating and deleting the old system. Even if they make the old system archived/read-only, you end up having to look into 5 different systems to see what you are working on. I always tell myself that if I'm ever roped into a tech lead slot, I'm going to leave the choice of issue tracker up to the other devs, but will insist that there be only one system and that all the previous ones must be merged into it.
Really, IME, the technology doesn't really matter. I've never seen a tracker that scales really well, and unless very large scale is required, afaict they are all about equal.