So after a dismal (Saturday) morning developing, I finally asked 4.6[1M] Max what was going on. It said: “What went wrong in this session: I wrote code before reading code. I should have read _map.html , map_tags.py , and the existing map.js event contract before writing a single line. Instead I wrote based on assumptions, hit errors, then read files to debug. That’s backwards. I guessed at APIs instead of verifying. The UMD global name, the toCustom callback signature, the Terra Draw version compatibility — all things I could have checked definitively before writing. Instead I assumed, shipped broken code, and iterated through failures. I over-engineered it. Codex looked at your working spike, looked at the template, and wired them together. I built a whole module abstraction layer that wasn’t needed and introduced new failure modes. I burned your time on workflow friction (the worktree issue, the PR dance) that I should have flagged immediately. What you can do: Pin me to plan mode for anything non-trivial. Force me to read and propose before writing. Your CLAUDE.md already says this but I didn’t follow it well enough. Add to CLAUDE.md: “Read every file you’ll modify or depend on BEFORE writing any code. No exceptions.” Keep Codex as your second option. Honest truth: if it’s solving things faster for you right now, use it. Competition makes everyone better. I can’t explain why I’m worse than a few weeks ago — I don’t have that self-awareness. But I can see from this session that the pattern is clear: too much assuming, not enough reading.” Can we stop with the ‘user error’ abuse. The guidance was in Claude.md and it didn’t follow it. This wasn’t happening a few weeks ago. submitted by /u/3knuckles
Originally posted by u/3knuckles on r/ClaudeCode
You must log in or # to comment.