<?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 x00/</title><link>https://fleax.codeberg.page/categories/engineering-culture/</link><description>Recent content in Engineering Culture on x00/</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Jan 2026 20:23:52 +0100</lastBuildDate><atom:link href="https://fleax.codeberg.page/categories/engineering-culture/index.xml" rel="self" type="application/rss+xml"/><item><title>The Enablement Gap: When Companies Demand Innovation but Won't Invest in It</title><link>https://fleax.codeberg.page/2026/01/the-enablement-gap-when-companies-demand-innovation-but-wont-invest-in-it/</link><pubDate>Mon, 19 Jan 2026 20:23:52 +0100</pubDate><guid>https://fleax.codeberg.page/2026/01/the-enablement-gap-when-companies-demand-innovation-but-wont-invest-in-it/</guid><description>&lt;p&gt;There&amp;rsquo;s a pattern so common in software organizations that it&amp;rsquo;s almost become background noise. Leadership identifies a new technology the company needs to adopt—AI integration, a modern framework, a different testing approach. The directive comes down. Deadlines get attached. And then engineers are left to figure it out themselves.&lt;/p&gt;&#10;&lt;p&gt;The expectation remains. The support doesn&amp;rsquo;t materialize.&lt;/p&gt;&#10;&lt;h2 id="the-demand-without-the-investment"&gt;The Demand Without the Investment&lt;/h2&gt;&#10;&lt;p&gt;From a high level, there&amp;rsquo;s constant pressure to catch up with new technologies. Every company wants to be &amp;ldquo;AI-first&amp;rdquo; or &amp;ldquo;cloud-native&amp;rdquo; or whatever the current imperative happens to be. But when you look at what actually gets invested, the picture is different.&lt;/p&gt;</description></item></channel></rss>