<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agentic-Engineering on Unladen swallow - Olivier Wulveryck</title>
    <link>https://blog.owulveryck.info/tags/agentic-engineering.html</link>
    <description>Recent content in Agentic-Engineering on Unladen swallow - Olivier Wulveryck</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Olivier Wulveryck</copyright>
    <lastBuildDate>Fri, 19 Jun 2026 10:27:56 +0200</lastBuildDate>
    <atom:link href="https://blog.owulveryck.info/tags/agentic-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vibe Coding at Scale? Engineering Strikes Back</title>
      <link>https://blog.owulveryck.info/2026/06/19/vibe-coding-at-scale-engineering-strikes-back.html</link>
      <pubDate>Fri, 19 Jun 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.owulveryck.info/2026/06/19/vibe-coding-at-scale-engineering-strikes-back.html</guid>
      <description>&lt;p&gt;Generative AI has transformed how code is produced. In just a few months, we went from autocomplete to agents capable of writing, testing, and deploying entire applications. The market is now flooded with methods for framing these agents and making them produce quality code.&lt;/p&gt;&#xA;&lt;p&gt;But this abundance raises a question few organizations are asking yet: &lt;strong&gt;what happens when you are not building one app, but fifty?&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
