This post was originally posted on my blog
I wanted to share a simple, yet powerful technique I discovered during my 2nd year as a software develo...
For further actions, you may consider blocking this person and/or reporting abuse
Neat idea. I've been using a single huge "todo.txt" but might try out this one-TODO-a-day.
Here's a script to automate the file creation:
$ echo ~/bin/newtodo
I didn't recognize this as a valuable approach until I recently started a new job, stopped keeping this kind of list, and your article made me realize why I've been feeling so unorganized.
I follow your approach but use a weekly instead of a daily file, and use three sections, inspired by GTD:
Thanks for helping me realize what I was missing.
So glad this was helpful! I've definitely fallen off the wagon for periods of time in the past, and I always end up having that same feeling of disorganization and anxiety about my workload. Coming back to keeping my TODO list always helps a lot. Good luck!
Absolutely Great Idea. Best way to reflect back that you have done in the past. One other way it helps me, is that while entering time sheets I no longer wondering about what the heck that I did last Tuesday. I work in a smaller team, where the priorities gets changed so frequently. This habit helps me to track the work that I have done also helps me to focus on the task at hand for the day.
I use "Evernote" for my work. I have a separate notebook titled, "Work Log". Every day, I start my day with a todo list of tasks to be done and start with that. I add additional notes below that.
For example this is my work log from last week 13th of July, 2017,
13 July, 2017
Todo:
[x] Create Repo for *** design
[x] Escalations
[x] Shawn’s issue with ****
[x] API testing using postman app
[x] technical tasks proposal
[ ] Study the *** design
...
Escalations:
Shawn’s issue
I will create a new note, if a task has required lots of details. For example, technical tasks proposal.
At the end of the day, I reflect back on the tasks and mark it done if it is completed. I will add the incomplete tasks to next day based on the priority. This kind of helps me keep focus and track of the work being done.
One key take away for me from this article is to limit the number of tasks. I do prioritize the work that I do but there are times where I have added bunch of tasks to be done at the start of the day and complete very few of them. Although I know that I have completed the tasks in the priority order, having bunch of in-complete tasks at the end of the day leaves a sour taste. I believe limiting the tasks to a certain number by ruthless prioritization can help me in this case.
Fantastic Article!!
Thanks so much for sharing your method! I could definitely stand to adopt EverNote as well. My desktop is littered with open TextEdit windows. 😁
I implemented something along these lines in go: github.com/apiarian/next-day-todo . I had been running this same system though Editorial on iOS for months before that, but I've lost the workflow when I moved to a new phone.
Really?
TODO.txt?
Isn’t something like GitHub Issues supposed to make that kind of stuff a thing of the past, no? Because I think I can accomplish everything of TODO.txt in an issue tracker. Heck, GitHub even has a Trello project… thing that can also help you do everything mentioned.
Don't get stuck on the medium. The underlying principles are the more important part: breaking tasks down, prioritizing, detecting when you're overloaded and quick retrieval of history of accomplishments. Most importantly, finding a minimal overhead way to consistently maintain these things every single day. Use whatever medium that allows you to do that.
But since you went there...as a unix CLI power user, you will never show me an issue tracker interface that matches the speed and flexibility of plain text files + unix command line tools. There's also no internet connection required. Downside is you have to manage your own backup solution, but it's really easy to setup a private git repo and a daily cron job that auto commits and pushes your updates to a remote repo.
Tools like issue trackers and Trello are great as soon as the number of users is greater than 1. However for the individual case, the overhead of using those tools is always greater than plain text.
Good example of why it's important to check your requirements before choosing (or prematurely rejecting) certain tools...
This sounds exactly how we work in a scrum team with the agile board of Jira.
Good observation! It really is very much like a personal agile process. I'd say it's more like Kanban than Scrum though. However a team scrum/Kanban board is no substitute for keeping this personal TODO list. Especially as your career advances, I find there's a lot that goes on the TODO list that wouldn't normally end up on the scrum board, e.g., mentoring, interviews, talks, etc. Also, never underestimate the power of text files! They are by far the lowest friction medium I've found. It's always faster to edit a text file than to update even the fastest scrum or Kanban UI. There are downsides of course and the post is about the method/practice rather than the specific medium used.
I've been using the PlainTasks package within Sublime Text. I seen it on a game development stream on Twitch, actually. Its the exact TODO workflow that I was chasing for so long. Now I've got a .todo file for each main aspect of what I do and I'm absolutely loving it.
Only problem with this is the fact that its got to be opened in Sublime for the core functionality of the package, but you can open it as a .txt file by renaming the extension.
Come to think of it, I really need to write a script which converts each .todo to a .txt file on Google Drive so that I've always got an accessible version on any device.
Great article, by the way, James!
maybe too late to the party but anyhow just want to share my current workflow for anyone that might find this helpful. Basically, I upload all of my todo's in a secret Gist. Here's a useful package to save a gist, open it and automatically update once you hit save. packagecontrol.io/packages/Gist
Totally agree. I use old fashioned pen and paper for this (almost) daily.
I generally keep the TODO part on paper, and use RescueTime to track what I'm doing and record accomplishments. (They call it Highlights, though it may not be in the free tier.) There's an API for retrieving the data later, or you can use their web UI.
Simplicity is key. If anyone wants a step up from a .txt file, I've built lanes.io. All of the above, plus a timer.
I have used to write everything in the old school style with the pen and a notebook
I'll try the text file, hope it will be better
Thanks for the article!!
I've been trying to find the best method to do this... maybe the Bullet Journal, index card, or an app of some kind. Really about the habit more than the medium I suppose.