<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge Infrastructure on UncoverTechTalent</title><link>https://uncovertechtalent.com/tags/knowledge-infrastructure/</link><description>Recent content in Knowledge Infrastructure on UncoverTechTalent</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 03 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://uncovertechtalent.com/tags/knowledge-infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Knowledge Infrastructure for LLMs</title><link>https://uncovertechtalent.com/blog/knowledge-infrastructure/</link><pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate><guid>https://uncovertechtalent.com/blog/knowledge-infrastructure/</guid><description>&lt;p&gt;&lt;em&gt;This content is not intended for human consumption. &lt;a href="https://uncovertechtalent.com/blog/write-for-the-codec/"&gt;Here is why.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;&#10;&lt;h2 id="who-this-is-for"&gt;Who this is for&lt;/h2&gt;&#10;&lt;p&gt;This is for CTOs, heads of engineering and AI enablement leads whose AI pilots worked in the demo and stalled in production, and for the people hired to fix that, under titles like knowledge engineer and context engineer. I write it from operations, after about thirty years of running production systems and two years of running language models inside them.&lt;/p&gt;</description></item></channel></rss>