#API ##Application Programming Interface Either you write Applications, or you connect to them. For Payments, for Identification, for Storage, for Connectivity and so on and so on, you will use more things the more people you want to reach. You need to connect to already existing networks so you need to learn the languages that software use to talk to each other This language is collectively called as the Application Programming Interface
In general there will be good API and bad API, meaning the more effort it is to deal with it, the worse it is. Good API in general doesn't require too much effort from anyone.
I believe that to achieve a good API, two things has to remain true in the lifetime of the API:
- no surprises, that is, no changes and no hidden quirks that are uncovered only in practice and require workarounds
- no versioning, if you want something new, you give it a new name. an API is not a tamagotchi, please don't treat it like one if you don't want to kill it eventually.