<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Human&#43;ai on Times New Rohan</title>
		<link>https://robrohan.com/tags/human&#43;ai.html</link>
		<description>Recent content in Human&#43;ai on Times New Rohan</description>
		<generator>Hugo</generator>
		<language>en-GB</language>
		
		
		
		
			<lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://robrohan.com/tags/human+ai/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>From Slide Rules to Quantization</title>
				<link>https://robrohan.com/2026/08/05/slide-rules-to-quantization.html</link>
				<pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://robrohan.com/2026/08/05/slide-rules-to-quantization.html</guid>
				<description>&lt;p&gt;In an effort to fight off atrophy from using AI too much, I&amp;rsquo;ve started playing with &lt;a href=&#34;https://en.wikipedia.org/wiki/Slide_rule&#34;&gt;slide rules&lt;/a&gt; - basically, calculators before calculators (after abacuses). They are quite hard to buy in this day and age, but there are some &lt;a href=&#34;https://sliderulemuseum.com/SR_Scales.shtml&#34;&gt;paper ones&lt;/a&gt; you can print out. And if you are good at PCBs maybe you can help me try to &lt;a href=&#34;https://github.com/robrohan/pcb-slide-rule&#34;&gt;make one&lt;/a&gt;?&lt;/p&gt;&#xA;&lt;p&gt;The way slide rules work is: if you mark a ruler with logarithmic spacing, multiplication becomes addition. This is a pretty cool maths trick in that you are adding exponents, and then you can &lt;em&gt;pow()&lt;/em&gt; them back to reality. I think of it as &amp;ldquo;working in Log10 space&amp;rdquo; which would probably make an actual mathemagician cringe. But basically, you slide one scale along another, read off the answer, and keep track of the decimal point in your head. It&amp;rsquo;s absolutely amazing engineers built bridges and got to the moon with this&lt;a href=&#34;https://youtu.be/xDLvUqhwHZc?si=PTHXMGsM4a4KiiQj&amp;amp;t=38&#34;&gt;.&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Who Tests the Testers</title>
				<link>https://robrohan.com/2026/06/04/who-tests-the-testers.html</link>
				<pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://robrohan.com/2026/06/04/who-tests-the-testers.html</guid>
				<description>&lt;p&gt;I was chatting with a fellow student about my LLM harness, and he offered up a great suggestion: &amp;ldquo;Why don&amp;rsquo;t you run the harness against some of the standard LLM benchmarks&amp;rdquo;. My initial thought, was the base model is already run against those benchmarks so what would be the point of re-running them through the harness. After a bit more discussion, I realised his point. Any deviation between the base model and the model running within the harness would likely be because of the harness. And, at the minimum, it would be a nice way to test if the harness was improving over time.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Ghost Installs via AI Harness</title>
				<link>https://robrohan.com/2026/05/09/ghost-installs.html</link>
				<pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
				<guid>https://robrohan.com/2026/05/09/ghost-installs.html</guid>
				<description>&lt;p&gt;This is a feature and a bug. Somewhat scary, but also has the potential for being cool.&lt;/p&gt;&#xA;&lt;p&gt;People are doing all kinds of interesting things with LLMs, but the original use case (and the thing I find them to be the best at) is translating from one thing to another; doing what is sometimes called a &lt;a href=&#34;https://arxiv.org/abs/2501.11639&#34;&gt;stylistic transfer&lt;/a&gt;. In fact, I believe the transformer architecture was created by Google when they were trying to make a better &lt;a href=&#34;https://translate.google.com/?sl=auto&amp;amp;tl=en&amp;amp;op=translate&#34;&gt;translate.google.com&lt;/a&gt; which should be an indication.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Testing a Spatial Memory Index for Strap</title>
				<link>https://robrohan.com/2026/05/05/octree-memory-strap.html</link>
				<pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
				<guid>https://robrohan.com/2026/05/05/octree-memory-strap.html</guid>
				<description>&lt;p&gt;One of the pieces I still need to build for &lt;a href=&#34;https://therohans.com/strap/&#34;&gt;strap&lt;/a&gt; is a long-term memory store. As I&amp;rsquo;ve written about &lt;a href=&#34;https://robrohan.com/2026/04/26/adventures-local-coding-agent.html&#34;&gt;before&lt;/a&gt;, strap compresses context to work within small token budgets. But context compression only handles what&amp;rsquo;s in the current conversation. The bigger question is how to surface relevant memories from past sessions.&lt;/p&gt;&#xA;&lt;p&gt;The obvious approach is brute-force cosine similarity over sentence embeddings. It works for a small number of stored memories, and it&amp;rsquo;s fast enough. But I got curious whether a spatial index could do better, and whether you could make that index inspectable at the same time.&lt;/p&gt;</description>
			</item>
			<item>
				<title>你的代币怎么样？(How&#39;s your tokens?)</title>
				<link>https://robrohan.com/2026/04/11/ni-de-dai-bi-zenme-yang.html</link>
				<pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate>
				<guid>https://robrohan.com/2026/04/11/ni-de-dai-bi-zenme-yang.html</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve been having fun playing with coding agents, and I&amp;rsquo;ve been playing with some different ways, skills calling tools mostly, to enhance them at inference time. Unfortunately, to do my experiments I need to run them within the context of a coding session which gets very costly very quickly.&lt;/p&gt;&#xA;&lt;p&gt;To try to get to a state where I can iterate, I decided to byte the bullet and try to get a local lab running. However, like most people I am GPU poor. The only thing I have is an old gaming PC with an Nvidia 1660 Ti with 6GB of RAM. That isn&amp;rsquo;t enough to run just about anything, but I am no stranger to constraints.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
