<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Calm-Ux on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/calm-ux/</link><description>Recent content in Calm-Ux on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 12 Oct 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/calm-ux/index.xml" rel="self" type="application/rss+xml"/><item><title>The Calmer Front Door</title><link>https://drlongnecker.com/blog/2026/10/the-calmer-front-door/</link><pubDate>Mon, 12 Oct 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/10/the-calmer-front-door/</guid><description>&lt;p&gt;Back in April, I wrote about &lt;a href="https://drlongnecker.com/blog/2026/04/agent-facing-product-design-api-first-interface/"&gt;the new front door&lt;/a&gt; that software organizations were beginning to build. The focus was on autonomous agents becoming legitimate product clients. We looked at &lt;code&gt;llms.txt&lt;/code&gt; files and Model Context Protocol (MCP) endpoints designed so synthetic callers could query products directly without scraping brittle HTML.&lt;/p&gt;
&lt;p&gt;Engineering teams have spent the past year or so writing up the necessary architectural work for these endpoints, but as that build-out accelerated, an unintended side effect crept into our product roadmaps. While we were busy optimizing structured data pipes for autonomous callers, the interfaces meant for actual people quietly turned into crowded, exhausting dashboards.&lt;/p&gt;</description></item></channel></rss>