I Use AI in 2026
The author describes their practical use of AI in software development workflows in 2026, focusing on integrating AI agents into their daily work with tools like Claude Code and speckit. They emphasize structured specifications, code review, and responsible use to maintain code quality in open-source projects. AI is used to generate and test code, but human oversight remains essential for refining output and ensuring reliability.
- ▪The author runs Claude Code in a libvirt VM with restricted permissions for security and isolation.
- ▪They use AI agents in teams for larger features, including coding, reviewing, and testing roles, while smaller tasks rely on hand-written instructions.
- ▪A well-defined spec improves AI output quality, and the author reviews all AI-generated code before submission to avoid offloading work to reviewers.
- ▪Tools like diffity streamline code review by enabling annotated feedback loops with AI agents.
- ▪The author stresses the importance of not pushing unreviewed AI-generated code, citing poor naming, redundancy, and weak tests as signs of low-quality contributions.
Opening excerpt (first ~120 words) tap to expand
How I use AI in 2026 April 25, 2026 10-minute read It’s funny Link to heading I had a draft post sitting in my local repo for a while, where I was about to scream about how AI is overestimated. Well, that post aged pretty badly. I never published it, and looking back at the notes I’m glad I didn’t. So what I’m going to write today will only be about my current workflow and how I actually use AI in my daily work — no hype, no predictions, just what I’ve found useful. My setup Link to heading I run Claude Code with --dangerously-skip-permissions inside a libvirt VM. Running it in a VM adds a layer of isolation I’m comfortable with when giving an agent broad permissions to run commands. My configuration and scripts for setting this up live at clauderunner.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Github.
