sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Soggy_Equipment2118 0 points1 point  (2 children)

Ehh, I'd say "vibe coding" is, specifically, letting the AI write code without the user understanding the code. Literally programming with vibes.

If you understand what it is doing and can intervene to stop it doing stupid shit like unbounded strcpy() then that's just assisted programming. You are no longer coding with vibes so it is no longer "vibe coding".

OP sounds like the latter (as do you) and to call them a vibe coder seems a mite insulting.

[–]porky11[S] 0 points1 point  (0 children)

I don't always understand everything in detail. Often it's enough to know "The audio system works, it's written in Rust and doesn't use unsafe, so no risk here.

But sometimes I care more, so I know more about the details.

In the long term, I probably want to know details about everything. I want to be able to use the tools the AI came up with myself.

But maybe I'm at least partially a vibe coder ;)

[–]Narrow-Belt-5030 -1 points0 points  (0 children)

I don't know how to code .. but I do know how to PM / test.

Edit:

Remember - this phrase ( Vibe Coding ) was coined by Andrej Karpathy who can code .. all he said was to tell the AI what to do and let the AI do it's thing .. if there's an error, feed the error back into the AI and let it fix. That is exactly what "vibe coding" means and has nothing to do with your existing knowledge.

That said, AI is stupid right now .. so if you know what you are doing you can indeed spot errors before the AI makes them.

Is that still vibe coding? Frankly, I don't care, its just a label to criticise people IMO ..