<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Opinion on Mad Blog</title><link>/tags/opinion/</link><description>Recent content in Opinion on Mad Blog</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><managingEditor>madking.direct@gmail.com (Mad King)</managingEditor><webMaster>madking.direct@gmail.com (Mad King)</webMaster><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/opinion/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Token Maxing is a Garbage Metric for Developer Productivity</title><link>/posts/token-maxing-productivity/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><author>madking.direct@gmail.com (Mad King)</author><guid>/posts/token-maxing-productivity/</guid><description>&lt;p&gt;There&amp;rsquo;s a new metric creeping into some engineering orgs, dressed up in fancy AI vocabulary: &lt;em&gt;token count&lt;/em&gt;. The idea sounds seductive at first glance — if developers are using AI coding assistants, why not measure how many tokens they generate? More tokens = more output. It&amp;rsquo;s just basic numbers, right?&lt;/p&gt;
&lt;p&gt;Wrong. It&amp;rsquo;s one of the worst productivity metrics you can imagine, and it has a long, embarrassing lineage.&lt;/p&gt;
&lt;h2 id="the-ghost-of-lines-of-code-past"&gt;The Ghost of Lines of Code Past&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s be clear — this isn&amp;rsquo;t new. &amp;ldquo;Lines of code&amp;rdquo; (LOC) has been the go-to misguided productivity metric for decades. And every senior engineer will tell you the same thing: &lt;strong&gt;it&amp;rsquo;s garbage.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>