<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IBERANT Blog</title>
    <link>https://www.iberant.com/blog</link>
    <description>Insights, engineering deep-dives, and product updates from the IBERANT team.</description>
    <language>en</language>
    <lastBuildDate>Mon, 22 Jun 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://www.iberant.com/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>It's Alive</title>
    <link>https://www.iberant.com/blog/its-alive</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/its-alive</guid>
    <description>Claude Code started returning the senior-engineer plan critique I used to ask for, before I asked. Auto-memory and Dynamic Workflows are why it feels alive, and here's how both work.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Claude Code</category>
    <category>Agents</category>
    <category>Workflows</category>
    <category>Developer Tools</category>
  </item>
  <item>
    <title>Own the Plumbing: Why Your AI Strategy Should Be an MCP Strategy</title>
    <link>https://www.iberant.com/blog/own-the-plumbing-mcp-strategy</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/own-the-plumbing-mcp-strategy</guid>
    <description>The AI provider is the part you rent and swap. The connections from your own systems, behind your own OAuth, are the part you own. Build those once with MCP and the same tools work in Claude, ChatGPT, Copilot, or a model you run yourself.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>MCP</category>
    <category>Enterprise</category>
    <category>Agents</category>
    <category>Integration</category>
  </item>
  <item>
    <title>AI Didn't Make Software Engineering Easier or Cheaper</title>
    <link>https://www.iberant.com/blog/ai-didnt-make-software-engineering-easier-or-cheaper</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/ai-didnt-make-software-engineering-easier-or-cheaper</guid>
    <description>AI ate the 80% of the job that was execution. The 20% that's left, judgment, design, knowing what not to build, is now the whole job, and the same human brain has to hold more of it. That work didn't get cheaper. It got rarer and more expensive.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Engineering</category>
    <category>Software Architecture</category>
    <category>Productivity</category>
    <category>Careers</category>
  </item>
  <item>
    <title>Winter is coming for AI developer wallets</title>
    <link>https://www.iberant.com/blog/winter-is-coming-for-ai-developer-wallets</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/winter-is-coming-for-ai-developer-wallets</guid>
    <description>Anthropic's June 15 billing split exposed what was already true: $200 Claude and Codex subscriptions subsidize agent workloads at 15–30x. The metered reality is $500–$2,000 a month for heavy users. Here is what the math actually says, what other tools are doing about it, and why Churro Coder embeds the native CLI instead of calling the SDK.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Pricing</category>
    <category>Claude Code</category>
    <category>Codex</category>
    <category>Churro Coder</category>
    <category>Economics</category>
  </item>
  <item>
    <title>Truly Autonomous AI Coder Agents: Where the Frontier Actually Is</title>
    <link>https://www.iberant.com/blog/truly-autonomous-ai-coders</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/truly-autonomous-ai-coders</guid>
    <description>Ralph loops, Playwright MCP, log and database access — what does an AI coder agent actually need to ship production work without a human in the loop? A grounded look at the stack, the limits, and a worked autonomous bugfixing workflow.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Autonomous Agents</category>
    <category>Ralph Loop</category>
    <category>MCP</category>
    <category>Engineering</category>
  </item>
  <item>
    <title>Is My Code Repo AI Ready?</title>
    <link>https://www.iberant.com/blog/is-my-code-repo-ai-ready</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/is-my-code-repo-ai-ready</guid>
    <description>AGENTS.md, CLAUDE.md, skills, workflows, OpenSpec — the conventions stack keeps growing, but how do you actually know your repo is legible to coding agents? A look at the agent-readiness tooling, what the ETH Zurich research really says, and the minimum path to a sensible maturity level for a small team.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Agent Readiness</category>
    <category>AGENTS.md</category>
    <category>Engineering</category>
  </item>
  <item>
    <title>Spec-Driven Development: Hype or Worth It?</title>
    <link>https://www.iberant.com/blog/spec-driven-development-hype-or-worth-it</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/spec-driven-development-hype-or-worth-it</guid>
    <description>Vibe coding without a harness ships hallucinations. Heavy spec frameworks slow small teams to a crawl. Here is why Spec-Driven Development matters in the AI era, where the sweet spot lives, and why OpenSpec is the lightweight harness most teams actually need.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Spec-Driven Development</category>
    <category>Engineering</category>
    <category>OpenSpec</category>
  </item>
  <item>
    <title>AI slop is a skill issue</title>
    <link>https://www.iberant.com/blog/ai-slop-is-a-skill-issue</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/ai-slop-is-a-skill-issue</guid>
    <description>AI is a multiplier, not a generator. Multiply zero by anything and you still get zero. Here is how senior architects at IBERANT drive AI to ship code worth shipping, and why the people complaining about AI slop are usually the ones producing it.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Engineering</category>
    <category>Code Quality</category>
  </item>
  <item>
    <title>Building AI-augmented software: our engineering philosophy</title>
    <link>https://www.iberant.com/blog/building-ai-augmented-software</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/building-ai-augmented-software</guid>
    <description>How IBERANT approaches software development in the era of AI — where human expertise and machine intelligence work as one to deliver at an entirely different speed.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate>
    <category>AI</category>
    <category>Engineering</category>
    <category>Methodology</category>
  </item>
  <item>
    <title>Introducing ChurroStack: Open-Source infrastructure for the AI era</title>
    <link>https://www.iberant.com/blog/introducing-churrostack</link>
    <guid isPermaLink="true">https://www.iberant.com/blog/introducing-churrostack</guid>
    <description>ChurroStack is our open-source answer to the complexity of deploying and managing AI infrastructure on-premises — as straightforward as making churros.</description>
    <author>Alejandro Tamayo</author>
    <pubDate>Sat, 10 Jan 2026 00:00:00 GMT</pubDate>
    <category>Open Source</category>
    <category>Infrastructure</category>
    <category>AI</category>
    <category>DevOps</category>
  </item>
  </channel>
</rss>