[rfw300]

I have little doubt where things are going, but the irony of the way they communicate versus the quality of their actual product is palpable.

Claude Code (the product, not the underlying model) has been one of the buggiest, least polished products I have ever used. And it's not exactly rocket science to begin with. Maybe they should try writing slightly less than 100% of their code with AI?

[rfw300]

More generally, Anthropic's reliability track record for a company which claims to have solved coding is astonishingly poor. Just look at their status page - https://status.claude.com/ - multiple severe incidents, every day. And that's to say nothing of the constant stream of bugs for simple behavior in the desktop app, Claude Code, their various IDE integrations, the tools they offer in the API, and so on.

Their models are so good that they make dealing with the rest all worth it. But if I were a non-research engineer at Anthropic, I wouldn't strut around gloating. I'd hide my head in a paper bag.

[rhubarbtree]

I don’t think that’s fair. ChatGPT and Gemini also seem to suffer random outages. They’re dealing with high load on a new type of product.

But it’s also true that Anthropic products are super buggy.

[jaapz]

It's almost as if a lot of anthropic's stuff is vibecoded

[jopsen]

Even when it's operating normal the webapp is constantly crashing.

Mobile app stops working..

It's a pain.

At least right now.

[bennycha]

I find the GitHub issue experience particularly hellish: search for my issue -> there it is! -> only comment "Found 3 possible duplicate" Generated with Claude Code -> go to start.

[jarjoura]

I am constantly amazed how developers went hard for claude-code when there were and are so many better implementations of the same idea.

It's also a tool that has a ton of telemetry, doesn't take advantage of the OS sandbox, and has so many tiny little patch updates that my company has become overworked trying to manage this.

Its worst feature (to me at least), is the, "CLAUDE.md"s sprinkled all over, everywhere in our repository. It's impossible to know when or if one of them gets read, and what random stale effect, when it does decide to read it, has now been triggered. Yes, I know, I'm responsible for keeping them up to date and they should be part of any PR, but claude itself doesn't always even know it needs to update any of them, because it decided to ignore the parent CLAUDE.md file.

[abustamam]

Sometimes the agent (any agent, not just Claude — cursor, codex) would miss a rule or skill that is listed in AGENTS.md or Claude.md and I'm like "why did you miss this skill, it's in this file" and it's like "oh! I didn't see it there. Next time, reference the skill or AGENTS.md and I'll pick it up!"

Like, isn't the whole point of those files to not have to constantly reference them??

[nonethewiser]

What bugs have you encountered? It's been a smooth experience for me.

[yaur]

Not a big exactly but if pip doesn’t work it goes straight to pip —break-system instead of realizing it needs a venv

Also if a prisma migration fails it will say “this is dev it’s ok to erase the database” before rerunning the command with —accept-data-loss

[abustamam]

Given how many projects I've seen that run prisma migrations on prod from their local CLI instead of CI...

This scares me.

[Aeolun]

Still better than the codex or gemini cli though :)