Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-03 · high
A practitioner argues the real risk is unplanned data models, not security bugs everyone blames.
Why now: The rescue-engineering post went up August 2, and Ankur Sethi's manual-retyping essay hit Hacker News' front page August 3, putting the same comprehension-over-speed argument in two places within 24 hours.
An AI consultancy veteran says a growing share of their work is rescuing vibe-coded startups, per an August 2 r/SaaS post.
More than 8,000 of roughly 10,000 startups that shipped production apps on AI coding tools by the end of 2025 needed rescue engineering by mid-2026. Each rescue job runs $50,000 to $500,000.
The post drew 66 upvotes and 41 comments, a 0.62 comment-to-score ratio that reads as practitioners arguing, not people agreeing.
Escape.tech's scan of 1,400-plus vibe-coded production apps found 65% carrying security issues and 58% with at least one critical vulnerability.
The practitioner puts the blame elsewhere: security holes are a symptom, not the disease. The disease is shipping before anyone understands the architecture. The tool invents a data model one prompt at a time, with no view of the whole system. You can patch a SQL injection. You can't patch a schema that was never designed.
That tracks with a design problem I've watched for years. Start pushing pixels before you know what the thing is, and you get something that looks finished and can't be changed. Same failure, different medium.
A separate r/SaaS post at 118 upvotes blames founder behavior instead: idea-hopping predates AI, and the poster only got users after quitting it.
The rescue numbers sharpen the day's other top r/SaaS post, at 204 upvotes: distribution became 10x more important than building another product. Coding got cheap enough that starting stopped being the constraint.
Ankur Sethi's Hacker News post on hand-typing every line his coding assistant proposes hit the front page August 3, with 112 points and 86 comments. He reports roughly 2x productivity instead of a claimed 10x. The trade buys a spatial map of the code, making bugs findable and refactoring possible.
Each link below shares sources, entities, or timing with this story.
Zendesk uses SaaS / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Zendesk uses SaaS); both cover SaaS, Security; overlapping topics (agent, security).
Shared entities / Same source / Shared topic / What happened next / Tension
Both cover Ankur Sethi, August; cite the same source (Ankur Sethi's post on preventing cognitive debt); overlapping topics (agent, behind).
Zendesk uses SaaS / Shared entity: SaaS / Shared topic / Earlier coverage
Linked by a graph relationship (Zendesk uses SaaS); both cover SaaS; overlapping topics (agent, data).
Shared entities / Same source domain / Shared topic
Both cover August, SaaS, Security; reported by the same outlet (reddit.com); overlapping topics (agent, data).
Intercom uses SaaS / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Intercom uses SaaS); both cover SaaS, Same; overlapping topics (agent, data).
Shared entities / Shared topic / Earlier coverage
Both cover August, Same, SQL; overlapping topics (agent, data); earlier August coverage from 2026-08-02.
Zendesk uses SaaS / Shared entity: SaaS / Earlier coverage
Linked by a graph relationship (Zendesk uses SaaS); both cover SaaS; earlier SaaS coverage from 2026-04-24.
Linked by a graph relationship (Zendesk uses SaaS); both cover SaaS; earlier SaaS coverage from 2026-04-05.