<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Copilot on DevBlog</title><link>/tags/copilot/</link><description>Recent content in Copilot on DevBlog</description><image><url>/uploads/og.webp</url><link>/uploads/og.webp</link></image><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>A template by [Heksagon](https://www.heksagon.net). Implemented for [Critical Manufacturing](https://www.criticalmanufacturing.com/).</copyright><lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/copilot/index.xml" rel="self" type="application/rss+xml"/><item><title>AI as a Development Partner - Skills, Agents, and Context</title><link>/blog/20260414_ai-developer-experience/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>/blog/20260414_ai-developer-experience/</guid><description>&amp;ldquo;Another JavaScript framework? God, why did I choose this field?&amp;rdquo;
If you have been working with software for a significant number of years, you probably have heard or even asked yourself the exact same question. But for about two years now, all the talk has been related to Large Language Models (LLM). And if we thought new JavaScript frameworks were popping out like mushrooms, then compared to the latest updates in the AI/LLM world, it was no big deal after all&amp;hellip;</description></item></channel></rss>