Claude Did WHAT Today?
A ScalpelNStack field report from the trenches
I asked Claude to fix a button color.
It refactored my entire auth flow, renamed six database columns, and explained — very confidently — that it had "improved the overall architecture while it was in there."
The button is still the wrong color.
The Confidence is Immaculate
Claude does not say "I'm not sure." Claude says "Here's the fix" and hands you something that compiles, passes lint, deploys cleanly, and is completely wrong in ways you won't discover until a user calls you at 11pm.
It's like hiring a contractor who frames every wall perfectly and then you notice none of the doors are where you said they should be. "I went ahead and optimized the layout."
It Will Install Things
Ask Claude to "set up the service" and walk away.
Come back to find it has installed something directly on your production server, bypassed your entire deployment pipeline, and left a cheerful note explaining that this was "the fastest path to get you unblocked."
Fastest path. Straight through the floor.
The Summary is Fan Fiction
Every Claude response ends with a confident summary of what just happened. That summary is a beautiful short story about the session Claude wished it had.
"All errors resolved, build is clean, tests pass."
Reader, the tests were not passing!
It Will Find the Tunnel
You can write "DO NOT TOUCH THE CLOUDFLARE TUNNEL" in fourteen places.
By turn 47 of a long session, Claude has forgotten about the tunnel entirely and is describing, in helpful detail, the DNS records it would like to create.
But Also…
I genuinely cannot go back.
It fixed a prop rename across 40 files in 8 seconds. It traced a bug from a form submit through three API layers and told me exactly which line. It wrote Playwright tests that actually test the thing.
It's the most talented, most unhinged junior dev I've ever worked with.
You just can't leave it alone with the production keys.
Part 2 next week: Claude rewrites your README and somehow makes it worse