patrickdevivo

I'm working a lot on https://www.tickgit.com, which is a glorified TODO comment finder for developers, to help us do simple project management in code.

It identifies code markers such as TODO, FIXME, HACK, XXX, etc (soon to be customizable) and surfaces them as cards in a web UI. There's a free and open-source CLI as well.

The web app is free for public repos and $3/month for private ones. I'm looking to add organization/team-based pricing soon too.

A feature that I'm hoping will have an impact will be a "TODO reminder" email that will email you within a configurable amount of time after a TODO is added to a codebase.

Right now it's just me working on it outside of the day job, I'm hoping I can turn it into a useful tool for developers!

the code is very clear and well commented! Nice work! could it be hooked into a notebook for visuals? I'm not sure if GitHub displays those well. Also, the # TODO comments: https://www.tickgit.com/browse?repo=github.com/llinsky/pande... in case you're interested!

thanks for the feedback! that's a really good point re non-mac users and I will start working on improving that experience

IIRC, https://harperdb.io/ might be somewhere up that alley?

this looks pretty awesome

And the github repo: https://github.com/verdaccio/verdaccio

or possibly there's a "time decay" element where more recently "popular" repos are prioritized, not just based on absolute start/fork count

This is really cool! Awesome work. I assume you've seen https://sourcegraph.com/ as well? This to me seems much clearer and a bit more intuitive (though I've only spent a little time in sourcegraph). Really really cool. Does it also search code comments?

Ah interesting! Thank you for the context, that makes a lot of sense. I notice all of them (well, haven't checked all 24k, but many of them) link to https://bugs.chromium.org/p/chromium/issues/list, and I wonder if that's ensured by some sort of policy or CI rule

My go-to are Next.js (https://nextjs.org/) and Hasura (https://hasura.io/). Graphql has a bit of a learning curve if you haven't worked with it, but those two tools deliver a pretty amazing developer experience.

Next.js is react + ssr + routing and more. Hasura exposes an auto-generated graphql API in front of a postgres instance, with hooks for auth/authz and much more.

I think this is an awesome idea, and I would totally use it. I do agree with some of the comments about the added weight of slack where possibly just an email could suffice. Or at least having the ability to tweak how I'm notified with a custom webhook option.

I think the value proposition is solid for just anyone on a team working in a medium-large sized codebase, where for some period of time, one person may only really be interested in changes to source in one particular subdirectory or file.

It might be silly, but I wonder if there could be value in the inverse of this - alert me when a file or certain parts of a codebase have not been updated in some time (6 months+ say). It could be a good indicator that maybe a feature/section of code ought to be reviewed again. Maybe even have the notification be based on the average time between changes in other files, not necessarily absolute timeframes.

For anyone interested, I wrote a piece last week taking a look at the 2k+ TODOs in the Kubernetes source code as well: https://medium.com/@augmentable/looking-at-kubernetes-2k-tod...

Most were from over a year ago.

I don't think TODOs are bad practice, and I've seen a diversity of opinions on them in the comments of various posts. I think they are notoriously forgotten, and major codebases like linux and k8s are no different.

Aggressively stale TODOs though are likely an indicator of an area of code that should probably be revisited or cleaned up.

Sorry about that! Didn't realize this would hit the frontpage, infra should be upgraded!

Creator here - this was a total pet project and no idea it'd hit the front page. Upgrading the infra now to handle the load . Sorry for the error rate

Hi everyone, I don't post here much, but wanted to showcase an idea I recently started playing with to see if it makes any sense. I'm curious to know what project management using git looks like, and if there's any value in tracking tickets for a codebase, within the codebase itself. There's more detail enumerated in the github repo, please share if you have opinions!