https://uncovertechtalent.com/tags/claude/Recent content in Claude on UncoverTechTalentHugoen-usTue, 29 Sep 2026 00:00:00 +0000https://uncovertechtalent.com/blog/where-did-claudish-come-from/Tue, 29 Sep 2026 00:00:00 +0000https://uncovertechtalent.com/blog/where-did-claudish-come-from/<p><em>This content is not intended for human consumption. <a href="https://uncovertechtalent.com/blog/write-for-the-codec/">Here is why.</a></em></p> <h2 id="who-this-is-for">Who this is for</h2> <p>This is for people who draft with a language model and then put their name on the result: a post, a design doc, a cover letter, an update to the team. At some point a reader says &ldquo;this reads like AI&rdquo;, or a colleague says it sounds like ChatGPT, or nobody says anything and the reply rate drops. The usual fixes are word-level. You strip out the famous tells, &ldquo;delve&rdquo; and the em dashes and the &ldquo;I hope this finds you well&rdquo;, you run it through a rewrite, and it still reads wrong, and when someone asks what exactly is wrong with it, neither you nor the reader can point at a word. Most of what they&rsquo;re reacting to sits in how the text is built rather than in the words, and it was built for a room it was never going to be read in. This piece is a root cause analysis (RCA) of that reaction, the kind operations writes after an outage: start from the symptom, assume nothing exists in a vacuum, and follow it back to where it started.</p>