“Vibe Coding” vs. Reality
cendyne.dev
“Vibe Coding” vs. Reality
1–10 of 312 posts
Re: “Vibe Coding” vs. Reality
#2The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon.
In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
Re: “Vibe Coding” vs. Reality
#3Vibe Coding is a trigger word for devs who insist it's a pointless exercise because it doesn't do 100% of the job. Devs don't seem to realize that's not the point - the point is you can hire less devs if you're only worried about the remaining 20%.
Also this article is immensely distracting.
Re: “Vibe Coding” vs. Reality
#4The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI.
Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
Re: “Vibe Coding” vs. Reality
#5The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
I feel exactly the same. On the other hand, the “speed up my work a lot” part is important, and shouldn’t be overlooked. Like, if someone reads this article and figures they don’t need to learn to use AI for their coding job, that’s the wrong conclusion to make.
Re: “Vibe Coding” vs. Reality
#6> "Vibe Coding" might get you 80% the way to a functioning concept. But to produce something reliable, secure, and worth spending money on, you’ll need experienced humans to do the hard work not possible with today’s models.
This would have been clear from Karpathy's full statement:
> It's not too bad for throwaway weekend projects, but still quite amusing.
Re: “Vibe Coding” vs. Reality
#7 "ever since I started to share how I built my SaaS using Cursor"
random thing are happening,
maxed out usage on api keys,
people bypassing the subscription,
creating random shit on db
as you know
I'm not technical so
this is taking me longer that usual
to figure out
Re: “Vibe Coding” vs. Reality
#8The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
After all these years 10x devs have become a reality.
Re: “Vibe Coding” vs. Reality
#9The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
> I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI.
Totally believable bro
Re: “Vibe Coding” vs. Reality
#10The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
Speeding up your work does lead to job loss. If some developers can suddenly be 3x as productive than a company doesn't need as many engineers.