One thing that we did differently, however, was to "assign" TODOs based on project or team rather than individual people. This way we could triage issues more flexibly to people according to their workloads and also build in more immunity to organizational change (when I was around we still had TODOs for the founders -- ten years in!).
If this works for your team, that’s awesome, but beware, I think you’d need a very disciplined team with good communication for this to work. I’ve found on some teams, if a task is not assigned to a single individual, nobody feels “on the hook” to do it. Things assigned to a group can tend to pile up un-looked-at, because everyone thinks someone else will take care of them. You can fix this by having some kind of rotating duty, where people pick up ownership of issues on some schedule but if you’re going that far might as well just assign directly from the start.
Looks like the tags and keyvals could cover some of that. Maybe a bit hard to express priority (or change it).
Would be neat if changes in the dashboard would update the todos in your code (bit scary though)
Also the edits you make in the UI actually are applied to the code! :D
My work flow is running a toodles server in a copy of our repo they we reserve for toodles, and commit the changes after planning meetings or similar.
I will some times look into tasks that are assigned to other people just to get an understanding on how I would solve the problem and learn the rest of the code base. I wouldnt assign it to myself unless I get approval because that would be stepping on others toes. If a dev doesnt like actively coding and isnt interested in fixing problems for the company that is not a problem with the layout that is the problem with the devs attitude.
lazy , unmotivated how ever you slice it, its unproductive. Ill say this is one reason why working at a company you enjoy is important. You should be happy to make they company better in general with small touchups or performance refactor overhauls. What good is a "todo" list if its just a list of things people wont do.
The annotation syntax looks powerful but do people
really edit thier code to adjust priorities and
On a related note, I review `TODO` in PRs and consider whether to allow them in the codebase; and `DEBUG` to indicate code that shouldn't even be checked in. Does anyone else have a codetag for this? DEBUG doesn't seem to be a well-known codetag, and I'd prefer to use something other people use.
My team now uses `TODO(#pr)`. The #pr tag meaning it should be taken care of in this pull request, but I don't think that's common. Though maybe if toodles gets some use it will become more common :)
Useful when you're putting in debug logging statements you want to remove later, or hard-coding your own credentials during development with the intent on making them configurable later, etc.
Not used it myself
If there's a way that the developers can run it without installing the Haskell suite (maybe binary releases for Windows, Linux, macOS), we will try it.
Does it ignore paths like node_modules/ and others or support command line arguments for that?
Great, I was waiting for someone to ask for a binary distribution before actually going ahead and setting it up. I'll go ahead and do that then.
> Does it ignore paths like node_modules/ and others or support command line arguments for that?
Yes, you set a list of regexes per project for toodles to ignore.
I created an issue suggesting a docker container, hope that's not annoying!
PS in case it helps others: for macOS10.12 + brew, I had to add:
I'll probably just upload some binaries to start, but that's a good next step
$ stack --version
Version 1.7.1 x86_64
...lots more output, skipped...
If you use Xcode, this link has a pretty nice script you can add as a Build Phase, and it generates warnings out or TODOs.