Comment by vehemenz
1 day ago
If one builds something with an agent, the process itself is largely opaque. Preserving the transcript shows the reasoning of the agent and the decision process of the builder. This way everyone's on the same page instead of re-prompting same CLAUDE.md but with different results, and/or going through similar work over and over again.
I understand the point, but shouldn't the code be documented and well structured so that the intent is clear without looking at the discussion around changes?
I'm working on a legacy system right now - I'd commit several felonies just to have well documented code, I don't really care about all the conversations that the original team had to decide what they eventually did.
Maybe I'm just too old and don't get it.
surely you could imagine that being able to sit in on a meeting that was had when they were designing the system would be useful for you?
theres a lot of context and decision making that is useful but not documented in the code. The code tells you how the system works, not how its supposed to work.
This is just the classic rehash of are comments in code an anti-pattern.
I tend to agree that at a certain point if you need to constantly think "gee, I wish I was in the meeting when they came up with this" the code you are looking at might just suck.
In such contexts it is also often the case that being in the meeting may not have helped. As they say, garbage in, garbage out.
1 reply →