<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ux-for-Ai on Fernando Ruiz</title><link>https://www.fernandoux.com/tags/ux-for-ai/</link><description>Recent content in Ux-for-Ai on Fernando Ruiz</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.fernandoux.com/tags/ux-for-ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Vibe coding vs. AI-assisted engineering: the difference that decides quality</title><link>https://www.fernandoux.com/en/wiki/ai/vibe-coding-vs-ai-assisted-engineering/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/ai/vibe-coding-vs-ai-assisted-engineering/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 &lt;strong&gt;Vibe coding&lt;/strong&gt; means programming with AI and accepting the code without reviewing it (the full definition is in [[what-is-vibe-coding|what is vibe coding]]). &lt;strong&gt;AI-assisted engineering&lt;/strong&gt; uses the same tools inside a process with a specification, a plan, human review and tests. The difference is not the tool but what happens before and after the AI writes.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-separates-one-from-the-other"&gt;What separates one from the other?&lt;/h2&gt;
&lt;p&gt;Both start the same way: a description in natural language and an AI that generates code. The difference shows up at three moments.&lt;/p&gt;</description></item><item><title>What is vibe coding? Programming by describing what you want</title><link>https://www.fernandoux.com/en/wiki/ai/what-is-vibe-coding/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/ai/what-is-vibe-coding/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 &lt;strong&gt;Vibe coding&lt;/strong&gt; is building software by describing in natural language what you want to an AI, and accepting the code it generates without a thorough review. Andrej Karpathy coined the term in February 2025, and in November 2025 Collins Dictionary named it Word of the Year.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="where-does-the-term-come-from"&gt;Where does the term come from?&lt;/h2&gt;
&lt;p&gt;Andrej Karpathy, a co-founder of OpenAI and former AI director at Tesla, coined it in a post on X in February 2025. He described &amp;ldquo;a new kind of coding&amp;rdquo; in which you fully give in to the vibes, embrace exponentials and forget that the code even exists. In practice: talking to a coding tool, accepting all changes without reading the diffs and pasting error messages back. He himself said it was not too bad for throwaway weekend projects.&lt;/p&gt;</description></item></channel></rss>