[gollum999]

> Suddenly, everyone was talking about HTTP APIs, when they said API.

I had a junior dev try to correct me when I used "framework" and "API" outside of a web context.

It caught me off guard at first, but the more I've thought about it, it seems inevitable as time goes on. The more abstractions we build, the more unreasonable it becomes to expect every developer to start with "bare metal" and work their way up. Schools are forced to teach with "the other side" (i.e. the highest-level abstractions) as the benchmark for graduating, because that's what employers need. So at some point they have to cut some of the more esoteric CS fundamentals and concepts to make room.

[01HNNWZ0MV43FF]

I had another dev mix up "object" and "response" and say "JSON response" in reference to a request that sent JSON. I asked 2 or 3 times, "Response to _what_?" before figuring it out. That still lives in my head.

[layer8]

From the point of view of the server, the request might be a response. ;)

[hahn-kev]

They did that before, it all depends on your definition of bare metal. They probably don't teach assembly, or circuit design even though that used to be bare metal