Skip Navigation

Question for software developers: how do you organize your To Do list at work?

I'm asking because I'm wondering if there's a more efficient way for me to handle my notes at work. Currently I just use a txt file in Notepad++. I use this file to track all of the stuff I have to do, such as tasks for stories I'm working on, next steps for projects, discussions I need to follow up on, questions and ideas I want to bring up, etc. The way I organize the document works pretty well for me, but I'm just curious how other people do it.

49 comments
  • 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.

  • 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.

  • 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.

  • 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.

  • I use notion which by default has a task list, kanban style board to manage each task. This way I can keep track of things I need to do eventually, things I’m currently working on, and stuff I’ve finished but might want to keep around for reference later.

  • I supplement team-based task management with post it notes on my monitor for the things I'm working on short term. Usually the Jira ticket number or a couple words about what needs done is enough, and putting it where I can't not see it keeps them from falling through the cracks.

    Plus it's fun when my boss gives me something and I can show him the post it I made

  • I work off a ticket system , Every morning I pick a ticket that looks like it is something I know how to solve and I work on it , at lunch I talk to coworkers about my task for the day and get their input and in turn I give my input to their tasks , then with luck I have the problem solved by 5pm when I go home for the day. I might continue to work on the ticket the next day or I might update the ticket as solved or unsolved as appropriate.

  • Same but s/Notepad++/nvim/g. I use a markdown-like list system.

     
        
    + [X] Task One
    + [ ] Task Two
    + [ ] Task Three
    + [X] Task Four
    + [ ] Task Five
      
49 comments