What happens when thirty-one years of accumulated experience meets tools that dramatically reduce the friction between an idea and its first working version?
Not a superhuman claimNot a productivity contestA living field note
Overclocking is a metaphor here. Humans are not processors, and burnout is not a performance benchmark.
01 / Origin story
It didn't begin six days ago.
The tools became faster. The human history behind the prompts didn't.
Education, organizational behavior, working life, family enterprise, psychology, music, perfumery, writing and the internet: years of wandering between disciplines created a store of questions and tastes.
Then came a new kind of workshop. Instead of waiting to master every implementation detail before building, a person could describe an experience, inspect a draft, critique it, revise it, and publish a working artifact.
> boot human_experience
[OK] curiosity: persistent
[OK] interdisciplinary references: loaded
[OK] tools: available
[WARN] judgment cannot be outsourced
[WARN] attention is finite
> build idea --iterate --test █
Before the build
Years of reading, study, work, experiments, relationships, mistakes and changing interests. Not visible in a deployment log.
October 2026
A personal domain becomes an atlas of essays, experiments, interactive pages and curious side quests. The exact count changes as the work evolves.
After launch
The hard part continues: checking facts, repairing broken links, making pages accessible, maintaining them and finding out whether visitors gain anything.
02 / Interactive lab
The Friction Console
Move the sliders to explore a conceptual model of creative throughput. This is an illustration, not a validated psychological test or a measure of your intelligence.
Illustrative output, arbitrary units
—
Loading…
Toy formula: clarity × tool leverage × review quality, discounted by context switching. It demonstrates trade-offs, not scientific causality.
03 / What acceleration changes
Faster first drafts ≠ finished understanding.
Gain
Lower activation energy
A rough idea can become a testable page before motivation evaporates. Prototypes invite feedback sooner.
Trade-off
More output to maintain
Every new site creates future work: bugs, accessibility, links, accuracy, hosting and stewardship.
Human responsibility
Judgment stays local
AI can draft and propose. A person still chooses what matters, checks claims and accepts responsibility for publishing.
Learning
Building teaches
Inspecting generated code, debugging, and asking why an approach works can grow capability. Blind copying may not.
Identity
Tools aren't the self
A microscope doesn't make its user a cell. A code generator doesn't replace the human's lived questions or make them infallible.
Value
Output isn't impact
Hundreds of pages may be interesting. Value is better tested by usefulness, reliability, meaning and what other people can actually do with them.
04 / Thermal limits of a human
Even the beast needs cooling.
A computer has thermal throttling. A person has sleep, relationships, emotional bandwidth, boredom, play and the need to be offline. The analogy is imperfect—but useful.
Important distinction: Working intensely or making many things does not establish exceptional cognition, nor does it mean the brain has literally been overclocked. Sustained sleep loss and chronic stress can impair attention, memory and judgment. This site celebrates creative leverage, not exhaustion.
The point of faster tools is not to turn a life into an endless benchmark. It is to leave more room for the parts of life that aren't benchmarks.
Build. Test. Learn. Repeat. But verify what the machine gives you.
05 / Evidence & further reading
Keep the metaphor honest.
These resources offer starting points on cognitive load, sleep, AI assistance and the distinction between capability and output. They do not validate the site's toy simulation.
Cognitive load
Sweller's foundational account of cognitive load in problem solving.
Editorial note: historical narrative reflects the creator's account; scientific references are background context, not proof of personal performance claims.