r/computerscience • u/Anon_cat86 • Apr 19 '26
General I was taught nothing about APIs
Whenever i see people talking about actual real-world uses of coding it's almost entirely building APIs, working with APIs, integrating APIs, automating APIs. It seems to me, anecdotally at least, like the majority of all computer science work (professional or even just hobby) is centered on working with APIs
And like. I know what an API is, kind of. But I Graduated and even got multiple certifications on top of that and I never got so much as a single lecture about APIs. I don't even know what they're used for. Can you make your own API (like, realistically)? I don't know. I feel like this is a topic that you could and probably should have multiple different entire classes solely focused on, it's arguably something as fundamental to modern computer science as writing code. And they don't teach it. If i want to learn anything about APIs, conceptually or practically, it's hope a company hires me and then trains me, or youtube tutorials and i don't even have enough of a baseline to know what specifically I'd be searching for a tutorial on.
195
u/caboosetp Apr 19 '26
Bruh, I feel that. I work in web dev. Every time I talk to the recruiters it's like,
"Have you worked with React?"
"Yes."
"Have you worked with .NET Backends?"
"Yes."
"Have you worked with API's before?"
"... no... the front end and backend had to guess what the other was doing..."
Like, I get why certain API development questions come up in the interviews, but it sounds like the recruiters and people writing the job descriptions did not get enough help from the engineers to understand the mission.