Content
@
0 reply
0 recast
2 reactions
Steve
@stevedylandev.eth
Of course I’m biased, but I still have to push back on this a bit as a developer. If you want developer adoption for your protocol or product, you’ve got to prioritize good documentation. Docs are often the first thing a developer will see, and it leaves a big impression on whether it’s worth staying or not. Sure if you’re already passionate about Farcaster then you’ll stick through it, but the majority of developers won’t. Good docs will make the developer not only stick around but also praise the product to others because of the experience. Web3 is already bad as it is, where you have cases like the one linked below where talented devs call it a day. If adoption is not goal right now, that’s totally ok. You have to build a platform that’s worth something first. But if you want adoption, prioritize docs. https://mtlynch.io/notes/im-still-confused-about-base/
3 replies
0 recast
18 reactions
Steve
@stevedylandev.eth
Would also clarify you don’t need a DevRel team to write good docs, just the right person
1 reply
0 recast
7 reactions
Justin Hunter
@polluterofminds
And to be honest, Farcaster does not have a lot of developer adoption. They have a small but vocal and creative core group of devs that are willing to put up with limitations. That’s called early adopters. The FC team will need to do something different to get to early majority imo.
1 reply
1 recast
3 reactions
Nastya
@nastya
100% agree about good docs as a priority for adoption. My point is also that many Web3 dev projects, even new ones, focus too much on marketing and DevRels. FC, on the other hand, shows that when you make something new and useful, devs are ready to overcome obstacles if they really need a platform to build something.
0 reply
0 recast
2 reactions
