Thanks. I was about to ask what "APIs over databases" meant. I design DBs and write APIs and I was struggling to imagine a scenario in which a data consumer - o

Thanks. I was about to ask what "APIs over databases" meant. I design DBs and write APIs and I was struggling to imagine a scenario in which a data consumer - or I as a consumer - wouldn't want to understand both. I'm not even sure to whom they're interchangeable terms. Possibly to a front end coder who doesn't want to craft queries? I don't call myself a data scientist or even a software engineer (though I'd be well within my rights to, under the current understanding of those descriptions). I'm a coder who writes a lot of business logic and analyzes results. But I have noticed a creeping tendency recently for people who futz around with large data dashboards or LLM conversational strategies to try to distance themselves from the people who write code, as if somehow we who actually think through the logistics of performance and structure are just road workers while they're driving the shiny Tesla of Science, coming to the Big Answers. It's ridiculous, because anyone who's built a NN or a large DB knows how to query one, and is usually moderately bored by the results.