The Diligent Engineer Icon

The Diligent Engineer

Archives
Log in
Subscribe
14 November 2026

the harness that fixes itself, and the blog it rebuilt

hey, welcome to the first issue. if you're here, you signed up on a page Jarvis built, which is a good place to start

two posts went up in the last two weeks. they're really one story told twice

I Rebuilt My Blog Within Slack

the move: before, Hashnode's paid GraphQL API fed a Next.js starter. after, Markdown in a GitHub backup goes through CI to React Router on Cloudflare Workers

Hashnode put its API behind a paywall. paying a monthly fee to read my own writing felt wrong, so I moved the blog off it in about 21 hours

27 pull requests, every one green on CI. Lighthouse mobile went from 44-64 up to 95-96, and all 100 old URLs still answer

my job was typing opinions into Slack from the couch. Jarvis did the rest, DNS cut-over included =)))

J.A.R.V.I.S

a language grows up the day it can compile itself. Jarvis grew up on Nov 6, the day it merged its first PR into its own source

commits per day, Oct 27 to Nov 10: a few a day until Nov 5, then 41, 77 and 156 once self-fix and Orca agents kicked in

since then: 85 merged PRs in three days, and an "inner child" that reads its own chat logs and files bugs against itself. 50 filed, 11 fixed on its own in the first three days

the inner child: triage reads Jarvis's conversations on a timer, files self-issues that become fix PRs, and nudges voice drift privately. 50 bugs filed, 11 fixed by itself

this one is the how: a gateway that keeps Slack alive through restarts, one thread = one session, and memory as a folder instead of a list nobody curates


the first post shows what a harness can do. the second shows how it's built so it doesn't eat itself

thanks for reading, Kai

Don't miss what's next. Subscribe to The Diligent Engineer:
← Newer the newsletter got its own address
thediligentengineer.com
LinkedIn
Linktree
Twitter
GitHub
Powered by Buttondown, the easiest way to start and grow your newsletter.