<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI on</title><link>https://eunus.dev/tags/ai/</link><description>Recent content in AI on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP-First Development: Letting AI Write, Run, and Maintain Your Tests</title><link>https://eunus.dev/blog/mcp-first-development-letting-ai-write-run-and-maintain-your-tests/</link><pubDate>Thu, 02 Jul 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/mcp-first-development-letting-ai-write-run-and-maintain-your-tests/</guid><description>I didn&amp;rsquo;t set out to change how I test my own code. It happened because of a task that started as plumbing work and ended up rewiring how I think about building anything at all.
I&amp;rsquo;d been asked to build an MCP server on top of a live production system, under strict rules: no touching the backend, no touching the existing frontend. Just wrap what was there so an AI could call it.</description></item><item><title>Don't Babysit One Coding Agent. Orchestrate a Fleet.</title><link>https://eunus.dev/blog/dont-babysit-one-coding-agent.-orchestrate-a-fleet./</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/dont-babysit-one-coding-agent.-orchestrate-a-fleet./</guid><description>Have been running parallel coding agents for more than a month now, so here are some of my takes.
It feels less like using a tool and more like changing how I execute the same kinds of tasks. A lot of it is just wiring things together (the skills) and letting agents handle the repetitive parts. There&amp;rsquo;s a natural ceiling here though: beyond 2-3 agents in parallel, it gets harder to keep track of what&amp;rsquo;s actually going on.</description></item></channel></rss>