Garry Tan and Why Speed Is the Whole Thesis
Garry Tan runs Y Combinator and spends a lot of time on X. If you follow him, you notice a pattern: he's obsessed with founders who move fast and show their work publicly. Not fast in the "ship broken things" sense, fast in the "don't let the idea die in a Google Doc" sense.
His framework for what he wants to see in great founders is simpler than most people think:
Make something people want. Talk to users. Move. That's it. The complexity is in the execution, not the concept.
But the part people underweight is the showing part. Garry talks about building in public not as a marketing tactic but as a forcing function. When you commit to showing something, you have to make something showable. That constraint eliminates a lot of the comfortable delusion that early-stage founders live in, the delusion that the thing is almost ready, almost good enough, almost worth sharing.
My read on what he actually wants to see in YC: proof that you ship. Not a pitch deck. Not a roadmap. Working software, real users, feedback loops that are already running. The application is almost secondary to the pattern of behavior it represents.
The thesis I keep coming back to: the speed at which you can turn an observation into a thing someone can touch is the variable that determines whether you get a company or a thought experiment. Ideas are cheap. Implementations, even rough ones, create surface area for reality to push back against.
In enterprise, this is heresy. Enterprise moves slow by design. Every workflow has a change control board, a testing cycle, a stakeholder review. Which is exactly why the people who figure out how to apply the YC velocity to enterprise problems have an enormous edge. The moats are deeper and the customers are stickier, but the builder has to be willing to operate like a startup in a slow-moving system.
That's what I think about when I think about building Aether Ops. Ship it. Show it. Let reality respond.