Substance over hype

TL;DR

Reduce every hyped category to its substrate. If the substrate is genuinely new, the excitement is earned. If not, refuse the rebrand.

The belief

When a new category arrives with a new label, the first move is to name what it actually is at the layer below. If the substrate is genuinely new, the excitement is earned. If the substrate is a renamed version of something already understood, the rebrand gets refused - in writing, regardless of financial exposure to the category being evaluated.

The substrate test is a single-move procedure: strip the marketing label, name the underlying mechanism, ask whether that mechanism is new. "Blockchain" becomes "a database innovation first." "GenAI" becomes "a platform that radically reduces the cost of cognition." "Agents" become "LLMs with tools and memory." The test forces one specific question - what is actually new here - before any evaluation begins.

How to apply

  1. Reduce before evaluating. When a new category claims your attention, name its substrate before forming a view. Ask: what is the mechanism underneath the label? A category that cannot be reduced to a clear substrate is noise.
  2. Name the substrate in one sentence. The reduction is done when it fits in a single declarative sentence. If it requires a paragraph, the substrate has not been found yet. "A database innovation first" is the form.
  3. Apply the same test inside a category as outside it. Hype operates at every level: the category claim, the product claim, the feature claim. A six-month implementation tax hidden behind "super customizable" is a failed substrate test at the product level.
  4. Withhold belief until the capability claim passes an observable test. State the condition under which you would believe it: "I would catch on to the hype once Devin replaces its founders to build Devin 2.0." This is not cynicism. It is a conditional that keeps evaluation honest.
  5. Refuse the rebrand regardless of exposure. The hardest application is inside a category where you have personal or financial stake. The test does not adjust for proximity. Inside-the-category honesty is the only version that counts.

What this is not

Argues against

Where to go from here

If you want the root framing this belief expresses - the disposition that licenses all downstream evaluations - go to the substance-over-hype theme.

If you want to see how this belief conditions agent-first - how refusing horizontal AI hype and accepting the substrate-layer claim produced the serving-lens thesis - go to agent-first.

If you want to see the substrate test applied to product craft - spec over sprint as the anti-generative-tools verdict from a single afternoon with Google Stitch - go to spec over sprint.

Evidence (7 dated rows - click to expand)
DateEntryPost
2018-02-10"Blockchain = Gamification decentralized." First visible substrate reduction.urn:li:activity:6367924728723795968/" target="_blank" rel="noopener" class="urn-link">view post →
2018-02-15"Somewhere in between blockchain and ICO the product is getting lost." Inside-category honesty while actively selling blockchain product.urn:li:activity:6369983938248699904/" target="_blank" rel="noopener" class="urn-link">view post →
2018-03-06"No one wants to accept the biggest database innovation as just a database innovation." Canonical statement: names the substrate test and the market's resistance to it.urn:li:activity:6376849689375019008/" target="_blank" rel="noopener" class="urn-link">view post →
2024-03-31"I would catch on to the hype once Devin replaces its founders to build Devin 2.0." Substrate test restated as a capability conditional.urn:li:activity:7180039976464650241/" target="_blank" rel="noopener" class="urn-link">view post →
2024-07-12"Technology that radically reduces the cost of something" as substrate definition of a platform revolution. Explicit callback to blockchain.urn:li:activity:7218568028266340352/" target="_blank" rel="noopener" class="urn-link">view post →
2025-12-04Anti-customization applied to PM craft: "super customizable" hides a six-month implementation tax. Substrate test at product level.urn:li:activity:7402319253036531712/" target="_blank" rel="noopener" class="urn-link">view post →
2026-04-09"Tried and dropped Google Stitch in under 30 minutes. Spec > Sprint / Taste > Execution / Context > Prompt." Substrate test compressed to a single afternoon verdict.urn:li:activity:7447981735901949952/" target="_blank" rel="noopener" class="urn-link">view post →