Vibe-coded output needs a separate round of testing
Quote
things that need to happen there for vibe code output where you come along and say, okay, now you use some sort of agent to then test for other things that could be wrong.
Episode 238: Podherpes (episode page, opens in a new tab) 00:53:45 (play audio from this timestamp, opens in a new tab)
Voice-matched
Summary
Since you didn't write vibe-coded software, you won't know in advance what could be wrong with it. Dave suggests a separate suite of checks: point another agent at the running web service and have it try the top web vulnerabilities, such as cross-site scripting and SQL injection.
Not in the audio. Guest episode (Barry Luijbregts; 0.35 threshold). In this segment Dave is interviewing Barry about his vibe-coding project (he asks the follow-up questions), so these Dave-labeled runs fit the host.