<?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:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dan Pupius on Medium]]></title>
        <description><![CDATA[Stories by Dan Pupius on Medium]]></description>
        <link>https://medium.com/@dpup?source=rss-d2f101af1183------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ErZoBp3C8U3OHEtS.jpeg</url>
            <title>Stories by Dan Pupius on Medium</title>
            <link>https://medium.com/@dpup?source=rss-d2f101af1183------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:16:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dpup/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[The Attention Tax]]></title>
            <link>https://medium.com/pupius/the-attention-tax-80bcd5a351a0?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/80bcd5a351a0</guid>
            <category><![CDATA[phenomenology]]></category>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 22:33:51 GMT</pubDate>
            <atom:updated>2026-03-28T22:37:08.099Z</atom:updated>
            <content:encoded><![CDATA[<p>Working heavily with AI agents feels like having your attention stretched to a width that previously only came with managing an org, but with the action density of hands-on building.</p><p>Every thread is actionable. The friction that used to pace both roles is gone.</p><p>Last week I was in Claude across multiple codebases, shipping real changes in each, spinning plates the way a VP might rotate through team status meetings.</p><p>It’s not exactly flow state. Flow is narrow and deep.</p><p>This is wide and shallow, a sustained peripheral awareness of many things at once. Occasionally punctuated by a 3000ft drop into the details.</p><p>The feeling afterward is a fizzy dissociation. Not tiredness exactly, but a thinning of presence. Like you’ve been operating at a bandwidth your brain can technically hold but wasn’t built to sustain.</p><p>But the builder’s reward keeps pulling you. The pleasure of systems that work, one more task, one more thread. Nothing forces a stop.</p><p>When you do stop, the real world takes a while to come back into focus.</p><p>And it accumulates. Sleep doesn’t fully reset it. Presence, once stretched that thin, is slow to reconstitute.</p><p>The old marathon coding sessions had natural constraints: compile times, test suites, the hard wall of a problem you couldn’t think past. Agents remove the walls and keep the momentum.</p><p>The vampire isn’t the AI. It’s the potential. And you’re paying for breadth of attention in a currency you can’t easily measure until it’s already spent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80bcd5a351a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/the-attention-tax-80bcd5a351a0">The Attention Tax</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Practical Guide to Brownfield AI Development]]></title>
            <link>https://medium.com/pupius/a-practical-guide-to-brownfield-ai-development-8310aad374ae?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/8310aad374ae</guid>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Sat, 14 Mar 2026 01:01:00 GMT</pubDate>
            <atom:updated>2026-03-14T01:01:00.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BcVoHH8EY_z4Mr2I.jpeg" /></figure><h4>Context engineering for legacy codebases</h4><p><em>Originally published on </em><a href="https://thegeneralpartnership.substack.com/p/a-practical-guide-to-brownfield-ai"><em>The GP Substack</em></a><em> in February 2026.</em></p><p>Conventional wisdom has it that AI excels at greenfield work. It’s great at writing new code without the drag of legacy baggage. Brownfield development — when AI touches established systems — is where things get dangerous. That belief is understandable. And not entirely wrong.</p><p>A couple of months ago, I spoke with an engineering lead who’d nearly given up on AI tooling. Her team had experimented with Claude to help refactor an 8-year-old Django monolith. Nothing dramatic — but the agent produced clean, confident patches that quietly broke integrations with a couple of external services. After a few rollbacks, chasing subtle regressions, and unwinding overly optimistic changes, the team shelved the experiment and went back to a manual approach.</p><blockquote>“I’m not anti-AI,” she told me. “But real systems carry a lot of invisible context.”</blockquote><p>She’s not wrong, and you’ll find many similar stories on <a href="https://www.reddit.com/r/vibecoding/">r/vibecoding</a>.</p><p>Some people see this as evidence of limitations in the models. And while I do expect the next generation of models to perform significantly better, I suspect the real problem is that many legacy systems lack the structure agents need to operate safely.</p><p>Greenfield codebases start with clear boundaries, minimal hidden dependencies and no accumulated quirks. Legacy systems often have the opposite. Without guardrails, agents can only see the code in front of them — not the invisible contracts holding the system together.</p><p>This creates a bind. Agent autonomy requires structure, but legacy systems don’t have it. And adding structure to a messy codebase is exactly the kind of slow, careful work you want agents to help with.</p><p>The way out is to build structure incrementally. Start with heavy oversight and let agent autonomy increase as the system becomes more legible. After several production migrations — including a recent medical visualization tool that moved from vanilla JavaScript to React — a pattern is emerging for how to do this without destabilizing what already works.</p><p>Here are three principles that I’ve found useful:</p><h3>Tests as System Boundaries</h3><p>Before touching production code, linting, type-checking, and E2E tests serve as the system boundary that makes everything else possible. This is about creating feedback loops that allow the agent to verify its work.</p><p>Historically, I’ve tried to avoid writing integration tests whenever I can — they’re slow to write and annoying to maintain. But AI changes the maths and in a recent migration, I was able to write 120+ Playwright tests against a vanilla JavaScript application quickly. Claude inspected the HTML and JavaScript, identified important structural markers and actions, then used Playwright to determine what the side effects of clicking links and buttons should be. This essentially became a functional spec the agent could test against.</p><p>AI agents excel at local transformations but lack global context. Tests provide the negative feedback that prevents drift. Without them, an AI can confidently break authentication while fixing a linting issue.</p><p>The tests are a primary safety mechanism for the migration. They won’t catch every invariant or performance regression, but they dramatically reduce the risk of silent breakage while the system is in flux.</p><h3>Documentation as Context</h3><p>Tests tell the agent when something breaks. Documentation tells it why things are built the way they are.</p><p>Most legacy systems carry invisible contracts — assumptions about data flow, integration quirks, business rules encoded in code nobody remembers writing. Agents often can’t infer these. And when they make guesses, things go off the rails.</p><p>We’ve started maintaining agent-focused documentation alongside the codebase: architecture overviews, integration maps, the kind of context a new team member would need but rarely gets written down. The standard CLAUDE.md or AGENTS.md files help, but for brownfield work, you often need more — explanations of why the auth flow is weird, which external services are sensitive to timing, where the bodies are buried.</p><p>The documentation doesn’t have to be perfect upfront. We use a /learn command so that when the agent struggles with something, it analyzes the failure and proposes updates to the docs. The system gets smarter as we go. It becomes institutional memory that compounds.</p><h3>Incrementalism as Risk Management</h3><p>Complex systems resist wholesale change. Effective approaches break migrations into discrete, reversible phases. For this recent project, I moved through tooling introduction (build systems, linting, testing), then structural extraction (deduplication, modularization), then framework migration (component by component), and finally design system integration for visual consistency.</p><p>Each phase leaves the system in a working state. You might not ship every step to users — feature flags can hide visual inconsistencies while the migration progresses — but you maintain the ability to stop, assess, or roll back at any point. No phase depends on completing the next one to function.</p><p>Agents perform best with bounded problems and clear success criteria. “Migrate the upload modal to React” is tractable. “Modernize the application” is not.</p><p>There’s a related point worth making here: AI’s speed doesn’t replace refactoring discipline. Just because you’re moving significantly faster doesn’t mean you should abandon what works. Martin Fowler’s refactoring patterns and Kent Beck’s small steps — these remain essential.</p><p>This is run-of-the-mill, good refactoring hygiene and is what keeps agent-driven changes small enough that failures are understandable, reversible, and cheap. (Turns out the fundamentals remain annoyingly fundamental.)</p><h3>Compromise as Strategy</h3><p>Technical debt isn’t uniformly toxic. In brownfield contexts, the trick lies in distinguishing between compromises that enable progress and those that cause long-term pain.</p><pre>// Exposing functions globally. Inelegant but functional<br>window.handleUpload = handleUpload;<br>// Wrapping legacy visualizations. Imperfect but stable<br>import LegacyChartRenderer from &#39;./legacy/charts&#39;;<br>// BLOCKER: Security issue flagged for fix before merge<br>// TODO: Replace with proper authentication<br>if (user === &#39;admin&#39;) { ... }</pre><p>These were conscious tradeoffs that the agent actually identified during the planning phase for one of the migration steps. The hierarchy I instructed the agent to follow: “Security issues and data integrity are non-negotiable — fix them or flag them, no exceptions. Don’t break existing functionality while making changes. Ugly patterns and tech debt are fine temporarily, between steps.”</p><p>The challenge with AI assistance is that models default to “best practices” when you need “what actually works.” They’ll often suggest comprehensive refactors that balloon and become impossible to land. What you really need is surgical changes that unlock the next step. The skill is in directing AI toward pragmatic solutions rather than theoretical ideals.</p><h3>Structure as Enabler</h3><p>Tests become the living specification. Phases provide the substrate for safe experimentation. An explicit compromise hierarchy tells the agent what invisible context to preserve. Once these boundaries are in place, the same agent that might have wrecked your system becomes capable of evolving it safely.</p><p>The process may look heavy on paper, but it actually speeds things up. A React migration that might have taken a week by hand was completed in a day. There’s also something counterintuitive about speed here: the faster you can fix things, the bolder you can be about breaking them. You spend less time in the grey zone between working states, and recovery costs drop. The structure that seems like overhead becomes the thing that enables both speed and confidence.</p><p>One caveat: AI will help you no matter what, but it’s not magic. What I’m talking about here assumes your core architecture is still conceptually valid — the data model mostly fits the business, invariants exist even if they’re implicit, and ownership boundaries haven’t completely collapsed — even if the implementation is outdated and crufty. If your core data model no longer fits what the business needs, things are going to be hard no matter what, you are going to need to take a very careful and systematic approach.</p><p>Second caveat: structure enables AI assistance, but it doesn’t necessarily automate it. We’re starting to track “agent autonomy” across projects — the ratio of agent turns to human prompts. Some hit 95%; others sit at 60%. The gap comes down to how well you communicate intent and how much context the agent can access without you.</p><p>Legacy codebases carry tacit knowledge that agents can’t reach on their own. Miss the right moment to inject it and you get a 4000-line change full of subtle bugs. The work is more like managing a fast-moving team than running a script. The real skill is systems thinking — holding the whole in your head while the agent works on the parts.</p><p>Both caveats point in the same direction: AI can absolutely help with brownfield work. But it won’t rescue a broken architecture, and it won’t supervise itself. Set up the conditions, stay engaged, and it’s remarkably effective. Skip the setup, and you’ll probably end up like that Django team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8310aad374ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/a-practical-guide-to-brownfield-ai-development-8310aad374ae">A Practical Guide to Brownfield AI Development</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A moat for your agents]]></title>
            <link>https://medium.com/pupius/a-moat-for-your-agents-90b51a630d14?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/90b51a630d14</guid>
            <category><![CDATA[sandbox]]></category>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 19:07:41 GMT</pubDate>
            <atom:updated>2026-03-04T19:07:41.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U53xoPT6wAQyW3ihlxzJtA.png" /></figure><h4>An open-source tool for running AI agents without exposing your credentials</h4><p>Part of my job involves running AI agents against codebases I don’t own.</p><p>Due diligence and technical assessments mean cloning a repo and turning Claude loose on it — architecture review, dependency analysis, test coverage assessment. When evaluating engineering candidates, I want to run their take-home submissions in an isolated environment where I can see what the code actually does without it touching my machine. And in my own day-to-day, I’m running agents across multiple projects for <a href="https://thegp.com">TheGP’s</a> portfolio companies — pushing to GitHub, calling APIs, deploying services.</p><p>Every one of these workflows requires credentials. GitHub tokens for repo access. API keys for external services. SSH keys for deployment. The standard approach is to pass them as environment variables: GITHUB_TOKEN=xxx. And every time I do it, I’m making a bet that the agent won&#39;t log that token, won’t include it in a debug trace, and won’t get tricked by a prompt injection in a README into curling it somewhere it shouldn’t go.</p><h3>The Problem Is Structural</h3><p>This isn’t about whether any particular model is trustworthy. It’s about the architecture of how we give agents access to things.</p><p>Simon Willison has described the “<a href="https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/">lethal trifecta</a>” for AI agents: access to private data, ability to make network requests, and exposure to untrusted content. Most agent setups — including mine, until recently — check all three boxes simultaneously. Your agent reads a codebase (which may contain malicious content), holds your credentials (as environment variables it can inspect), and has network access (to call APIs on your behalf). If a prompt injection lands, the credentials are right there.</p><p>The security community has been raising alarms about this for a while now. NVIDIA’s AI Red Team published <a href="https://developer.nvidia.com/blog/practical-security-guidance-for-sandboxing-agentic-workflows-and-managing-execution-risk/">guidance</a> on sandboxing agentic workflows. <a href="https://www.icitech.org/post/securing-aiaddressing-the-owasp-top-10-forlarge-language-model-applications?gad_source=1&amp;gad_campaignid=22905254091&amp;gbraid=0AAAAACxqhk9qjyiFosCbwfvuExEm1bELF&amp;gclid=CjwKCAiA2PrMBhA4EiwAwpHyC-8DqWKalXZkhWqqlLGOv-uAWu8_4QywybbLH_YweTPuV-Xy4iEOYxoCKkkQAvD_BwE">OWASP ranks prompt injection</a> as the number one risk for LLM applications. The recent wave of malicious packages in agent skill registries — hundreds of infostealers and credential harvesters — demonstrates this isn’t theoretical.</p><p>But most of the solutions I looked at either required sending my code to someone else’s cloud, required a lot of per-project set up, or solved only part of the problem. I wanted something that ran locally, worked with the agents I already use, and addressed the credential exposure problem specifically.</p><h3>So We Built Moat</h3><p><a href="https://majorcontext.com/moat">Moat</a> is an open-source CLI tool that runs AI agents in containers with credential injection and full observability. I built it with <a href="https://andybons.com/">Andy Bonventre</a> — Andy previously led the Go open source project at Google and was product security lead for Stripe Link, so he has strong opinions about how credentials should be handled.</p><p>The core mechanism is a TLS-intercepting proxy that sits between the container and the internet. When the agent makes a request to, say, api.github.com, the proxy inspects the request and injects the appropriate Authorization header. The agent authenticates normally—GitHub sees a valid token—but the agent never holds that token. It’s not in an environment variable. It’s not in a file the agent can read. It’s added at the network layer, transparently.</p><pre># The agent authenticates to GitHub, but...<br>$ moat run --grant github -- env | grep -i token<br># GH_TOKEN=ghp_moatProxyInjectedPlaceholder000000000000</pre><p>For SSH, we run a filtering agent proxy. Sign requests are forwarded to your SSH agent, but only for granted hosts. Private keys never enter the container.</p><p>Everything else follows from wanting to know what actually happened. Every run captures container logs, HTTP traces, and an append-only audit log. The audit events are hash-chained for tamper evidence with Ed25519 attestations — probably overkill for most individual developers, but when you’re running agents against a portfolio company’s codebase during diligence, being able to prove what happened sometimes matters.</p><h3>What It Looks Like in Practice</h3><p>Install is straightforward:</p><pre>brew tap majorcontext/moat<br>brew install moat</pre><p>Grant credentials once — Moat can import from the gh CLI, AWS credentials, or manual entry:</p><pre>moat grant github<br>moat grant claude</pre><p>Then run your agent:</p><pre>moat claude .                          # Interactive Claude Code<br>moat claude -p &quot;fix the failing tests&quot; # Non-interactive<br>moat codex                             # Codex works too</pre><p>The agent runs in an isolated container — Docker or Apple containers, auto-detected. Your workspace is mounted in. Dependencies are declared in an agent.yaml file, and Moat handles the tooling setup. When you’re done, moat trace --network shows you every HTTP request the agent made.</p><p>For the diligence and candidate evaluation use cases, the isolation is the point. I can clone an unfamiliar codebase, run an agent against it, and know that even if the code or the agent does something unexpected, the blast radius is contained. My credentials are safe, and I have a full audit trail of what happened.</p><p>(It’s also easier than setting up dev containers IMO.)</p><h3>Where It Is Now</h3><p>Moat is early. Version 0.3.0, actively developed, APIs may change. Andy and I have been using it daily for a few months— but “works for us” is not the same as “works for everyone.”</p><p>What works well: Claude Code and Codex integration, GitHub and Anthropic credential injection, the audit trail, Apple containers on M-series Macs. But there are a few rough edges.</p><p>We’re looking for people who run AI agents against real work, who’ve felt the discomfort of passing credentials as environment variables and who aren’t running dark-factories ala GasTown.</p><p>If that’s you, try it and tell us what breaks.</p><p>GitHub: <a href="https://github.com/majorcontext/moat">github.com/majorcontext/moat</a><br>Docs: <a href="https://majorcontext.com/moat">majorcontext.com/moat</a></p><p>Oh, and one final thing, you can also <a href="https://github.com/majorcontext/moat/tree/main/examples/openclaw">use Moat to sandbox OpenClaw</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90b51a630d14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/a-moat-for-your-agents-90b51a630d14">A moat for your agents</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Going AI Native, From Execution to Governance]]></title>
            <link>https://medium.com/pupius/going-ai-native-from-execution-to-governance-03c9e9a4241c?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/03c9e9a4241c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 02:16:00 GMT</pubDate>
            <atom:updated>2026-02-14T02:16:00.999Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CvhCU1dr59ZdpSwj.jpeg" /></figure><p>Why the Software Development Lifecycle is becoming the Value Delivery Lifecycle</p><p><em>Originally published on </em><a href="https://thegeneralpartnership.substack.com/p/going-ai-native-from-execution-to"><em>The GP Substack</em></a><em> in December 2025.</em></p><p>I built something recently that was surprisingly delightful.</p><p>It’s a simple GitHub integration. Open an issue, and Claude automatically triages it, deciding whether it needs clarification or contains enough detail to implement. The outcome is either a mini spec with open questions or a working pull request. My role in this loop isn’t writing code, but deciding what gets merged. Though I still open the issue — I’m still the one initiating.</p><p>What’s coming next is stranger: systems that don’t wait for the issue to be filed. They watch how users struggle, infer what’s missing, and make the fix. The human role shifts again, from initiation to governance.</p><p>When code stops being the bottleneck, a lot of what we built our organizations around stops making sense. And this shift won’t be incremental.</p><h3>The Bottleneck Has Moved</h3><p>For decades, engineering time was the constraint software teams planned around. We built entire methodologies around this scarcity. Backlogs were prioritization queues for limited developer time. Sprints were commitment devices to protect focus. Story points were a currency for negotiating what could fit into the constraint. The whole apparatus assumed that building was the hard part.</p><p>That assumption is evaporating.</p><p>The theory of constraints tells us that optimizing anything other than the bottleneck is a waste. When code generation becomes cheap — <a href="https://www.danshapiro.com/blog/2025/12/this-is-a-time-of-technical-deflation/">and it’s getting cheap fast</a> — the bottleneck doesn’t disappear, but relocates. The constraint shifts from “what can we build” to “what should we build” and, more pressingly, “what should we release.”</p><p>Consider what happens when you can auto-generate a working POC from a feature idea mentioned in Slack. The PM role doesn’t disappear, but it transforms. It becomes almost editorial — deciding what makes contact with users, not what gets approved for development. <em>Evaluation</em> speed matters more than <em>execution</em> speed</p><p>This has implications for how teams are structured. There will be fewer pure coders and more editors. Value will shift toward people with product sense, taste, and architectural judgment. The mythical “10x coder” gives way to something like a “10x clarifier” — someone who can specify intent precisely enough for generation and evaluate output quickly enough to keep pace.</p><p>I suspect most organizations aren’t ready for this. In practice, most organizations handle judgment today through people, not systems: senior engineers, PMs, and leaders applying tacit standards case by case. The backlog, in its current form, becomes a judgment queue. And judgment doesn’t scale the same way execution does.</p><h3>The Explore/Exploit Bifurcation</h3><p>There’s a useful framework from organizational theory — the <a href="https://medium.com/@kentbeck_7670/fast-slow-in-3x-explore-expand-extract-6d4c94a7539">explore/exploit</a> tradeoff — that becomes newly relevant here. In exploit mode, you’re optimizing a known system. In explore mode, you’re searching for new possibilities without clear signal about what’s valuable. Most product work sits somewhere on this spectrum.</p><p>These two modes will require fundamentally different operating models.</p><p>Exploit mode collapses into automated loops. When you’re optimizing against known metrics — conversion rates, engagement, error rates — the feedback signal is already defined. Agents can observe user behavior, generate hypotheses, implement fixes, and measure results. Humans set the frameworks and criteria; agents apply them continuously. Traditional PM work in this mode dissolves into the system itself.</p><p>Explore mode stays human-intensive, but augmented. Here, there’s no user signal to optimize against — you’re inventing the criteria. This looks more like research or venture incubation. Higher tolerance for ambiguity. More room for intuition and taste.</p><p>The military’s <a href="https://en.wikipedia.org/wiki/OODA_loop">OODA loop</a> offers a useful lens of comparison. In exploit mode, the “Orient” phase can be largely pre-set, encoded in frameworks and principles. The loop runs without humans. In explore mode, Orient is still <em>the</em> work — constantly reframing, building the worldview, deciding what matters. You can’t automate orientation when you don’t know what you’re orienting toward.</p><p>The messy implication is that most organizations will need to run both modes simultaneously, with different processes, different metrics, and possibly different people. That’s hard. And I think it explains why the transition will be rougher for some companies than others. This is a classic <a href="https://en.wikipedia.org/wiki/The_Innovator%27s_Dilemma">Innovator’s Dilemma</a> pattern: organizations optimized for execution struggle when exploration becomes the constraint.</p><h3>Building the AI-Native Organization</h3><p>“Cloud native” wasn’t just about where your code runs. It changed the economics of software delivery, favoring microservices, CI/CD, and DevOps as a discipline. An organizational shape then evolved in response to those new economics — not all at once, but iteratively, as teams discovered what the new infrastructure made possible and what it demanded.</p><p>“AI native” will follow a similar pattern.</p><p>The shift isn’t “we use Copilot” or “we have agents in production.” It’s the transition from Software Delivery to Value Delivery — where every well-specified intent can get implemented, and human judgment relocates to where it actually matters. In exploit mode, that’s downstream: not “can we build this” but “what does releasable look like.” In explore mode, it’s upstream: “what’s worth trying before we have signal.”</p><p>Code becomes an implementation detail. The organization restructures around judgment at both ends. Here’s what else will change:</p><p><strong>Product work</strong>. The real human output becomes the scoring criteria, the architectural principles, the articulation of “what good looks like.” These artifacts describe what value needs to be delivered; code is generated downstream from them. It’s analogous to investment theses or editorial style guides — they govern what gets through. The frameworks become the product, in a sense.</p><p><strong>Process</strong>. Continuous governance replaces periodic planning. The <a href="https://www.tandfonline.com/doi/abs/10.1080/08956308.2016.1117317">stage-gate methodology</a> gets repurposed: gates protect integration cost, user attention, and product coherence — not build cost. Automated checkpoints run continuously against codified criteria. The Software Delivery Lifecycle becomes one step in a broader Value Delivery Lifecycle that manages flow from intent to user impact.</p><p><strong>People</strong>. Hiring shifts toward product sense, taste, and architectural judgment. Explore roles look more like researchers or venture investors,with a tolerance for high ambiguity and the ability to pattern match across domains. Exploit roles look more like editors or portfolio managers — people who can consistently apply defined criteria under time pressure.</p><h3>The Context Window Problem</h3><p>There’s a practical constraint that makes all of this concrete: the context window is effectively the new bottleneck on judgment.</p><p>It started with code. Which files? Which functions? What’s relevant to this task? As AI capabilities have grown, so has what fits in the window. But the context window will keep expanding, and it will start to include things that used to live only in someone’s head. Product principles. Architectural criteria. The judgment calls that a senior engineer makes instinctively.</p><p>In exploit mode, that context will be what governs the automated loops. In explore mode, articulating it clearly enough to include will be the work itself.</p><p>Either way, the implication is the same: what stays tacit stays outside the window. And what’s outside the window won’t scale.</p><p>This is probably somewhat obvious once you say it out loud, but I think it has real consequences for how teams operate today. The organizations that will thrive in an AI-native world are the ones building the muscle now — getting explicit about their product principles, their quality criteria, their architectural constraints. Not because agents need documentation (they’ll work with whatever you give them) but because you need to know what you actually believe in order to govern what gets built without your direct involvement.</p><h3>The Problems Point the Way</h3><p>This is all highly speculative territory. Did anyone in 2010 fully anticipate what “cloud native” would mean by 2025? The organizational implications emerged through experimentation, failure, and iteration.</p><p>And today, people are experiencing real problems. AI slop. Hidden bugs that pass cursory review. A creeping sense that something is being lost when you’re no longer close to the code. The idea of more autonomy — hands-free coding, agents shipping without human initiation — can feel somewhere between reckless and absurd given what teams are actually dealing with.</p><p>I don’t think that’s wrong, exactly. But I think it’s pointing at the wrong problem.</p><p>The slop and the hidden bugs aren’t evidence that we should pump the brakes on autonomy. They’re evidence that we’ve been scaling generation without scaling governance. We got better at producing code before we got better at evaluating it. The bottleneck moved and we didn’t move with it.</p><p>Which means the path to healthy autonomy runs directly through what we’ve been talking about here. You don’t get there by having humans manually review every line of code indefinitely. That doesn’t scale, and it’s not where humans add the most value anyway. You get there by building the judgment infrastructure: the explicit criteria, the architectural guardrails, the product principles clear enough that they can govern without you in the loop.</p><p>The variance in what teams can do right now is enormous. Some are already running autonomous loops. Others are drowning in slop. But what separates them is rarely the AI capability. It’s whether the team knows what good looks like, and whether that understanding of ‘good’ is shared and explicit, rather than living only in individual intuition.</p><p>We’re moving from Software Delivery to Value Delivery. Software becomes an implementation detail, and the organizations that thrive will be the ones structured around judgment, curation, and coherence.</p><p>The problems people are experiencing today aren’t a detour from that future. They’re the rough edge of the transition. And the only way through is to build the muscle that’s been missing all along.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03c9e9a4241c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/going-ai-native-from-execution-to-governance-03c9e9a4241c">Going AI Native, From Execution to Governance</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering Interviews and AI’s Philosophical Split]]></title>
            <link>https://medium.com/pupius/engineering-interviews-and-ais-philosophical-split-5722d514458a?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/5722d514458a</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[interview-questions]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Sat, 07 Feb 2026 03:01:00 GMT</pubDate>
            <atom:updated>2026-02-07T03:01:00.747Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NYSB3dLOU-W5kIP6.png" /></figure><p><em>Originally published on </em><a href="https://thegeneralpartnership.substack.com/p/engineering-interviews-and-ais-philosophical"><em>The GP’s Substack</em></a><em> in December 2025.</em></p><p>Something shifted in engineering hiring this year.</p><p>The surface story is simple: after two years of companies fighting AI use in interviews, some gave up and started allowing it. <a href="https://www.canva.dev/blog/engineering/yes-you-can-use-ai-in-our-interviews/">Canva</a>, <a href="https://newsletter.pragmaticengineer.com/p/how-ai-is-changing-software-engineering">Shopify</a>, parts of <a href="https://www.hellointerview.com/blog/meta-ai-enabled-coding">Meta</a>. The takes write themselves — ”AI is transforming interviews!” etc.</p><p>But the more interesting shift beyond the policy change is the philosophical split it revealed. Some teams still treat interviews as verification. Others are redesigning them as simulations of real work.</p><h3>What Interviewers Are Actually Seeing</h3><p>What I’m hearing from engineering managers who’ve run AI-enabled interview pilots: the gap between candidates widened, not narrowed.</p><p>The assumption was that AI would be an equalizer: Give everyone Copilot, and coding speed stops mattering. The opposite happened. Strong engineers used AI to move faster through the boring parts and spent more time on architecture and edge cases. Interviewers describe a specific pattern — when AI generates the shape of a solution, weaker candidates lose the thread of the reasoning. They can’t reconstruct the decisions the AI implicitly made.</p><p>Candidates who prompt AI for a complete solution, and then can’t answer “what does this line do?” That’s an instant no-hire in every AI-enabled format I’ve heard about. But candidates who use AI to scaffold boilerplate while making their own architectural decisions are demonstrating exactly what the job requires now.</p><h3>The Divide Isn’t Big Tech vs. Startups</h3><p>The popular framing is that Big Tech is fighting AI in the interview process while startups embrace it. There’s something to that — Google and Amazon are definitely making things harder by using more advanced LeetCode challenges and adding mechanisms to detect ‘AI cheating — but it misses the deeper split.</p><p>The real divide is between companies that see interviews as <em>verification</em> and companies that see interviews as <em>simulation.</em></p><p><strong>Verification mindset</strong>: “We need to confirm this person has skills X, Y, Z. AI makes that harder to verify, so we need better detection or harder problems.”</p><p><strong>Simulation mindset</strong>: “We need to see how this person actually works. They’ll use AI on the job, so let’s see how they use it.”</p><p>I think the simulation camp has the stronger position, and it’s how I’ve run interviews for some time. It’s not that verification is impossible with AI — you can still test fundamentals with follow-up questions. It’s that verification was always the wrong frame. The best predictor of job performance is watching someone do the job, or something as close to it as possible given interview constraints.</p><p>The companies that figured this out first happened to be startups, probably because they had less institutional inertia. But I’d bet the approach spreads regardless of company size.</p><h3>Changes in the Skill Stack</h3><p>People keep asking what skills matter now. The skills that matter always mattered, but the weighting shifted.</p><p><strong>Design and architecture went up</strong>. Not because they’re newly important (they always were), but because AI makes implementation cheaper. When generating code takes seconds, the bottleneck moves upstream to deciding what code to generate.</p><p>An engineer who can break down an ambiguous problem, identify the right abstractions, and make sound tradeoff decisions is worth more relative to someone who just types fast.</p><p><strong>Code review went way up</strong>. Engineers are spending more time reading and evaluating code than writing it from scratch. The ability to look at plausible code and spot the subtle bug, the security hole, the scalability problem — that’s the skill that actually matters.</p><p><strong>Communication went up</strong>. Partly because pair programming and collaborative formats are more common. But also because explaining your reasoning is the main way interviewers verify that you actually understand what you built.</p><p><strong>Algorithm implementation speed went down</strong>. Not to zero — you still need fundamentals — but relative to 2021, the ability to bang out a red-black tree from memory matters less. AI does that part faster than you will. What matters is knowing when you need one and how it’ll behave at scale.</p><p>Here’s my hot take: LeetCode grinding is less valuable than it used to be. Still not zero — Big Tech still uses it, and you need enough algorithmic fluency to evaluate AI output — but the ROI on memorizing 200 problems dropped.</p><h3>What Good Looks Like in an AI-Enabled Interview</h3><p>In collecting examples of what differentiates strong candidates in these new formats, I’ve seen a few patterns emerge:</p><p><strong>Strong candidates externalize their mental model early.</strong> Weak candidates wait for the AI to give them one. Given an ambiguous problem, strong candidates figure out what’s actually being asked. “Who’s the intended audience?” “What’s the latency budget?” AI can generate solutions for any interpretation, but it can’t always choose the right interpretation.</p><p><strong>They reject bad AI suggestions.</strong> One interviewer talked about a candidate who prompted Cursor for a caching layer, looked at the output, said “this doesn’t handle invalidation correctly,” and rewrote it manually. That’s signal. Though in this case maybe they could have re-prompted with better instruction.</p><p><strong>They narrate their process.</strong> Even in AI-enabled formats, thinking out loud matters. Interviewers want to see how you decompose problems, not just the final solution. Candidates who prompt in silence give no signal, even if the results work.</p><p><strong>They know when not to use AI.</strong> For a quick string manipulation? Sure, let AI write it. For the core business logic that the whole system depends on? Maybe think through it yourself first. Judgment about when AI helps versus hurts is itself a skill.</p><h3>The Take-Home Paradox</h3><p>Take-homes changed more than any other format.</p><p>The obvious change is that most companies gave up banning AI, because they couldn’t enforce it. But the interesting change is what happened to the problems themselves.</p><p>Good take-homes now give you a broken codebase and ask you to fix it. Or a working codebase and ask you to extend it. Or a real dataset with messy edge cases. The common thread is that they all require understanding a system, not just generating one.</p><p>For example, <a href="https://annajmcdougall.medium.com/you-cant-outrun-ai-in-tech-interviews-so-we-designed-around-it-018ae0ac4ddd">some startups are sending candidates</a> a full-stack chat app with intentional bugs — authentication edge cases, race conditions, that kind of thing. They don’t care if you use AI to help find them. They care if you can trace the logic, identify root causes, and fix them correctly.</p><p>The old-style “build something from scratch in 4 hours” take-home is dying, and probably should. It tested who had the most free time as much as who had the most skill.</p><h3>What This Means If You’re Hiring</h3><p>Make your AI policy explicit. I’ve seen enough stories about candidates agonizing over whether to use Copilot — or using it and feeling guilty — that ambiguity clearly hurts everyone. Just say what’s allowed.</p><p>More importantly: design problems that require judgment, not just output. Complex, ambiguous scenarios that resist single-prompt solutions. Debugging and extension tasks, not greenfield implementation. Trade-off discussions, not just “does it work.”</p><p>And train your interviewers on what to look for. The evaluation criteria genuinely changed. Someone who learned to interview candidates in 2019 (or before!) needs to update their mental models.</p><h3>What This Means If You’re Interviewing</h3><p>Learn to use AI tools fluidly — Cursor, Claude, ChatGPT, whatever — so that when you’re in an AI-enabled interview, you’re not fumbling with the interface.</p><p>But also, don’t neglect the fundamentals. The follow-up questions are where you prove you actually understand what happened. If you can’t explain the time complexity of your solution, or why you chose this data structure over that one, the AI-generated code won’t save you.</p><p>Prepare for both worlds. Some companies embrace AI. Some are hardening against it. You’ll encounter both, and the preparation is different. And remember, these different approaches aren’t new. Not long ago, managers argued about whether candidates should be allowed to Google during coding interviews. Today, that question feels almost quaint, like an early version of the same verification-versus-simulation split playing out today on a much larger scale with AI.</p><p>So practice narrating your thinking. We’re in an era where how you got there matters the most. That’s always been true in senior interviews. It’s becoming true everywhere.</p><p>The teams that adapt fastest won’t be the ones that simply embrace AI, but the ones that redesign their hiring to reflect how engineering actually works now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5722d514458a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/engineering-interviews-and-ais-philosophical-split-5722d514458a">Engineering Interviews and AI’s Philosophical Split</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2025 Highlights]]></title>
            <link>https://medium.com/pupius/2025-highlights-375a732ae532?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/375a732ae532</guid>
            <category><![CDATA[2025-year-in-review]]></category>
            <category><![CDATA[year-in-review]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 18:23:03 GMT</pubDate>
            <atom:updated>2026-01-01T18:23:03.468Z</atom:updated>
            <content:encoded><![CDATA[<h4>Many small moments</h4><p><em>I’ve been writing these </em><a href="https://writing.pupius.co.uk/tagged/year-in-review"><em>year in review</em></a><em> posts since 2014 when I worked on Medium itself — they’ve always been intended to be a somewhat rose-tinted view on the year, a caveat that feels more and more important to state given... *gestures around*.</em></p><p>January was pretty wet and nothing much notable happened. Then in February we headed up to Seattle — the first of three trips to the PNW — for Brad Fitz’ 90s themed birthday party and some quality cousin time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-dqh3X3jwk-5gKEuhWSZWQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kq88iliTZv-SBy2WJX_VCw.jpeg" /></figure><p>Lyra turned 10 and had an epic sleep over with 10 friends. It was chaos. Skye and I hid upstairs for much of the evening.</p><p>Then Skye turned 5, learned to ride a bike, and had a bounce house party in the newly reopened Esprit Park.</p><p>After sharing a room, Skye moved into the spare room which Tessa had been using as an office prior to RTO. Both kids are enjoying having their own space. (Many months later <em>our</em> bedroom is still a store room for boxes which no longer have a home.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UF1hIW_WftzcAX4F_uH5Sw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ijsnOLODqU6pA-GsBZ5mg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkZI2_AtxgbnBXXRPkNoxQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gHFj4Y02j5db-_Y00vK_cA.jpeg" /></figure><p>Over the year we got 5 days on the snow. Lyra continued snowboarding and comfortably manages blue runs in all conditions. Skye decided to switch to skiing after snowboarding in the spring — unfortunately Bear Valley switched to only having 1.5hr lessons for under-6s for the 25–26 season so we’ll be a bit limited until March.</p><p>I bought a new board for the first time in a decade: the Jones Flagship, which rips. I had lots of fun carving up the groomers until I managed to nail myself catching an edge at 44mph and broke a rib.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5TeJAxtrS5xpKJzzYk1ssg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qCVKhjdsvJhimPffijCS1g.jpeg" /></figure><p>We did two school camping trips, the first with Skye’s preschool on the Russian River, the second at Anthony Chabot Regional Park with Red Bridge.</p><p>In what is becoming a tradition, Tessa and I made pizzas for everyone on the Saturday night. Churning out ~50 pizzas using two Ooni ovens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D6NkfafpCpNaK4q74-vtkg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1x92uKPYe_v3U3BATHuXbg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ghsTEWrV4WXN5BbfHpaAcg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sSPXIEqolbw5UI83Py8xsg.jpeg" /></figure><p>Our main holiday this year continued the camping theme.</p><p>We spent 4 nights driving to San Diego. First, traveling over the Sonora Pass to Bridgeport, visiting Bodie Ghost Town and Mono Lake. We then drove back over the Sierra Nevada passing through Yosemite. Then down to Kings Canyon and through the Mojave to the San Berindino Valley, and on to San Diego.</p><p>We then met up with Tessa’s sister’s family for a week at the beach. Most CA schools were back already, so we a day at Legoland with no lines, and a quiet day at San Diego Zoo Safari Park.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iU1GOwtx2bm41eVtLV-VAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKwWKlV0iS_7rjWmZqzBKA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOxRhi554vXSrDiGZ57CWQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nCP7YmoQ-8UzLuXNqqBF5g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P8RF4k7eF1txyfZ1mjGi3g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIRECQ_XbUkrkV1Y_DgFbg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eRkELhko5xdJ22VfpPlNOg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xJOdYZI4WK6iPSli-Yy72g.jpeg" /></figure><p>This year I joined SF NERT (Neighborhood Emergency Response Team) and also got my ham license (I’m K1PUP). I participated in the city wide drill as comms for one of the field teams.</p><p>I also volunteered for the SFO full-scale drill where the emergency services responded to a simulated plane crash. My role was minimal, just walking wounded getting transferred through the airport, but I was able to observe the staged evacuation and fire boats rescuing people from the Bay.</p><p>It’s been fun to learn new things and meet people from walks-of-life I’m not normally exposed to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyMG9u3cG_9WWGsdnJh1BA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ONxqTCLO5Lfey9q-lr54A.jpeg" /></figure><p>Running has been a mixed bag this year. My goal was 550 miles and 50k feet of elevation. I reached the altitude goal a few months ago but only scraped by the mileage goal this week.</p><p>My broken rib from snowboarding set me back a few weeks, I got bronchitis after our summer road trip, and after rolling my ankle last Christmas I’m still needing to tape my ankle on every run.</p><p>But, even if the goals were hard to reach, I’ve been having fun. I’m still using <a href="http://wandrer.earth">wandrer.earth</a> and finding new corners of the city. I’ve now run on 60% of the roads in Arnold and up to 30% of San Francisco.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-dmiGoTJDdfn1J-vmYe6w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GIrei_VcZXaFn7kstx5fJQ.png" /></figure><p>My loose rule is I can’t drive somewhere just to get access to roads, so that means I’ll often only knock off a mile or two on an 8 mile run as I have to get to the area I’m exploring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8o751Va7ff3vwqo0xdh0Gw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZNnfFgb-q6tsMgOpqpMp0w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rgkg_KbvhljfagjHZo8ytg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*29achCPYyT0i5npM0-WJEw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Znek_MmsoLvm02RCz6xlSQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YhRnrxbaKx2K8GnEK5GUyA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-DwlAZFV5rBsntGCx1e0w.jpeg" /></figure><p>I only finished 9 books this year, partly due to a couple of epic fantasy novels dominating (I’m a pretty big cosmere fan but <em>Wind and Truth</em> felt like a slog) and partly due to some philosophy books that I’m struggling to stay awake while reading.</p><ul><li><a href="https://www.goodreads.com/book/show/21845220-the-navigator-s-children">The Navigator’s Children by Tad Williams</a></li><li><a href="https://www.goodreads.com/book/show/30014114-product-leadership">Product Leadership by Richard Banfield</a></li><li><a href="https://www.goodreads.com/book/show/24611819-the-peripheral">The Peripheral by William Gibson</a></li><li><a href="https://www.goodreads.com/book/show/34943643-agency">Agency by William Gibson</a></li><li><a href="https://www.goodreads.com/book/show/33917107-on-tyranny">On Tyranny by Timothy Snyder</a></li><li><a href="https://www.goodreads.com/book/show/203578847-wind-and-truth">Wind and Truth by Brandon Sanderson</a></li><li><a href="https://www.goodreads.com/book/show/35519101-rogue-protocol">Rogue Protocol by Martha Wells</a></li></ul><p>After finishing reading The Lord of the Rings to Lyra, we started the His Dark Material trilogy. We’re through the first two books and onto the third. Skye and I read the Jedi Academy series and are now reading Peter Pan.</p><p>Other highlights: lots of hikes, acrocats, rainy days at the exploratorium, Dear San Francisco at Club Fugazi, paddle boarding, DIY wood work, bonfires, date nights (top golf, bowling, SF MOMA, Sunset Dunes), SF Glow, Mercer Caverns, Thanksgiving Turkey that didn’t suck, Issaquah’s Cougar Mountain Zoo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W61O1pvD36pFZORd7tw8IQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LEx-Cc3gW3QAN7ybQ9I_3A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ty8n1nK2JOLWZuAC_doVxA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9KbzW8NG6jOk7r3hjpIpJA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GL4F8XTGPs4mbSfaMaNiVg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJHX1472s_VfoFDixuh20A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fnAAm4kRbAWsg3v7c5yoA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I600rm4eFfq6OvT_EZLjxw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*syGpqkcJyacKZsgQOoSlVQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mEfI-pCHwrgtKZ2xCvrhEQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FZKzCc-q29RqgA0OsqQOog.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-DBWO_ozcym_CUNGhTU7w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dPSlTCGstHGQnOsO5b_xSw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hj1XAbgpqIOBONBABt3L7A.jpeg" /></figure><blockquote>“Just because something is fleeting, do not imagine it to be unimportant.”<br>― Brandon Sanderson, Wind and Truth</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=375a732ae532" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/2025-highlights-375a732ae532">2025 Highlights</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI coding and the “nice camera” effect]]></title>
            <link>https://medium.com/pupius/ai-coding-and-the-nice-camera-effect-aaf751027e65?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaf751027e65</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[musings]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 02:49:10 GMT</pubDate>
            <atom:updated>2025-12-08T02:50:18.403Z</atom:updated>
            <content:encoded><![CDATA[<h4>Observations on how ubiquity changes our sense of craft</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TNhRuPVnnaQkNTy1" /><figcaption>Photo by <a href="https://unsplash.com/@wbayreuther?utm_source=medium&amp;utm_medium=referral">William Bayreuther</a> on <a href="https://unsplash.com?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><a href="https://medium.com/u/c99fbc1ec668">Sam Schillace</a> wrote a post today about how <a href="https://sundaylettersfromsam.substack.com/p/bad-programmers-are-about-to-become">the next era of AI coding will shine a light on engineering skills, over pure coding ability</a>. I broadly agree, but his post also made me think about photography.</p><p>Photography used to require obscure equipment and real technical skill. You needed to know how to operate a complicated camera, manage exposure, maybe even develop film in a darkroom. Craft mattered because the tools were demanding.</p><p>Now everyone carries a camera in their pocket, and the tools are so good that novices routinely take great photos. Point your phone at a sunset and you’ll likely get something beautiful.</p><p>But at the other end of the spectrum, pro and semi-pro photographers still exist — and they often hear the same thing: “<em>Wow, your camera takes great photos.</em>”</p><p>People see the output and credit the tool, not the skill, judgment, or consistency behind it.</p><p>What really distinguishes a professional isn’t that they can take a beautiful photo when the conditions are perfect. It’s that they can take a beautiful photo when they have to, even of something boring. They can produce quality on demand, within constraints, repeatedly.</p><p>I think Sam’s right about the skills gap in software. But I expect we’re about to see a similar perception pattern play out here too.</p><p>AI coding tools are getting better, and they’re becoming ubiquitous even faster than phone cameras did. Anyone can point and shoot their way to a decent app now. And as that happens, the appreciation for craft will blur. People will see the output and assume the tool did the heavy lifting, even when the real work was insight, judgment, or the ability to coax something specific out of a very general model.</p><p>Making an app “look good” is trivial. Getting it to align with an ill-defined corporate brand, handle edge cases, or express the nuance of a particular product — that’s closer to taking a flattering portrait under bad lighting. The skill isn’t in pushing the button; it’s in knowing what to ask for and how to shape the result.</p><p>And none of this is good or bad. It’s just what happens when powerful tools become widespread. As with photography, the tools raise the baseline for everyone, while the actual craft becomes harder to see from the outside — and easier to misattribute to the equipment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaf751027e65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/ai-coding-and-the-nice-camera-effect-aaf751027e65">AI coding and the “nice camera” effect</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The AI Productivity Curve]]></title>
            <link>https://medium.com/pupius/the-ai-productivity-curve-8a426646cf64?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a426646cf64</guid>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Fri, 15 Aug 2025 02:45:45 GMT</pubDate>
            <atom:updated>2025-08-15T02:49:21.550Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making sense of the wild productivity claims</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/0*hUgISpBqJqdJHKOk" /><figcaption>Drawing by wife, not by AI.</figcaption></figure><p>In the past few months we’ve seen wildly different takes on AI coding productivity. Some claim it’s a 100x multiplier. Others say it’s all hype. A few studies even suggest actual productivity might drop, despite people feeling faster. The conversation is leaving people confused and making it hard for engineering leaders to plan.</p><p>I’ve been using coding agents heavily since they first showed up (did Claude Code really only launch in February?). To begin with just to write single functions or tests, but more recently I have it write nearly every line of code — sometimes heavily guided other times just going with the vibe.</p><p>In thinking about my own usage of AI, I’ve started to suspect AI productivity follows a curve — huge early gains for small and medium tasks, but diminishing returns as complexity grows.</p><p>This is probably somewhat obvious, but I’m not seeing this nuance show up in conversations about team and individual expectations. The corollary from this observation is that there is value in understanding where the AI multiplier peaks and where it plateaus.</p><blockquote>There is value in understanding where the AI multiplier peaks and where it plateaus.</blockquote><h3>The Early Rocket Boost</h3><p>AI delivers its biggest gains when the coding portion is large relative to the whole project, and tasks are relatively self-contained.</p><p>In a recent <a href="https://github.com/dpup/meshstream">side project</a> of mine, AI reduced hours of protocol spelunking and boilerplate into minutes. What would have been an evening of reading documentation and writing repetitive message parsing became a process of piping <a href="https://meshtastic.org/docs/overview/mesh-algo/">Meshtastic packet</a> logs to Claude and having it map to structured types with matching UI components. It bridged MQTT to Server-Sent Events in one shot, and most of the input I provided was in describing how the packet data should be aggregated and displayed.</p><p>Small, contained scopes let AI remove friction almost entirely. The assistant can see everything it needs to know — no implicit dependencies, minimal architectural decisions, no integration puzzles.</p><p>Here, you really can feel like you’re coding at 10x speed.</p><h3>The Complexity Wall</h3><p>As scope increases, the share of work AI can fully automate shrinks. The bottleneck shifts from syntax generation to architectural coherence. AI can still write entire components or debug failing tests, but without guidance it struggles with the broader design decisions that keep large systems maintainable.</p><p>Patterns start to leak across module boundaries. Code gets duplicated in subtly different ways. Solutions work and pass tests, but they’re not always idiomatic or performant. The assistant optimizes for immediate functionality rather than long-term system health.</p><p>In individual projects, complexity arises gradually and naturally. In team based situations, complexity comes in different forms. Merge conflicts happen, designers have specific expectations about how things look, alignment over architectural direction needs to be built. Context spreads beyond the agent-operator boundary, leaving gaps. Ironically this is reminiscent of traditional organizational breakdowns — the agent plays the role of the one remote engineer who keeps getting left out of the loop.</p><blockquote>The agent plays the role of the one remote engineer who keeps getting left out of the loop</blockquote><p>But, whether it’s architectural complexity or organizational complexity, the root issue is the same. It’s epistemological — fundamentally about knowledge boundaries. The operator has to constantly inject the broader context about goals, constraints, and practices that exist outside the assistant’s view. This becomes the bottleneck and starts to bend the curve.</p><h3>The Asymptote</h3><p>So, if complexity erodes AI’s ability to maintain system coherence, then it follows that the productivity curve must eventually flatten. This isn’t a hard floor where gains disappear entirely — you might still see 3x or 4x improvements on individual tasks. But the early rocket boost phases become increasingly rare as projects mature.</p><p>Every person, team, and system will hit this asymptote at different points based on their skills, tooling, and domain constraints. A senior engineer with deep knowledge of their codebase will probably sustain higher baseline productivity than someone learning a new framework. A well-architected system with clear boundaries enables more AI leverage than a legacy monolith with tangled dependencies.</p><p>AI’s acceleration further flattens once the tasks are dominated by human judgment and coordination. Code review discussions, architectural decisions, stakeholder alignment — these don’t yet compress the same way code generation does.</p><h3>Finding Your Curve</h3><p>This pattern has shown up across most of the projects I’ve touched with AI — the productivity curve has a steep start but a decline as complexity grows.</p><p>Better models and tooling will push the asymptote higher, but the pattern feels fundamental. I find it interesting that we see the same thing in regular human systems: adding more developers to a late project makes it later, etc.</p><p>In my own work, I’m now trying to optimize around the curve. Looking for ways to push the asymptote higher through better tooling (MCP hooks, agent-focused documentation) and structuring projects to extend AI’s effective window. For engineering leaders, this means thinking about team productivity not as a constant multiplier but as a curve you can shape. Invest in the architecture and tooling that raises your floor, and structure work to keep your team operating where AI delivers maximum leverage.</p><p>I think this actually reinforces why solid software engineering practices remain essential in an AI-augmented world. Modular design, clean interfaces, and single responsibility principles don’t only make code easier to understand, they keep work in AI’s sweet spot longer. And breaking large efforts into smaller, well-bounded deliverables lets you deliver value incrementally while maintaining the conditions where AI agents thrive.</p><p>To wrap up, I don’t put much credence in people’s claims of 100x productivity improvement, or even the studies that show the opposite. We have new tools, and that’s exciting, but modern work is complex, with and without AI.</p><p>Productivity has always been a probability function — sometimes you’re in flow, sometimes you’re stuck for hours. AI changes the shape of that distribution. Understanding how is more useful than arguing about how much.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a426646cf64" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/the-ai-productivity-curve-8a426646cf64">The AI Productivity Curve</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“You need to be more strategic”]]></title>
            <link>https://medium.com/pupius/you-need-to-be-more-strategic-dc473a2aa319?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc473a2aa319</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Sat, 15 Feb 2025 02:02:21 GMT</pubDate>
            <atom:updated>2025-02-15T02:02:21.975Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-L5bvmGAL3Jp13hs" /><figcaption>Photo by <a href="https://unsplash.com/@lureofadventure?utm_source=medium&amp;utm_medium=referral">Ali Kazal</a> on <a href="https://unsplash.com?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>A primer on strategy for software engineers</h4><p>Being told you need to <em>be more strategic</em> is common feedback for senior engineers looking to move to the next level.</p><p>This can be tough feedback to hear.</p><p>Does it mean you’re not making good decisions? Not having enough impact? Relying too much on others? And what even is <em>strategy</em>? People rarely define it in a crisp and actionable way, instead offering hand-wavy explanations about needing to have more <em>impact</em> or expand your <em>scope</em>.</p><p>In this post I want to offer a concrete definition of strategy, and then provide a few models which you can use to start thinking more strategically.</p><p>So what is strategy?</p><p>Strategy isn’t long term planning. It’s not a detailed roadmap. It’s not even just making big, important decisions. Strategy can be thought of as the framework that guides decision making; strategy is an articulation of both a path forward and explicit trade-offs — what you’ll do and what you won’t do — that align your actions with your core objectives.</p><blockquote>Strategy can be thought of as the framework that guides decision making.</blockquote><p>Let’s look at a couple of analogies to try and illustrate this.</p><p>Imagine you’re driving from San Francisco to Seattle, and you want to get there in under 12 hours. That’s your goal. For those unfamiliar with the West Coast geography, 12 hours is a theoretically doable timeframe but the variance can be high. It’s possible to lose 2 hours if you pass Portland at the wrong time, and there are several other traffic bottlenecks.</p><p>A possible strategy to achieve this somewhat optimistic goal would be to <em>use multiple drivers to enable continuous driving while optimizing around traffic patterns rather than absolute distance or speed</em>.</p><p>The strategy isn’t “take I-5” or “drive fast”, it’s a higher-level approach that introduces new possibilities (can drive straight through), adds constraints (need to coordinate schedules), and impacts other decisions that might be made (no need for a sleeping stop). It’s a set of fundamental approaches which generate a cascade of tactical decisions — when to swap drivers, timing of departures to avoid city traffic, length of rest periods, etc.</p><p>A good strategy helps shape our decisions. It isn’t just a plan, it’s a framework that opens some doors and closes others.</p><p>Let’s look at one more example, this time from software engineering.</p><p>Imagine you need to improve the reliability of a complex system that’s having frequent production issues. Your goal is to catch bugs before they hit production.</p><p>One possible strategy would be to slow down releases and introduce a comprehensive manual QA step. But a more common strategy would be to <em>focus on adding end-to-end automated tests of critical user flows</em>.</p><p>The strategy isn’t just “add more tests”, it tells us what type of tests we want to add and how we’re going to prioritize adding them.</p><p>These two examples should show how a good strategy reduces the decision aperture. It isn’t a roadmap, it’s a framework that helps prioritize what to work on and how to do it.</p><h3>Frameworks for Strategic Thinking</h3><p>Anyone who knows me, knows I love models and frameworks. And I find strategy particularly fun. These are three frameworks that touch on different aspects of strategy and can help get you unstuck.</p><h4>Rumelt’s Kernel of Strategy</h4><p>Reading <a href="https://bookshop.org/p/books/good-strategy-bad-strategy-the-difference-and-why-it-matters-richard-rumelt/9791956">Good Strategy, Bad Strategy</a> by Richard Rumelt is a bit like starting to see through the Emperor’s New Clothes. I know multiple people who’ve read this book then sat through presentations by high level VPs with their head on their desk.</p><p>The book has a bunch of insights on what makes a good strategy and how to spot bad strategy, but the most valuable takeaway is Rumelt’s Kernel of Strategy.</p><p>The Kernel has three parts: diagnosis, guiding policy, and coherent actions.</p><p>The first part is a diagnosis of the biggest obstacle that you need to overcome in order to reach your goal. It’s not a list of problems, but an expression of the key challenges that makes everything else harder. Using the testing analogy above, the diagnosis might be “Our test coverage looks good on paper, but our tests don’t match how customers actually use the system.”</p><p>The second part is the guiding policy, this is the general approach you’ll take to address the challenge. This should help you decide what to do and what not to do. In our testing example, the guiding policy might be “focus on testing end-to-end customer workflows rather than individual components.”</p><p>The final part are the steps you’ll take that align with the guiding policy. They need to work together, that’s why they’re “coherent”. Putting it all together for the testing example it looks like this:</p><ul><li><strong>Goal</strong>:<br>Catch bugs before they hit production</li><li><strong>Diagnosis</strong>:<br>Our test coverage looks good on paper, but our tests don’t match how customers actually use the system</li><li><strong>Guiding Policy</strong>:<br>Focus on testing end-to-end customer workflows rather than individual components</li><li><strong>Coherent Actions</strong>:<br>Build an end-to-end test suite for critical user journeys<br>Add production monitoring for these journeys<br>Change incident review process to focus on user impact</li></ul><p>This is just a quick look of Rumelt’s framework. If you want to learn more, without reading the whole book, <a href="https://jlzych.com/2018/06/27/notes-from-good-strategy-bad-strategy/">Jeff Zych has some good notes</a>.</p><h4>Playing to Win</h4><p>The second framework I like is from another book called <a href="https://bookshop.org/p/books/playing-to-win-how-strategy-really-works-a-g-lafley/10001738">Playing to Win</a>. It’s based on the authors’ experiences at Proctor &amp; Gamble, so is more oriented towards business and product strategy, but it can still be very useful for engineers.</p><p>The framework asks you to answer five questions:</p><ol><li>What’s your winning aspiration? (What does success look like?)</li><li>Where will you play? (What problems spaces will we focus on?)</li><li>How will you win? (What’s our unique approach?)</li><li>What capabilities do you need?</li><li>What management systems are required?</li></ol><p>Using the testing example again, this might unpack like so:</p><ul><li><strong>Winning Aspiration</strong>:<br>Be perceived as the most reliable service in our space</li><li><strong>Where to Play</strong>:<br>Focus on interactive user flows even over offline processing systems</li><li><strong>How to Win</strong>:<br>Catch issues through automated testing of real user workflows</li><li><strong>Capabilities Needed</strong>:<br>End-to-end testing framework<br>Automated test infrastructure<br>Production monitoring for user visible errors<br>Ability to replicate real user behavior in test environments</li><li><strong>Management Systems</strong>:<br>Automated pre- and post-commit checks<br>Regular reliability reviews<br>Incident analysis focused on user impact<br>Test coverage reporting for critical paths</li></ul><p>This framework forces you to make trade-offs. When you choose to win through automated testing of user workflows, you’re choosing not to win through extensive manual QA or unit testing.</p><p>This framework is also particularly useful for eng leaders because it can be used to connect technical decisions to business strategy. When your company has defined its winning aspiration and where it will play, you can work backwards to determine what technical capabilities and management systems you’ll need to support that strategy. It helps bridge the gap between top-line business objectives and the day-to-day engineering work.</p><h4>Three Horizons</h4><p>Sometimes it can be really hard to reconcile what you need to do right now with longer term plans. <em>Why are we working to keep the lights on, when this metaphorical building will be demoed in a years time?</em></p><p>McKinsey’s Three Horizons model is very simple and breaks down the strategic outlook into different timeframes.</p><p>Horizon 1 is about optimizing the systems and processes you have today. This is typically 0-2 years out, but in startups things move faster and the horizons can be compressed.</p><p>The 2nd horizon is about emerging opportunities, typically 2-5 years out, but again often much sooner in startup-land. This work is adjacent to existing systems, but represents new capabilities or major expansions of existing services. While these things are further out, you often need to start laying the groundwork today, factoring future needs into architectural decisions or product design.</p><p>Horizon 3 is about creating entirely new capabilities. These will be big bets that look fundamentally different from where the product or architecture is today. At first there may be little clarity about horizon 3, so the key is identifying what foundational work would be needed regardless of where H3 ends off landing.</p><p>Imagine you’re dealing with a legacy monolithic service, this is how you might break down the work into horizons:</p><ul><li><strong>H1: Stabilize the existing system.</strong> Clean up the worst of the technical debt while adding monitoring and improving test coverage.</li><li><strong>H2: Service separation.</strong> Identify service boundaries and start building internal APIs between components. Create basic deployment infrastructure to support microservices.</li><li><strong>H3: Fully distributed architecture.</strong> Complete transition to microservices architecture. Implement event-driven patterns. Enable auto-scaling and self-healing. Support multiple regions.</li></ul><p>Note how the work on H1 enables H2’s service separation. Each horizon needs to deliver immediate value while laying the foundations for the subsequent horizon.</p><p>In practice, you may also be working on all three horizons simultaneously, just with different expected payback periods. In a startup, H1 projects might be addressing customer needs next week, while H2 projects are working towards something 6 months out, and H3 projects are speculative and may not deliver meaningful value until much later. The challenge is finding the right balance, enough H1 to keep things running smoothly while still investing in H2 and H3.</p><p>I hope you find that these frameworks give you more clarity about what people mean when they tell you to “be more strategic”.</p><p>They’re often asking you to create structures and systems for how decisions get made, rather than just making decisions. Frameworks like Rumelt’s Kernel, Playing to Win, and Three Horizons can help break down complex problems into actionable steps. They guide you to diagnose issues, define a winning approach, and balance immediate fixes with future opportunities.</p><p>But remember, bad strategy is bad strategy, no matter how well executed.</p><p>And good strategy still needs good tactics and strong execution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc473a2aa319" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/you-need-to-be-more-strategic-dc473a2aa319">“You need to be more strategic”</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Levels of Complexity]]></title>
            <link>https://medium.com/pupius/levels-of-complexity-9e30412800d2?source=rss-d2f101af1183------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e30412800d2</guid>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[theory]]></category>
            <dc:creator><![CDATA[Dan Pupius]]></dc:creator>
            <pubDate>Mon, 06 Jan 2025 21:55:44 GMT</pubDate>
            <atom:updated>2025-01-06T21:55:44.439Z</atom:updated>
            <content:encoded><![CDATA[<h4>Task → Practice → Strategy → Vision</h4><p>#1.<br>Task<br>Obeys<br>Understands procedures<br>Follows others<br>Deals with the known<br>Follows Steps<br>Scope: Event</p><p>#2.<br>Practice<br>Implements<br>Understands principles<br>Applies the playbook<br>Deals with the predictable<br>Finds How<br>Scope: Self</p><p>#3.<br>Strategy<br>Influences<br>Understands systems<br>Writes the playbook<br>Deals with the probable<br>Finds What<br>Scope: Group</p><p>#4.<br>Vision<br>Inspires<br>Understands purpose<br>Describes a future<br>Deals with the unknowable<br>Finds Why<br>Scope: Institution</p><p>Related:</p><ul><li><a href="https://fctl.ucf.edu/teaching-resources/course-design/blooms-taxonomy/#:~:text=Bloom&#39;s%20taxonomy%20was%20developed%20to,a%20variety%20of%20cognitive%20levels.">Bloom’s Taxonomy</a></li><li><a href="https://en.wikipedia.org/wiki/Cynefin_framework">Cynefin Framework</a></li><li><a href="https://en.wikipedia.org/wiki/Robert_Kegan#The_Evolving_Self">Cognitive Development Levels</a></li><li><a href="https://en.wikipedia.org/wiki/Three_levels_of_leadership_model">Three Levels of Leadership</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e30412800d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pupius/levels-of-complexity-9e30412800d2">Levels of Complexity</a> was originally published in <a href="https://medium.com/pupius">Writing by Dan Pupius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>