<?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: Mike Wei</title>
    <description>The latest articles on DEV Community by Mike Wei (@michael_wei_d93a005ecc379).</description>
    <link>https://dev.to/michael_wei_d93a005ecc379</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%2F4019900%2Fc2e2ed27-540a-4bb8-a833-9887f4a49b0c.png</url>
      <title>DEV Community: Mike Wei</title>
      <link>https://dev.to/michael_wei_d93a005ecc379</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/michael_wei_d93a005ecc379"/>
    <language>en</language>
    <item>
      <title>The fix for bad AI isn't a bigger brain. It's better structure.</title>
      <dc:creator>Mike Wei</dc:creator>
      <pubDate>Thu, 09 Jul 2026 23:30:25 +0000</pubDate>
      <link>https://dev.to/michael_wei_d93a005ecc379/the-fix-for-bad-ai-isnt-a-bigger-brain-its-better-structure-3a0c</link>
      <guid>https://dev.to/michael_wei_d93a005ecc379/the-fix-for-bad-ai-isnt-a-bigger-brain-its-better-structure-3a0c</guid>
      <description>&lt;p&gt;Most AI support bots top out at 30-50% resolution and get stuck around 3.5/5.0 CSAT.&lt;/p&gt;

&lt;p&gt;Customers describe them with one word: robotic.&lt;/p&gt;

&lt;p&gt;We kept hitting the same wall, and the reason turned out to be structural. A single generic model tries to force every refund, every connectivity issue, every warranty claim, every shipping question through one path. But real business problems aren't linear. They're full of ambiguity, overlapping systems, and incomplete information. Rigid decision trees and one big model both break the moment real complexity shows up.&lt;/p&gt;

&lt;p&gt;So we stopped trying to build one model that knows everything.&lt;/p&gt;

&lt;p&gt;Instead: divide and conquer. A sub-agent is a specialist focused on one domain — refunds, connectivity, shipping, warranty, finance, product damage. On each execution, a super agent plans the work, activates the right specialists, gathers facts from them, and makes the final call. Multiple sub-agents can contribute to the same request and cross-check each other — which is exactly why the output is more reliable than any single-agent system.&lt;/p&gt;

&lt;p&gt;The results across Q1 2026 deployments:&lt;/p&gt;

&lt;p&gt;83% resolution (vs. the 30-50% ceiling)&lt;br&gt;
4.8/5.0 CSAT (vs. ~3.5)&lt;/p&gt;

&lt;p&gt;And because each sub-agent is measurable — traffic, resolution, NPS, CSAT at the specialist level — you don't just learn whether the AI works. You learn about your own products, customers, and processes.&lt;/p&gt;

&lt;p&gt;The counterintuitive part: running multiple agents per request should cost more than a single model. After continuous engine optimization, it's often more cost-effective than single-model alternatives — while doing deeper reasoning.&lt;/p&gt;

&lt;p&gt;The lesson we keep relearning: reliability in AI doesn't come from a bigger model. It comes from better structure.&lt;/p&gt;

&lt;p&gt;How the architecture works: &lt;a href="https://aissist.io/technology/multi-agent-platform" rel="noopener noreferrer"&gt;https://aissist.io/technology/multi-agent-platform&lt;/a&gt;&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>architecture</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>The "Moore's Law for AI" everyone promised you? It didn't happen.</title>
      <dc:creator>Mike Wei</dc:creator>
      <pubDate>Thu, 09 Jul 2026 23:24:39 +0000</pubDate>
      <link>https://dev.to/michael_wei_d93a005ecc379/the-moores-law-for-ai-everyone-promised-you-it-didnt-happen-25e4</link>
      <guid>https://dev.to/michael_wei_d93a005ecc379/the-moores-law-for-ai-everyone-promised-you-it-didnt-happen-25e4</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%2F5sv9rs4tm9fib0x05f5y.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%2F5sv9rs4tm9fib0x05f5y.png" alt=" " width="800" height="569"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Everyone building AI agents is about to learn the same expensive lesson: capability and economics are two different problems.&lt;/p&gt;

&lt;p&gt;I've spent 15+ years building large-scale ML systems, and here's the uncomfortable math behind agentic AI in 2026:&lt;/p&gt;

&lt;p&gt;→ Token prices haven't fallen in a straight line. The cheapest models have flattened out, and flagship pricing turned upward again this year (GPT-5.4 launched at 2x GPT-5's input price).&lt;/p&gt;

&lt;p&gt;→ Reasoning tokens are billed as output tokens — deeper thinking raises cost even when the visible answer stays short.&lt;/p&gt;

&lt;p&gt;→ One agentic request expands into planning, retrieval, verification, and tool calls. More useful work, way more tokens.&lt;/p&gt;

&lt;p&gt;Betting your unit economics on "models will get cheaper" is not a strategy. Power constraints alone make that assumption shaky — AI demand is now colliding with the electricity grid, not just GPU supply.&lt;/p&gt;

&lt;p&gt;What actually works is treating token efficiency as an architecture problem:&lt;/p&gt;

&lt;p&gt;System design is the strongest lever. A system tightly coupled to the problem spends less because it already knows the workflow, the boundaries, and the next step. Generic agents pay a "rediscovery tax" on every single run.&lt;/p&gt;

&lt;p&gt;Task optimization comes second. Routing, classification, extraction — these don't need frontier reasoning. The first big savings usually come from stopping the model from doing work it never needed to do.&lt;/p&gt;

&lt;p&gt;Custom models come last, and only at scale. Trade a recurring inference bill for a predictable training cost — but only when the task is stable and you have real evaluation discipline.&lt;/p&gt;

&lt;p&gt;This is why we treat cost as a core design constraint at Aissist, not a cleanup task for later. AI that can't scale economically fails the business case no matter how smart it is.&lt;/p&gt;

&lt;p&gt;Full analysis: &lt;a href="https://aissist.io/technology/token-efficiency" rel="noopener noreferrer"&gt;https://aissist.io/technology/token-efficiency&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
