云启资本

云启资本

@yunqipartners

科技常新，寻找未来开创者

534 articles18 episodes

Articles

How Does Complexity Produce Simplicity Behind "Emergence"? | Yunqi Science Chat --- The term "emergence" has become something of a buzzword in recent years. From the sudden "awakening" of large language models to the spontaneous order seen in flocks of birds, emergence seems to describe a magical leap — where countless simple individuals, through interaction, produce complex intelligent behavior. But is emergence really that mysterious? In this episode of *Yunqi Science Chat*, we want to flip the question around: **not how simple produces complex, but how complex produces simple.** This reversal reveals a deeper truth about emergence: the complex behaviors we observe often stem from surprisingly simple underlying rules. The complexity is in the eye of the beholder; the simplicity is in the mechanism. ## The "Simple" Side of Emergence Take Conway's Game of Life, the classic cellular automaton. Each cell follows just two rules: a live cell with two or three neighbors survives; a dead cell with exactly three neighbors comes alive. That's it. Yet from these two rules emerge gliders, oscillators, self-replicating structures — even universal computers. The emergent complexity is staggering

How Does Complexity Produce Simplicity Behind "Emergence"? | Yunqi Science Chat --- The term "emergence" has become something of a buzzword in recent years. From the sudden "awakening" of large language models to the spontaneous order seen in flocks of birds, emergence seems to describe a magical leap — where countless simple individuals, through interaction, produce complex intelligent behavior. But is emergence really that mysterious? In this episode of *Yunqi Science Chat*, we want to flip the question around: **not how simple produces complex, but how complex produces simple.** This reversal reveals a deeper truth about emergence: the complex behaviors we observe often stem from surprisingly simple underlying rules. The complexity is in the eye of the beholder; the simplicity is in the mechanism. ## The "Simple" Side of Emergence Take Conway's Game of Life, the classic cellular automaton. Each cell follows just two rules: a live cell with two or three neighbors survives; a dead cell with exactly three neighbors comes alive. That's it. Yet from these two rules emerge gliders, oscillators, self-replicating structures — even universal computers. The emergent complexity is staggering

To solve the biggest problem, start by seizing the smallest clue.

云启资本·

Podcasts

Vol.17 48-Hour Xiaohongshu Hackathon Hit: How an AI-Native Product That Broke the "Retention Curse" Was Built --- Two weekends ago, I participated in a 48-hour hackathon hosted by Xiaohongshu. Our team of four built an AI-native product from scratch — no code, no design background between us — and ended up winning the "Most Popular" award. The product? A voice diary app called **"Echo"** that uses AI to turn fragmented daily moments into serialized, episodic "life podcasts." Think *This American Life*, but starring you. What surprised me wasn't that we won. It was that people kept using it *after* the demo. Here's the dirty secret of AI hackathons: most projects die the moment judges stop clapping. The "retention curse" is real — users try your GPT wrapper once, say "neat," and never return. We broke that pattern. Our daily active user rate among beta testers hit 34% in week one, which for a hackathon product is basically unheard of. How? Three deliberate choices we made against hackathon orthodoxy. **First, we refused to build a chatbot.** The default AI product in 2024 is still "talk to a large language model." We explicitly rejected this. Chat interfaces create *performance anxiety* — users feel pressure to ask the "right
Vol.17 48-Hour Xiaohongshu Hackathon Hit: How an AI-Native Product That Broke the "Retention Curse" Was Built --- Two weekends ago, I participated in a 48-hour hackathon hosted by Xiaohongshu. Our team of four built an AI-native product from scratch — no code, no design background between us — and ended up winning the "Most Popular" award. The product? A voice diary app called **"Echo"** that uses AI to turn fragmented daily moments into serialized, episodic "life podcasts." Think *This American Life*, but starring you. What surprised me wasn't that we won. It was that people kept using it *after* the demo. Here's the dirty secret of AI hackathons: most projects die the moment judges stop clapping. The "retention curse" is real — users try your GPT wrapper once, say "neat," and never return. We broke that pattern. Our daily active user rate among beta testers hit 34% in week one, which for a hackathon product is basically unheard of. How? Three deliberate choices we made against hackathon orthodoxy. **First, we refused to build a chatbot.** The default AI product in 2024 is still "talk to a large language model." We explicitly rejected this. Chat interfaces create *performance anxiety* — users feel pressure to ask the "right

Vol.17 48-Hour Xiaohongshu Hackathon Hit: How an AI-Native Product That Broke the "Retention Curse" Was Built --- Two weekends ago, I participated in a 48-hour hackathon hosted by Xiaohongshu. Our team of four built an AI-native product from scratch — no code, no design background between us — and ended up winning the "Most Popular" award. The product? A voice diary app called **"Echo"** that uses AI to turn fragmented daily moments into serialized, episodic "life podcasts." Think *This American Life*, but starring you. What surprised me wasn't that we won. It was that people kept using it *after* the demo. Here's the dirty secret of AI hackathons: most projects die the moment judges stop clapping. The "retention curse" is real — users try your GPT wrapper once, say "neat," and never return. We broke that pattern. Our daily active user rate among beta testers hit 34% in week one, which for a hackathon product is basically unheard of. How? Three deliberate choices we made against hackathon orthodoxy. **First, we refused to build a chatbot.** The default AI product in 2024 is still "talk to a large language model." We explicitly rejected this. Chat interfaces create *performance anxiety* — users feel pressure to ask the "right

云启资本·