Maybe 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.
You don't need ML/AI, you need SQL
41–50 of 87 posts
Re: You don't need ML/AI, you need SQL
#42> say a person bought a pair of shoe, sunglasses and a book. For their newsletter, we will show include shoes, sunglasses and books. This was a lot more relevant than sending random stuff. I 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…
In fact this is a perfect example of how NOT to do purchase-history-based suggestions, which unfortunately also seems to be how most companies do it. They see a big purchase (or search terms relating to one) and spam you with options for that purchase. But if I just bought a car, or a drone, or a laptop, then the last thing I want to see is ads for other cars or drones or laptops.
Even applying just a little intelligence and showing ads for accessories (floor mats? spare batteries? bluetooth mice?) would make things substantially more useful.
Re: You don't need ML/AI, you need SQL
#43> say a person bought a pair of shoe, sunglasses and a book. For their newsletter, we will show include shoes, sunglasses and books. This was a lot more relevant than sending random stuff. I 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…
Re: You don't need ML/AI, you need SQL
#44* How does every additional coupon-dollar affect the total amount a customer buys?
* What is the relationship between customer age and retention for my store?
* Does giving a customer more purchase options help or hurt their chances of making a purchase?
My experience is that each of these questions can be solved, in part, using 3 lines of Python code:
from sklearn.linear_model import LinearRegression
lr = LinearRegression()
lr.fit(X,y)
Then look at the beta coefficients of the model, and you have a rough idea of how different features are correlated. Doing something like this in SQL sounds difficult. If you have data to interpret, it makes sense to use similar methods. I can't think of an example where you have data but refuse to look at it until your company is "bigger".Re: You don't need ML/AI, you need SQL
#45Maybe 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.
Re: You don't need ML/AI, you need SQL
#46Maybe 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.
The comment lists at least two "questions" that can be answered easily with SQL and a graph and even in ways that give more nuance than linear regression can capture.
Re: You don't need ML/AI, you need SQL
#47Maybe 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.
People mentioned resume building and FOMO, I'll add to this: funding and sales. Investors and corporate managers are into this hype as much as engineers - if not more, so AI/ML is a label people want to use to get more money.
Re: You don't need ML/AI, you need SQL
#48Good post, but I couldn't disagree more. Regardless of your business size, it will always be valuable to know information such as: * How does every additional coupon-dollar affect the total amount a customer buys? * What is the relationship between customer age and retention for my store? * Does giving a customer more purchase options help or hurt their chances of making a purchase? My experience is that each of thes…
As a workaround, you could look for high VIF to detection multicollinearity, use some sort of stepwise selection / penalized regression, or use something like relaimpo (https://cran.r-project.org/web/packages/relaimpo/index.html) - not sure of a Python equivalent - to judge overall feature importance in the model.
Re: You don't need ML/AI, you need SQL
#49I like to think I'm not too nitpicky about fonts, but that st ligature is incredibly distracting. It's the second article I've seen here that uses it over the last few days, but I'm not sure if it's the same site or not.
Re: You don't need ML/AI, you need SQL
#50> say a person bought a pair of shoe, sunglasses and a book. For their newsletter, we will show include shoes, sunglasses and books. This was a lot more relevant than sending random stuff. I 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…
So you know... I don’t think it’s unfair to say that for smaller vendors, the cost/effort of setting up a ML model may dwarf the fractional improvement it offers over just having one person doing human generated SQL queries.
The point is this isn’t like machine vision or voice, where its almost expontentionally better than traditional approaches.
It’s just... a bit better. Which is worth it only if the fractional improvement pays for the setup cost.