3 ms·
Sadly there are people who would use a tool like this to make decisions like what to pay their employees. I guessed based on the title that you might fall into
by digitallogic 13y ago
Sadly there are people who would use a tool like this to make decisions like what to pay their employees. I guessed based on the title that you might fall into that camp. Glad to hear I was wrong.
I could imagine search with some standards (commit message format, branch/rebase strategies, requiring an associated tickets) would be really effective, though not so much the general case. Hope you can share in a follow up post if you find ways to deal work around these problems.
- garysieling 13y agoThe people who've been most interested so far have either been in some type of architect role where they had some advisory involvement in what a large number of teams are doing, or people who took over a flailing project. Part of the idea of this is to show something that's useful and relatively easy to set up, it could easily show attributes other than the author - it'd be nice to tie together tickets involving database issues or browser rendering for instance. I have some material for a couple follow-ups to this, so stay tuned - dealing with code separate from natural language text is an interesting topic as well.