top | item 47213333

(no title)

aspenmartin | 1 day ago

post mortems / bug hunting -- pinpointing what part of the logic was to blame for a certain problem.

discuss

order

monster_truck|1 day ago

this is what granular commits are for, the kilobytes long log of claude running in circles over bullshit isn't going to help anyone

ahupp|1 day ago

I think the parent comment is saying “why did the agent produce this big, and why wants it caught”, which is a separate problem from what granular commits solve, of finding the bug in the first place.

causal|16 hours ago

Then look at the code, the session will only confuse. To read an LLM's explanation is to anthropomorphize what will just be a probabilistic incident.

aspenmartin|13 hours ago

no you look at the session to understand what the context was for the code change -- what did you _ask_ the llm to do? did it do it? where did a certain piece of logic go wrong? Session history has been immensely useful to me and it serves as an important documentation of the entire flow of the project. I don't think people should look at session histories at all unless they need to.