The problem with this article is that he stresses that you need to check the code and step in when needed - yet relying heavily on LLMs will invariably make it impossible for you to tell what's wrong and eventually how to even read the code (since it will produce code using libraries you never experimented with because the LLM can just write the code).

Also "vibe-coding" is stupid af. You take out the human element altogether because you just accept all changes without reading them and then copy/paste errors back in without any context.