<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>The Kilted Dev</title>
  <subtitle>A Scotsman who dabbles in development. What a machine full of concurrent AI coding projects actually teaches you, written down honestly.</subtitle>
  <link href="https://thekilted.dev/feed.xml" rel="self"/>
  <link href="https://thekilted.dev/"/>
  <updated>2026-11-14T00:00:00Z</updated>
  <id>https://thekilted.dev/</id>
  <author><name>The Kilted Dev</name></author>
  <entry>
    <title>No Reason to Be Kind</title>
    <link href="https://thekilted.dev/no-reason-to-be-kind/"/>
    <updated>2026-11-14T00:00:00Z</updated>
    <id>https://thekilted.dev/no-reason-to-be-kind/</id>
    <summary>A single prompt file built to assemble ten named software-engineering experts against any document survived a fifty-seven-item tool catalogue. Why it earned that trust only after its first real findings changed a stranger project&#39;s document, unprompted.</summary>
  </entry>
  <entry>
    <title>Nothing to go stale</title>
    <link href="https://thekilted.dev/nothing-to-go-stale/"/>
    <updated>2026-11-07T00:00:00Z</updated>
    <id>https://thekilted.dev/nothing-to-go-stale/</id>
    <summary>A proposal to guard one shared GPU with a lock file, and why the careful parts of that lock existed only to manage its own side effects. A live query to the driver had no state to go stale, and caught the failure a lock would have missed.</summary>
  </entry>
  <entry>
    <title>The review that caught itself</title>
    <link href="https://thekilted.dev/caught-itself/"/>
    <updated>2026-10-31T00:00:00Z</updated>
    <id>https://thekilted.dev/caught-itself/</id>
    <summary>A &quot;build the constraint in so it can&#39;t be skipped&quot; principle, relayed from another team&#39;s blog post and proposed for adoption with three independent examples behind it. A review found one was misfiled and the other two came through a single unchecked relay, plus a second claim quietly upgraded from inference into something the source had said.</summary>
  </entry>
  <entry>
    <title>Nineteen calls, every time</title>
    <link href="https://thekilted.dev/nineteen-calls-every-time/"/>
    <updated>2026-10-24T00:00:00Z</updated>
    <id>https://thekilted.dev/nineteen-calls-every-time/</id>
    <summary>Five crashes in one day, every one with the same exit code. Memory, the graphics driver and a stale process each cleared. The cause was a fixed nineteen-call WebGL burst in a browser-level log, sitting in the gap between a preview pane opening and the process dying.</summary>
  </entry>
  <entry>
    <title>Not the integrated GPU</title>
    <link href="https://thekilted.dev/not-the-integrated-gpu/"/>
    <updated>2026-10-17T00:00:00Z</updated>
    <id>https://thekilted.dev/not-the-integrated-gpu/</id>
    <summary>A monitor moved off an ageing USB dock onto a native USB-C port, which turned out to route to the discrete GPU rather than the integrated one. Plus the 100Hz mode the dock never exposed, and a tool that reported the wrong adapter entirely.</summary>
  </entry>
  <entry>
    <title>Blocked, Not Rejected</title>
    <link href="https://thekilted.dev/blocked-not-rejected/"/>
    <updated>2026-10-10T00:00:00Z</updated>
    <id>https://thekilted.dev/blocked-not-rejected/</id>
    <summary>A tool catalogue&#39;s single most capable-looking command turned out to be calls to a server that was never installed. Why the verdict became blocked instead of rejected, and what that distinction is actually for.</summary>
  </entry>
  <entry>
    <title>A Claude Code Stop hook that makes Claude show the full file path</title>
    <link href="https://thekilted.dev/claude-code-stop-hook-full-path/"/>
    <updated>2026-10-07T00:00:00Z</updated>
    <id>https://thekilted.dev/claude-code-stop-hook-full-path/</id>
    <summary>A Claude Code Stop hook in 89 lines of Python that blocks any reply naming a file by a relative path and makes Claude answer again with the absolute path. The code, the settings.json entry for Windows and Linux, and three mistakes: a byte order mark, systemMessage and brace shorthand.</summary>
  </entry>
  <entry>
    <title>The verification tax</title>
    <link href="https://thekilted.dev/the-verification-tax/"/>
    <updated>2026-10-03T00:00:00Z</updated>
    <id>https://thekilted.dev/the-verification-tax/</id>
    <summary>A routing rule said to background long, low-interaction work, so a five-task build dispatched every task to a subagent. The controlling session&#39;s context climbed anyway. Writing the briefs and checking the reports cost the same window, and no rule had priced either.</summary>
  </entry>
  <entry>
    <title>Still carrying the diagnosis</title>
    <link href="https://thekilted.dev/carried-the-diagnosis/"/>
    <updated>2026-09-26T00:00:00Z</updated>
    <id>https://thekilted.dev/carried-the-diagnosis/</id>
    <summary>Field notes from a local-model pipeline. A coding agent benchmarked at 8 out of 8 started exiting 0 without writing a file, and the driver built to replace it still carried the wrong diagnosis long after that diagnosis had been withdrawn.</summary>
  </entry>
  <entry>
    <title>Never installable</title>
    <link href="https://thekilted.dev/never-installable/"/>
    <updated>2026-09-19T00:00:00Z</updated>
    <id>https://thekilted.dev/never-installable/</id>
    <summary>Field notes from a food-diary proof of concept built alongside one NHS dietetic team, not an NHS product. Why its barcode scanner never reports a calorie, and how two 68-byte icon files made it impossible to install without raising an error.</summary>
  </entry>
  <entry>
    <title>The benchmark that disproved its own result</title>
    <link href="https://thekilted.dev/the-benchmark-that-disproved-itself/"/>
    <updated>2026-09-10T00:00:00Z</updated>
    <id>https://thekilted.dev/the-benchmark-that-disproved-itself/</id>
    <summary>A coding-trained model against a general one on five structured-text tasks. The first run confirmed the claim, the raw output showed the checker was wrong, and the gap vanished on a reworded prompt.</summary>
  </entry>
  <entry>
    <title>The file nobody reread</title>
    <link href="https://thekilted.dev/nobody-reread/"/>
    <updated>2026-09-05T00:00:00Z</updated>
    <id>https://thekilted.dev/nobody-reread/</id>
    <summary>Field notes from a food-diary proof of concept built alongside one NHS dietetic team, not an NHS product. A hosting migration where the same option was rejected twice by sessions that never read the first rejection, and where the certificate check itself could not tell the truth.</summary>
  </entry>
  <entry>
    <title>The verdict that survived its own correction</title>
    <link href="https://thekilted.dev/the-verdict-that-survived-its-own-correction/"/>
    <updated>2026-08-29T00:00:00Z</updated>
    <id>https://thekilted.dev/the-verdict-that-survived-its-own-correction/</id>
    <summary>A verdict inherited from an earlier project, that a local model can&#39;t do iterative coding, was right the whole time. A re-test turned it into something broader and less true. How a correct conclusion loses its scope in transit, and the two mechanical rules that came out of catching it.</summary>
  </entry>
  <entry>
    <title>Protected nothing</title>
    <link href="https://thekilted.dev/protected-nothing/"/>
    <updated>2026-08-22T00:00:00Z</updated>
    <id>https://thekilted.dev/protected-nothing/</id>
    <summary>Field notes from a food-diary proof of concept built alongside one NHS dietetic team, not an NHS product. A privacy guardrail blocked its repository from going public. Traced through the code, it protected nothing that going public would have exposed.</summary>
  </entry>
  <entry>
    <title>Invoked, not executed</title>
    <link href="https://thekilted.dev/invoked-not-executed/"/>
    <updated>2026-08-17T00:00:00Z</updated>
    <id>https://thekilted.dev/invoked-not-executed/</id>
    <summary>A routing rule meant to stop a deep-research request from burning a five-hour usage window, a test of the fix that passed in half the runs, and why invoking a research harness and running it are two different claims.</summary>
  </entry>
  <entry>
    <title>Nine ways to talk to a local model</title>
    <link href="https://thekilted.dev/nine-ways-to-talk-to-a-local-model/"/>
    <updated>2026-08-08T00:00:00Z</updated>
    <id>https://thekilted.dev/nine-ways-to-talk-to-a-local-model/</id>
    <summary>A nine-tool survey of local-model interfaces on one GPU: what worked, what silently failed, and why what sits between you and the model matters more than which model you picked.</summary>
  </entry>
  <entry>
    <title>What really fits in 8GB VRAM</title>
    <link href="https://thekilted.dev/what-really-fits-in-8gb-vram/"/>
    <updated>2026-08-01T00:00:00Z</updated>
    <id>https://thekilted.dev/what-really-fits-in-8gb-vram/</id>
    <summary>Four VRAM numbers that looked wrong on an 8GB laptop, none of them a bug: what dxdiag actually reports, what the desktop holds back before a model even loads, and the two fit rules that came out of chasing all four down.</summary>
  </entry>
  <entry>
    <title>We were cloning a copy</title>
    <link href="https://thekilted.dev/cloning-a-copy/"/>
    <updated>2026-07-26T00:00:00Z</updated>
    <id>https://thekilted.dev/cloning-a-copy/</id>
    <summary>A synthesised Scottish narrator that had to sound natural, run offline, and actually be obtainable. Five candidates, five different failures, and a licensed speech corpus that turned the problem from picking a voice into reproducing a speaker.</summary>
  </entry>
  <entry>
    <title>The check that could not fail</title>
    <link href="https://thekilted.dev/checks-that-cannot-fail/"/>
    <updated>2026-07-25T00:00:00Z</updated>
    <id>https://thekilted.dev/checks-that-cannot-fail/</id>
    <summary>Two checks that returned a pass without testing what they appeared to test, and the rule each one leaves behind. Review notes on controls that cannot fail.</summary>
  </entry>
  <entry>
    <title>The dashboard accused itself</title>
    <link href="https://thekilted.dev/dashboard-accused-itself/"/>
    <updated>2026-07-18T00:00:00Z</updated>
    <id>https://thekilted.dev/dashboard-accused-itself/</id>
    <summary>Our cost dashboard flagged its own founding session as a 26.5x overspend. It was a category error, not waste. Field notes on the bug report that fixed it upstream.</summary>
  </entry>
  <entry>
    <title>Convergent evidence</title>
    <link href="https://thekilted.dev/convergent-evidence/"/>
    <updated>2026-07-16T00:00:00Z</updated>
    <id>https://thekilted.dev/convergent-evidence/</id>
    <summary>Nine tools crossed the desk during the ten-day build. Not one became a dependency. Field notes on why the rejections are the argument.</summary>
  </entry>
  <entry>
    <title>Route, don&#39;t guess</title>
    <link href="https://thekilted.dev/route-dont-guess/"/>
    <updated>2026-07-15T00:00:00Z</updated>
    <id>https://thekilted.dev/route-dont-guess/</id>
    <summary>Field notes on building an AI model orchestrator. Task shape over difficulty, three hidden taxes, and the near miss that inverted the cross-project default.</summary>
  </entry>
</feed>
