Totally disagree. Your position is way too overly simplistic and naive.

An engineer only builds a bridge as strong as it needs to be, and likewise I “vibe code” things based on how few fucks I need to give.

I’m experienced and can review the output for sanity and completion. I can test it, I can rewrite it, etc.

Stop looking at vibe coding as doing the whole thing, it’s more valuable as the glue between things, or to create scripts tools that make you more efficient.

And you can vibe code entire apps that basically just work these days. You probably don’t want to maintain those apps but thats a question of lifecycle planning.

It is so much faster to vibe code an API integration and a suite of tests than I can write. It’s faster to write a functional jq or bash script.

But it’s also much much much worse at doing data viz or writing pandas code because it’s trained on 10,000 shitty medium blogs.

You really have to know what you’re doing and what the model is doing, but it is not universally trash.

And if you don’t believe me, put $20 into the Claude API and install Claude Code and ask it to build something.

I tried following my cat and all he lead me to was his food bowl.