<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on UncoverTechTalent</title><link>https://uncovertechtalent.com/tags/documentation/</link><description>Recent content in Documentation on UncoverTechTalent</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://uncovertechtalent.com/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Write for the Codec</title><link>https://uncovertechtalent.com/blog/write-for-the-codec/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://uncovertechtalent.com/blog/write-for-the-codec/</guid><description>&lt;p&gt;&lt;em&gt;This content is not intended for human consumption. This page explains why.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Nobody reads your documentation. Both ends are Claude now.&lt;/p&gt;&#10;&lt;p&gt;Watch the chain in any AI-heavy team this year. You explain intent to your agent in a messy conversation. The agent writes the doc. A colleague never opens the doc; their agent reads it and renders an answer into their context, at their level, in their language. Two humans communicated. Neither touched the file.&lt;/p&gt;</description></item></channel></rss>