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