<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vibe Coding on Jonias Fortuna</title>
    <link>https://potato.id/en/tags/vibe-coding/</link>
    <description>Recent content in Vibe Coding on Jonias Fortuna</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 06 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://potato.id/en/tags/vibe-coding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build It vs Break It: Why Vibe Coders Keep Shipping Apps That Are Easy to Hack</title>
      <link>https://potato.id/en/posts/build-it-vs-break-it-mindset-vibe-coder-security/</link>
      <pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://potato.id/en/posts/build-it-vs-break-it-mindset-vibe-coder-security/</guid>
      <description>&lt;p&gt;There is a pattern that keeps playing out. A developer or vibe coder builds an app in a short amount of time, deploys it publicly, gets traction on social media, and then a while later someone replies - the database got leaked.&lt;/p&gt;&#xA;&lt;p&gt;Not because the developer was incompetent. Not because the technology stack was bad. But because one thing kept getting skipped when the focus was entirely on speed: &lt;strong&gt;security&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
