Emilie Kormienko

Broadly, the best way to get better at developing strategy: s pend time understanding your market (including your competition); s pend time understanding your customers and their needs; spend time crafting and executing strategies — and learn from those experiences; study colleagues who are great strategic thinkers; read about strategy.

Before investing your money into a particular project, make sure you do your due diligence.

I tried to embrace “learning in public” as much as I could. In addition to writing blog posts and tweeting, I created a bunch of other artifacts, like conference talks (developer conferences are a thing, which was new for me!), interviews, a podcast series, and lists published as GitHub repositories.

As Nassim Taleb wrote in Fooled by Randomness, “Mild success can be explainable by skills and labor. Wild success is attributable to variance.”

A promising technology is a piece of your project’s puzzle, not to be thrown all over it.

Keep your community guidelines simple, visible, and easily accessible.

While educating users, entice them with your product's value so they're willing to put up with the boring parts of onboarding. Tease them with how amazing life will be once they are done.