I use Git and a markdown file.<p>I keep a repo on all my systems that track a Gitlab repo (any Git repo would work). This repo contains a primary ToDo file with an overall list. When necessary, I spawn dedicated lists for specific projects or events. This is all written in Markdown (usually Github flavored).<p>The text editor is left to the reader's preference :) I'm strongly preferential of Vim, and use a few different Markdown plugins to ease writing.<p>Occasionally, if needed I build a printable PDF using Pandoc. Usually I only do this when I need to bring it with me.<p>Of course this doesn't bring any sort of notifications or reminders, so I supplement this with Google Calendar (and more recently Google Keep) when needed.
I wrote a thing for this!<p><a href="https://github.com/josefdlange/doit" rel="nofollow">https://github.com/josefdlange/doit</a><p>To be fair, I don't use it anymore because I'm a disorganized wreck (but that's just a personal problem!). Despite that, I think it's a neat tool. It was inspired by Zach Holman's "Boom" -- and its Python port, "Bam" (credit goes to Ben Tappin for Bam). It borrows a handful of code from the latter for data persistence in particular, and for the scaffolding that the CLI rests upon. Thanks Ben! I haven't updated it in almost two years but it serves its purpose when I choose to use it.<p>I wrote it because I found that switching context away from my terminal was detrimental to my workflow. My day-to-day work has since evolved from being buried in a tmux session, so it doesn't really make sense for me anymore.<p>Feel free to contribute to it, file an issue, or generally bitch about it; it was honestly a couple-hour job to play around with creating something from a nascent idea, and with learning how Python / PyPI packaging goes. I'd love to revisit it and improve it if there are reasonable issues/features worth fixing/implementing!
Well, no one mentioned Bullet Journal: <a href="http://bulletjournal.com/" rel="nofollow">http://bulletjournal.com/</a><p>They've already done a good job explaining the system, so I won't do it here.<p>I used it when I was still in graduate school writing a paper. I managed to track tons of tiny details in the writing process.<p>I think the most useful thing is the task migration. You must migrate unfinished tasks from today's log to next day's log, <i>manually</i>. During the migration, I sometimes cross out some random thoughts that I put as tasks.<p>This is the time that you _must_ spend everyday. It somehow can keep up your sensation of completeness. I know some apps can help you do this automatically, like todoist, but I don't think that really works for a long run (at least not for me). I find that if I didn't do the review (migration), I intended to get slow start the next day, and gradually the system would collapse. That's how I failed todoist :(<p>Just my 2 cents.
Index cards and a pencil. I organize the cards into columns that represent calendar weeks (Thur-Wed), and I keep the next six weeks' worth of columns at all times. There's an additional column for "future" that holds everything with a date more than six weeks away.<p>Stuff that doesn't have a date, but is a nifty idea to do in the future, gets put into a stack of future ideas. They're categorized. At any given time, I'm working on just a few ideas. When an idea is finished, I can take a new idea from the "future ideas" pile. In practice, I often know what I want to work on next and I don't look at the pile.<p>Cards are estimated in terms of points. I know from experience how many points I can get done in a week. At the beginning of each week, I count up the estimates on the date-sensitive cards. If there's extra time available, I either pull forward cards that need to be done in the future or bring in cards that will progress one of my current ideas.<p>Every day, I completely clear my inbox. Spam, no-response, and quick-response email gets taken care of immediately. Everything else gets turned into a card and put into the calendar. There's enough slack in my weekly budget that I can absorb these sorts of administrative tasks.<p>When I finish a card, I mark it with a little sticky dot. At the end of the week, I bundle up the cards with a rubber band and put it in a cardfile. I also add up the total estimates and write down the ideas I was working on for future reference. That info gets put on another card, of a different color, that acts as a sort of "cover sheet" for the bundle. I don't need to do this, but it makes me feel a sense of progress.<p>Been doing this for years and it works very well for me. It breaks down when I travel as I'm (a) busy and distracted, and (b) don't bring the cards with me, so I have trouble staying on top of my inbox.
Google Keep as a write-only TODO.
A sheet of paper with a pen with a few entries for my "tasks-of-the-day", and I strike any "done" entry.<p>Didn't find anything more efficient.
I use my side project, MindAUX.<p>Creating Todos is pretty easy; i can create as many as I want at once via an email or entry in the search.<p>Categorizing them is the next trick: I get emails every other day for todos I created that aren't classified yet.<p>After that, they get regularly reviewed and timestamped as reviewed so they don't need to reappear for a while. I get emails for any todos that have never been reviewed, or that are overdue for a review.<p>When I'm deciding what to do in the next i select several I think I can tackle and add them to my list of active todos, then sort them based on priority.<p>Anything with a due date gets noisy (pesters me via email) as the date approaches as well as if its overdue; until it's removed or completed.<p>I could but haven't needed to use contexts yet or time estimates; primarily it's been a matter of making sure something is at least in the system and being tracked/reviewed in a way that I can forget about because I know it remembers and will remind me through a variety of ways.<p>I also get a weekly report of open todos, new todos, and other statistics.<p>This works for me, because it is easy to do brain dumps of this or that, while also making it harder for me to drop a particularly important ball, or lose track of it.
Trello board with lists setup like so:<p>[Inbox][Queue][This Week][Today][Done][Done Apr 2nd]<p>Text files version controlled in git:<p><pre><code> /notes/
/notes/project1/todo.txt
/notes/project2/todo.txt
/notes/project3/todo.txt
</code></pre>
Since I'm in terminal all day I quickly jot down todos in .txt files as I go. The real management of them is done in Trello.
I use a notebook and write a * followed by a one-line description of the task. If I create a task, I have to do it. When I finish it, I cross out the whole link. When I finish all the tasks on a page (I put notes in there too) I put a checkmark in the top lefthand corner of the page. I have a todo.txt for work stuff that contains all ongoing todo items.
Taskpaper. There are vim, atom, emacs, and sublime text plugins to support the format, but I use the official Taskpaper app. I also have a handful of scripts that I use to help manage the file, including an any.do-like daily review in a terminal (i.e. find all the overdue stuff and for each one, prompt to either mark as complete or assign a new due date or delete it; same with @today and some others). I use a separate file for an inbox, and part of the daily review is moving each of the inbox tasks to an appropriate project list in my main tasks file. I use IFTTT and the DO Note app to append new tasks into my inbox file, and I have a couple other triggers set up (for instance, a Github project of mine will drop a task into my inbox when a PR is opened to go review the PR -- this is much less distracting than an email notification or similar).
Pen and paper pad. Usually put exclamation points next to things I think are priorities. The next morning, I copy over things I didn't get done the previous day. Eventually, if I keep copying them long enough, I stop because I come to term with the fact that they aren't high enough priorities.
I'm using Workflowy. Tried it for a few hours and I was pretty sold on it. Got a whole year sub for it. Got buyer's remorse shortly after. Gave it another shot and now I can't live without it.<p>I use it mainly to track ALL of the things that is going on at work.
Zim-wiki is very good for general note taking and simple todo. It's worth to try.<p>Highlights:
* Markdown to visual in real-time
* Create pages and tags link between them
* ! Back links, where a page or tag is being referenced
* Past images
* Drag drop file
* Save storage is in folders files
* Python plug-ins<p>It looks simple at first, but is actually very powerful.<p><a href="http://i.imgur.com/iPE9OIS.png" rel="nofollow">http://i.imgur.com/iPE9OIS.png</a><p><a href="http://zim-wiki.org/screenshots.html" rel="nofollow">http://zim-wiki.org/screenshots.html</a>
<a href="http://zim-wiki.org" rel="nofollow">http://zim-wiki.org</a>
I run Spacemacs org-mode first. I use it to commit all the todos that I can think of to paper.<p>Todos with timeframes and deadlines get done. So I peruse the todo list and set their timeframes. I use Google Calendar to schedule them.
somefile.rst<p>Which is plain text, and vim knows how to display headings and such. I never render it, .rst is just for syntax highlighting in vim. My current file is 2742 lines, and goes back to Sept. 2014.<p>I have the following shell script:<p><pre><code> dt="$1" || "today"
date --date="$dt" +"%Y-%m-%d %a"
echo "--------------"
echo "- "
echo
</code></pre>
I call it from vim:<p><pre><code> :r!newday
</code></pre>
or:<p><pre><code> :r!newday tomorrow
</code></pre>
Which creates this, which I then fill in as I go:<p><pre><code> 2016-04-03 Sun
--------------
- Commented on HN.
- > Make another comment on HN.
</code></pre>
A plain bullet records what I did. A bullet followed by '>' means something I
need to do today (or tomorrow). Most of the time when I complete a todo, I
just remove the '>'. If it's still there at the end of the day I move it to
the next day's entry. In the manner of .rst, I sometimes have sub-bullets.<p>A new entry goes at the top. I have a few undated long-ish term entries at the very top.<p>That's for my work life. For my personal life I just sit on the couch and wait for emails from my ex-wife.
Vim with some todo plugins, Emacs orgmode, but there are also some lists which I need daily on mobile, for that purpose I use Wunderlist with abbreviated descriptions ( Yea I know I'm paranoid, but hey it's in the cloud and Microsoft owns it )
Professionally I use Jira, there's really notting quite like it.<p>Personally I tend to use Google Spreadsheet, it allows for collaboration on small teams.<p>Sometimes I use a plaintext file in a git-repo (usually formated as a markdown or org-mode file).
I use Trello.<p>Three lists:
TODO, DOING, DONE<p>Items in DONE get archived the next day. Items in DOING get moved back to TODO if not completed. I organise them in their list by importance - i.e. ones at the top are most important.<p>I use labels pretty heavily too such as red for BLOCKED.
I use Google Keep app for short lists. For more involved projects, I use Trello. When neither of these are available, I use a simple text based file with markdown.
after trying many apps and tools like trello, todo lists, a simple .txt file. I found that the most useful thing for me is just a pen and a small notebook and write the things down and cross them out when it's done