The ± Factors Wake up! It's API-time!

Wake up! It's API-time!

E-mail Print PDF

Many years ago I went through a list of the most common languages we use. Yes, the list was comprehensive and included all languages people use to communicate. Nicely sorted out according the language business. As always, the list included English, Chinese, Arabic and Spanish as the most common languages being used, but some languages were missing in the list. I made the same observation some weeks ago discovering that still one of the most common languages we use every day was not on the list.


"Hey, I do not speak Java!" you may say. You may not speak it, but you use it. Every day. So do Brazilians, Turks, Swedes, people in China...the list can go on forever. I promise. You use it to see this page and read this text.

As with all languages you will get dialects. And we got it. Some useful and some not. The last couple of years I have been involved in a couple of projects that utilized the dialect in a good way, I have also been involved in a couple of projects that didn't. Guess which projectsthat survived.

Now we are heading towards a paradigm shift in handling languages, including the ones we do not speak, which makes me want to talk about APIs. APIs is according to wikipedia:

An application programming interface (API) is an interface implemented by a software program to enable interaction with other software, much in the same way that a user interface facilitates interaction between humans and computers. APIs are implemented by applications, libraries and operating systems to determine the vocabulary and calling conventions the programmer should employ to use their services. It may include specifications for routines, data structures, object classes and protocols used to communicate between the consumer and implementer of the API.[1][2][3]