I think an engineer can vibe code if he/she just doesnt look at the code (even though he would know what is going on if he did).

IMO a better definition of vibe coding would be in regards to reading the actual code. Eg. I started videcoding this project but after I made it to X, I actually had to manually rewrite the code, thats where the vibes stopped.

If you despise the term, why validate it by writing an article about it? Not only does the article give such validation, it actually encourages the term to be used because it expands the term to include all types of AI-assisted coding. It sure seems like a counter-productive bit of writing if the inspiration was hating the term.