This is terrible. I have no desire to read your Claude conversation. I don’t even want to read mine if I do use Claude.
The code is the artifact. There’s no value in trying to make the noisy, verbose conversation one. It’ll likely be dead in future years anyway.
Also, while commenting is good, commit messages can stick around longer.
Not really. Why is always more important than how. Even what is more important. Relevancy of a particular block of code is in the specs and some technical aspecs of computing/library/platform, not in the thought process of the developer.
Fwiw i don't like a session link in the commit message, because of link rot reasons.
If the code is artisan to any degree (authored, edited, reviewed, etc.), it's a bit ridiculous.
It does makes sense to me if the human driver was hands-off the code because the conversation becomes the artifact.
I'm older, and have very mixed feelings about the latter case but it seems inevitable that engineers will be working at a higher level where conversational governance becomes important. We'll stop this charade of hiding AI contributions behind human identities. (Note: I don't think conversation IDs are what we need but it's a step down this path.)
Are they relevant questions? I've often commented on lines of code in a PR that "so and so gave me the idea".
> Or how about all the stack overflows I read?
Would be nice to link to them either in a code comment (if they're not changed very much) or again somewhere in the PR discussion
> Maybe I should voice record all the times I swore about Gary the junior dev not documenting something?
If you noticed something severely lacking that would help other people out if that wasn't the case then yes I hope you would bring it up?