<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Anchor Engineering on Napping to Heavy Metal</title><link>https://nappingtoheavymetal.com/tags/anchor-engineering/</link><description>Recent content in Anchor Engineering on Napping to Heavy Metal</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 15 Sep 2026 01:06:42 -0700</lastBuildDate><atom:link href="https://nappingtoheavymetal.com/tags/anchor-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Principles of Anchor Engineering</title><link>https://nappingtoheavymetal.com/post/2026-09-15-principles-of-anchor-engineering/</link><pubDate>Tue, 15 Sep 2026 01:05:56 -0700</pubDate><guid>https://nappingtoheavymetal.com/post/2026-09-15-principles-of-anchor-engineering/</guid><description>&lt;p&gt;I have often seen one engineer get much faster with AI coding agents; then adding a second engineer or a third on the same team doesn&amp;rsquo;t necessarily speed up development. Sometimes the &amp;ldquo;fast team&amp;rdquo; is just one person operating in a silo. What I wanted to understand was why teams didn&amp;rsquo;t seem able to move faster, even when they were trying.&lt;/p&gt;</description></item></channel></rss>