I keep a daily log like this at my job. Basically, if I have a list to-dos, I add them to today's log and if they don't all get done, I copy-paste them into tom

I keep a daily log like this at my job. Basically, if I have a list to-dos, I add them to today's log and if they don't all get done, I copy-paste them into tomorrow's entry. Like the author, I tried various productivity apps (even created my own to-do app), but the one constant for the last 15-20 years of working for me is the daily log. For my personal coding projects, I just keep track of tasks using a TODOs.md file. Whenever I encounter a new bug, a design idea, feature request, etc., I add it to the file. I check off the items as I do them and move them around the file to keep it easy to find incomplete tasks. Here's an example of one: https://raw.githubusercontent.com/allenu/slouchdb4/master/TODOs.md https://raw.githubusercontent.com/allenu/slouchdb4/master/TO... The big learning for me is simple tools are often good enough. Just get things done and don't worry too much about complicated tools or workflows that you may end up getting tired of and ditching.