Intro
How much do we actually trust the code our AI assistants spit out?
Recently, we had the opportunity to present at WALK, the innovation center at the Aristotle University of Thessaloniki that helps startups turn ideas into sustainable ventures. We spoke with founders and engineers about the rise of Vibe Coding and the hidden risks that come with it. Following the session, we surveyed 23 startups about their AI habits and the levels of trust they place in these tools.
The results were a wake-up call for anyone merging AI pull requests.
The Daily Dependency
First, we wanted to know how deep the AI rabbit hole goes. It turns out, we are reaching a point of total dependency.
Nearly half (47.8%) of developers use these tools daily as part of their core workflow, and another 34.8% use them several times a week. Only 4.3% of respondents said they rarely or never use AI.
The 100% Incident Rate
This is where it gets interesting–and a bit scary. We asked if AI-assisted code has ever caused problems.
The "No, never" category was a flat 0.0%. Every single respondent reported that AI had caused an issue, with 78.2% facing problems occasionally or all the time. This creates a massive contrast: 95% of us are using it, yet nearly 80% of us are dealing with major breakages because of it.
The Pressure Trap
If the code breaks so often, why do we trust it?
Most developers (52.2%) claim to be cautious and review code carefully. However, the "WTF" moment happens under pressure. Over a third (34.8%) admit they mostly trust the AI when they are under a deadline. We check the code when we have time, but we skip the rigor exactly when the stakes are highest.
The Security & Privacy Blind Spot
When a security tool flags AI code, the reaction is generally healthy: 69.6% investigate further.
But when it comes to the data we give the AI, the logic disappears.
Despite constant headlines about data breaches, 43.5% of respondents are either "not very concerned" or "not concerned at all" about sharing proprietary data with AI models.
Conclusion: The Auditor Era
This survey reveals a "Verification Paradox". AI has become a daily necessity, but its 100% incident rate proves that our value as developers has shifted. We aren't just writers anymore; we are auditors.
The greatest risk isn't the AI's lack of logic–it's our human tendency to trust it most when time is shortest.
How are you auditing your AI output? Let’s discuss in the comments.
Top comments (1)
That 34.8% "mostly trust under time pressure" stat is the whole story. We run a payments platform — FCA-authorised, SOC2 certified — and the pressure to ship fast is constant. We use AI agents daily for things like scanning config drift and validating schemas across our services. But we learned early: the verification layer isn't optional, it's the product. An AI agent flagged 23 env variable inconsistencies across our services in minutes. Incredible speed. But 4 of those were intentional — legacy integrations with partner-specific naming that the agent had zero context for. If we'd auto-fixed them, we'd have broken production. The paradox you're describing isn't really about AI trust — it's about building systems where the human verification step is a first-class citizen, not an afterthought you skip when the deadline hits.