"尽早发布并频繁发布"
Quote meaning
The core idea here is all about getting your work out into the world quickly and frequently. Rather than waiting for something to be perfect, it's better to share it as soon as it's functional. You make small, regular updates rather than one big one. This approach helps you learn and adapt faster based on real-world feedback.
This concept has roots in software development, specifically in the open-source community. Eric S. Raymond, a major figure in this space, popularized this idea in his book "The Cathedral and the Bazaar". He argued that the sooner you get your software into the hands of users, the sooner you can find out what's working and what's not. This philosophy isn't just for techies, though—it can apply to any creative process.
Imagine you're an artist working on a series of paintings. Instead of spending months or even years perfecting each piece, you start sharing your works-in-progress online. Maybe through social media or a personal blog. This way, you get immediate feedback—people can tell you what they love, what confuses them, and what they'd like to see more of. You can then use this input to tweak your future pieces. It creates a feedback loop that makes your work better and better over time.
So, how can you apply this wisdom in your own life? Let's say you're a writer. Instead of laboring over your novel for years without showing it to anyone, try sharing a chapter at a time on a writing forum or with a critique group. This way, you get early feedback that can help shape the rest of your story. Plus, it keeps you motivated. Knowing that people are waiting for the next chapter can be a powerful incentive to keep writing.
Think about the rise of agile methodologies in project management. These methods emphasize delivering work in small, usable increments. Take the example of a startup developing a new app. Instead of spending a year building what they think users want, they release a basic version as soon as possible. Users start interacting with it, and the team gathers feedback. They find out which features are popular, which are confusing, and what new ideas users have. With this data, they can prioritize their next steps. This cycle repeats, allowing the app to evolve based on real user needs rather than just the developers' assumptions.
Imagine this scenario: you're learning guitar. Instead of waiting until you've mastered a song to play it for friends or record a video, you share your progress every few weeks. At first, it might be a bit rough—missed notes, awkward transitions. But your friends might give you tips or encouragement. Maybe someone points out a cool strumming pattern or a finger placement hack. Over time, you get better, and your improvements are visible not just to you, but to everyone following your journey.
In short, don't wait for perfection. Share your work early, share it often, and use the feedback to make it better. You'll learn more quickly and stay motivated—and who knows, you might just inspire someone else to get started too.
This concept has roots in software development, specifically in the open-source community. Eric S. Raymond, a major figure in this space, popularized this idea in his book "The Cathedral and the Bazaar". He argued that the sooner you get your software into the hands of users, the sooner you can find out what's working and what's not. This philosophy isn't just for techies, though—it can apply to any creative process.
Imagine you're an artist working on a series of paintings. Instead of spending months or even years perfecting each piece, you start sharing your works-in-progress online. Maybe through social media or a personal blog. This way, you get immediate feedback—people can tell you what they love, what confuses them, and what they'd like to see more of. You can then use this input to tweak your future pieces. It creates a feedback loop that makes your work better and better over time.
So, how can you apply this wisdom in your own life? Let's say you're a writer. Instead of laboring over your novel for years without showing it to anyone, try sharing a chapter at a time on a writing forum or with a critique group. This way, you get early feedback that can help shape the rest of your story. Plus, it keeps you motivated. Knowing that people are waiting for the next chapter can be a powerful incentive to keep writing.
Think about the rise of agile methodologies in project management. These methods emphasize delivering work in small, usable increments. Take the example of a startup developing a new app. Instead of spending a year building what they think users want, they release a basic version as soon as possible. Users start interacting with it, and the team gathers feedback. They find out which features are popular, which are confusing, and what new ideas users have. With this data, they can prioritize their next steps. This cycle repeats, allowing the app to evolve based on real user needs rather than just the developers' assumptions.
Imagine this scenario: you're learning guitar. Instead of waiting until you've mastered a song to play it for friends or record a video, you share your progress every few weeks. At first, it might be a bit rough—missed notes, awkward transitions. But your friends might give you tips or encouragement. Maybe someone points out a cool strumming pattern or a finger placement hack. Over time, you get better, and your improvements are visible not just to you, but to everyone following your journey.
In short, don't wait for perfection. Share your work early, share it often, and use the feedback to make it better. You'll learn more quickly and stay motivated—and who knows, you might just inspire someone else to get started too.
Related tags
Continuous improvement Incremental improvement Iteration Lean startup Mvp Product management Software development
MORE QUOTES BY Kevin Rose