Comment by manmal
2 months 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.
2 months 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.
This. Git ( / tig!) blame and log -p --stat -S SEARCHSTR are extremely powerful for understanding the what why and when about code..
I 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.
Maybe time to find an employer with a better culture? I rarely have meetings that I would be comfortable skipping.
That also leads to more noise and opportunities to get lost in the woods.
Do we already have tools to do thar automagically ?
Yes there are MCPs for git and Jira. I‘m not sure about the utility with the current context sizes.