3 ms·
I think it might be more useful to store a summary of the key decisions, but with mistakes, AI fumbles, iterating on test failures, and all the noise boiled out
by ltbarcly3 2mo ago
I think it might be more useful to store a summary of the key decisions, but with mistakes, AI fumbles, iterating on test failures, and all the noise boiled out. If you kept, maybe as part of the commit log a summary of the AI discussion leading to that commit I could set that as very valuable.
- rufasterisco 2mo agoI went there, and walked back to full sessions, mostly to be able to resume chats. As a general principle, why would i want to lose precision? A senior might care about seeing a junior conversation to provide advice. A colleague might spot another one making as different assumptions about X, and have a chat about it. AI grepped file XX instead of XY and made a wrong decision based on that. An engineering manager might care about completely different metrics. But to your point, think it's fair to say that there isn't a single correct answer to this: different people like different stuff and at eventually standards will emerge (or not).