Schrödinger Code

I don't know how it works. I know it works. That's enough.

We're at 100% Claude at work. Not "Claude helps us." Claude writes the code. We review, we ship, we move on.

And we're not even special. Sundar Pichai said in late 2024 that over a quarter of new code at Google was AI-generated, and every engineering org since has been racing to post their own bigger number.

Claude Does Weird Stuff Sometimes

Let's be honest, it's not perfect. Sometimes Claude:

• Wraps a function call in a wrapper that calls the function. Inception. Pointless. Beautiful.
• Forgets our naming conventions exist.
• Decides this one module deserves to be written in Lua. In a Rust codebase. Without mentioning it.

Cool, cool. We get bugs. We fix bugs. With Claude.

The Rig

Here's the thing — Claude isn't just typing into an editor anymore. It's wired into the whole machine:

• It writes the tests that prove the feature works.
• It's plugged into our observability stack. p95 spiking? It pulls the traces, finds the hot span, ships a patch, hands you a before/after flamegraph.
• It has a local DB and an iso-prod test DB. Real data shapes, zero prod nukes.

So Claude doesn't just produce code. It produces code + proof the code does the thing + proof the perf goal is hit.

So… Who Cares How?

Honest question.

Tests green. Bug closed. p95 where we want it. What am I supposed to be upset about, that the variable names hurt my feelings?

"But what if Claude leaves an SQL injection in there?"

Sure. Quick check: does your current test suite cover SQL injection on every endpoint? Mine neither. Nobody's does.

At work, that's what the pentester is for. They poke at it for two weeks. They find stuff or they don't. They don't? We ship. That was always the security model. AI didn't change it, it just made the surface area bigger faster.

Schrödinger Code

So that's what I call my code now. Schrödinger code.

I don't know how it works. I know it works. Tests green. Dashboards green. Pentester paid.

The box is closed. Inside? Maybe it's a wrapper-around-a-wrapper-around-a-Lua-script. Maybe it's pristine, idiomatic Rust. Doesn't matter until something breaks, and when it does, we open the box, take one look, Claude closes it again.

The bar was never "every line is artisanal." The bar was: does it work, can we prove it works, can we fix it when it doesn't. Three for three.

If you'll excuse me, I have a PR to review.

Fine. To skim.