For the last few weeks, I have been building a system at work that picks small bugs from Jira, gives each one to a coding agent running in a cloud development VM, and gets back a draft pull request that a developer reviews.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
An Unattended Bug-Fixing Agent: Temporal, Jira, a Cloud VM, and a Draft Pull Request
-
Faster Rust Builds on Windows With a Few Small Adjustments
My desktop has a 24-core Core Ultra 9 285K, 32 GB of RAM and a fast NVMe drive.
-
AudioRouter Performance Round Two: Canvas GPU, a Native Leak, and Fewer Background Walks
The ended with one open item: while audio played, the window used about one core, mostly drawing the animated connections on the canvas.
-
AudioRouter and MCP: How It Works and How to Set It Up
I built AudioRouter so I could route Windows audio by drawing a graph instead of maintaining a pile of hidden mixer settings.
-
AudioRouter's Memory Diet: From 960 MB to 30 MB in Four Steps
I noticed something odd while was running my streaming route: Task Manager showed the window using between 800 MB and 1 GB of memory.
-
AudioRouter's Backend: JSON-RPC, One API for Everything, and Why MCP Barely Grew
The first three AudioRouter posts talked about how the project got built and what it does.