<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tech Leadership on</title><link>https://geekyschmidt.com/tags/tech-leadership/</link><description>Recent content in Tech Leadership on</description><image><title/><url>https://geekyschmidt.com/images/papermod-cover.png</url><link>https://geekyschmidt.com/images/papermod-cover.png</link></image><generator>Hugo</generator><language>en</language><copyright>Copyright ©2002-2026, Nicholas Schmidt; all rights reserved.</copyright><lastBuildDate>Sun, 31 May 2026 06:10:00 +0000</lastBuildDate><atom:link href="https://geekyschmidt.com/tags/tech-leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>Scaling the Moat: Overcoming the Talent Constraint in Domain-Driven AI Development</title><link>https://geekyschmidt.com/post/2026-6-01-ai-moat/</link><pubDate>Sun, 31 May 2026 06:10:00 +0000</pubDate><guid>https://geekyschmidt.com/post/2026-6-01-ai-moat/</guid><description>&lt;p&gt;Aaron Brethorst&amp;rsquo;s &lt;a href="https://www.brethorsting.com/blog/2026/05/domain-expertise-has-always-been-the-real-moat/"&gt;recent piece&lt;/a&gt; argues that domain expertise is the ultimate moat in an AI-driven world. He is spot on. AI has commoditised code generation, shifting the bottleneck from &amp;ldquo;can you build it&amp;rdquo; to &amp;ldquo;do you actually understand the problem well enough to know if the output is right.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;But a deep domain moat introduces a brutal operational reality: it drastically shrinks your talent pool. Finding engineers who understand high-performance architecture and niche industry nuance is like searching for a unicorn.&lt;/p&gt;</description></item></channel></rss>