4 ms·
Management: "Hey guys, we need to implement some sort of payment system". Developers: "Ok, we'll see what's out there." Developers: "This one isn't well documen
by cinntaile 4y ago
Management: "Hey guys, we need to implement some sort of payment system".
Developers: "Ok, we'll see what's out there."
Developers: "This one isn't well documented, this one isn't either... Oh hey this one is."
Developers: "We suggest Stripe."
Management: "Ok"
I think you vastly underestimate the importance of ease of use.
- raverbashing 4y agoWell it is a hard problem, isn't it? First impressions do matter, sure Management might also have a problem later in case of non-payment/chargebacks etc But, in general, people need to look past the first impression
- 3np 4y agoAccurate, appropriately detailed, and up-to-date documentation and references are about way, way more than "first impressions". I really don't see how it's a hard problem either? How often does a payment gateway API really need to change? Just spend the resources necessary to get it right. If you really need to, hire (another) FTE on docs.
- spinlock 4y agoI feel like stripe changed their api every day. They support legacy apis forever but you could definitely have a full time job keeping up with the latest version of stripe.
- raverbashing 4y agoYes but you'll only know how good it really is once you try it At first glance some docs look good but when you go to use it, it's confusing/incomplete/outdated
- 3np 4y agoI don't think anyone argued that great docs are sufficient for a great API. They are a requirement, though.