<?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: Tony Adams, MBA</title>
    <description>The latest articles on DEV Community by Tony Adams, MBA (@truvisory).</description>
    <link>https://dev.to/truvisory</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%2F3988044%2Faaf13539-d505-4f25-b9a6-99aa82fab129.jpg</url>
      <title>DEV Community: Tony Adams, MBA</title>
      <link>https://dev.to/truvisory</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/truvisory"/>
    <language>en</language>
    <item>
      <title>How I Build Production AI Apps on Cloudflare with Claude Code</title>
      <dc:creator>Tony Adams, MBA</dc:creator>
      <pubDate>Wed, 17 Jun 2026 00:03:39 +0000</pubDate>
      <link>https://dev.to/truvisory/how-i-build-production-ai-apps-on-cloudflare-with-claude-code-2hka</link>
      <guid>https://dev.to/truvisory/how-i-build-production-ai-apps-on-cloudflare-with-claude-code-2hka</guid>
      <description>&lt;p&gt;AI makes it trivial to generate a working demo. Making something that survives real traffic is a different skill. Here's how I approach it — the principles from a talk I gave recently, with the full video at the end.&lt;/p&gt;

&lt;p&gt;Start simple — and earn the complexity&lt;/p&gt;

&lt;p&gt;Gall's Law: a complex system that works invariably evolved from a simple system that worked. AI tools make it tempting to scaffold a sprawling architecture on day one. Resist it. Ship the simplest thing that solves the problem, then let real constraints pull you toward complexity — not the other way around.&lt;/p&gt;

&lt;p&gt;Treat the model like an engineering team you manage&lt;br&gt;
Working well with Claude Code is less about clever prompts and more about setup. The pieces that actually move the needle:&lt;/p&gt;

&lt;p&gt;CLAUDE.md — standing context and conventions for the project&lt;br&gt;
Skills (SKILL.md) — reusable folders of know-how, not one-off prompts&lt;br&gt;
MCP servers — give the model real tools and data instead of guesses&lt;br&gt;
Subagents and plan mode — break work down, and review the plan before any code gets written&lt;/p&gt;

&lt;p&gt;You're the CTO of a small team. Prompt engineering isn't planning.&lt;br&gt;
Build at the edge&lt;br&gt;
My default stack, and the reasoning behind each piece:&lt;/p&gt;

&lt;p&gt;Workers — stateless compute and routing, running close to the user&lt;br&gt;
Durable Objects — one per stateful entity (a chat room, a document), each with its own SQLite for strongly-consistent state&lt;br&gt;
D1 — relational, cross-entity queries: the things a single Durable &lt;br&gt;
Object shouldn't own&lt;/p&gt;

&lt;p&gt;KV — read-heavy config and cache&lt;/p&gt;

&lt;p&gt;The distinction that matters: a Durable Object owns one entity's state; D1 owns the relationships across entities. Get that boundary right and most of the architecture falls into place.&lt;/p&gt;

&lt;p&gt;Don't skip the fundamentals&lt;/p&gt;

&lt;p&gt;AI will happily write code that works in the demo and falls over in production. The details you have to enforce yourself:&lt;/p&gt;

&lt;p&gt;Idempotency on anything that mutates&lt;br&gt;
Kill N+1 queries; index what you actually query&lt;br&gt;
Observability from day one — at the edge, slow is expensive&lt;br&gt;
Semantic HTML and accessibility on the front end&lt;/p&gt;

&lt;p&gt;The throughline&lt;/p&gt;

&lt;p&gt;Stay aware of everything you build. "Vibe coding" skips the awareness; intentional coding keeps it. AI is leverage on top of judgment — not a replacement for it.&lt;br&gt;
Full talk (~59 minutes, chapters in the description):&lt;br&gt;
  &lt;iframe src="https://www.youtube.com/embed/rwkAksbNsTg"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
