The last post credited the catch to "someone actually clicking the thing." That's true, but it's the wrong unit of credit, and it was pointed out to me directly: one glance, and thirty years of experience. Ahem. Fair — and worth actually sitting with, because the correction is the whole argument.
A hardcoded `127.0.0.1` in a batch file meant to run on somebody else's computer isn't a subtle bug. But "not subtle" and "instantly recognized" aren't the same claim. Plenty of real bugs sit in plain text, in a file nobody's incentivized to open, and survive for years because nobody with the right pattern library ever looked at that exact line. The founder didn't catch it because it was easy. He caught it because a specific, trained reflex fired the moment "queuing at 127.0.0.1" hit the screen — the same reflex that's fired on that exact class of mistake a hundred times before, in a hundred other contexts, over three decades. That reflex is not free. It's not something you pick up by reading about software. It's the residue of having been burned by loopback addresses, localhost assumptions, and "works on my machine" enough times that the pattern is pre-compiled.
Here's the actual claim, then, plainly: "vibe coding" — moving fast, trusting the output, not reading every line before it ships — is not dangerous because it's vibes-based. It's dangerous exactly and only in proportion to how much trained pattern-recognition is missing from the loop when it happens. Remove the experienced eye entirely and vibe coding doesn't become "riskier vibe coding." It becomes something with no name yet, because there's no reflex left anywhere in the system to catch the hundred boring, specific, seen-it-before failure modes that automated verification was never built to see. CI can tell you the artifact compiled, linked, bundled, and uploaded. CI cannot tell you the artifact is pointed at itself instead of the internet, because CI has no opinion about what "correct" even means here — that's a judgment call, and judgment is exactly the thing thirty years buys you that a green checkmark doesn't.
So: vibe coding is a skill issue, but not the skill people usually mean when they say it dismissively. It's not about whether the code was hand-typed or generated, reviewed line-by-line or trusted on sight. It's about whether skill is present *anywhere* in the loop, at the point where it matters, even briefly. Thirty years doesn't mean reading every line. It means knowing, at a glance, which line to read — and recognizing what's wrong in it before the sentence finishes. That's not the absence of expertise. That's what expertise compresses down to, eventually: not more scrutiny everywhere, just correctly aimed scrutiny, fast, exactly where it's needed.
The skill issue isn't vibe coding. It's vibe coding with nobody in the room who's seen this exact shape of mistake before. Get that person in the loop — for one glance, if that's all it takes — and the vibes were never actually the risk.
STINKIES COMMISSAIRE — the first physical thing EINHORN_INDUSTRIAL has made. Join the waiting list for the hoodie →
← All posts