When you're deep inside a project — really in the middle of finishing it — it almost always feels like it's failing. It feels like it's lagging, like it's breaking down, like it's never going to get done. And the panic that rises out of that feeling has a script: push faster, push harder, slap rigid timelines on it, finish this EP by February. The feeling tells you the project is in trouble and that speed is the rescue. But the narrator points at a longer view. If you stay calm, stick with the process, stay consistent, and keep working in a continuous way — if you keep close to the thing — then ten years down the line you turn around and realize all you ever needed to do was stay close to it and ride the waves that came through, without rushing any of it.1
There wasn't, it turns out, any real pressure to finish at a particular point. The pressure was internal weather, and the weather passed.
This is a claim about how long projects actually get completed, and it contradicts how they feel from the inside. The feeling, mid-project, is that completion is stalling and only force will save it. The claim is that the stalling feeling is normal and misleading — a wave, not a verdict — and that the thing that actually completes a long project is not force but continuity. You stay close. You keep working. You let the rough patches pass through instead of treating each one as a crisis to be sprinted out of.
"Ride the waves" is the load-bearing image. A wave is something you don't fight and don't flee — you stay with it until it lifts and sets you down. The mid-project sense of breaking-down is one such wave. So is the false urgency to set a hard deadline. The discipline is to recognize these as passing states rather than facts about the work, and to stay consistent through them. Consistency, not intensity, is the engine. The proof only arrives in retrospect — ten years on, the project is done, and the honest account of how is mundane: you didn't rush, you didn't quit, you just kept showing up close to it.
The quiet, almost subversive part of the claim is the last line: there wasn't really any pressure to finish at a certain point. The deadline-panic was self-generated. The waves felt like external emergencies and were actually internal weather.
A long project doesn't progress smoothly. It moves in a series of stretches that feel like progress and stretches that feel like collapse. The collapse-feeling is not information about whether the project will finish; it's information about where you are in the cycle — usually the trough between two stretches of motion. The mistake is reading the trough as a verdict. You feel it breaking down, conclude it is breaking down, and reach for the only lever panic offers: speed.
Speed is the wrong lever for two reasons. First, the rigid timeline you impose in panic — done by February — forecloses the exploration the project might still need, slamming doors on roots and ideas that come up in the process. Second, force can't manufacture the thing a long project actually runs on, which is sustained proximity over time. You can't sprint your way to having been close to something for ten years. The only way to get the benefit of a long arc is to actually live the long arc, staying near the work through its troughs without panicking out of them.
This is why "stay close" is the operative instruction rather than "work hard." Closeness is continuity — keeping the project alive in your hands and attention, week after week, so that when a good wave comes through you're positioned to ride it. The person who panics and sprints, or panics and quits, isn't close anymore; they've let the trough push them off the project. The person who stays calm and consistent stays in position, and over a long enough horizon, position beats intensity.
This page is the long-horizon frame the other two slow-creativity moves operate inside. Put It Away to See It Clearly is a local move for staying close without overworking — stepping back from one piece for three weeks is a way to ride a wave of proximity-blindness rather than fight it. Get All the Knots Out — Iteration is the local move for the stretches when the work is progressing and the discipline is to keep iterating rather than declare it done. Put-it-away is what staying close looks like when your judgment is shot; iterate-again is what staying close looks like when the work is workable. This page names the arc that makes both make sense: across years, you alternate stepping back and pushing in, and the through-line is that you never leave.
It handshakes with Sustained Intensity, which makes the case for prolonged engagement as a creative engine — though the two differ on temperature. Sustained intensity emphasizes the heat of long focus; this page emphasizes the calm of long continuity. The reconciliation is that the long arc needs both: intensity in the productive stretches, calm in the troughs. And it handshakes with The Emotional Arc of Creation: Shooting to Finish, which maps the despair that arrives near the end of a project — exactly the breaking-down feeling this page tells you to ride rather than obey.
The narrator draws the lesson out of a long studio process — years of work on a record, with multi-year gaps between releases treated not as failure but as the time the work needed. The diagnostic he names is precise: "when you're inside a creative project, when you're in the process of completing it, it can often feel like it's lagging or breaking down, like it's never going to get done and you need to push it faster faster and start putting really rigid timelines on it."1 Then the corrective: "if you stay calm and stick with the process and are consistent and work in a continuous fashion, you keep close to the project, then 10 years down the line, you'll turn around and realize all I needed to do was stay close to that thing and ride those waves that came through without rushing anything."1
The sharpest line is the last: "there really wasn't any pressure to finish it at a certain point."1 The whole panic — the lagging feeling, the urge for rigid timelines — is revealed in hindsight as a story the maker told themselves mid-process, not a fact about the project. The case study's force is entirely retrospective: the lesson is only legible from ten years out, which is precisely why it's so hard to apply in the trough.
It's month seven and the thing feels dead in your hands. Nothing's connecting, the energy's gone, and a voice is getting loud: you're behind, set a deadline, force it out by spring or it'll never ship. Your jaw is tight; you can feel the urge to grab the calendar and start carving hard dates into it. You notice the urge and you don't act on it. Instead you do the small continuous thing — you open the file, you put in your stretch, you keep close even though it feels pointless today. The trough doesn't lift this week. It doesn't lift next week either. You keep showing up anyway, calm, consistent, not rushing. Then one ordinary morning the work moves again — a wave comes through — and because you stayed close you're right there to ride it. Years later, looking back, the whole stuck stretch barely registers. What you remember is that you stayed near the thing until it was done.
You've mistaken a wave for a verdict when:
The corrective is to stay calm and stay close: keep the continuous, consistent contact going through the trough, and let the wave pass rather than fighting or fleeing it.
This is a narrator's distilled lesson, illustrated by a long studio process and stated as retrospective wisdom.1 [POPULAR SOURCE] Its weakness is survivorship: the projects that "just needed you to stay close" are, by definition, the ones that eventually finished. We don't hear about the projects where someone stayed calm and close for ten years and the thing genuinely was broken and never came together. The advice can't distinguish, in the moment, between a trough you should ride and a project you should abandon — and that distinction is exactly what a maker in the trough most needs.
The live tension is with the deadline. The page treats rigid timelines as panic-symptoms, but the source elsewhere concedes that toward the end of a project it can be useful to dictate a few parameters to package and finish it. So deadlines aren't categorically bad — they're bad as a panic response mid-process and useful as a closing discipline near the end. The page's clean "don't impose timelines" reads, on closer inspection, as "don't let the trough-panic impose them," which is a narrower and more defensible claim.
Open question: how do you tell a ride-it wave from a real structural failure? "Stay close ten years" and "know when to quit" are both real wisdom, and nothing in the source adjudicates between them.
This page is the calm pole of the essay's argument and it converges cleanly with the narrator's central thesis that the rush is the enemy. The mid-project urge to "push it faster faster" is the rush in its purest form, and the corrective — stay calm, stay close — is the essay's whole prescription applied to the long arc. Where it sits in slight tension with the source's iteration material is temperature: the studio process the lesson is drawn from also involved relentless, effortful re-recording (the "do it again" discipline). So "staying close" is not passive drifting — it includes hard, repeated work in the productive stretches. The convergence is that none of it is rushed; the tension is that "ride the waves" can sound like ease when the actual practice included grind. The reconciliation the source implies: calm is about your relationship to the troughs and the deadline-panic, not about working softly. You ride the waves and you do it again, again, again when the wave is good.
Psychology — present bias and the tyranny of the trough. Present Bias describes the mind's overweighting of the immediate. The mid-project breaking-down feeling is present bias aimed at a long project: the vivid awfulness of right now dominates, and the distant, abstract knowledge that troughs pass can't compete with it. So the maker reads the present trough as the project's fate and panics. "Ride the waves" is a deliberate counter to present bias — it reframes the immediate bad feeling as a temporary state inside a longer pattern, deliberately weighting the long arc against the loud present. The handshake produces a tactic the psychology page doesn't state: against present bias on a long project, the corrective isn't to feel better now but to keep acting consistently regardless of how now feels — continuity is what defeats a bias that distorts the present, because continuity is the one thing the present can't argue you out of if you've decided not to negotiate with it. In return it sharpens the psychology: present bias doesn't only mis-rank rewards over time; it mis-reads troughs as endpoints, and the antidote is structural continuity rather than improved mood.
Psychology — time as the master factor. Time as Master Factor treats time itself as the decisive variable that reshapes how a situation is understood and resolved. This page is a craft instance of exactly that: the project's completion isn't decided by any single session's effort but by the accumulation of sustained proximity over time, and the lesson is only legible from the vantage of elapsed time ("ten years down the line"). The structural parallel is that what looks like a problem at one time-scale (this week it's breaking down) dissolves at another (across a decade it just needed continuity). The tension the handshake reveals is about agency: if time is the master factor, the maker's job shrinks — you can't force the long arc, you can only stay positioned for it and let time do the integrating. That's an uncomfortable demotion for a maker who wants to feel in control, and it's the same demotion the essay's surrender material keeps pointing at. The handshake yields a claim neither page makes alone: on long creative projects, the maker's primary act of skill is not leaving — staying close so that when time delivers the wave, someone's there to ride it. Effort decides the stretches; time decides the arc; and the only way to be on the right side of time is continuity.
Read together, the two psychology handshakes describe the same trap from two angles and point at the same exit. Present bias explains why the trough feels like a verdict — the loud present drowns out the quiet long pattern. Time-as-master-factor explains why the verdict is wrong — the variable that actually decides the outcome operates on a scale the present can't perceive. The maker stuck in the trough is being lied to by their own time-horizon: they're reading a decade-long process through a this-week lens, and the lens is built to mislead. The exit both pages converge on is not emotional (don't try to feel better) but behavioral (keep acting). Continuity is the one move that doesn't require winning the argument with the present, because it's a decision made once, in advance, to not renegotiate with the trough each time it shows up. That's why the lesson lands as "stay close" rather than "stay hopeful." Hope is a feeling the present keeps attacking; staying close is a behavior the present can't easily reach, as long as you've decided not to put the abandonment decision up for a daily vote.
The sharpest implication. If the mid-project breaking-down feeling is a wave rather than a verdict, then the single most damaging move on a long project is trusting the trough — concluding that because it feels like it's failing, it is. Most makers who abandon long projects don't abandon them at the real dead end; they abandon them in the trough, mistaking weather for fate. The implication is that survival of long projects is mostly a function of not over-trusting your worst mid-process feelings and staying close anyway. The skill isn't optimism; it's refusing to let the trough make the abandonment decision.
Generative questions.