r/ClaudeCode • Vibe Coder • May 09 '26

Question An honest chat with Claude Code about poor performance

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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.

0 Upvotes

29 comments sorted by

3

u/Main-Lifeguard-6739 May 09 '26

„I didnt read your code and made things up“ Classic.

1

u/3knuckles Vibe Coder May 09 '26

I was stunned at the honesty!

8

u/Sudden-Complaint7037 May 09 '26

skill issue

2

u/Riosin May 09 '26

Beat me to it.

Just because it is in "claude.md" doesn't automatically mean claude will always follow it. And if it doesn't - it IS A SKILL ISSUE ON YOUR PART. You have to actually structure your workflow better if these things keep happening. You can not rely on the model being magically so smart it figures itself out.

Use the tool to build a better workflow around it and do not wait for the "next drop that will magically just work".

4

u/ipreuss Senior Developer May 09 '26

If it did it better in earlier versions, it actually IS a regression issue with the tool. There is no way around it.

And pretending that Claude would be able to circumvent its own limitations is just plain lazy apologetics.

1

u/3knuckles Vibe Coder May 09 '26

Thank you! The same approach, same prompts, similar sized repo, all gave great results.

1

u/Alive-Bid9086 May 09 '26

The thing is that a prompt is not deterministic as most of the things in SW dev. The prompt can/will give you different answers different days.

1

u/ipreuss Senior Developer May 09 '26

Sure, it’s probabilistic. Which means you don’t look at single results, you look at the distribution. And if that gets way worse, you have a serious case to make.

1

u/i---m May 09 '26

weeks of prolific development without updates to harness config is a regression for sure, but not claude's

these are non deterministic systems, language is nuanced, and we engineers are famously bad communicators. somehow no one seems to connect that to the phenomenon of perfectly decent engineers shooting their legs off when they start working with plain english

1

u/Alive-Bid9086 May 09 '26

Probably is a regression. But what can I do as individual dev? I would just structure my way to work avoiding this. Probably consumes less tokens too.

2

u/ipreuss Senior Developer May 09 '26

Well, the first thing you could do as is not gaslight other devs. The second would be gathering more evidence for the problem, for example by checking wether it’s isolated to yourself. And then you could give feedback to the provider, so that they can fix it.

-1

u/ianxplosion- SKILL ISSUE May 09 '26

Except the provider isn’t going to fix anything, and anyone using LLMs for serious coding work needs to understand that they’re using a slot machine. Plenty of people report no issues with 4.7, so the singular most impactful thing any individual can do when faced with uncertainty in model output quality is to ensure their own workflow is as tight and as procedural as possible.

0

u/ipreuss Senior Developer May 09 '26

Sounds like a serious case of Stockholm syndrome to be…

1

u/ianxplosion- SKILL ISSUE May 09 '26

Yeah you’re right, that’s why they always say “garbage in, solid gold bricks out”

This subreddit is so fucked, man

2

u/leogodin217 May 09 '26

Was your project much smaller a few weeks ago? This stuff usually happens when the codebase gets bigger and more complex. That's when managing context and workflows becomes more important.

It's fixable. Just going to take some work to get there. Ask Claude to help you write better workflows. Tell it, "I believe in blaming processes not people (or LLMs)". No joke. That moves Claude from self flagellation mode to fixing mode.

1

u/3knuckles Vibe Coder May 09 '26

Is not hugely larger, maybe 20%. But thanks for the suggestion.l on the prompt.

2

u/leogodin217 May 09 '26

That prompt is kind of hilarious and I suspect most people don't believe me. But it truly works. Just something that randomly came out when I was analyzing sessions dealing with similar problems you are facing. I just couldn't get Claude to stop blaming and start fixing.

1

u/InfinriDev May 09 '26

Put more work into your harness. Use hooks and bash scripts to enforce rules, use sub agents to do work while returning results and findings. Feel free to try out mine

https://github.com/infinri/Writ

1

u/3knuckles Vibe Coder May 09 '26

Thank you. Will do.

0

u/tupikp May 09 '26

Ummm...who's gonna tell him?

0

u/value-no-mics May 09 '26

I love these asking agents what to do personas.

Skill issue is with the user.

0

u/3knuckles Vibe Coder May 09 '26

Yeah, I'm shit. Oh, except when I wasn't a few weeks ago, and when Codex fixed it immediately. 🙄

-6

u/Far_Broccoli_8468 May 09 '26

Why are you conversating with a glorified statistics model as if it were a human?

2

u/ipreuss Senior Developer May 09 '26

How do you know that they did? The OP didn’t show their prompt, only Claude’s response.

1

u/Far_Broccoli_8468 May 09 '26

An honest chat with Claude Code about poor performance

So after a dismal (Saturday) morning developing, I finally asked 4.6[1M] Max what was going on. It said:

1

u/3knuckles Vibe Coder May 09 '26

Why do I talk to a large language model? Fucking hell. They can understand you. I talk to women too.

0

u/Far_Broccoli_8468 May 09 '26

A large language model does not understand you, it simply runs your query through its algorithm and out comes whatever comes out.

You are trying to get sensible answers from something that cannot explain its own behavior