I have "vibe coded" a few internal tools now that are very low risk in terms of negative business impact but nonetheless valuable for our team's efficiency.

E.g one tool packages a debug build of an iOS simulator app with various metadata and uploads it to a specified location.

Another tool spits out my team's github velocity metrics.

These were relatively small scripting apps, that yes, I code reviewed and checked for security issues.

I don't see why this wouldn't be a valid professional tool? It's working well, saves me time, is fun, and safe (assuming proper code review, and LLM tool usage).

With these little scripts it creates it's actually pretty quick to validate their safety and efficacy. They're like validating NP problems.

The original definition of vibe coding meant that you just let the agent write everything, and if it works then you commit it. Your code review and security check turned this from vibe coding into something else.

This is complicated by the fact that some people use “vibe coding” to mean any kind of LLM-assisted coding.