“You won't be able to find this as it isn't possible.”
Our reading, the sentence that was checked:
Someone who cannot code cannot build a fully functional, secure, useful app entirely by vibe coding.
Assessment: Unresolved Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, How To Argue With An AI Booster, paragraph 399.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-how-to-argue-with-an-ai-booster-965aba-a1
We recorded 35 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2025-08-25. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Observation
- Deadline, as the speaker wrote it
- None stated. This site does not add one.
- Deadline state when assessed
- No horizon
- Deadline state on 2026-10-29
- No horizon (the release’s reference date)
Conditions
- made entirely by someone who cannot code (qualifier, stated by the speaker)
From the speaker
- a fully-functional, secure, and useful app
- made entirely by someone who cannot code
- You won't be able to find this as it isn't possible.
Our interpretation
- Read as an impossibility claim about applications existing at publication on 2025-08-25.
- A qualifying app must perform its intended tasks, have demonstrated practical use, and meet reasonable security requirements for its intended deployment. Secure does not mean mathematically immune to every possible vulnerability.
- Entirely means that no programmer supplied application-specific implementation or repairs. Using ordinary libraries, hosting, and platform services is allowed.
- Independent validation is an evidentiary requirement added by the evaluator, not a requirement Zitron explicitly stated.
Counts as supported if: Evidence establishing that the specified development process could not produce a qualifying app with the tools available at publication. Failed examples or an unsuccessful search alone cannot establish impossibility.
Counts as contradicted if: One documented app meeting all requirements at publication, with credible evidence of its builder's lack of coding ability, complete build history, useful functionality, and independent security validation.
Retrospective: these criteria were written after the outcome was public.
Current assessment
Was it true for the period described?
Outcome: Unresolved
The record was checked, and the evidence available by the cutoff does not settle it.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- No horizon
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
Lovable's Elora Health account identifies a plausible non-coder app, but does not establish every part of Zitron's test. The security documentation acknowledges limitations without showing that secure apps are impossible. Neither the testimonials nor the unsuccessful search for complete validation settle this categorical claim.
Limitations
- The main candidate evidence comes from a tool vendor.
- Lack of a public audit does not establish that an app is insecure.
- The conclusion depends partly on how security and exclusive non-coder authorship are defined.
Evidence (2 items)
Context only: Lovable,
no coding experience
Why it matters here: The vendor describes a relevant non-coder app candidate. This earlier account does not independently establish security, exclusive non-coder implementation, or the app's condition at publication.
- Publisher
- Lovable
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
Context only: Lovable,
incorrect database security setups
Why it matters here: The platform acknowledges that its checks can miss security problems. That warrants checking individual apps, but does not prove secure apps are impossible.
- Publisher
- Lovable
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
What would settle it
A dated build record and independent functionality and security assessment establishing one qualifying app at publication would contradict the claim.
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, How To Argue With An AI Booster
You won't be able to find this as it isn't possible.
- Where
- paragraph 399
- Published
- 2025-08-25
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-how-to-argue-with-an-ai-booster-965aba-a1: Current. Outcome: Unresolved. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.
About assessment wyea-how-to-argue-with-an-ai-booster-965aba-a1.