- What loop would keep my software improving with LLMs?
A hypothesis I am still sorting out: whether I can wire my own project to LLMs and turn it into a loop that keeps improving itself.
- AI-Written Firmware: What to Hand Over, Where to Stop It
3-Tier Trust sorts PRs, then verification gates (spec, TDD, RAG, HIL, deterministic analyzer, more) take them to merge. Each catches its own defect class.
- AI-Written Firmware: Measuring the Gap With 233 Tests
Sonnet 4.6 scored 68.0% and Haiku 4.5 56.9% on 233 firmware cases. EmbedEval is my open benchmark: 5-layer eval, n=3, Wilson 95% CI, Zephyr, STM32 HAL.
- AI-Written Firmware: What Breaks Outside the Function
AI-written firmware breaks where a single function can't show it. I found 3 patterns visible in the diff and 3 that only surface after 49 days.
- AI-Written Firmware: What I Didn't Tell It
A junior wrote a logging daemon with an AI tool. It passed my review, ran fine, and later wore out an eMMC. The risk was in what the prompt left out.
- AI Agents in Embedded: Learning Context Engineering
AI agents wrote good Yocto recipes but silently corrupted sensor data and misconfigured SPI registers. What fixed it was the context I gave them.