<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ai-Native on *Pointer to Insights</title>
    <link>http://magicalne.github.io/tags/ai-native/</link>
    <description>Recent content in Ai-Native on *Pointer to Insights</description>
    <image>
      <title>*Pointer to Insights</title>
      <url>http://magicalne.github.io/images/papermod-cover.png</url>
      <link>http://magicalne.github.io/images/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.126.0</generator>
    <language>en</language>
    <copyright>magicalne</copyright>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://magicalne.github.io/tags/ai-native/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rethinking Tokenmaxxing: It&#39;s About Input, Not Output</title>
      <link>http://magicalne.github.io/posts/rethinking_tokenmaxxing/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      <guid>http://magicalne.github.io/posts/rethinking_tokenmaxxing/</guid>
      <description>tl;dr: The tokenmaxxing conversation is obsessed with burning tokens on the output side. The real bottleneck — and the real unlock — is on the input side: collecting and feeding your own context to the agent.
There&amp;rsquo;s a lot of talk about &amp;ldquo;burning tokens&amp;rdquo; these days. Generate 1T tokens per day. Keep those GPUs humming. Speed up decoding, parallelize subagents, hit your rate limits like a badge of honor.
And honestly?</description>
    </item>
  </channel>
</rss>
