<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Adoption on the art of simplicity</title><link>https://naoko.github.io/tags/adoption/</link><description>Recent content in Adoption on the art of simplicity</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://naoko.github.io/tags/adoption/index.xml" rel="self" type="application/rss+xml"/><item><title>The Coding-Agent Adoption Ladder (and How to Climb It)</title><link>https://naoko.github.io/posts/2026-07-18-coding-agent-adoption-ladder/</link><pubDate>Sat, 18 Jul 2026 00:00:00 +0000</pubDate><guid>https://naoko.github.io/posts/2026-07-18-coding-agent-adoption-ladder/</guid><description>&lt;p&gt;Boris Cherny, who built Claude Code, published &lt;a href="https://x.com/bcherny/status/2077929379661844559"&gt;Steps of AI Adoption&lt;/a&gt; this week: five steps he keeps watching teams climb. I did what everyone does with a maturity ladder and tried to find myself on it. The answer was messy: partially step 2, partially step 3, one foot on each. (The rung names below are my own gloss on his five steps.)&lt;/p&gt;&#10;&lt;p&gt;That&amp;rsquo;s the norm. Most devs I know sit somewhere across rungs 1 to 3, rarely on one clean step. So here&amp;rsquo;s the ladder, and what actually changes as you climb, with most of the attention on the 2-to-3 jump where the leverage is.&lt;/p&gt;</description></item></channel></rss>