yes I'm aware it's nitpicking, which is why I said I agree and that it just need more clarification. but you don't need machine learning to hit these cases jus

yes I'm aware it's nitpicking, which is why I said I agree and that it just need more clarification. but you don't need machine learning to hit these cases just a mismatch between what want to do and how/where it's stored. examples: - a noSQL db that cant directly do what you want and now you need to download lots of document to string them together before updating that field. - a SQL data schema not matching your tasks where need lots and lots of joins and aggregations. - data scattered across multiple web APIs that may have rate limits, now you may have to use a batch API if it exists and find a new route. - data scraped from multiple places, going from 10 to 10 000s now will get you banned from most website, now you need to rewrite your code to circumvent that. none of these examples involve data science, heavy processing algorithms, just moving data and selecting from it. and they seems like the kind of things business/people with no coding experience might want to do. (I want to keep track of prices from competitor, department X,Y, and Z have these info in their databases and gave us read-only access since they don't have time to do things for us, etc ...)