▲ | manmal 2 days 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. | ||||||||
▲ | eMPee584 2 days ago | parent | next [-] | |||||||
This. Git ( / tig!) blame and log -p --stat -S SEARCHSTR are extremely powerful for understanding the what why and when about code.. | ||||||||
▲ | Cthulhu_ 2 days ago | parent | prev | next [-] | |||||||
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. | ||||||||
| ||||||||
▲ | internet_points 2 days ago | parent | prev | next [-] | |||||||
That also leads to more noise and opportunities to get lost in the woods. | ||||||||
▲ | ttoinou 2 days ago | parent | prev [-] | |||||||
Do we already have tools to do thar automagically ? | ||||||||
|