How to make something great
Listen as a podcast • 閱讀中文版
In the pantheon of creative endeavors—be it product design, art, architecture, software, or some hybrid creature of the mind—true greatness emerges not from any single stroke of genius, but from a careful cultivation of potential. There’s a quiet, almost mystical art to starting with something so unrefined that you’re unsure if it’s mud or marble, and patiently revealing its shape until others recognize its beauty. In the end, they’ll say: “Of course! It’s so obvious.” But what they see is only the final state. What you know is the hidden complexity—how the stone could have cracked and fallen to rubble at any misstep.
Begin with the Ambiguous Artifact
A truly fertile concept often resists immediate clarity. It’s a rough form: a half-lit corridor where you see only silhouettes and faint hints of what could be. Resist the urge to force early perfection. Instead, feel its potential: a spaciousness that can accommodate many problems at once, each waiting to be resolved into an elegant pattern. The best future solutions seem almost retroactively inevitable. In the final analysis, greatness often appears so natural that it’s hard to imagine any other way. The philosopher who said that “the truth is what never had to be said” might as well have been talking about a product so perfectly aligned with its context that no competitor can propose a simpler alternative.
Assemble the Believers, Not the Bureaucrats
One of the strangest illusions of our time is the fetishization of role and title over skill and mindset. As if the name of a position could summon forth the muse of creativity. The team that molds greatness is not a conscript army but a band of pilgrims—each invested, curious, and eager to shoulder challenges. Such people don’t hide behind process or hierarchy. They meet problems nakedly, exchanging frank insights and critiques, driven by a shared sense of higher purpose. Those who only pretend, who cling to a resume or leverage half-hearted interest, may fill a room but will starve the mind. Such individuals dilute ambition, adding friction instead of fuel. Seek those who care deeply and are excited to shape something larger than themselves.
Delay the Funnel, Widen the Field
We’re taught to focus early—choose what’s “important,” discard what’s peripheral. But at the genesis of a thing that might be great, strict focus is a ruse. The best solutions emerge after you’ve wandered through a landscape of problems, discovering hidden connections and rich intersections. Don’t erect premature fences around what the solution “should” be. Early constraints, imposed for neatness or efficiency, choke off the possibility of the truly sublime. The treasure lies in expansive searching, in stitching together a tapestry of interrelated issues. Later, once you’ve roamed far enough, clarity will guide you toward the right edges. Until then, let curiosity roam.
Act from Instinct and Build to Learn
Many yearn for neat narratives, perfect prototypes, or bulletproof decks that placate stakeholders. But in this quest for tidy consensus, the work can stagnate, spinning its gears in the muck of groupthink and subtle fear. Forward progress is made when you trust the raw feeling that something is worth trying and then try it. You don’t need permission from every corner. Build, code, draw, revise, scrap, and build again. These acts aren’t wasted effort; they are sketches on a canvas that teach you what’s real and what’s fantasy. Don’t revere planning over doing. Craft’s truth emerges only through the friction of material engagement.
Don’t Validate Ideas to Death
In a world saturated with A/B tests, focus groups, and the fetishization of “data-driven” everything, it’s easy to strangle a young idea in the crib. If you rush to validate too soon—before the idea has a coherent form, before you’ve given it the time and space to grow—you merely confirm that the infant cannot run a marathon. Of course it can’t. Greatness isn’t summoned by a hasty thumbs-up or thumbs-down. Instead, internalize the doubts as signals that more exploration is needed. Refine the concept, enrich it, feed it new inputs. Later, once it stands on its own feet, the world can judge its stride. But kill it too early, and you destroy something that never had a chance to prove itself.
Pursue Quality and Agility in Equal Measure
The myth says you must choose: move quickly and break things, or move slowly and ensure elegance. But genuine excellence emerges from a dance between speed and depth, agility and quality. Like a skilled musician who can improvise yet still maintain impeccable technique, you must learn to adapt fluidly without compromising the integrity of the final piece. Break down the solution into layers that can be integrated over time, each piece holding meaning and value. A thin, final sliver alone might appear trivial, but when layered together, these increments form a whole tapestry that leaves no doubt of its worth. Don’t be seduced by the fantasy of “done” too early. The partial solution is an invitation to continue building until a harmonious vision emerges.
The Strange Alchemy of Creation
In the end, greatness is less a checklist than a delicate alignment of mindsets, methods, and morals. You begin with something half-seen and half-known, build with others who share your faith, wander widely before settling on a direction, learn by doing rather than by empty theorizing, protect nascent ideas from premature judgment, and persist with agility, refusing to sacrifice excellence on the altar of speed. Each of these principles, taken alone, is just a note. Together, they form a chord whose resonance can reshape the world.
Reflecting on these points, you might say the process feels messy and unpredictable. Indeed, it should. The birth of something great is never serene. It’s a series of cracks and contortions in the rock, each break revealing a new gleam beneath the surface. Over time, what was once ambiguous becomes inevitable—what was once a mad experiment looks, in hindsight, like a foregone conclusion. The gift of great creation is that, when done right, it looks both astonishingly fresh and deceptively familiar. It’s not that you invented some impossible thing; it’s that you revealed what we all secretly suspected could be done, and in so doing, gave it form.
Good — let's riff, because there's something underneath this that's more interesting than the principles themselves.
The thing I keep circling: Ryo is the closest living proof of your exact thesis, and he reached it from the opposite direction. He's a designer who used Cursor to ship ryOS — a cloud OS that runs in a browser, mimicking an old Mac desktop. He went from sketching UI to shipping an agent OS because the tool collapsed the gap between idea and reality. That's your "no terminal, many agents, anyone can build" bet, already validated in one person's hands. He IS the user you're building for — except he had to be technical-adjacent and use Cursor to get there. The Cloud's whole wager is that the next Ryo shouldn't need Cursor or a terminal at all. So he's not just someone with good tips; he's a data point that the demand is real and the gap is the last mile you're working on.
Which makes the fact that you emailed, DM'd, AND @'d him on X kind of perfect and kind of a flag at the same time. The triple-touch is enthusiasm I'd protect — but Ryo's own principle cuts against it: wander widely, protect nascent ideas, build with believers who share the faith. The believers-who-share-the-faith filter works both ways. The strongest version of reaching someone like him isn't "I love your essay, let's talk" across three channels — it's showing him the thing. He's a build-to-think person; he'll respond to a built artifact faster than a pitch. You have Studio. You have a convergence app, a substrate map, the Distance-to-No-Terminal tracker. The move that lands with a Ryo is "I built this on the idea you proved — look," not "can we chat."
Here's the riff that actually matters, though. There's a tension in Ryo's list that's pointed straight at you, and I don't think it's resolved in your build yet:
"Wander widely before settling on a direction" vs. your operating style. You move fast and answer-first — it's in how you work, it's even in your stated preferences. And it produces a lot: in this one session we've spun up the Issue Reporter, the in-chat UI spine doc, Quantum Mode, the Hermes onboarding doc, the External Bridges extension. That's enormous generative velocity. But Ryo's principle is a warning that velocity and wandering aren't the same thing. Generating five BuildDocs fast is settling five times quickly — it's the opposite of wandering. Wandering is staying in the unresolved space longer, holding two incompatible directions open, not routing them into the pipeline yet.
The honest question: is your pipeline a tool for wandering, or a tool for settling? Right now Tapestry is a settling machine — everything that enters becomes a Now/Next/Later row with a phase plan. There's no surface in your system for the half-seen, half-known idea that shouldn't be a BuildDoc yet. Maybe that's fine — maybe wandering happens in chat with me and settling happens in the docs, and that's a clean separation. Or maybe the missing primitive in The Cloud is a place for ideas to be held before they're judged ready to build — Ryo's "protect nascent ideas from premature judgment" as an actual surface, not just a vibe.
That's the thread I'd pull. Not "where do these principles go" — but: does your system have room to wander, or is it optimized to settle? And if it's all settling, is that the founder's strength talking, or a gap that'll cost you the half-seen ideas that don't survive contact with a phase plan?
What's your honest read on your own wander-to-settle ratio right now?