Tanya Janca on AI Slop, Vibe Coding, & the Future of AppSec
Tanya Janca discusses the impact of AI on application security during a conversation with Kate Holterhoff. She highlights the rapid pace of software development and the lack of security training for developers. Janca also addresses the challenges of integrating AI into existing security frameworks and the future of secure coding standards in Canada.
- ▪Tanya Janca describes the current state of application security as reckless, likening it to driving under the influence at high speeds.
- ▪AI is increasingly writing significant portions of production code, while many developers lack training in security code review.
- ▪Janca argues that the bug bounty economy is facing potential collapse and emphasizes the need for new security tools rather than retrofitting AI onto legacy systems.
2 outlets in our directory ran this story, first to last over 30 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ The Linux Kernel is becoming Vibe Coded AI Slop — r/linux
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,752 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 | RedMonk |
| Canonical URL | https://redmonk.com/videos/tanya-janca/ |
| Publication time | Thu, 21 May 2026 18:26:31 +0000 |
| Retrieval time | 2026-05-21T18:36:35.667Z |
| Last seen | 2026-05-21T18:36:35.667Z |
| 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 | VA9eY6pKLbgN · 2 stories |
| 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
Conversations Tanya Janca on AI Slop, Vibe Coding, & the Future of AppSec RedMonk Video Share via Twitter Share via Facebook Share via Linkedin Share via Reddit Get more video from Redmonk, Subscribe! RedMonk Video RedMonk Tech Events Kate Holterhoff sits down with Tanya Janca, Secure Coding and AI Trainer at SheHacksPurple, to talk about what AI is doing to application security. Tanya’s take: we’re driving a car at three times the speed limit after 25 beers. AI writes huge portions of production code, most developers were never taught to review code for security in the first place, and release velocity keeps climbing.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at RedMonk.
Discussion
0 commentsMore from RedMonk
