'Vibe Coding'
I’m hearing the term vibe coding more often, and I understand why. It reflects a real shift: developers working in flow, supported by AI, shipping faster, iterating constantly, and prioritising momentum over ceremony.
In my role, I don’t see vibe coding as reckless. I see it as inevitable.
Technology culture has changed. The question is whether security leadership adapts with it.
Speed Isn’t the Enemy-Opacity Is
When teams move fast, the risk isn’t usually dramatic. It’s subtle:
Individually, these choices feel harmless. Collectively, they create invisible security debt.
My responsibility isn’t to slow teams down. It’s to ensure that velocity doesn’t erode resilience.
Guardrails Over Gates
Traditional, approval-heavy security models don’t work in a vibe coding environment. Developers will always optimise for flow. If security becomes friction, it gets bypassed.
So I focus on building systems where:
Recommended by LinkedIn
When security is embedded in the platform, it doesn’t interrupt creativity, it supports it.
AI Shifts Accountability
AI has amplified vibe coding. But regardless of who-or what-generated the code, accountability remains with us.
As a CIO, one have to ensure:
Innovation cannot come at the expense of governance. But governance must evolve to keep pace.
Culture Writes Code
The biggest risk isn’t insecure code. It’s misalignment. If engineering optimises for speed while security optimises for control, tension is guaranteed.
My role is to align both around trust, resilience, and long-term sustainability.
In today’s environment, I see myself less as a gatekeeper and more as an architect of trust. Culture will always move faster than policy.
If security wants to stay relevant, it must move at the speed of culture-not against it.
