Ask HN: What should we call vibe coding when it's LLM-assisted problem solving?
6 comments
You are vibecoding because you are not coding. If you don't like the idea that AI-assisted coding = vibecoding, don't vibecode.
"What should we call (adverbial-moniker) when it's (other-adverbial-moniker)?"
--
(Mant crawls up building exterior like King Kong as people on street stare in amazement)
- What do you call that thing?!
- Bill.
--
(Mant crawls up building exterior like King Kong as people on street stare in amazement)
- What do you call that thing?!
- Bill.
Naming things is hard for a reason. It shapes how we think and communicate. When I'm pointing an LLM at PostgreSQL internals vs. asking it to make a navbar prettier, I'm collaborating in fundamentally different ways. Having distinct terms helps us share ideas and set appropriate expectations.
You're dealing with the real limitations of LLMs
Vibe coding is a false story that arose from the hype cycle
Vibe coding is a false story that arose from the hype cycle
When a creative task is automated into repetition, it forms bureaucracy. You are a techno bureaucrat.
Techno bureaucrating is unironically a better term than vibe coding.
The original Karpathy definition says it’s only “vibe coding” if you aren’t reading the code it produces. So if I am not vibe coding, what am I doing?