Agreed, when I first started I was very confused by what an API actually was. I would definitely provide at least 3 different examples in addition to spelling out the acronym. At the simplest level, a function could be used as a pseudo-example of an API and build from there. At least it helped me to think of it that way. Now I see pretty much everything as an API.
Thanks, Elijah! This time I will most likely not go much into detail around functions (it will be too technical for the audience). Interesting suggestion to look at a function as a pseudo-example of an API. Similarly one could see an APIs resource as a function, meaning that the API can have multiple functions.
Indeed everything is interconnected and the simplest/ideal way to do that nowadays is via an API or via an interface. There's one analogy for interfaces / APIs that I recently received as an example from a colleague that I find very easy for anyone to relate to: our own biological interfaces with the world, ie our senses.
Elijah, small clarification: my above comment on API resources as functions makes sense in the context of REST APIs. The simplification you mentioned is totally legit!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Agreed, when I first started I was very confused by what an API actually was. I would definitely provide at least 3 different examples in addition to spelling out the acronym. At the simplest level, a function could be used as a pseudo-example of an API and build from there. At least it helped me to think of it that way. Now I see pretty much everything as an API.
Thanks, Elijah! This time I will most likely not go much into detail around functions (it will be too technical for the audience). Interesting suggestion to look at a function as a pseudo-example of an API. Similarly one could see an APIs resource as a function, meaning that the API can have multiple functions.
Indeed everything is interconnected and the simplest/ideal way to do that nowadays is via an API or via an interface. There's one analogy for interfaces / APIs that I recently received as an example from a colleague that I find very easy for anyone to relate to: our own biological interfaces with the world, ie our senses.
Elijah, small clarification: my above comment on API resources as functions makes sense in the context of REST APIs. The simplification you mentioned is totally legit!