The Vibe Coding Debate: The good, the bad and the ugly

The conversation the industry has been avoiding

Vibe coding is already happening inside most organisations. Product managers are building pricing tools. Operations teams are automating workflows. Finance leads are writing reconciliation scripts. None of it went through IT. Most of it works. And increasingly, teams are quietly depending on it.

The conversation this has generated tends to sit at two extremes. Either vibe coding is democratising software development in ways that will fundamentally change how organisations operate, or it is producing a wave of unreviewed, undocumented tools that will create serious problems the moment something goes wrong.

Both positions contain something real. Neither is the complete picture.

This debate brings together a panel of practitioners to work through the argument properly, examining:

• Where vibe coding genuinely accelerates value and for whom
• Where the output gap sits between what gets built and what was actually needed
• What happens to ownership, accountability and governance when the barrier to building software disappears
• How organisations should be drawing the line between what can be built informally and what cannot
• Whether the risk is in the tool itself, or in the absence of process around it

The format is structured debate, not consensus. Expect disagreement, direct challenge and positions that are genuinely held.

This is not a conversation about whether vibe coding is useful. It demonstrably is. It is a conversation about whether most organisations have yet built the conditions to use it responsibly, and what the cost of getting that wrong actually looks like.