The How Tax: Understanding as a Moat

Everybody wants the system. Nobody wants to understand the system.

That's the defining tension of AI-assisted work. The tools have never been more powerful. The barrier to producing output has never been lower. And the gap between what people ship and what people comprehend has never been wider.

I call this gap the How Tax.

The How Tax

The How Tax is the compounding cost of using systems you don't understand.

It starts small. You generate code you don't read. You deploy infrastructure you can't diagram. You ship features whose failure modes you've never considered. Each shortcut feels free because the invoice is deferred.

But deferred isn't free. Deferred is worse than expensive. It's expensive at the worst possible moment. The bill arrives when the system breaks at 2am and nobody knows why. When the vendor changes pricing and you can't migrate. When a security audit reveals architecture decisions nobody remembers making.

The How Tax compounds at three scales:

Individual. A developer who can't explain their own system can't evolve it. They can add features the AI suggests. They can't redesign the architecture when requirements change. Every AI-generated layer they don't understand becomes a wall between them and their own product.

Company. An organization that builds on systems nobody internally understands becomes hostage to vendors, consultants, and the one person who set it up. Institutional knowledge evaporates. The bus factor drops to zero, not because people leave, but because understanding was never acquired in the first place.

Civilization. A society that consumes technology it can't produce or maintain negotiates from weakness. Dependency at this scale isn't a supply chain problem or a trade problem. It's a knowledge problem. And knowledge problems compound across generations.

The Evidence

This isn't philosophy. The data is specific.

The Comprehension Gap

An Anthropic study (2025) measured developer performance with and without AI assistance. The finding: developers using AI scored 17% lower on code comprehension tests while self-reporting that they felt faster and more productive.

The perception of speed masked the erosion of understanding. They shipped more. They understood less.

METR corroborated this with experienced developers. Their study found that developers using AI were 19% slower on real tasks, but believed they were 24% faster. The gap between perceived and actual performance was 43 percentage points.

Not a training problem. These were experienced engineers. The tool created an illusion of competence that the data didn't support.

The Security Invoice

CodeRabbit analyzed millions of pull requests and found that AI co-authored code contains 2.74x more security vulnerabilities than human-written code. Not 10% more. Not 50% more. Nearly three times more.

The mechanism is straightforward: AI optimizes for "it works." Security requires understanding how it works, including edge cases, failure modes, and trust boundaries. "It works" and "it's secure" are different claims. The How Tax shows up as vulnerabilities that pass every functional test.

The Critical Thinking Deficit

A Microsoft/CMU study found that 40% of AI-assisted tasks had zero critical thinking applied. Developers accepted AI output without evaluation, not because they were lazy, but because the output looked correct. Plausible isn't the same as sound.

When the tool produces working code on the first try, the incentive to understand that code approaches zero. The How Tax isn't paid by bad developers. It's paid by rational ones responding to the wrong incentives.

The Rewrite Rate

Low-code and no-code platforms promise speed without understanding. The data on outcomes: 25-30% of projects built on these platforms are rewritten within 2 years. Not refactored. Rewritten, often on a different platform entirely.

The pattern is consistent. Phase one: rapid construction. Phase two: requirements change. Phase three: the system can't adapt because nobody understands its internals. Phase four: rewrite.

Speed without understanding is a loan. The rewrite is the interest payment.

Judgment as a Subscription

A 2025 CEO survey found that 62% of chief executives outsource "most decisions" to AI systems. Not operational decisions. Strategic ones.

When the people responsible for organizational direction can't articulate why their systems made a given recommendation, judgment becomes a subscription service. Cancel the subscription, lose access to the model, and the organization discovers it's been renting its decision-making capacity.

Historical Parallels

The How Tax isn't new. AI accelerates the pattern, but the pattern predates software by millennia.

Rome's Foederati

By the 4th century, Rome had outsourced its military capability to foederati, allied barbarian troops who fought under their own commanders. The arrangement was efficient. Rome got soldiers without the cost of training them. The empire maintained its borders without maintaining the institutional knowledge of warfare.

The bill arrived over generations. Roman citizens lost the capacity for organized combat. The foederati gained it. By the 5th century, Rome was paying barbarian generals to defend it against other barbarian generals. The outsourcing of military understanding preceded the collapse of the empire.

Rome didn't fall because it lacked soldiers. It fell because it lacked the knowledge to produce them.

