Vericoding: The End of "Trust Me Bro, The AI Wrote It"
The article discusses the growing concerns around AI-generated code, highlighting a significant drop in trust among developers. While AI tools are widely used, they are associated with increased security vulnerabilities and technical debt. The introduction of vericoding aims to address these issues by ensuring code is mathematically proven correct rather than just tested for bugs.
- ▪92% of developers use AI coding tools daily, but trust in AI-generated code has fallen from 77% to 60%.
- ▪AI co-authored code has 2.74 times more security vulnerabilities than human-written code, with 45% failing security tests.
- ▪The term vericoding refers to generating formally verified code from formal specifications, which is mathematically proven correct.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,312 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | ICME Labs Blog |
| Canonical URL | https://blog.icme.io/vericoding-the-end-of-trust-me-bro-the-ai-wrote-it/ |
| Publication time | Sun, 24 May 2026 22:07:38 +0000 |
| Retrieval time | 2026-05-24T22:22:34.899Z |
| Last seen | 2026-05-24T22:22:34.899Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | LHkEaVks5wPq |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
By Wyatt Benno — Apr 7, 2026 Vericoding: The End of "Trust Me Bro, The AI Wrote It". 92% of developers use AI coding tools daily. Trust in AI-generated code has dropped from 77% to 60%. The gap between those two numbers is where the next billion-dollar problem lives. Vibe coding won. That debate is over. GitHub says 46% of all new code is AI-generated. Among Y Combinator's Winter 2025 cohort, 21% of startups have codebases that are 91% or more AI-generated. Gartner forecasts 60% of all new software code will be AI-generated by end of 2026. The machines are writing the code. Congratulations.Now the bad news.AI co-authored code has 2.74x more security vulnerabilities than human-written code. 45% of it fails security tests. Vibe-coded projects accumulate technical debt 3x faster.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at ICME Labs Blog.