Reading through the comments under this thread, there are many users who swear by a plain text file, but who then build quite a lot of snowflake software to regain functionality offered by more structured TODO applications. That includes: - having your computer alert you to things that come up - being able to tag notes - being able to add events to a calendar - being able to set priority of tasks - expecting prioriti…
I tried every todo app and ended up with a .txt file
271–280 of 831 posts
Re: I tried every todo app and ended up with a .txt file
#272for longer term planning i’ve found todoist to be indispensable. UI and features haven’t changed much in years, great cross platform, pretty enable to different styles of planning, etc
Re: I tried every todo app and ended up with a .txt file
#273sigh I've done the text file thing, and it’s fine. Up to a (very small) point. What the author describes as their “workload” barely registers. For context, for me, Things on any given day has over 100 individual actions, most of which are recurring. By doing this, I can stay on top of an extremely broad surface area. There is no way a text file can handle the number of parallel work streams my (or really many) people…
Re: I tried every todo app and ended up with a .txt file
#274Re: I tried every todo app and ended up with a .txt file
#275I use Todoist in a very light weight fashion. I add tasks and they sit on my screen until they're done, basically identical to a text file. I've never used the points, projects, labels, etc. It does one thing a text file struggles at: scheduling recurring tasks and adding notes to a recurring task. I have annual reminders for infrequent, but important stuff. For example, I have a recurring annual task to review my in…
> Todoist: Great until I realized I was gaming the points system instead of doing actual work. Turns out completing “drink water” 8 times a day doesn’t make you productive.
Why didn't he turn off the points system if it was distracting, instead of migrating to the next shiny new TODO workflow? Not sure I understand, but I guess that might've left nothing to blog about.
Re: I tried every todo app and ended up with a .txt file
#276Closest to that is a .txt file in my specific format, but even that is not quite as good.
The days/weeks I can maintain discipline with a legal pad are much more productive. It works well if you work out of an office or a single location, but breaks down quickly if you are moving around.
A notebook is a close second, just not quite as easy to go page through quickly to figure out wtf you were doing 3 weeks ago or find that one note you're pretty sure you have but not quite sure where or when.
I've tried pretty much every electronic form out there, but have never been able to maintain it. The Remarkable 2 comes the closest, but I've found it tends to be very much "write only" compared to a legal pad. Hard to go through it and reference past notes quickly.
Re: I tried every todo app and ended up with a .txt file
#277I have a very simple todo list, it's essentially the same every day! - check mail - check calendar - check jira - check azure devops board - check Microsoft Tasks - check confluence - check Teams - check home calendar - check home e-mail - check signal - check whatsapp - check client e-mail - check client jira - renew prescription for benzos
Re: I tried every todo app and ended up with a .txt file
#278sigh I've done the text file thing, and it’s fine. Up to a (very small) point. What the author describes as their “workload” barely registers. For context, for me, Things on any given day has over 100 individual actions, most of which are recurring. By doing this, I can stay on top of an extremely broad surface area. There is no way a text file can handle the number of parallel work streams my (or really many) people…
Most programmers are far better off with a maker's schedule. Far fewer things in a day. Each with a significant block of time associated with it.
An absolutely minimal productivity system is perfect for anyone on a maker's schedule. You're right that it wouldn't work for your life.
See https://paulgraham.com/makersschedule.html if you're not familiar with the terms "manager's schedule" and "maker's schedule". It also provides context for why those different kinds of schedules are appropriate for different people. (One of the big mistakes that people on manager's schedules often make is to not recognize and respect the impact that a "quick 15 minute meeting" has on employees who need to be on a maker's schedule.)
Re: I tried every todo app and ended up with a .txt file
#279Re: I tried every todo app and ended up with a .txt file
#280Then adds structure back, as it suits their persona. Not too much, not too little, just right - goldilocks. It's very personal, even more than a smartphone.
For me - $ githome add logBook to git $HOME solves versioning and replication:
giho() { (cd "$HOME" && git --git-dir="$HOME"/.githome/ --work-tree="$HOME" "$@";) } # prior must $ git init --bare $HOME/.githome
And in the logBook structure currently at:
1. Sections FIXME, TODO, DONE, DONTDO. Keep them vi searchable /^SECTION$.
2. Entry start searchable /^-(space).
3. Entry end separator from next is empty line searchable /^$.
4. New items add at the top, push old items down.
5. Items move wholesale, no change on between sections move.
6. Items spending too long in TODO moved into DONTDO.
7. No new items added in TODO if FIXME is not empty.
8. If really really need to add to TODO - then move blocking FIXME entries to TODO.
9. Above are rules of thumb - break them with a reason, don't break them without reasons.