Vibe coding is shit, and will always be shit no matter who is doing it.
Comment on Vibe coding takes the "science" out of computer science
cryptTurtle@piefed.social 1 day ago
I think it depends on who you ask. Some people who "vibe code" definitely use it as a crutch for a lack of understanding. But others (often more senior) tend to use it as just a really really complex auto-complete. Mostly it generates chunks and patterns but the ideas and how those pieces connect come from the dev
NocturnalMorning@lemmy.world 1 day ago
panda_abyss@lemmy.ca 1 day ago
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.
spankmonkey@lemmy.world 1 day ago
I’m experienced and can review the output for sanity and completion. I can test it, I can rewrite it, etc.
You aren’t vibe coding if you do it properly…
jwmgregory@lemmy.dbzer0.com 1 day ago
why do you guys always just move the goalposts?
“X thing isn’t real AI, because real AI sucks and I might have to concede the positive attributes of X about AI generally… [OCR, chess bots, etc.]”
“Y thing isn’t real vibe coding, because real vibing coding sucks and I might have to concede the positive attributes of Y about vibe coding…”
like… you seem like you’ve just decided these things are “bad things” in your head and just shift your definitions the moment you meet reality and see anything that might evoke cognitive dissonance about it.
Rooskie91@discuss.online 1 day ago
I feel like not knowing what you’re doing is a critical piece of the vibe coding definition tho. If a sr developer is using AI, understands the code generated, and can manipulate it in a secure, industry standard way, then that’s just a developer.