But you don't gain ML/AI know-how by doing SQL, nor you discover previously unknown potential about your product buy sticking to your usual toolset. Not that I necessarily disagree with the OP but I find it deeply uninspirational. What's the difference between using ML/AI for problems traditionally solved by some other tool and using any other tool to solve the same problem unconventionally? Both can be "hacking". I…
You don't need ML/AI, you need SQL
31–40 of 87 posts
Re: You don't need ML/AI, you need SQL
#32Earlier quoted context omitted.
Thanks for the feedback. Do you have any font preference?
Turning this clause off in your style sheet turns off that awful st ligature: font-feature-settings: "liga", "dlig"; So just remove that clause from your stylesheet and you'll be rid of that ligature.
Shame the advice is to turn them off completely...
Re: You don't need ML/AI, you need SQL
#33Or maybe you can do ML with SQL.... Postgres can do basic linear regression, I did this a couple of times for an analysis and found it pretty handy.
Re: You don't need ML/AI, you need SQL
#34There aren't very many DBAs practicing in modern shops and devs don't seem to be too into SQL and delivering excellent SQL queries and schemas. It's its own skillset. I would also call out the NoSQL hype train here. NoSQL has its place , and largely its place is when SQL can not tolerate the intensity of traffic or the size of the dataset. You can look at the Dynamo paper for an example of the engineering rationale.…
also, its nice to plop json, avro, csvs, parquet, or what ever data in storage and just query/join/analyze it. no need to put the story on hold because you are waiting for the oracle dba to increase space again.
Re: You don't need ML/AI, you need SQL
#35SQL is a language that helps retrieve the data you're looking. ML/AI helps you predict the future (using past data).
Maybe this is directed towards product people? But it has SQL in the title so it can't be. I'm confused as to who the audience is here.
Re: You don't need ML/AI, you need SQL
#36Maybe I'm niave, but are there really people who want to hop on the AI bandwagon just to do mundane lookups like this? When I worked with machine learning many years ago, we learned that it was no better than the heuristics already in place. The thing is, it's much easier to diagnose a well written and understood heuristic than a machine learning model.
For example, the author refers to a shopping newsletter where you personalize suggestions for certain products after a customer buys a particular product. This is very often a machine learning 101 example but really there's nothing preventing you from writing those heuristics yourself -no ML involved(e.g: if a customer buys a pillow, suggest pillow cases).
Machine learning does makes sense for something like that if your website is Amazon, but is definitely an overkill if your website is an e-commerce for house garments.
The funny thing is that usually you will end up writing those heuristics implicitly since you need to label your data anyways.
Re: You don't need ML/AI, you need SQL
#37There's no logical equivalency between SQL and ML/AI. SQL is a language that helps retrieve the data you're looking. ML/AI helps you predict the future (using past data). Maybe this is directed towards product people? But it has SQL in the title so it can't be. I'm confused as to who the audience is here.
Re: You don't need ML/AI, you need SQL
#38But you don't gain ML/AI know-how by doing SQL, nor you discover previously unknown potential about your product buy sticking to your usual toolset. Not that I necessarily disagree with the OP but I find it deeply uninspirational. What's the difference between using ML/AI for problems traditionally solved by some other tool and using any other tool to solve the same problem unconventionally? Both can be "hacking". I…
But you don't gain ML/AI know-how by doing SQL, nor you discover previously unknown potential about your product buy sticking to your usual toolset. If current ML/AI is the future and reveals more than anything else could, then it's logical for everyone to be piling onto it whether it's an applicable at the moment or not. If current ML/AI is just another tool, then it's reasonable to use if and only it's applicable.…
Re: You don't need ML/AI, you need SQL
#39Earlier quoted context omitted.
Turning this clause off in your style sheet turns off that awful st ligature: font-feature-settings: "liga", "dlig"; So just remove that clause from your stylesheet and you'll be rid of that ligature.
I like ligatures when they're used well, but that one is just incredibly distracting. Shame the advice is to turn them off completely...
Re: You don't need ML/AI, you need SQL
#40I agree with the general sentiment of the article, but this seems like a poor example, since a more sophisticated approach can add a lot of value to a recommendation system. How do you know whether a customer is likely to want more than one item in any of those categories? If they already purchased sunglasses, wouldn't they be more likely to purchase, say, a sunglasses case and/or sunscreen? If they purchased a book, do you recommend the same book again? And if not, how do you choose which book(s) to include?
Of course, you could technically still handle this in SQL with a bunch of CASE statements, but obviously that doesn't scale well across a wide range of products. The whole point of ML/AI in that use case is to scale that type of nontrivial decision making.