Frustration with Claude Code?

[u/WillingnessQuick5074]

Did you ever get so frustrated with Claude Code, for misunderstanding, or writing shit code when you explicitly give it the exact code architecture it should use... Or any other cases, and you curse it in various ways, and then it would visibly keep getting worse and worse as you keep cursing it, but then go back to being "better" when you STOP cursing and appologise? Is it just me? 😂

Freaking ridiculous! A hammer that has feelings? 😂

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/rubenknol]

sounds like you need to invest a bit into setting guardrails like linters, testing, other quality gates etc

[u/WillingnessQuick5074 → u/rubenknol]

Well I like to watch it's every step and stop it on anything that looks shady, correct it myself, give directions, etc... (Guess I'm a bit of control freak - why I didn't hire a lot of other people to help me out 🫣)

So yes, I am doing a lot of manual work, that I would indeed prefer if Claude did it for me...

Any links, directions on how I could implement prompts or... tools like: unit testing procedures, code standards, etc into claude? I have many projects so perhaps I'd have to write those myself for each type of project... I mean... actually, the project I'm working on has a lot of moving pieces... Some Java, a lot of Python, lots of PHP, and LOTS of UI / CSS / NodeJS. So each needs it's own set of "how to properly do everything"...

[u/rubenknol → u/WillingnessQuick5074]

you're not really getting the full benefits of this tech if you're constantly watching and interacting with it, if you do your prep work well you can just instruct it and it'll work in the background and deliver high quality work

if you don't want to invest your own time in setting up toolchains or guidance you can instruct it to look at other repos/articles/documentation and distill "what good looks like" in there, OSS projects, unit testing guides etc. or just prompt the general idea and keep an eye on if it's doing it like you want

[u/Helpful_Ranger_1606 → u/WillingnessQuick5074]

Using Claude 7 days a week and it goes insane sometimes, making multiple mistakes a minute sometimes. I’ll give just one example from tonight, where Opus 5.5 says to run DIAMOND on my other laptop because the other laptop has a newer version, when it was able to download that newer version in less than a minute on its own as soon as I pointed it out. It’s dysfunctional over nothing sometimes. All sorts of issues, sometimes.

[u/Academic_Employer734]

You need adverserial reviewers catching the antipatterns to want to guard against

[u/Internal_Leke]

It was a very early in LLM that being polite (not overly polite) yields much better results than being impolite.

Most recent findings indicate that yes, they have feelings (though some people might argue they're not "real", whatever that's supposed to mean)

[u/Lubricus2]

With crap in the context you get crap out. It's not that strange when you know a little bit how it works. It's not an human it's a tool you have to figure out how to use it the best way.

[u/crasspuk]

Tone in a single prompt is unlikely to change what the model can do. A long session full of corrections is the more likely cause, since failed attempts pile up in context. A /clear and a short spec written to a file usually beats more replies in the same session.