Comment by eru
13 hours ago
> Its much the same problem as asking, for example, if every single line you write, or every function, becomes a commit.
Hmm, I think that's the wrong comparison? The more useful comparison might be: should all your notes you made and dead ends you tried become part of the commit?
When a human writes the code should all their slack messages about the project be committed into the repo?
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
Ideally, yes. Although Slack is a vendor lock-in and we need a better platform to archive the sessions.
Here is a recent example that lack of archived discussion causes problem: https://github.com/triton-lang/triton/issues/9539
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?
In some cases this is what I ask from my juniors. Not for every commit, but during some specific reviews. The goal is to coach them on why and how they got a specific result.
What is a junior? I don't see it in claude.
It's how a middle manager can improve its standing, so the Junior will be a thing in bigger orgs for quite a while.