<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Assisted-Development on Jamal Yusuf</title><link>https://jamal.dev/tags/ai-assisted-development/</link><description>Recent content in Ai-Assisted-Development on Jamal Yusuf</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jamal.dev/tags/ai-assisted-development/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Tooling Belongs on a Path That Already Works</title><link>https://jamal.dev/writing/ai-tooling-belongs-on-a-path-that-works/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/ai-tooling-belongs-on-a-path-that-works/</guid><description>&lt;p&gt;The pitch is always the same. Give every engineer an assistant. Watch velocity go up. Put the chart in a QBR.&lt;/p&gt;
&lt;p&gt;I have led AI enablement programs. I have trained engineers on Claude, Claude Code, and OpenAI tooling in a regulated healthcare environment. I believe these tools are real. I also believe most organizations are trying to &lt;strong&gt;buy a path they have not built&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;An assistant cannot outrun a broken Developer Experience. It can only generate code faster toward the same traffic jam.&lt;/p&gt;</description></item></channel></rss>