3 ms·
There’s sentiment here on HN that any documentation is good documentation - and while it is better than NO documentation, it’s just not correct to dismiss truly
by arthurofbabylon 7y ago
There’s sentiment here on HN that any documentation is good documentation - and while it is better than NO documentation, it’s just not correct to dismiss truly great documentation.
For example, Stripe (the workplace of the author) has incredible documentation that single-handedly enabled me to build with it, despite my being a wretched server-side developer.
That the documentation alone doubled the potential user-base, thus fostering growth and engagement with the product, is a testament to the power of great document versus just documentation.
V1 docs in markdown - fine. But V2 for an ambitious tool should probably start approaching what Stripe is accomplishing.
- hwayne 7y agoSmall correction: I don't work at Stripe! The person who made Buttondown does, I just use it for my newsletter.
- arthurofbabylon 7y agoAhh ahh, my bad, and thank you for the correction.
- localhost3000 7y agoWe use quite a bit of markdown at Stripe :)
- QuesnayJr 7y agoI was at a conference once that was mainly sales pitches for cryptocurrency startups. Most of the people were very polished, but one guy was clearly a developer who had been pressed into service as a presenter. In the middle of his presentation he started talking about how great the documentation for Stripe is. That's got to be some damn good documentation.