…Which brings up an interesting point: when you introduce an API, you are deciding to create a second type of customer - the developer. And that customer should be treated with equal respect as any other customer, even if there are fewer of them. Too often companies will release an API because they can or because they should, and then leave it to rot. If you’re going to do it, do it all the way.
I’ve dealt with at least one company who put out an API, bragged about it, then became immediately fearful when I started using it to make up for some shortcomings in their product. They hadn’t foreseen the possibility that people would use the API to do anything serious.
(via stoweboyd)
