The Duolingo Handbook could be a great framework for Nostr development. I've given some of my highlight takeaways and added *my thoughts on a few points.
Full PDF attached.
Duolingo TL;DR
- Take the Long View
- Raise the Bar
- Ship It
- Show Don't Tell
- Make It Fun
Luis had already sold his first company, reCAPTCHA, in 2009. As he put it: βThis gave me the flexibility and perspective to think about our mission first and foremost.β
We are tech optimists. From the beginning, weβve believed that technology will advance enough to make our most ambitious ideas possible. And betting on that has been crucial to how we operate. For example, we invested in early text-to- speech systems instead of recording human voices: even though our audio sounded robotic at first, we knew the technology would improve with time.
*What does this look like for Nostr?
We built Shake to Report, a simple tool that lets anyone in the company snapshot and report an issue instantly by shaking their device. Over the years, Shake to Report has become a vital part of our development process, making excellence in the app a shared responsibility.
*What does this look like for Nostr apps and leveraging eager users and early adopters to shorten the feedback loop for iterating?
V1s > MVPs
The difference is important: MVPs often have a lower standard of quality and can be used as an excuse to ship subpar work. V1s, on the other hand, are polished. They may not have all the bells and whistles, but they meet our bar.
*Ship early yes but make sure the first version solves the core problem or at least makes enough progress users will stick around as it's built out.
Crafting strong TL;DRs boosts the chances that your work will be seen and remembered. They make complex information more digestible and, importantly, encourage clearer thinking. To write a TL;DR, you have to distill your message down to its most essential points.
*More literal TL;DRs or memes
π.pdf
