Show HN: Toodles – Project management directly from the TODO's in your code

Post by aviaviavi » Thu, Oct 25, 2018, 7:01 PM UTC

tln wrote: post #14

Looks interesting! I'm looking forward to trying it. The annotation syntax looks powerful but do people really edit thier code to adjust priorities and assignees? 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 pr…

Post by aviaviavi » Thu, Oct 25, 2018, 7:42 PM UTC

0xffff2 wrote: post #22

aviaviavi wrote: post #21

Earlier quoted context omitted.

> 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 :)

Do you open PR's before you start writing code? How do you know what number to fill in?

Post by tijs » Thu, Oct 25, 2018, 8:22 PM UTC

ryandrake wrote: post #12

newhouseb wrote: post #4

We used something like this on the teams I lead at Dropbox to (what I felt) was great effect. We had a script that would regularly run and sync with Phabricator, our bug tracking tool of choice. 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…

> One thing that we did differently, however, was to "assign" TODOs based on project or team rather than individual people. 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 pi…

Post by exabrial » Thu, Oct 25, 2018, 8:30 PM UTC

Post by aviaviavi » Thu, Oct 25, 2018, 8:38 PM UTC

tijs wrote: post #25

ryandrake wrote: post #12

Earlier quoted context omitted.

> One thing that we did differently, however, was to "assign" TODOs based on project or team rather than individual people. 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 pi…

* differentiate between backlog and ready for development: (bi)weekly triage * bugs first, then code reviews, then features * order features by priority; PM? Triage as well? * work ready for development list top to bottom 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 scar…