<?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>No Coding Required</title><link>https://nocodingrequired.ai/</link><description>Recent content on No Coding Required</description><generator>Hugo -- 0.156.0</generator><language>en-us</language><lastBuildDate>Wed, 25 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nocodingrequired.ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Measuring AI Adoption by Who Has Copilot Open</title><link>https://nocodingrequired.ai/posts/stop-measuring-ai-adoption-by-who-has-copilot-open/</link><pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate><guid>https://nocodingrequired.ai/posts/stop-measuring-ai-adoption-by-who-has-copilot-open/</guid><description>Weekly active users tells you nothing about AI proficiency. A metric-driven framework that works better.</description></item><item><title>About</title><link>https://nocodingrequired.ai/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://nocodingrequired.ai/about/</guid><description>&lt;p&gt;Engineering is changing fast. This blog is where I write up what works, and what doesn&amp;rsquo;t, when an engineering org adopts AI for real. Working on something similar? I want to hear how you handle the measurement piece.&lt;/p&gt;</description></item></channel></rss>