3 ms·
> Maybe we should just commit the signature change with a TODO I'm fascinated that so many folks report this, I've literally never seen it in daily CC use. I c
by zingar 6mo ago
> Maybe we should just commit the signature change with a TODO
I'm fascinated that so many folks report this, I've literally never seen it in daily CC use. I can only guess that my habitually starting a new session and getting it to plan-document before action ("make a file listing all call sites"; "look at refactoring.md and implement") makes it clear when it's time for exploration vs when it's time for action (i.e. when exploring and not acting would be failing).
- dabbledash 6mo agoI wonder if it has to do with how often TODOs appear in the existing code.
- zingar 6mo agoWhat's your hypothesis about the relationship between TODOs and action?
- dabbledash 6mo agoI have only seen "go do X" result in CC adding "TODO: X" to the working file on one occasion. When it happened, I noticed that the file contained a very similar todo for a similar action already. My guess is that because the agent had the whole file in context, that influenced it to produce output similar to what was already there.