I "vibe code" but to me, it's a random thought and test to see what I can produce quickly. It doesn't have to be AI assisted/generated either. Maybe more ADHD, ooh, Ball! Or epiphanies where I have to try something out right away.
I think the best description of modern AI-driven coding is "thinking things into existence".
All the vision, direction, yea-or-nay answers to LLM suggestions comes from the human, all the coding, testing, bug-hunting is done by the LLM.
An LLM is excellent at pulling together paths between nodes in its weights database and providing solutions to link these two hitherto disparate states, but it lacks the creativity of the human, the desire to make something, the passion of creation, admittedly at a slightly farther distance than has been the case to date.
"Vibe coding" and "AI Slop" are terms (~coined~) employed by the threatened and the scared, IM(NSH)O. They denigrate unfairly, and while they may have been appropriate for early-stage LLMs, todays systems are different constructs entirely.
In a decade, you'll be the uncommon software engineer if you're doing things all on your own, a curiosity, akin to the Amish. Life is change, and embracing the change is the only way to succeed in an ever-changing world. Yes, there will be fallout; yes there will be consequences, and yes there will be opportunity.
"Vibe coding" was originally coined by Andrej Karpathy.
I didn't wrote so because it would made me perceive the flow of my prose "clunky". In other words, i didn't want acclaimed scientist's name in my argument as it would made it too complex to me.
But it accurately describes how most people use AI for code generation. For every person doing careful, meticulous testing and only using AI to incrementally generate code they personally understand and that they personally test and validate - to automate the "boring parts" - there are ten thousand "lol model go brrr" coders who don't care, and don't want to care. Who just let Claude chew on their prompt and burn tokens for a couple of days then push straight to Github.
When AI coders in general care about anything more than the "vibe" and no longer consider touching the code to be beneath their contempt, we can stop calling it what it is.
I hate the term "vibe" anyway. Only appropriate for epilepsy-filled, crowded electronic music dance parties. Using it anything else gives me regurgitation tingling.
I "vibe code" but to me, it's a random thought and test to see what I can produce quickly. It doesn't have to be AI assisted/generated either. Maybe more ADHD, ooh, Ball! Or epiphanies where I have to try something out right away.
Could be trash or could be gold.
It's also become insulting and a bit of a slur. We need to stop doing this. It's disrepsectful.
Doesn't deserve respect.
I imagine that's what the horse riders said about "driving" for the people using horseless carriages.
Please don't let this become an "us versus them" ideology.
Progress is always uncomfortable for some people. Jobs and skills have always been displaced by advancements in technology.
I think the best description of modern AI-driven coding is "thinking things into existence".
All the vision, direction, yea-or-nay answers to LLM suggestions comes from the human, all the coding, testing, bug-hunting is done by the LLM.
An LLM is excellent at pulling together paths between nodes in its weights database and providing solutions to link these two hitherto disparate states, but it lacks the creativity of the human, the desire to make something, the passion of creation, admittedly at a slightly farther distance than has been the case to date.
"Vibe coding" and "AI Slop" are terms (~coined~) employed by the threatened and the scared, IM(NSH)O. They denigrate unfairly, and while they may have been appropriate for early-stage LLMs, todays systems are different constructs entirely.
In a decade, you'll be the uncommon software engineer if you're doing things all on your own, a curiosity, akin to the Amish. Life is change, and embracing the change is the only way to succeed in an ever-changing world. Yes, there will be fallout; yes there will be consequences, and yes there will be opportunity.
"Vibe coding" was originally coined by Andrej Karpathy.
I didn't wrote so because it would made me perceive the flow of my prose "clunky". In other words, i didn't want acclaimed scientist's name in my argument as it would made it too complex to me.
I was inaccurate - I meant employed, not coined.
But it accurately describes how most people use AI for code generation. For every person doing careful, meticulous testing and only using AI to incrementally generate code they personally understand and that they personally test and validate - to automate the "boring parts" - there are ten thousand "lol model go brrr" coders who don't care, and don't want to care. Who just let Claude chew on their prompt and burn tokens for a couple of days then push straight to Github.
When AI coders in general care about anything more than the "vibe" and no longer consider touching the code to be beneath their contempt, we can stop calling it what it is.
if we keep it new products should be coined "corporate vibes"
I hate the term "vibe" anyway. Only appropriate for epilepsy-filled, crowded electronic music dance parties. Using it anything else gives me regurgitation tingling.