Org-mode FTW! You only need to know emacs for it, which you can master in just a couple of measly decades.

Jokes aside, org-mode is unironically incredible. I use something called Getting Things Done (GTD). I do not regret spending some weeks truly learning about it.

deleted by creator

I use todo.txt format, created my own cli https://github.com/jecxjo/todo.hs

I set up tasks with priorities:

• A: tasks i am doing now/today
• B: tasks i am planning on soing this week
• C: tasks that need to be done but aren’t high priority
• D: tasks I delete if not done by the end of the month

I make sure all my tasks have a +ProjectName and if i have to deal with a @SpecificService or @EmployeeName i note that. I will also add in things like jira:StoryNumber or other data.

Due dates are rare, only when there is a hard stop. End of a sprint is not a hard stop. If i need to remind someone I’ll use due date and @Reminder

100% of the time all tasks go in my list. Nothing is left for me to remember. It goes into my list before it ends up in a Jira ticket or Conflience page. Remind me first, everyone else second.

First thing in the morning i process my list. Move tasks to A. End of the week at the end of the month I delete all the D tasks.

As for notes, i use vimwiki with automation to compile into html when files are written. I’ve also setup coworkers with an automated process using pandoc to go from markdown to html. Then i have a little a bookmark on my browser to pull it all up nice and pretty. I’ll post the scripts later, not at my computer.

Daily diary entry made every morning when i do my todo list prep, entry for each meeting. Add notes during meetings and links or other details when looking for solutions to problems.

Well, there is Jira with the tickets of course, but when I’m working actively on a ticket I do two things:

1. Text file in Notepad++ (something with custom markup so I have regions) or recently OneNote (just so this crap is backed up), write my hours down before putting them into the system, current ToDo things, notes, etc. till the ticket is through. Anything actually worth keeping gets puts into the Jira ticket as comment on close

2. While working on the code and I need to do something before committing it I use comments. Like // todo# do x, I’m using todo# because if I text search the code base for just todo I’ll find a hundred entries… adjust to whatever is unique to you so you find your own comments again

It’s a shit system, but has worked for me. I also write everything down so I don’t forget it, that has saved me several times.

In the past I even took my text notes and put them into an archive (with the Jira ticket linked) just if an old issue pops up and I still have my thoughts from around that time. But nowadays I do less of that because code changes too fast anyway.

I use a cheap paper notebook, like 5x8 inch size. Each day, first thing when I start work, I write the date at the top of the next blank page, copy the items from the previous page that are not done, and add new items at the bottom of the list as they come up. Tasks I haven’t started have a blank box next to them, tasks I’ve started get a half-filled box, and finished items get a filled box. Anything that moves from one day to the next that hasn’t been started gets a digit in the box that increases by one each day. If the number gets to 10 I cross the item off as cancelled. When I’m picking a new task I try to prioritize some the tasks with higher numbers.

If I need to take notes I’ll use nearby blank space, sometimes a facing page. Generally I keep notes very short, long details go into whatever ticketing system we’re using with the ticket number in my notebook so I can find it again. There are a few other habits I use that are generally in line with the Getting Things Done (GTD) productivity techniques, like simple flags for what sort of action I can take on the item (completable (about half a day or less), needs more info, needs decomposition (more than half a day of work)), with the notable difference that I don’t make any effort to ‘capture everything’. I load-shed aggressively and early, which is in-line with the way I want to live my life.

Mostly I don’t keep very many active tasks, so it’s rare that I have to cancel items. If my list is getting long I stop putting new items on it and just tell people I’m too busy to accept new stuff. I used to try to track more stuff, but I learned that just meant I ended up with lots of notes about stuff that I never had time to do, so I quite wasting my time tracking them.

When the notebook is full I put it on the shelf and get a new one.

I keep the notebook next to me on my desk. If someone asks me for something I check the book, if it looks like I’ve got time, I add it to the book. When I go to a meeting, I take it with me. If I don’t happen to have it I usually remember what’s on the current page because I just wrote it there that morning.

It’s low-tech, and I like it that way. Partly because I like to find nice pens to write with.

I used to use org-mode, then switched to markdown for compatibility across things, currently I use taskwarrior for tasks and quick temporary notes, and markdown for knowledge bases, although I’m looking into Notion instead of Markdown.

Amazed no one else mentioned taskwarrior since it’s made especially for tasks, and should be very easy for programmers since it’s CLI and very intuitive to do things and I usually have one terminal window open anyways.

Todo.txt plain text file. Use Vim. Date and todo statement. Sometimes more for explanations. I never delete anything in it; just make an X next to todo’s I’ve completed. File goes back many years. I can easily search for something I did a long time ago.

And then there’s MS OneNote for capturing howto’s, quick script one-liners, cheat sheets, diagrams, notes on various industry interfaces, etc.

Then there’s SCM for bug, feature, and track tasking.

And usually notepad paper and pen for meetings, which if there are todo’s, go into my electronic todos.txt file.

A mix of Obsidian for myself and OneNote for team stuff because it’s what they all use.

I might try orgmode now because I prefer to procrastinate with new things rather than doing work, especially when it is organization reheated because then I can tell myself there will be a net gain in work productivity.

I’ve found Notion to be quite good. I just started with a blank page, then added the date as a heading, a smaller heading for each project, then todo boxes for each task. I tick them off as I go. Then, the next day, I copy yesterday’s todos and paste it above, change the date, then delete the crossed off items. This gives me a history log off what I did on previous days, so if I forget what I did yesterday I can just look back at what I ticked off that day.

I used to use a paper notebook but found it annoying because I couldn’t add a task in between other tasks. That’s the benefit of a computer; I can move things around

There are a billion ways to organize your stuff. I used org-mode a lot in the past but it’s a bit difficult to setup, especially on Windows. Nowadays, I use a mix of GTD, https://johnnydecimal.com/, Markdown (with Sublime Text), and https://taskwarrior.org/. Don’t forget calendars too (like the one on Outlook) because you can freely add meetings or things to do inside this application.

You have to find something that works for you, there is no perfect solution. You can also ask the same question on [email protected].

Two ways:

1. I create a jira issue or
2. I send a mail to myself so I don’t forget the thing.

I always keep my mailbox clean so that I have an overview on what’s open.

A bit basic, but I have a TODO.md in my documents folder that I keep up to date. Markdown so I have an easier time formatting links to websites or other relevant documents.

I’m using Logseq. It’s a great tool to document things and connect information that belongs together. If tasks need additional details, I simply link them to corresponding resources or tags. Additionally I set up Syncthing to synchronize everything across all my devices (desktop and mobile). Takes some time to get used to, but I don’t want to miss it anymore.

Issues on jira/GitHub/gitlab/whatever is used and their planning boards. Assign them to me, put them in to-do/planned and do them until they’re all closed/to be reviewed. Occasionally I will put a reminder in the reminders app of my phone with a timed alert if I mustn’t forget something rather urgently.

Wow. Many people have digital methods. I create jira tickets because it’s required but my actual work list I follow is handwritten in a notebook. When it gets more than 50% completed I copy the incomplete items onto a new page.