How do people who write a lot of code keep track of stuff they plan to write but haven’t? Just curious. I usually write #TODO and then whatever. Often a placeholder function or something. Seems messy tho

I usually have 2 ways :

• Todo on the readme file
  
• create my own tickets (github issues, or jira, or … depending on the system I am using)

Maybe I should just make a new branch for each line of code? 🤔

@will@twtxt.net I use this one https://frantic.im/project-todo/

And I connect the TODO comment in some random file, to the TODO list to remember where it is.

And searching for open TODOs in the project is usually something good to do every week or so

thanks guys these are some good ideas 😊

@will@twtxt.net I of course use git.mills.io – But @eaplmx@twtxt.net link to that post on using a text file is brilliant! It even looks like Markdown actually so you could even render it nicely, hmmm gives me some ideas 🤔

@eaplmx@twtxt.net @will@twtxt.net I use some custom aliases to have this workflow:

• nn: “New Note” create and link a notes.org file in my pwd from a common git synced repo
  
• n: Search recursively a notes.org for pwd up to ~/ and open it.
  

For quick tasks I use a todo.txt and display the tasks for “today” with conky on my screen.

All file are in a single repo I can sync on my phone and use the apps “orgzly” and “todo.txt” to edit them on the go.

As of writing style I write down in org-mode as iterations of the current project with sub tasks tree for what I need to do.

I tend to use the # TODO: as a “What you where doing yesterday.” in my code.