The Vibe Coder is the Problem, Not the Solution. And They Will Never Work With Us.
At Worksdem, we hold a very clear stance on vibe coding. We do not adopt this methodology for several reasons primarily concerned with the security and long-term sustainability of our projects.
Why Worksdem Rejects Vibe Coding
The Vibe Coder will never be part of our team because they carry the risk of accumulating technical debt and security issues. "We've received CVs listing 'Bolt, Replit' under 'skills' — with nothing under 'languages'. That application didn't proceed further." This anecdote perfectly illustrates our approach towards vibe coding: if there isn't real thought behind the code, we cannot accept working with such foundations. The risks associated with technical debt and the impact on software security are just some of the many concerns that arise.
The Dangers of Vibe Coding in Today's Context
Using vibe coding in companies tends to automate technical debt, increasing complications over time Source. Moreover, industries that use AI code generation without proper governance face a substantial increase in technical debt Source. We have also found that vibe coding encourages intuition-based code generation, significantly raising the risks of security issues and systematic failures Source.
The first time we saw code generated 90% by AI in a client's project, the codebase compiled perfectly. Then we tried to modify a secondary requirement and realised no one really understood what was doing what. This is emblematic of the systematic failures that come from a lack of code comprehension and control.
Effective Alternatives to Vibe Coding Techniques
This is not a stance against AI — we use AI every day. It is a stance against the notion that understanding the code you write has become optional. Robust AI governance and human validation of code are essential to mitigate risks. The question we pose to every developer during selection is not "do you use AI?" but "when AI gives you a solution you don't understand, what do you do?" That answer reveals everything.
A Vibe Coder offers immediate speed with technical debt they don't even realise they've accumulated. We inherit that debt when a client calls us six months later. Code governability means every line has a responsible author — even if that line was suggested by a model. If you can't explain why you wrote it that way, you're not an author: you're a fast copier.
We refused to take on a project because the previous team was entirely composed of Vibe Coders. It wasn't an issue of code quality — it was an issue of complete lack of reasoning behind the code. We didn't know where to begin asking questions.