<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/styles/rss-style.xsl"?>

<rss version="2.0"
 xmlns:blogChannel="http://backend.userland.com/blogChannelModule"
>

<channel>
<title>troglodyne.net</title>
<link>http://troglodyne.net//posts/b2601b8d-fe3f-4bcc-b95a-69a419abdece?format=xml</link>
<description>troglodyne.net : /posts/b2601b8d-fe3f-4bcc-b95a-69a419abdece</description>
<language>en</language>
<pubDate>2026-08-21T12:24:59</pubDate>
<lastBuildDate>2026-08-21T12:24:59</lastBuildDate>

<image>
<title>troglodyne.net</title>
<url>/favicon.ico</url>
<link>http://troglodyne.net</link>
<width>32</width>
<height>32</height>
<description>troglodyne.net favicon</description>
</image>
<item>
<title>The best use of LLMs: testing your production process</title>
<link>http://troglodyne.net/posts/b2601b8d-fe3f-4bcc-b95a-69a419abdece</link>
<description><![CDATA[<p>
In an earlier <a href="https://troglodyne.net/posts/72ca7893-97df-11ec-9eb9-a330e32c2df2">post</a>, I described what the "magic" of software development really is - reducing the time and cost of the OODA loop for experimentation.  In another recent <a href="https://troglodyne.net/posts/700faa37-3287-430c-b78d-639184d69f9c">post</a>, I relayed our experience with regards to getting good results from LLMs.  Taken together these point out the actual path to achieving the total factor productivity gains which I had pointed out in an earlier <a href="https://troglodyne.net/posts/8aded219-209e-47dc-a151-d3e44677b649">post</a> that had yet to materialize.
</p>
<p>
Improving the production process is often an expensive process, with it's improvement loop being on the timescales of sprints or entire projects.
Even then it has to overcome all the usual human failings of outright lying to simple ignorance and everything in-between.
This process can be hyper-accelerated with simulations of the worst employee ever, e.g. clod the robot.
You can do an entire <em>year's</em> worth of projects in a day's worth of tokens, and likely find all the places your production process would fail with people too.
</p>
<p>
Through this simulation of <em>flawed, very human</em> interactions you can cheaply shake out the <em>most pathological</em> failings in your production process via <em>structural interventions</em>.
Even if you throw away the prototypes produced during such simulations entirely, the process changes you enact in the pursuit thereof are of immense value.
The <a href="https://austinkleon.com/2019/02/03/why-wasnt-i-consulted/">WWIC</a> effect plaguing projects since time immemorial with expensive rework can be exterminated thereby.
When you've already gone through twelve simulations of the project and how it goes you'll have a pretty good idea of what you want on the other end.
</p>
<p>
Managers of all sorts have to re-orient their thinking along these lines, or they will fail.
If they are not capable of understanding this core loop is <em>the most important thing</em> they will be replaced by those that do.
This is the closest thing to actually predicting the future we will get in our lifetimes, and we'd be fools not to use it.
</p>]]></description>
<author>george</author>
<guid isPermaLink="true">http://troglodyne.net/posts/b2601b8d-fe3f-4bcc-b95a-69a419abdece</guid>
<pubDate>2026-08-20T15:53:36</pubDate>
<enclosure type="text/html" url="http://troglodyne.net/posts/b2601b8d-fe3f-4bcc-b95a-69a419abdece" />
</item>
</channel>
</rss>
