100%. Author's point is more like "don't vibe code if you have to maintain it".

The code is your responsibility, and it's your responsibility to understand it and maintain it (using the tools your have available).

Strange article. If their point was "…but vibe coding is really tempting, so you have to exercise a lot of discipline" I'd be on board.