On: If AI writes code, should the session be part of the commit?

[panarky]

When a human writes the code should all their slack messages about the project be committed into the repo?

[blharr → panarky]

Ideally, yes? Or a reference ticket number pointing to that discussion

The main limitation is the human effort to compile that information, but if the LLM already has the transcript ready, its free

[woctordho → panarky]

Ideally, yes. Although Slack is a vendor lock-in and we need a better platform to archive the sessions.

[eru → woctordho]

You can scrape slack when you make the commit, and archive that.

[woctordho → woctordho]

Here is a recent example that lack of archived discussion causes problem: https://github.com/triton-lang/triton/issues/9539

[fragmede → panarky]

That would be amazing! In the moment, it's a lot of noise, but say you're trying to figure out a bit of code that Greg wrote four years ago and oh btw he's no longer with the company. Having access to his emails and slack would be amazing context to try reverse engineer and figure out whytf he did what he did. Did he just pick a thing and run with it, so I can replace it and not worry about it, or was it a very intentional choice and do not replace, because everything else will break?