Insanely inefficient. It's 10x more productive to watch the thinking traces and edits in real time and steer the model appropriately.
If your workflow is typical no wonder my team members who use claude code are so much less productive.
Insanely inefficient. It's 10x more productive to watch the thinking traces and edits in real time and steer the model appropriately.
If your workflow is typical no wonder my team members who use claude code are so much less productive.
If I work with one agent / few subagents on one feature I can steer it as soon as I notice it drifting into the direction of waste. This way I only review the total diff 1.5-2 times. And I also don't waste my own mental energy on context switching between tasks agents are producing diffs for in parallel.
If that’s what you got from my comment then you need to review it again.
When thinking first started and you would still see the whole "thinking process", I thought it was a ploy to 10x token use because it was just the most inane bullshit. "But wait, the user is asking me to" in loops.
Wasn't there a study recently that even found a model's performance was sometimes better when the "reasoning" was nonsense? As in, no clear correllation between what the reasoning says in a human's interpretation, and how the model actually did with the task.
I sometimes read the traces out of boredom or morbid curiosity. My favourite bit with Claude is how, even if you give a very comprehensive prompt in complete sentences, almost every trace will contain a variation of "the user asks me to X, but their thought cuts off mid-sentence."
Fever dream.