5 entries
Across 267 tracked sessions, 62% last under 10 minutes. Long sessions (>1h) account for only 15% of the total. The micro-session is the real productive pattern — not tool underuse.
The agent types code faster than I do. That was never the bottleneck. Across my tracked sessions, most last under ten minutes, half go down the wrong approach, and a small minority end in a commit. The blocker didn't disappear — it moved, from writing to framing.
An agentic workflow isn't about "using AI to code faster" — it's a restructuring of how you break down, delegate, and verify work. The real gains come from three practices: decomposing tasks into verifiable units, actively managing context, and treating the agent like a competent junior who needs precise instructions.
Across 128 auto-scored Claude Code sessions, 68 had a "wrong_approach" friction — 53%. The agent's first instinct is wrong half the time. This isn't a problem to fix, it's a pattern to integrate into the workflow.
Three patterns that naturally emerged in a daily agentic workflow: automated morning briefing, versioned custom commands in Git, and parallel sessions in tmux splits. Each came from a real friction, not from theory.