AI Picked My Keyboard Then Got the Firmware and Compiled It
2026-04-28 / 4 minThe full pipeline. Claude researched keyboards, picked one, emailed the manufacturer for GPL source code then compiled it. I just flashed it.
Technical writeups on AI, reverse engineering, and building things that work.
The full pipeline. Claude researched keyboards, picked one, emailed the manufacturer for GPL source code then compiled it. I just flashed it.
Driving lessons are £35 an hour. A Logitech G923 is way less. Claude handled the entire NixOS setup, Wine bugs and all, and I was doing laps the same evening.
Five Claude Code instances running at once, NixOS managing the fleet, MCP servers handling email and messaging. This is my actual daily workflow.
OpenSnitch blocking every outbound connection by default, Mullvad with SOCKS proxies, encrypted Firefox vaults, firejailed apps and a full pentesting toolkit. All declarative.
Declarative config means agents understand my whole infrastructure instantly. And if they mess something up I can always roll back. Here is why that matters.
I built a site, optimised it for AI crawlers, then discovered Cloudflare was silently blocking every single one. Here is what I found and how to fix it.
Goroutines give you thousands of concurrent scrapers on 2kb of memory each. No GIL, no garbage collection pauses, no runtime overhead. Here is why I use Go for all my scraping.
Cloudflare for zero-friction deployments, Protonmail for multi-domain agent email through one MCP server, Resend for transactional mail. The stack matters more than people think.
Most AI content is obvious. Em dashes everywhere, Oxford commas, the same generic structure. Here is how to actually automate content that sounds like you.