The Ottoman Press Ban

When Gutenberg's printing press spread across Europe in the 15th century, the Ottoman Empire banned Arabic-script printing for over 250 years. The rationale was protective: preserve the authority of scribes, maintain quality control over religious texts, protect existing institutions.

The result was 250 years of stagnation in knowledge dissemination while Europe compounded its information advantage. The Ottoman Empire didn't lack resources or territory. It lacked the knowledge infrastructure that the press created, because it chose to protect the gatekeepers instead of understanding the tool.

Protecting existing structures against new tools is a form of the How Tax: the cost of not understanding what you are refusing.

Rare Earth Processing

Rare earth elements exist on every continent. The minerals aren't scarce. But the processing knowledge (the metallurgy, the chemical separation, the environmental management) concentrates in one nation that invested decades in understanding the "how" while others outsourced it.

The result is a geopolitical chokepoint built not on resource scarcity but on knowledge scarcity. Nations that treated rare earth processing as someone else's problem discovered that "someone else" now controls their supply chain for semiconductors, batteries, and defense systems.

The How Tax at civilizational scale: when you outsource understanding, you outsource sovereignty.

The Pattern

Three different domains. Three different centuries. The same structure:

1. Delegate the hard, unglamorous work of understanding
2. Enjoy the short-term efficiency gain
3. Discover the dependency when conditions change
4. Pay the compounding bill — in lost capability, lost sovereignty, or lost options

The question is never whether the bill arrives. It's whether you have the capacity to pay it.

The Independence Premium

If the How Tax is the cost of skipping understanding, the independence premium is the return on investing in it.

Understanding your systems buys you three things no tool can provide:

Debuggability. When something breaks (and it will break) understanding is the difference between diagnosing the root cause and restarting the service and hoping. AI can help you debug. It can't debug for you if you don't understand the system well enough to evaluate its suggestions.

Portability. Tools change. Vendors raise prices. Platforms shut down. If you understand the architecture, migration is a project. If you don't, migration is a rewrite. Understanding makes you independent of any single tool, including AI itself.

Evolvability. Requirements change. Markets shift. What you build for today's requirements must adapt when those requirements shift — and they will. Systems you understand can be reshaped. Systems you merely assembled from generated components resist change, because every modification requires re-understanding what should have been understood the first time.

The independence premium isn't about writing every line by hand. It's about understanding every decision. There's a difference between delegating execution and delegating comprehension.

How to Invest in "How"

Understanding doesn't mean doing everything manually. That's the wrong tradeoff, and it's the strawman that every "just vibe code" argument relies on.

The real practice:

Read what AI produces. Not every line. But the architecture: the boundaries, the data flow, the failure modes. If you can't explain the system to someone else, you don't understand it yet.

Understand before you automate. Automation is leverage. But leverage on a system you don't understand isn't leverage. It's acceleration toward a wall you can't see. Understand the process first. Then automate it. The sequence matters.

Ask "why" before "what." AI is extraordinary at answering "what should I build?" It's less useful for answering "why this architecture instead of that one?" The "why" questions are where understanding lives, and where AI is most likely to give you a plausible but wrong answer.

Maintain the ability to rebuild. Not the intention to rebuild, the ability. Could you reconstruct the core of your system on a different stack? If the answer is no, the How Tax is accumulating. Understanding is the asset that makes rebuilding possible.

Treat AI as a research partner, not an oracle. The difference between inquiry and delegation defines the How Tax. Inquiry means using AI to explore options, challenge assumptions, and accelerate learning. Delegation means accepting output without engaging your own judgment.

Delegation produces output. Inquiry produces understanding. Only one of them compounds.

The Thesis

AI is the most powerful leverage tool in the history of software. It's also the most powerful understanding-avoidance tool in the history of software. The same capability enables both.

The market will split. On one side: people and organizations that use AI to produce more while understanding less. They'll ship fast, accumulate How Tax, and discover the bill when conditions change. On the other: people and organizations that use AI to understand more while producing at the same speed. They'll compound their independence.

The gap between these two groups won't be visible in their output. It'll be visible in their options: what they can debug, what they can migrate, what they can evolve, what they can build next.

Understanding is not a bottleneck. It is a moat.

The "how" is where independence lives.

---

More on building systems that compound in the Building category. On independence and sovereignty in the Freedom category.