You wake up and the day is already moving. Before the rest of the world is up, you down a strong coffee and catapult straight into the work. It feels like good stress — eagerness, momentum, an edge that drives you through a lot of projects. The narrator of this video essay lived in that state through his 20s and early 30s. The work was plentiful and the frenetic energy carried him through it. Then sometimes he'd catch himself, breathless, in the morning, and wonder what exactly the energy was.1 Looking back, he stopped asking what the work was and started asking a colder question: what kind of engines were strapped to his back? And — this is the turn — what feeling was he avoiding that forced him to create so much noise around his work, so much rush, every morning?2
That is the whole concept in one move. The rush feels like ambition. It is often a defense.
Rush-as-avoidance is the recognition that high-speed, high-output working states are frequently not fueled by love of the work. They are fueled by the need to not feel something. The narrator names the fuel directly: "a common insecurity or an almost natural state of avoidance."3 The speed is the symptom. Underneath it sits a discomfort the worker is outrunning — and the work, paradoxically, becomes the vehicle for the outrunning rather than the thing being served.
The tell is in the body. He describes waking "in a state of rush and kind of stress," a "breathless thing in the morning," and a tendency to "become pretty irritable" if he couldn't protect that frenzied window.1 Notice the giveaway: irritability when the rush is interrupted. If the morning charge were simple love of the craft, a disruption would be a mild annoyance. Irritability of that intensity is the signature of a defense being threatened — the addict-like reaction when the substance is pulled away. The substance here is the speed itself.
The second half of the concept is what the rush is avoiding. The narrator is specific. When we "lock in" or "push hard towards some certain goal," we are often doing it "in order to avoid the important steps we're not taking" — the steps "that would lead us towards more uncertain paths or towards real discomfort perhaps real intimacy or real possibility for failure in our work."4 Speed feels like progress. But the high-speed lane is usually the safe lane: the known goal, the controllable deliverable, the EP finished by February. The uncertain, slow, exposing moves — the ones where you might actually fail at something that matters, or be genuinely seen — get bypassed precisely because you are moving too fast to take them.
So the rush does double work. It medicates the discomfort, and it routes you around the exposures that would force you to feel it.
Start with the function. Avoidance is efficient. A feeling you don't want — inadequacy, fear of being ordinary, the dread of being seen and found wanting — is genuinely unpleasant to sit inside. The nervous system will take almost any exit. Frenzied productivity is one of the best exits available, because it is socially rewarded. Nobody intervenes on the person who works too fast and ships too much. The culture calls it drive. So the defense gets reinforced from outside even as it corrodes from inside.
The narrator points at the mechanism of self-enforcement. "Working at that speed, there's a threat that we can end up becoming our own enforcer of our boundaries," he says — "suppressing those quieter voices inside that might be asking to change or expand."5 This is the load-bearing line. At speed, you don't need an external censor. You become your own. The pace itself silences the part of you that would ask a slower, riskier question: what if this whole project wants to become something else? what if I'm scared of the thing I keep not doing? Those questions "require more presence or more time," and presence and time are exactly what the rush refuses to grant.5
There's a related move he describes earlier, which is the verbal form of the same defense. We "virulently proclaim" what we are not — talk in an animated, impassioned way about how our work "could never exist" in some environment, or how we "don't need" some thing.67 The loudness is the diagnostic. "By proclaiming it loudly," he notes, we are "carrying those deep beliefs with us" — convincing ourselves that the thing we're simply avoiding "is not for us."8 So rush has a quiet form (speed in the body) and a loud form (virulent proclamation of a non-identity). Both are the same engine: motion and noise generated to keep a feeling at a distance.
The cruelty of it is that the engine works as creative fuel. He's honest: "this kind of energy drove me through a lot of different projects and a lot of work."1 The defense is productive. That's why it's so hard to see — the output looks like proof that the state is healthy. The output is real. The question the concept forces is not "is this productive?" but "is this productive of the work that matters, or only of the work that lets me keep moving?"
This page is one node in a tight cluster from the same source, all circling the same wound from different angles.
The clinical engine underneath it lives at Work Hard vs. Work Too Hard. There, a physician names the precise driver: not the good reasons you took up your work, but the unconscious need to justify your existence — to prove you're worthwhile — rooted in a loss of confidence from early childhood. Rush-as-avoidance is what that driver looks like from inside the morning. Work-hard-vs-work-too-hard is the diagnosis; rush-as-avoidance is the symptom you can actually catch yourself in. Read them as a pair: the feeling you're avoiding is the deficiency the physician describes.
The compass for finding what you're avoiding lives at Control as Signpost to Insecurity. The narrator's instruction there — watch what you grip in a project, because it's a "compass arrow" toward what you actually need to release9 — is the same instruction applied to a different surface. Control-as-signpost reads the grip; rush-as-avoidance reads the speed. Both are the visible outside of the same hidden fear. When you can't find what you're running from, look at what you're squeezing.
The fuel-quality frame lives at Burning Clean Engines. That page names the larger question — which motivations are you burning, and do they align with your best work? — and rush-as-avoidance names one specific dirty fuel: avoidance itself. Clean engines (curiosity, love of the material, a question you genuinely need to answer) don't produce the breathless irritable morning. Avoidance does. The presence of the rush is evidence the tank is full of the wrong thing.
It also pairs with the through-line that runs across the whole source: avoidance and self-sabotage. The same defense shows up as childhood stories worn like old layers of clothing — the adult who has the tools to handle a fear but whose brain still defaults to the childhood self-sabotage. Rush is one of those default layers. You wear it without noticing it's a costume from twenty years ago.
The cleanest moment is the one that opens and closes the source — the narrator's own morning. Watch the structure of his self-catch.
First, the behavior: wake, rush, strong coffee, straight into work, before the world is awake.110 Second, the rationalization: "It felt like good stress most of the time, an eagerness to get on."1 Third — and this is the rare part — the crack in the rationalization: "sometimes I would catch myself in a kind of breathless thing in the morning and wonder what that energy that was driving me was."1 The defense almost held. Most people stop at step two; the eagerness explains itself and the inquiry never starts. What breaks it open here is a somatic anomaly — breathlessness — that the "good stress" story can't fully absorb.
Then the diagnostic questions, stacked: "what kind of work was it? What sort of engines were actually attached to my back here? And what feeling was it that I was perhaps avoiding that was forcing me to create so much noise around my work."2 Three questions, escalating inward. The first is about the output. The second is about the fuel. The third — the only one that matters — is about the feeling being dodged. The movement from "what did I make" to "what am I not feeling" is the entire diagnostic arc of the concept.
And the resolution refuses comfort. He doesn't answer the question. He leaves it open, then generalizes it: "when you wake up and down a strong coffee and rush into that work that feels good and feels like ambition at the time, you might want to ask yourself if there's anything that you're avoiding."11 The case study is honest precisely because it ends in a question, not a cure. The point isn't to have found the avoided feeling. The point is to have started looking — and to notice that the thing that feels most like drive is the most likely place for the avoidance to hide.
It's 6:40 in the morning. The kettle is on and your hand is already reaching for the strong stuff, the cup that will detonate the next four hours. The laptop is open to the project. There's a familiar tightening across the chest, a leaning-forward, a sense that if you can just get into it before anyone texts you, the day is won.
Stop with the cup halfway to your mouth.
Feel the breath. Is it shallow and high in the chest, or low and slow? Notice the leaning-forward. Notice the small irritation that's already there at the thought of being interrupted — the way you'd snap if someone needed you right now. Let that irritation be information, not an enemy. It's pointing at something.
Don't open the file yet. Sit with the discomfort the not-yet-working produces. There it is — a low hum of I should be moving, I'm wasting the window. Stay in it for ninety seconds. Watch what the mind reaches for to escape it. That reach is the engine. Name it out loud if you can: I am rushing toward the safe part of this project so I don't have to do the part where I might fail.
Now ask the quieter voice what it wants. Not the deadline voice. The one underneath, the one the speed usually drowns. It might say: the EP doesn't have to be done in February. It might say: the scene you keep skipping is the real one and you're scared of it. It might say nothing at all the first ten mornings, because it's not used to being asked.
Then drink the coffee — fine, drink it — but enter the work at the pace of the quieter voice, not the louder one. Open to the uncertain step, the one with real exposure in it, not the controllable deliverable. The breathlessness eases when you stop running. That easing is the signal you were running.
You are likely burning avoidance as fuel when:
The diagnostic kernel: the rush feels like ambition and functions like a defense. If interrupting the speed produces something closer to panic than to rest, the speed is medicating something.
The evidence is a single narrator's introspective self-report — first-person, retrospective, unfalsifiable.12 This is its strength and its weakness. Strength: introspection is the only instrument that can detect a motive, and motives are exactly what's at stake. Weakness: a person can be wrong about their own engines, and a confessional frame rewards a tidy story (I was avoiding something deep) over a messier truth (I just liked working and slept badly).
The honest tension the source itself preserves: the rush works. "This kind of energy drove me through a lot of different projects."1 The concept does not claim avoidance-fueled work is bad work or that the productive rush should be killed. It claims the rush has a cost the output hides — the bypassed exposures, the silenced quieter voice. That leaves a real open question the source doesn't resolve: how much of high creative output across history has been avoidance-fueled, and would the work have been better or worse without the engine? Plenty of major work has been made by people outrunning something. The concept can't tell you whether to keep your engine or change it; it can only make you see it.
A second open question: is all morning urgency avoidance? Clearly not. Genuine eagerness exists. The source's own diagnostic — breathlessness, irritability, the spike when slowing — is the attempt to draw the line, but the line is fuzzy. Where does healthy creative momentum end and defended rush begin? The somatic markers help, but a determined avoider can learn to relabel the panic as passion.
A third: the source assumes the avoided feeling, once surfaced, can be tolerated and the work redirected. But it offers no method for what you do after you catch it beyond "ask yourself." The diagnostic is sharp; the cure is gestured at, not built.
The narrator is an artist-essayist reasoning from his own life, and he holds a productive internal tension he never fully resolves: he is grateful to the rush and suspicious of it at once. He credits the frenetic energy with carrying him through a decade of work, and in the same breath asks what it cost him.12 He does not land on "the rush was bad." He lands on "I should know what it is." That refusal to condemn the engine is the mature move — it keeps the concept diagnostic rather than moralizing.
He converges hard with the physician he cites later in the source. Where the narrator works by introspection, the physician works by clinical naming — the unconscious drive to justify existence, traced to early childhood, the thing that makes you work too hard rather than merely hard.12 The narrator's "feeling I was avoiding" and the physician's "need to prove I'm worthwhile" are the same object seen from two vantage points: the artist feels it from inside the morning; the doctor names it from outside, with a clinical history attached. The convergence is strong enough that the two pages function as one argument split across a felt account and a diagnosed one.
The one place the narrator could be pushed: he frames the quieter voice as wiser, the rush as the distortion. But sometimes the quieter voice is just fear wearing humility's clothes, talking you out of finishing things. He doesn't address the failure mode where "listening to the quieter voice" becomes its own avoidance — the avoidance of shipping. The frame is built to catch the over-driver. It's less equipped for the under-shipper who hides behind "I'm honoring my slowness."
Psychology — Deficiency Motivation vs. Growth Motivation. Maslow's distinction maps with almost uncomfortable precision onto the narrator's two engines. Deficiency motivation is driven by a felt lack — a hole that must be filled, an inadequacy that must be outrun. Growth motivation is driven by the pull of the thing itself, by curiosity and expression that need no wound underneath them. The narrator's rush is deficiency motivation rendered as tempo: the breathless morning is what a lack feels like when it's been converted into speed. The structural parallel is exact — both name a force that produces real output while quietly distorting the person producing it. But the creative-practice frame adds something the psychology frame doesn't make obvious: deficiency motivation has a signature in time. It runs fast, it can't tolerate stillness, it gets irritable when slowed. Maslow describes the two motivations as states of being; the narrator shows that one of them has a measurable tempo you can catch yourself in before breakfast. The diagnostic gift runs the other way too — if you suspect your work is deficiency-driven, you don't need to excavate the childhood lack to confirm it; you can just watch whether slowing down produces rest or panic. The body reports the motivation type faster than introspection does. That is the insight available only when you hold the tempo-frame and the motivation-frame together: deficiency motivation is legible as speed, and speed is legible to the body in real time.
Psychology — Psychic Retreat and Anti-Wholeness Defenses. A psychic retreat is a defended internal position the self hides in to avoid the pain of genuine contact — with reality, with others, with the harder parts of itself. The clinical literature usually pictures the retreat as a withdrawal: a fortress, a numbing, a going-quiet. Rush-as-avoidance reveals a retreat that runs in the opposite direction at the surface — not withdrawal but acceleration. The frenzied productive morning is a psychic retreat dressed as its opposite. You are not hiding in a numb fortress; you are hiding in motion, in noise, in output. The structural function is identical — both keep the self out of contact with the exposure it fears (real intimacy, real possibility of failure, the quieter voice). But the camouflage is better, because the culture reads withdrawal as a problem and reads frantic productivity as health. The tension this exposes: a retreat that generates achievement is far harder to see and far harder to give up than a retreat that generates obvious dysfunction, because the achievement keeps paying the defense's rent. Anti-wholeness defenses, the clinical page argues, actively resist healing — and the productive rush is the most resistant of all, because every shipped project is fresh evidence that nothing is wrong. The creative-practice angle supplies the disguise the clinical frame doesn't emphasize: the most successful psychic retreats don't look like retreats. They look like a strong work ethic. And the cost-detection runs the other way too — the clinical frame warns the creative reader that a retreat experienced as energizing (the good-stress morning) is more dangerous than one experienced as numb, precisely because nothing in the felt experience flags it as a hiding place. The numb retreat at least feels bad enough to question. The accelerating one feels like thriving, so it never gets questioned until the body forces the issue.
The sharpest implication. If the rush is a defense, then your highest-output periods deserve your deepest suspicion. This inverts the usual self-trust. Most people audit themselves when they're blocked — they treat low output as the symptom and search for what's wrong. The concept says the opposite is at least as urgent: audit yourself when you're flying. The breathless, plentiful, irritable-when-interrupted productive streak is the prime suspect, precisely because it produces the evidence that exonerates it. The work you're proudest of having pushed through may be the work you used to not feel something. That doesn't make it worthless. It makes it worth interrogating while it's working, which is the one time nobody ever does.
Generative questions.