By IT Brew Staff
less than 3 min read
Definition:
Vibe coding has allowed people with no coding or even technical experience to quickly build and iterate software products, including mobile apps, websites, games, and highly customized internal systems, using AI tools. However, vibe coding also comes with its share of cybersecurity and infrastructure concerns. For example, the AI might use a natural-language prompt (particularly a vague one) given by the vibe coder to generate code that doesn’t interact well with an organization’s existing tech stack, or feature vulnerabilities that leaves precious data open to cyberattackers.
IT pros at organizations that allow vibe coding can evaluate new vibe-coded software with the following checklist:
- Is it maintainable?
- Is it secure?
- Does it touch user data?
- Is the code sloppy?
- Does the code have automated tests?
- Is it optimized for mobile?
Answering these questions can determine whether vibe-coded software should stay in the tech stack. In addition, IT pros should evaluate software for coding bloat, as LLMs might not optimize the code, as well as suspicious packages, libraries, and third-party APIs.
At this juncture, it might prove difficult for IT pros to completely stop employees from vibe coding apps and services; in fact, there are studies suggesting that senior software developers, for example, may benefit significantly from using LLMs as part of their coding work. But IT teams must remain vigilant about how vibe coding is being used within their organizations, particularly in terms of cybersecurity, and encourage transparency from employees who decide to build.
