4 ms·

Vibe coding is not a 0/1 skill. LLMs generate code as the prompt says, so when you ask what you want, you get it. If you want a specific pattern or architecture

by kmac_ 1y ago

Vibe coding is not a 0/1 skill. LLMs generate code as the prompt says, so when you ask what you want, you get it. If you want a specific pattern or architecture, explicitly ask for that. It works really well when you (not the LLM) drive the development.

dncornholio 1y ago
This is true, but also made me realize I usually spend more time telling the AI what to do then if I would have figured it out myself.
ApeWithCompiler 1y ago
Prompt: "Please make the code secure and apply best practices where possible..."
exitb 1y ago
Wasn't the original definition of vibe coding asking us to "forget that the code even exists"?
- simonw 1y ago
  It was, but annoyingly a lot of people now use "vibe coding" to mean any form of AI-assisted development. It's got to the point where if someone talks about "vibe coding" you have to confirm with them which definition they are using, because otherwise you risk people talking right past each other because they're not actually talking about the same thing.
  - ninkendo 1y ago
    > people talking right past each other because they're not actually talking about the same thing. Just like every HN thread about vibe coding!
  - kmac_ 1y ago
    Yes, the term isn't universally defined yet. Also, the number of available tools doesn't help here (e.g., my workflow in Cursor and CC differ). My "vibe coding" is probably different than blog post authors' "vibe coding." At my work, we have "AI in dev" meetings to discuss the topic, the variety of opinions resembles comments here, and we try to boil down where the issue is.
serial_dev 1y ago
This has not been my experience. Many times I ask explicitly what I want, and the tools fail to deliver. Of course, don’t throw the baby out with the bathwater, plenty of times they are helpful and can really deliver 10x improvements. The key is recognizing the patterns when these tools can deliver and when they can’t. Don’t forget to reevaluate every couple of weeks, as the tools improve all the time.
anonzzzies 1y ago
And how many times do you have to correct that? Because I have not seen that in practice. With Opus / Claude Code it will follow instructions until it doesn't and then suddenly, in the SAME prompt/todo agent blabber, it creates a web worker instead of using Bull which it did first for exactly the same case. Sure, context overload, but this is the same prompt. And the models claiming larger context like Gemini don't fare any better (well, worse actually). Now you might tell me; make the tasks smaller and more focused, yes, that's true, it performs better, but then i'm just faster myself coding. Most what I use CC for is exploration & frontend; generating slabs of mind numbing crap react and tailwind is fantastic. But for most other stuff, we have patterns and libs in place where i'm much faster and better than AI as it's not much code, just more logic/thinking.

by kmac_ 1y ago

dncornholio 1y ago

This is true, but also made me realize I usually spend more time telling the AI what to do then if I would have figured it out myself.

ApeWithCompiler 1y ago

Prompt: "Please make the code secure and apply best practices where possible..."

exitb 1y ago

Wasn't the original definition of vibe coding asking us to "forget that the code even exists"?

simonw 1y ago
It was, but annoyingly a lot of people now use "vibe coding" to mean any form of AI-assisted development. It's got to the point where if someone talks about "vibe coding" you have to confirm with them which definition they are using, because otherwise you risk people talking right past each other because they're not actually talking about the same thing.
- ninkendo 1y ago
  > people talking right past each other because they're not actually talking about the same thing. Just like every HN thread about vibe coding!
- kmac_ 1y ago
  Yes, the term isn't universally defined yet. Also, the number of available tools doesn't help here (e.g., my workflow in Cursor and CC differ). My "vibe coding" is probably different than blog post authors' "vibe coding." At my work, we have "AI in dev" meetings to discuss the topic, the variety of opinions resembles comments here, and we try to boil down where the issue is.

serial_dev 1y ago

This has not been my experience. Many times I ask explicitly what I want, and the tools fail to deliver. Of course, don’t throw the baby out with the bathwater, plenty of times they are helpful and can really deliver 10x improvements. The key is recognizing the patterns when these tools can deliver and when they can’t. Don’t forget to reevaluate every couple of weeks, as the tools improve all the time.

anonzzzies 1y ago

And how many times do you have to correct that? Because I have not seen that in practice. With Opus / Claude Code it will follow instructions until it doesn't and then suddenly, in the SAME prompt/todo agent blabber, it creates a web worker instead of using Bull which it did first for exactly the same case. Sure, context overload, but this is the same prompt. And the models claiming larger context like Gemini don't fare any better (well, worse actually). Now you might tell me; make the tasks smaller and more focused, yes, that's true, it performs better, but then i'm just faster myself coding. Most what I use CC for is exploration & frontend; generating slabs of mind numbing crap react and tailwind is fantastic. But for most other stuff, we have patterns and libs in place where i'm much faster and better than AI as it's not much code, just more logic/thinking.