Hacker News new | ask | show | jobs
by verdverm 149 days ago
The author spent much time defining the differences. Where do you see conflation?
2 comments

They explain it as if one has transformed into the other. Vibe coding has always been where you ignore the output.
The author describes how their use of agents has transformed, not how "vibe" coding has transformed. See these passages for example

> But a year of daily use changes things. The way most engineers I know actually work with these tools now—myself included—has evolved into something different.

> What we’re actually doing # So if “vibe coding” doesn’t describe it, what does? I’ve been calling it agentic coding. The distinction matters: it’s using AI agents while maintaining the expertise and judgment that keeps the output good, rather than letting it rip with zero validation.

See also their passages around how using vibe coding for side projects is different from agentic coding for professional projects

> Vibe coding has always been where you ignore the output.

Does this definition apply to (say) Fortran compilers from the 50s?

The difference is the author has zero clue what they’re talking about and likely vibe coded this whole waste of time post.
lol thanks