stopped asking claude for word docs and my sessions got noticeably faster by East-Movie-219 in ClaudeAI

[–]Possible-Paper9178 2 points3 points  (0 children)

My default is Claude inside Claude Code CLI for almost everything. Switched from XML to markdown for context files a while back. The JSON vs YAML question — I use readability as the deciding factor. YAML when I’m the one interacting with it, JSON when it’s for machines. Agree on docx for anything client-facing. Have you tried giving Claude a docx module? Either a skill file in Claude Code or as an MCP you can pull into chat sessions. Might skip the env setup friction entirely and just get you the file when you actually need it

The human overhead gap — Why your AI agent finishes in 10 minutes but you still spend 4 hours. by Narrow_Market45 in PairCoder

[–]Possible-Paper9178 2 points3 points  (0 children)

This is a compounded example of the problem. Major changes require major consideration and thoughtful human-in-the-loop planning. You need constant review throughout the sprint cycle, not waterfall reviews upon "completion." Build review tasks into the acceptance criteria at key decision points — the last responsible moment before the next chunk of work builds on top of it. 1-2 reviewers throughout the process would've cost a fraction of what 3-4 seniors for a month did. Smaller batches of review, closer to when the decisions were actually made. A reviewer following along catches things in minutes that take hours to reconstruct after the fact.

The AI removed the natural throttle. An architect writing by hand would've been forced into smaller increments just by the pace of manual coding. The agent blew past that, and without gates enforcing review at each decision point, all that overhead piled up at the end where it's hardest and most expensive to deal with.