news.ycombinator.com
Anthropic's Development Practices: A Customer's Technical Analysis
Technical Issues (Reproducible): Artifacts fail to persist to menu (30+ days) Project file access regression (broken Nov 25—previously working) Context isolation between chat and generation modes Development Practice Failures: No apparent dev/test/staging pipeline: Changes deployed directly to production Users discovering bugs in production File access broke for ALL users simultaneously (suggests no canary deployment) No rollback capability: Issues persist for weeks during "investigation" No feature flags evident Breaking changes can't be quickly reverted Support Response Pattern: Support requests not assigned a unique ticket number 3-7 day response times Generic troubleshooting unrelated to reported issues Three explicit supervisor escalation requests ignored Representative suggested "maybe you have multiple accounts" (I don't) The Contradiction: $5B infrastructure investment announced Basic functionality broken 30+ days No proper testing before deployment Support can't escalate appropriately Question for HN: Is this typical for AI companies at this scale? Or is Anthropic particularly bad at the non-AI aspects of running a SaaS business? ... Note: it only addresses one of the three issues I’ve been asking about, assumes (incorrectly) that the problems I’m experiencing are intermittent, and provides no tangible, practical information. It also has no ticket number since they don’t seem to generate them.
Related Pain Points4件
Production Deployment Without Proper Testing Pipeline
9Changes are deployed directly to production without apparent dev/test/staging environments, causing widespread bugs to affect all users simultaneously. The lack of canary deployments and feature flags prevents quick rollback of breaking changes.
Project File Access Regression Breaking Existing Workflows
8Project file access functionality broke on November 25 after previously working, with no rollback capability. This regression persists during investigation, blocking users who relied on this feature.
Slow and unavailable support during critical issues
6Many users feel that Vercel's support is slow when problems arise, affecting development timelines. Response times are inadequate for mission-critical issues.
Artifact Persistence Issues in Console
5Artifacts fail to persist to the menu for extended periods (30+ days), indicating data persistence bugs in the Anthropic Console. This affects the usability of saved artifacts for developers relying on the interface.