3 ms·
They could read the whole git history and have all issue tracker tickets in the context, and maybe even recordings from meetings. It remains to be seen though i
by manmal 1y ago
They could read the whole git history and have all issue tracker tickets in the context, and maybe even recordings from meetings. It remains to be seen though if such large context will yield usable results.
- ttoinou 1y agoDo we already have tools to do thar automagically ?
- manmal 1y agoYes there are MCPs for git and Jira. I‘m not sure about the utility with the current context sizes.
- eMPee584 1y agoThis. Git ( / tig!) blame and log -p --stat -S SEARCHSTR are extremely powerful for understanding the what why and when about code..
- Cthulhu_ 1y agoI find most meetings I'm in nowadays are mostly noise; there's no clear "signal" that "this is the outcome", which I think is what an AI should be able to filter out. Of course, it'd be even better if people communicated more clearly and succinctly.
- manmal 1y agoMaybe time to find an employer with a better culture? I rarely have meetings that I would be comfortable skipping.
- internet_points 1y agoThat also leads to more noise and opportunities to get lost in the woods.