<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog – Fernando Ruiz on Fernando Ruiz</title><link>https://www.fernandoux.com/blog/en/</link><description>Recent content in Blog – Fernando Ruiz on Fernando Ruiz</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.fernandoux.com/blog/en/index.xml" rel="self" type="application/rss+xml"/><item><title>I Made Claude Opus 4.8 Manage Another AI Agent While I Worked</title><link>https://www.fernandoux.com/blog/en/claude-opencode-two-agent-workflow/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/blog/en/claude-opencode-two-agent-workflow/</guid><description>&lt;p&gt;Have you ever used your best AI model for work that clearly did not deserve your best AI model?&lt;/p&gt;
&lt;p&gt;I have. Not because I did not understand model routing. I use cheaper models for cheaper tasks all the time. But when you are deep inside a real codebase, with tests failing, files changing, and context moving fast, it is easy to let your strongest session become the planner, executor, reviewer, secretary, and background worker at once.&lt;/p&gt;</description></item><item><title>AI Pipelines: How I Built Systems That Work While I Sleep</title><link>https://www.fernandoux.com/blog/en/ai-pipelines-claude/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/blog/en/ai-pipelines-claude/</guid><description>&lt;p&gt;Most people use AI to generate code, write copy, or fix their lives in a thousand small ways. You feed it something, it spits back something better or more structured. That&amp;rsquo;s fine. That&amp;rsquo;s the obvious use case. But one of the highest-value applications I&amp;rsquo;ve found for AI is building &lt;strong&gt;pipelines&lt;/strong&gt;, specifically with Claude.&lt;/p&gt;
&lt;p&gt;Claude is built for this. The model has a strong orientation toward multi-step workflows, tool use, and persistent context. And while there are other capable models out there, including some surprisingly good Chinese models, I&amp;rsquo;m going to focus on what I&amp;rsquo;ve actually been experimenting with. The results speak for themselves.&lt;/p&gt;</description></item><item><title>I Built a Medical SaaS With AI. Then I Got Hacked. Here's the Case Study.</title><link>https://www.fernandoux.com/blog/en/medical-saas-case-study-dark-forest/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/blog/en/medical-saas-case-study-dark-forest/</guid><description>&lt;p&gt;The first night I deployed my sister&amp;rsquo;s medical scheduling system to production, I went to bed feeling like a king. By 9am the next morning, my server&amp;rsquo;s CPU was pinned at 300%, and someone else was mining cryptocurrency on my rented hardware.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the middle of the story, though. Let me back up.&lt;/p&gt;
&lt;p&gt;This is a case study about the SaaS I always wanted to build, the one that finally found me, and everything I broke and learned getting it to work. It&amp;rsquo;s also the story of a Product Designer who thought he understood software, and discovered the internet is a much stranger, more hostile place than any Figma file ever suggested.&lt;/p&gt;</description></item><item><title>Designing in Words: How AI Turned UX Designers Into Their Own Frontend Engineers</title><link>https://www.fernandoux.com/blog/en/designing-in-words-vibe-coding-for-ux-designers/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/blog/en/designing-in-words-vibe-coding-for-ux-designers/</guid><description>&lt;p&gt;The design review went perfectly. You handed off a Figma file that was pixel-perfect: the right spacing, the right micro-interactions, the hover states, all of it. Three weeks later, the thing that shipped looked like it was built from memory by someone who saw your design once in a dream. Sound familiar?&lt;/p&gt;
&lt;p&gt;That story has been playing on loop for the entire history of digital product design. The designer creates. The developer interprets. Something gets lost, always. Sometimes a lot. And the designer files it under &amp;ldquo;developer error&amp;rdquo; and moves on to the next project.&lt;/p&gt;</description></item><item><title>Claude Code Skills: The Professional Layer Most Users Ignore</title><link>https://www.fernandoux.com/blog/en/claude-code-skills-the-professional-layer-most-users-ignore/</link><pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/blog/en/claude-code-skills-the-professional-layer-most-users-ignore/</guid><description>&lt;p&gt;You&amp;rsquo;re already in Claude Code. You know the basics. You&amp;rsquo;ve seen what it can do. But every new session starts the same way: you spend the first five minutes re-explaining your context, re-typing the prompts you&amp;rsquo;ve written a hundred times, and re-establishing the ground rules before any real work gets done.&lt;/p&gt;
&lt;p&gt;That friction isn&amp;rsquo;t a Claude problem. It&amp;rsquo;s an infrastructure problem. And the fix is a feature most users walk right past: &lt;strong&gt;Skills&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Vibe Coding: What AI Won't Tell You Before Building Your First App</title><link>https://www.fernandoux.com/blog/en/vibe-coding-what-ai-wont-tell-you-before-building-your-first-app/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/blog/en/vibe-coding-what-ai-wont-tell-you-before-building-your-first-app/</guid><description>&lt;p&gt;There&amp;rsquo;s a conversation happening thousands of times a day around the world. It goes something like this:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&amp;ldquo;Hey Claude, I need you to build me a YouTube-like application but without bugs.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;And the [[AI]] responds happily, generates code, and the user thinks they&amp;rsquo;ve just hired an engineering team for $20 a month. Three weeks later, the application has 47 bugs, nobody knows why login fails on Tuesdays, and the creator can&amp;rsquo;t change a button color without breaking the payment system.&lt;/p&gt;</description></item><item><title>Spec-Driven Development: The End of Amateur Vibe Coding and the Dawn of Systems Engineering for UX</title><link>https://www.fernandoux.com/blog/en/spec-driven-development-the-end-of-amateur-vibe-coding-and-the-beginning-of-systems-engineering-for-ux/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/blog/en/spec-driven-development-the-end-of-amateur-vibe-coding-and-the-beginning-of-systems-engineering-for-ux/</guid><description>&lt;p&gt;The concept of [[Vibe Coding]] is appealing. You write in natural language, AI spits out code, and you have a prototype in minutes. It works perfectly for a 100-line script. Try scaling that to a real product, and the system collapses.&lt;/p&gt;
&lt;p&gt;I sat down with &lt;a href="https://dot.cards/ryanedge"&gt;Ryan Edge&lt;/a&gt; to break down exactly how he&amp;rsquo;s using [[AI]] agents to build complex software. The consensus is clear: relying on chat interfaces to code has a glass ceiling. You lose context, the AI hallucinates, overwrites existing logic, and you end up doing manual work to correct a robot.&lt;/p&gt;</description></item></channel></rss>