|
I have used both. While I'm currently on Org-mode, I used to use Taskwarrior exclusively in my previous job. The switch between the two happened because my job responsibilities changed, and Org-mode is better at supporting my current role as a team lead and developer. Taskwarrior was better when I was only developing software. Personally, I feel this says something about what usage patterns the two are best for. As a developer, I spent almost all my time in a terminal. Taskwarrior (plus a few shell aliases) allowed me to create tasks the moment I thought of them. I could then get back to work and see the task list later. Switching to Emacs every time I needed to create a task would have been unproductive and I probably would not have done that. As a team lead, I spend most of my day researching, helping out team mates, building product road maps, etc. I spend time in the terminal, but not as frequently as before. And I'm not developing as much either, which means I can now take the time to switch to Emacs, capture a task or thought in Org-mode along with any details, and then get back to it later. My perspective on the two:
- Taskwarrior never gets in your way. It takes a few seconds to record a task and then get back to what you were doing. But you end up not recording many details about the task, mostly it's just the title. Great for small bugs fixes or development tasks that come up while your developing.
- Org-mode is great when you want to record details for the tasks you are recording, take notes, and just generally write anything with details. Hope this helps. |