[dhussoe]

> Initially, everything looked great. The build succeeded, all components were found and added. But when I opened KiCad… nothing was wired up.

Maybe this is pedantic, but I thought that the core point of "Vibe Coding" is that you do not look at the code. You "give in to the 'vibes'".

I don't know how to translate it into a physical hardware product exactly, but I think it would be manufacturing it without looking at it, plugging it in for your use-case and seeing if it works, then going back to the model, saying it didn't work, rinse, repeat.

[vunderba]

That's how Karpathy defined it - it's throwing and rethrowing it back to the LLM agent until you have a result that roughly matches the goal.

It's the behaviorism of programming. (Pay no attention to the man behind the curtain).

Personally I use the term "agentic coding" if you are high leveling describing the specs to the LLM agent but still taking some minimal amount of time to review the diffs.

[peteforde]

I'm not saying you're wrong, or that I know better.

Yet I have to say that if you are correct, the term is no different than eating tide pods or dry swallowing cinnamon. Why tf would anyone impose such an absurd artificial constraint on themselves, on the tool, or on whatever they are trying to build? Good faith question, I promise.

Constructing detailed prompts to ultimately pair program impressive, complex outcomes is what I assumed vibe coding was. After 35 years of not being able to tell a computer to write the code for me, even getting an 80% coherent first pass of a sophisticated refactor was already radical enough.

If that's what vibe coding is, then nobody should be using that term because it might be the perfect example of "just because you can, doesn't mean you should".

[dhussoe]

> Yet I have to say that if you are correct, the term is no different than eating tide pods or dry swallowing cinnamon. Why tf would anyone impose such an absurd artificial constraint on themselves, on the tool, or on whatever they are trying to build? Good faith question, I promise.

IDK! I don't think Vibe Coding, with the definition that I understand, is a good idea.

But the term comes from here: https://x.com/karpathy/status/1886192184808149383

And the key parts are:

> "forget that the code even exists"

> "I don't read the diffs anymore"

I myself am unclear on what the "vibes" that one is giving into actually are. But terms should have meanings and my understanding from reading the original tweet is that "Vibe Coding" means something distinct from "coding using some AI to help".

[peteforde]

Wild.

I appreciate the explanation. Off to get some cinnamon, I suppose.

[kennywinker]

In this case the netlist is the code, and the pcb is the output. Idk if vibe coding has rules, but if it does that seems well within the rules.

[iopapa]

The next stage in `ato build` process would have caught the missing connections in the DRC check and the LLM could have fixed it itself.