<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Emanuele Sparacca</title>
    <description>The latest articles on DEV Community by Emanuele Sparacca (@e-man).</description>
    <link>https://dev.to/e-man</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4030856%2F638d0e9e-699e-42a2-b564-2a9db3c39c7d.png</url>
      <title>DEV Community: Emanuele Sparacca</title>
      <link>https://dev.to/e-man</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/e-man"/>
    <language>en</language>
    <item>
      <title>Vibe Coding Is Dead. Welcome to Intentional Coding.</title>
      <dc:creator>Emanuele Sparacca</dc:creator>
      <pubDate>Wed, 15 Jul 2026 17:59:18 +0000</pubDate>
      <link>https://dev.to/e-man/vibe-coding-is-dead-welcome-to-intentional-coding-2347</link>
      <guid>https://dev.to/e-man/vibe-coding-is-dead-welcome-to-intentional-coding-2347</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbsjvjz7tyi4mh4p93y6l.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbsjvjz7tyi4mh4p93y6l.png" alt=" " width="800" height="447"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;When I was sixteen, a summer book left a mark on me that never faded. It was philosophy, not code: Alexandre Koyré's essay on our passage "from the world of the approximate to the universe of precision."&lt;/p&gt;

&lt;p&gt;His thesis stayed with me. For most of history we lived in a world of "more or less" and "roughly." Science, and nearly everything it built, became possible only when we crossed into a universe of measurement and precision.&lt;/p&gt;

&lt;p&gt;Many years have passed. The foundations I learned that summer have not moved.&lt;/p&gt;

&lt;p&gt;AI marketing wants universal adoption, and I understand why: it grows revenue. But it also does something genuinely good: it democratizes creativity and puts it into more hands than ever.&lt;/p&gt;

&lt;p&gt;I won't take anything away from that honest part of the mission. But the technical reality is sadder: a tool built to "help" has quietly left too much behind. Too many details, and not only technical ones: philosophical, social, and ethical ones too. We can no longer ignore them without drawing the lessons that let us grow.&lt;/p&gt;

&lt;p&gt;The good news: many teams are already learning, fast. They understand AI as an extraordinary Swiss Army knife: in the hands of an expert MacGyver, it solves an astonishing number of problems. The human stays at the center, directing the tool, as it has always been.&lt;/p&gt;

&lt;p&gt;But the next lesson is already waiting: how detailed must the thing we ask for actually be?&lt;/p&gt;

&lt;p&gt;An archetypal sketch of a house may be enough to imagine it, to plan it, even to picture yourself living in it. The vibe is enough to dream.&lt;/p&gt;

&lt;p&gt;It is not enough to build.&lt;/p&gt;

&lt;p&gt;You don't pour foundations "more or less." You don't vibe-code the load-bearing wall. Even the term's own inventor draws that line: Andrej Karpathy, who coined vibe coding, now calls the serious craft "an engineering discipline." Meanwhile, AI agents have wiped production databases they were told not to touch, and vibe-coded apps have shipped with user data wide open.&lt;/p&gt;

&lt;p&gt;And since rigorous logic is still not a domain AI has mastered, perhaps we should pay a little more attention to the order and the method with which we lay the foundations of this house.&lt;/p&gt;

&lt;p&gt;That is what I have started to call Intentional Coding.&lt;/p&gt;

&lt;p&gt;AI still belongs in the process. Intentional Coding just asks for method again, built on two old, very human ideas:&lt;/p&gt;

&lt;p&gt;• FSOP, a full-stack optimization mindset: best practice (security, correctness, tests, maintainability) as the default at every layer, instead of bolted on at the end.&lt;br&gt;
• ITIL-style discipline: the lifecycle rigor, order, and accountability IT service management has quietly taught us for decades.&lt;/p&gt;

&lt;p&gt;Intentional, because you choose the structure you're building, at every layer. Nothing is left to chance.&lt;/p&gt;

&lt;p&gt;The approximate is a wonderful place to dream. It is a terrible place to build.&lt;/p&gt;

&lt;p&gt;Where does your team draw the line between AI as copilot and AI as author, and who's accountable when it's crossed?&lt;/p&gt;

&lt;p&gt;The approximate is a terrible place to build—especially when compliance, data sovereignty, and security are on the line.&lt;/p&gt;




&lt;p&gt;I am currently building a Sovereign European, AI-assisted GRC (Governance, Risk, and Compliance) and Cybersecurity platform designed precisely for teams that cannot afford to "vibe-code" their security posture.&lt;/p&gt;

&lt;p&gt;If you are a CTO, CISO, or Engineering Leader navigating European compliance and AI security, let’s connect:&lt;/p&gt;

&lt;p&gt;Follow me on &lt;a href="https://www.linkedin.com/in/emanuelesparacca/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; for updates on our journey and early beta access.&lt;/p&gt;

&lt;p&gt;Join our private waitlist &lt;a href="mailto:contact@praesidai.fr"&gt;contact@praesidai.fr&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>sre</category>
      <category>programming</category>
      <category>leadership</category>
    </item>
  </channel>
</rss>
