<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Intent on Vic Boomer</title>
    <link>https://vicboomer.com/tags/intent/</link>
    <description>Recent content in Intent on Vic Boomer</description>
    <generator>Hugo</generator>
    <language>nl</language>
    <lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vicboomer.com/tags/intent/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>After vibe coding comes the intent layer</title>
      <link>https://vicboomer.com/essays/en-after-vibe-coding-comes-the-intent-layer/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://vicboomer.com/essays/en-after-vibe-coding-comes-the-intent-layer/</guid>
      <description>&lt;p&gt;A developer built a complete SaaS application in a single weekend in March 2025. Login flow, Stripe integration, dashboard, REST API. Cursor open, typing prompts, accepting suggestions, fourteen hours later: a working product. Two weeks later it was offline. The code did exactly what the prompts asked. The product did nothing anyone needed.&lt;/p&gt;&#xA;&lt;p&gt;This pattern repeats at scale since vibe coding — the term Andrej Karpathy coined — became the standard approach for a growing group of developers and non-technical builders. The production costs of software are declining. The number of projects nobody uses is not declining with them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
