# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 10
# self = https://watcher.sour.is/conv/pvgxmca
will
twtxt.net
View Thread
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
tkanos
twtxt.net
View Thread
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)
will
twtxt.net
View Thread
Maybe I should just make a new branch for each line of code? ๐Ÿค”
eaplmx
twtxt.net
View Thread
@will 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
will
twtxt.net
View Thread
thanks guys these are some good ideas ๐Ÿ˜Š
prologic
twtxt.net
View Thread
@will I of course use git.mills.io -- But @eaplmx 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 ๐Ÿค”
prologic
twtxt.net
View Thread
@will I of course use git.mills.io -- But @eaplmx 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 ๐Ÿค”
justamoment
twtxt.net
View Thread
@eaplmx @will 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.
abucci
anthony.buc.ci
View Thread
@will It depends.
- If there is existing code I plan to modify, I use TODO:, FIXME: etc. Sublime Text has a nice plugin called Todo Review that you can run on a project to produce a report of all your TODOs and FIXMEs (or any other tag you want). The report is clickable so you can click any instance of a tag and be taken to the spot in the code where the tag is located
- If there is existing code I plan to add significant features to, I usually use issues/enhancements in gitbucket (another self-hosted github clone like gitea)
- If I'm still planning, I use a kanban board of some kind. I like kanboard, which is a self-hosted web app, but lately I've been using Obsidian for general notetaking and it has a kanban board plugin that is pretty handy
lyse
lyse.isobeef.org
View Thread
@will It depends on several factors. Smaller stuff will just get a TODO comment right in the code itself. For bugs I sometimes use FIXME instead, but that's getting rarer over time. It's super easy to just grep -rn TODO and find all open TODOs. I don't find this messy but actually rather elegant.

Bigger stuff like a new feature goes in the README for my private stuff. I never used a dedicated TODO file, always just threw it in the README. At work we of course use a ticket system, so I create a story/task/whatever there. For open source projects I use whatever the project figured out worked for them. But I usually don't add TODOs in open source projects.