<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Architecture on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/software-architecture/</link><description>Recent content in Software-Architecture on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 05 Oct 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/software-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Do I Need These 7,100 Lines?</title><link>https://drlongnecker.com/blog/2026/10/due-diligence-ai-code-footprint/</link><pubDate>Mon, 05 Oct 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/10/due-diligence-ai-code-footprint/</guid><description>&lt;p&gt;A developer&amp;rsquo;s pull request shows up for a working feature and thorough end-to-end tests backing it. The implementation works as promised, passing every validation check without a hitch. Yet when you ask how the architecture hooks together under the hood, they hesitate. The code runs and the test suite passes, but nobody can explain what the system actually does behind the interface.&lt;/p&gt;
&lt;p&gt;That gap between functional execution and human comprehension is quietly turning into a serious operational hazard. When teams celebrate delivery speed without interrogating the footprint left behind, they trade immediate progress for long-term fragility.&lt;/p&gt;</description></item></channel></rss>