<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering-Culture on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/engineering-culture/</link><description>Recent content in Engineering-Culture on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 14 Aug 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/engineering-culture/index.xml" rel="self" type="application/rss+xml"/><item><title>Leading Both Ends of the Adoption Curve</title><link>https://drlongnecker.com/blog/2026/08/leading-both-ends-of-the-adoption-curve/</link><pubDate>Fri, 14 Aug 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/08/leading-both-ends-of-the-adoption-curve/</guid><description>&lt;p&gt;Put a twenty-year engineer and a fresh from college junior in the same office tech rollout meeting and two completely different objections usually show up. The veteran says there was nothing wrong with the old system. The junior says the antiquated setup isn&amp;rsquo;t how they work.&lt;/p&gt;
&lt;p&gt;Both sound like resistance to change on the surface. Treat them as the same complaint, though, and the standard playbook (more patience, more generic training) ends up failing both people because they&amp;rsquo;re &lt;strong&gt;not actually describing the same problem&lt;/strong&gt;. One is about &lt;strong&gt;workflow fluency&lt;/strong&gt; or the muscle memory and judgment built from years in a specific tool ecosystem. The other is about &lt;strong&gt;device fluency&lt;/strong&gt; or the interaction model someone has spent years internalizing&amp;ndash;phone-first, touch-native, app-centric&amp;ndash;that doesn&amp;rsquo;t map to a keyboard, file system, and windowed desktop.&lt;/p&gt;</description></item></channel></rss>