<?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 The Angry Dev</title><link>https://www.darrenhorrocks.co.uk/tags/vibe-coding/</link><description>Recent content in Vibe-Coding on The Angry Dev</description><generator>Hugo 0.125.0</generator><language>en-gb</language><lastBuildDate>Tue, 30 Jun 2026 13:59:17 +0100</lastBuildDate><atom:link href="https://www.darrenhorrocks.co.uk/tags/vibe-coding/index.xml" rel="self" type="application/rss+xml"/><item><title>Vibe Coding vs Coding with AI</title><link>https://www.darrenhorrocks.co.uk/vibe-coding-vs-coding-with-ai/</link><pubDate>Tue, 30 Jun 2026 13:59:17 +0100</pubDate><guid>https://www.darrenhorrocks.co.uk/vibe-coding-vs-coding-with-ai/</guid><description>&lt;p>I think there&amp;rsquo;s a huge difference between &amp;ldquo;vibe coding&amp;rdquo; and &amp;ldquo;coding with AI&amp;rdquo;, and that difference comes down to one thing: you still need to know what you&amp;rsquo;re doing.&lt;/p>
&lt;p>Vibe coders are often people who are new to programming. They don&amp;rsquo;t yet understand software architecture, how systems fit together, or how to translate requirements into a working solution. To them, AI can feel like a magic box that somehow produces software.&lt;/p>
&lt;p>But&amp;hellip;&lt;/p></description></item></channel></rss>