60 days with Claude Code on a production ERP: the honest balance (no hype, raw numbers)

Short summary

After 60 days solo on a production ERP with Claude Code, the author shares 984 commits, 131K lines of code, and nine iterations of operating doctrine. Two key mechanisms earned through incident: falsify hypotheses before any fix (prevents 30-90 min rollback cycles, recovering roughly one day monthly), and classify stored columns by data freshness—live-computed, snapshot, or cached. This rare, numbers-backed field report contradicts both vendor marketing and reflexive skepticism.

• •60-day solo production ERP build with Claude Code: 984 commits, 131K lines of TypeScript, 276 database migrations
• •Falsify-before-fix discipline prevents rollback cycles; live-snapshot-cache column classification prevents data staleness bugs
• •Operating doctrine evolved through nine versions; honest field report grounded in Sentry incidents and failed deployments, not marketing

Generated with AI, which can make mistakes.