3 ms·
When writing a new library with little adoption, with a goal of driving adoption where do you think effort should be dedicated between documentation, features,
by paddy_m 3y ago
When writing a new library with little adoption, with a goal of driving adoption where do you think effort should be dedicated between documentation, features, and promotion?
I think they all together a bit. I see documentation as a way of marketing features that have been written... but it doesn't help until people discover the project.
How do you know when documentation is holding you back?
- jarbus 3y agoProbably features. If existing libraries can already do what you are marketing, and are better documented, there’s no point in using your library all else held equal. I think first you need to build distinguishing features to get people to notice the tech, and then document it to make it more usable and drive adoption into actual software