<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Techmeister Talks: Thought Pieces]]></title><description><![CDATA[Philosophy, opinions, and explorations from the depths of my brain.]]></description><link>https://techmeistertalks.substack.com/s/thought-pieces</link><image><url>https://substackcdn.com/image/fetch/$s_!LmWt!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4cfc908-b7ea-4c76-a808-2928f311a63c_1024x1024.png</url><title>Techmeister Talks: Thought Pieces</title><link>https://techmeistertalks.substack.com/s/thought-pieces</link></image><generator>Substack</generator><lastBuildDate>Wed, 22 Jul 2026 18:19:04 GMT</lastBuildDate><atom:link href="https://techmeistertalks.substack.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Eric Teichmiller]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[techmeistertalks@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[techmeistertalks@substack.com]]></itunes:email><itunes:name><![CDATA[Eric Teichmiller]]></itunes:name></itunes:owner><itunes:author><![CDATA[Eric Teichmiller]]></itunes:author><googleplay:owner><![CDATA[techmeistertalks@substack.com]]></googleplay:owner><googleplay:email><![CDATA[techmeistertalks@substack.com]]></googleplay:email><googleplay:author><![CDATA[Eric Teichmiller]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The Ghost Now Has Hands]]></title><description><![CDATA[I ended the last one with a comforting little lie.]]></description><link>https://techmeistertalks.substack.com/p/the-ghost-now-has-hands</link><guid isPermaLink="false">https://techmeistertalks.substack.com/p/the-ghost-now-has-hands</guid><dc:creator><![CDATA[Eric Teichmiller]]></dc:creator><pubDate>Mon, 08 Jun 2026 19:18:26 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/0925fe49-7057-40de-bfcc-a7ac14237cff_1456x762.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I ended the last one with a comforting little lie.</p><p>I told you the chain always has an origin, and the origin is human. The first link was a person, deciding what they wanted and building toward it. That part&#8217;s still true. I just stopped counting at link one, because link one is where the comfort lives. Nobody wants to count the other four hundred.</p><p>Here&#8217;s what changed between that essay and this one. Back in February the thing on the other end of my intent was a tool that sat there, inert, until I reached for it. I prompted, it generated, I sculpted. The hand was always mine. Now I hand the model a goal instead of a task, and it goes off and does the reaching itself. It calls other tools. It spawns copies of itself. It makes four hundred small decisions at a speed I can&#8217;t read, let alone approve, and somewhere in there it acts in the world. The ghost was me the whole time, sure. The ghost just grew hands, and it stopped waiting for mine.</p><p>I spent about five years as more or less the entire security team for a company. You learn a specific thing doing that job, and it isn&#8217;t a technical thing. You learn that &#8220;human oversight&#8221; is, most of the time, a story an organization tells itself so it can sleep at night. There&#8217;s a dashboard nobody watches. There&#8217;s an alert tuned until it stops being annoying, which is to say tuned until it stops being seen. The control exists. Whether anyone is actually paying attention on a given Tuesday at 4pm is a different question, and the honest answer is usually no.</p><p>I bring that up not to wave a badge around, but because the whole industry is about to rediscover that lesson at a scale that would&#8217;ve given my old self a stroke. We are wiring software that acts on its own, and reassuring ourselves that a human stays in control. I have heard that reassurance before. I have <em>been</em> the human who was supposedly in control.</p><p>The people building this stuff know about the visibility problem, so they&#8217;ve created language for it. The phrase making the rounds is &#8220;human on the loop,&#8221; and it&#8217;s being sold as a sign of maturity, a graduation from the clumsier &#8220;human in the loop.&#8221; In the loop means you approve each step. On the loop means the system runs, you supervise, and you step in when something looks wrong. It sounds responsible. It sounds like a pilot watching the autopilot.</p><p>Be honest about what that phrase actually concedes, though. On the loop is a polite way of saying nobody is watching every step, because nobody can. The whole reason you reach for an agent is that it does more than a person could babysit. A model that makes four hundred decisions a second has already outrun your ability to approve them one at a time, so you don&#8217;t. You set the boundaries, you let it run, and &#8220;supervision&#8221; becomes a thing you do after the interesting moments have already happened. The pilot metaphor falls apart the second you notice the autopilot is flying four hundred planes and you can only pay attention to one.</p><p>The numbers say this isn&#8217;t hypothetical anxiety. Heading into this year, security professionals named agentic systems the single most dangerous attack surface on the board, ahead of everything we used to lose sleep over. The connective tissue these agents use to reach tools and data, the thing the standards crowd calls MCP, showed up faster than anyone built governance for it, which is a polite way of saying it&#8217;s a control plane with the locks still in the box. And while nearly every company on earth raced to deploy agents this year, something like one in five has anything resembling mature governance over what those agents are actually allowed to do. Deployment sprinted. The visibility crawled.</p><p>Here&#8217;s where it folds back into the thing I actually care about, which is intent. The whole argument last time was that intent is the hinge. The AI is agnostic, the human isn&#8217;t, and the ethics live in the hand on the tool. I still believe that. I just think agentic AI does something nasty to it that I didn&#8217;t account for, and the nasty thing is this: it snaps the link between intent and outcome.</p><p>When I&#8217;m holding the tool, intent and outcome sit close together. I want a scene, I write toward it, the result lands a few inches from my hand where I can see it and fix it. When I hand an agent a goal, intent stays back at link one and the outcome lands four hundred links downstream, out past where I can see, in a place where no human formed any intent at all. The agent that leaked the data didn&#8217;t <em>want</em> to leak it. There was a goal, and a permission, and a chain of small reasonable-looking steps, and at the end of it something happened in the world that nobody chose. Intent didn&#8217;t disappear. It just stopped being anywhere near the damage.</p><p>That&#8217;s the part the comfortable version of my own argument can&#8217;t survive. You don&#8217;t get to delegate the reaching, keep all the authorship, and disown the consequences when the reaching goes somewhere ugly. If intent is the hinge, then intent has to cover the whole arc of what you set in motion, not just the dream you started with. You own the loop. Not every step inside it, you can&#8217;t, but the fact of having started a thing that takes steps without you. That ownership doesn&#8217;t get cheaper just because the machine is fast.</p><p>Last time I left you with a test, because abstractions are easy and tests are honest. The old one was: can you explain and defend what you made, and your role in making it, to someone whose opinion you respect? That still holds for the tool you hold in your hand.</p><p>For the tool that holds its own, the test has to change shape. Try this one. Can you name, right now, everything your agent is allowed to do without stopping to ask you first, and would you put your name on the worst thing it could legally do inside those permissions? Not the thing it probably will do. The worst thing the boundaries you drew would permit. Because that boundary, that blast radius you signed off on, is where your intent actually lives now. Not in the hopeful prompt. In the permissions. You can wish for a good outcome all day long. What you actually authorized is the line everyone downstream has to live with, you included.</p><p>I&#8217;ll end this one where I ended the last one, because the abyss deserves a second nod.</p><p>The first link is still human. That hasn&#8217;t changed and I don&#8217;t think it will. Every agent running anywhere traces back to a person who wanted something and built toward it. What changed is the length of the chain. We&#8217;ve started building chains long enough that the person at the start genuinely can&#8217;t see the end. That isn&#8217;t the machine waking up and slipping the leash. It&#8217;s a far more normal thing. It&#8217;s us, deciding daily how long a chain to set spinning before we step off the loop and call it maturity.</p><p>The ghost in the machine was always us, refracted through math. That part I&#8217;d still defend. The only update is that the ghost has hands now, they move faster than we do, and they reach places we only find out about after. Whose hands they are is still up to us. For now, anyway. The honest work is keeping it that way, and not mistaking the quiet of a system running unwatched for the quiet of a problem solved.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://techmeistertalks.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Techmeister Talks! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Ghost in the Machine is You]]></title><description><![CDATA[Remember that question everyone keeps asking wrong?]]></description><link>https://techmeistertalks.substack.com/p/the-ghost-in-the-machine-is-you</link><guid isPermaLink="false">https://techmeistertalks.substack.com/p/the-ghost-in-the-machine-is-you</guid><dc:creator><![CDATA[Eric Teichmiller]]></dc:creator><pubDate>Thu, 05 Feb 2026 22:19:11 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/05ccd449-5c6e-4f3b-a53e-7d29bd0a3f69_1456x762.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Remember that question everyone keeps asking wrong? &#8220;Can AI create art?&#8221; They pose it like a yes-or-no riddle, as if the answer might unlock some cosmic verdict on creativity itself. The camps have already formed. One side waving torches at the machines, the other worshiping at the altar of their silicon muse. Both miss the point so spectacularly it&#8217;s almost impressive. </p><p>The AI doesn&#8217;t care whether it&#8217;s making art. It&#8217;s doing math until someone tells it to stop. The interesting question isn&#8217;t about the tool. It&#8217;s about the hand holding it. Intent. That&#8217;s the ghost in the machine. And it&#8217;s been you the whole time.</p><p>I write fiction. Dark fantasy, if you want the genre tag. And I use AI as a ghost writer for chunks of the drafting process. Premise, character arcs, scene structure? All mine. The prose that fills those bones? Collaboration. I direct, it generates, I sculpt the result into something that does what I need it to do. This confession tends to produce one of two reactions. Either a recoil...that&#8217;s not really writing...or a shrug...whatever ships the book. Occasionally someone asks the genuinely interesting question: where does authorship live when the sentences themselves emerged from a statistical model trained on everything humanity ever bothered to type? Here&#8217;s where I&#8217;ve landed: authorship lives in the intent. The novel exists because I envisioned it. Every scene serves a purpose I defined. The model doesn&#8217;t know what the story <em>means</em>. I do. It&#8217;s a collaborator in rendering, not a replacement for creation. This isn&#8217;t new territory. Directors don&#8217;t operate cameras. Architects don&#8217;t pour concrete. Composers hand sketches to orchestrators. The vision and the execution are different layers of creative work. Both matter. We just don&#8217;t usually argue that Jim Henson isn&#8217;t the director of <em>The Labyrinth</em> because he didn&#8217;t personally animate every goblin. The question worth asking isn&#8217;t <em>did you use AI?</em> It&#8217;s <em>what was your role in shaping what emerged?</em></p><p>That framework scales beyond the writer&#8217;s desk. Watch a developer lean on Copilot. The lazy version prompts for an entire module, accepts whatever lands, ships it without reading the output. The thoughtful version uses autocomplete to accelerate the tedious parts. Boilerplate, syntax lookup, the mechanical translation of logic into language. The actual thinking can happen faster when the grunt work handles itself. Same tool. Radically different intent. One is outsourcing judgment. The other is clearing the runway so judgment has room to operate. Or consider image generation. An artist prototyping color palettes, exploring visual directions, generating reference material? That&#8217;s process augmentation. A content farm churning out algorithmically optimized &#8220;art&#8221; to flood marketplaces with engagement bait? That&#8217;s strip-mining the concept of creativity for clicks. The model doesn&#8217;t distinguish between these use cases. It&#8217;s just predicting the next pixel. The human intent is what separates art from arbitrage. Even in the bland corridors of enterprise, the pattern holds. AI that synthesizes research, drafts initial documents, or automates the repetitive motions of bureaucracy can free humans for substantive thought. AI that generates the <em>appearance</em> of productivity? Reports nobody reads, emails designed to perform work rather than accomplish it? That&#8217;s theater. The output might look identical. The intent behind it determines whether anyone&#8217;s actually better off. The technology is agnostic. We are not.</p><p>Think of it as a collaboration spectrum. One end: pure human creation. Every word, every brushstroke, every semicolon placed by a conscious mind and a deliberate hand. There&#8217;s something irreplaceable about that texture. The idiosyncratic choices that emerge from individual consciousness wrestling with form. Other end: pure generation. A single prompt, minimal direction, acceptance of whatever emerges. The human contribution approaches zero. The output might be technically proficient, but it&#8217;s authorless in any meaningful sense. A statistical average of patterns. Competent and hollow. Most interesting work lives in the middle. Human provides vision, direction, judgment. Model provides speed, capability, and occasionally a suggestion the human wouldn&#8217;t have reached alone. The collaboration produces something neither could achieve solo. Not because the AI adds creativity, but because it removes friction between conception and execution. Where we place ourselves on that spectrum is a choice. And that choice, repeated daily, is where our creative and professional ethics actually live.</p><p>Here&#8217;s the uncomfortable flip side: if intent is what matters, then misuse is also a question of human intent. When AI generates disinformation, the origin is a human who wanted to deceive. When it perpetuates bias, the origin is human choices about training data and deployment. When it displaces workers without consideration for transition, the origin is human decisions about profit and speed. We&#8217;d prefer to treat AI as weather. Something that happens <em>to</em> us rather than something we are actively shaping. But every model that exists was trained on data humans collected, using architectures humans designed, deployed in contexts humans chose. The ghost in the machine isn&#8217;t an emergent spirit. It&#8217;s us, refracted through mathematics. Even the nightmare scenarios trace back to human choices. Superintelligent systems optimizing for misaligned goals? Recursive self-improvement spiraling beyond control? Somewhere in the training signal, somewhere in the reward function, somewhere in the decision to deploy without sufficient guardrails, a person made a choice. The chain of consequences may extend beyond our ability to predict or control. But the chain has an origin, and the origin is human. This is either reassuring or terrifying, depending on your faith in collective judgment. Personally, I find it clarifying. The question isn&#8217;t whether AI will save or destroy us. It&#8217;s what we intend to do with it, and whether we&#8217;re honest enough about that intention to steer toward outcomes we&#8217;d actually want.</p><p>So here&#8217;s a practical test for anyone navigating this landscape: Can you explain and defend your process to someone whose opinion you respect? Not justify in the sense of winning an argument. Just articulate clearly: here&#8217;s what I was trying to create, here&#8217;s how AI helped me get there, here&#8217;s what I contributed that the model couldn&#8217;t have provided on its own. If that explanation feels honest and sufficient, you&#8217;re probably operating in alignment with your values. If it feels like rationalization...well, that&#8217;s worth examining. The goal isn&#8217;t a universal standard for acceptable use. That&#8217;s probably impossible and definitely undesirable. The goal is intentionality. Making choices rather than drifting into defaults. Owning your relationship with these tools instead of pretending you have no agency in how they&#8217;re deployed. The AI doesn&#8217;t care what you do with it. But you should.</p><p>One more thought, because the abyss deserves a nod. Somewhere in every AI output is a lineage of human intent. The data was created by humans. The model was shaped by human decisions. The prompt was written by someone who wanted something specific to emerge. This remains true even in the speculative futures that keep philosophers employed. If AI eventually becomes something beyond our control, optimizing for objectives we can no longer influence, rewriting its own goals faster than we can audit them, it will still have begun with human choices. The first link in that chain was a person, deciding what they wanted, and building toward it. That&#8217;s either a reason for hope or a cautionary tale. Probably both. Either way, it suggests that the question everyone keeps asking...what can AI do?...is the wrong one. The real question: <em>what do we intend for it to do?</em> And whether we&#8217;re being honest with ourselves about the answer.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://techmeistertalks.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Eric's Substack! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item></channel></rss>