Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

41–46 of 46 posts

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

#41

Post by adrianmsmith »

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…

FWIW I have seen tag NOCOMMIT used to indicate that a commit should be rejected by a pre-commit hook.

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.

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

#43

Post by tln »

adrianmsmith wrote: post #41
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…

FWIW I have seen tag NOCOMMIT used to indicate that a commit should be rejected by a pre-commit hook. 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.

Exactly! Thank you

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

#44

Post by tln »

camtarn wrote: post #37
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…

We used FIXME to denote temporary changes that shouldn't be checked in, or sections which hadn't been written yet, and had a Git hook which stopped code being committed with that tag. (It also looked for 'console.log' and 'debugger' statements in our JS and blocked those, too.)

FIXME is definitely a recognizable codetag, I'm glad to hear other people have found a similar use.

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

#45

Post by honestlyidk »

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…

looks like the team was lazy in some regard or some other negative adjective if "lazy" is too mean: -dev has extra time -queue has tasks ready to be done -dev doesnt do tasks becuase they are not specifically assigned to them

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.

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

#46

Post by LeonB »

mgalgs wrote: post #42
LeonB wrote: post #39

This is great. Aaaaand here’s a Microsoft patent covering it: http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=6,748...

Wow... Out of curiosity, how did you find this?

Someone left it as a comment on my blog 10 years ago when I talk about Todo driven programming. I remembered this happening.
Post reply on HN