SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Badly Trained AI


Badly Trained AI

Author
Message
skeleton567
skeleton567
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4070 Visits: 758
Eric M Russell - Thursday, January 10, 2019 1:01 PM
skeleton567 - Thursday, January 10, 2019 11:00 AM

One case that hits all of us is in insurance risk calculations. Even though you have not had a claim in years or decades, your premium is going to be based on claim history in your area, your age group, etc. I relocated from a rural area to a metropolis, and my premium increased five times in the first six renewals, even though there still have been no claims, because I am now perceived as being a greater risk due to location instead of events. The bias is evident in the selection of criteria on which decisions are made.

Obviously this can also be a good thing, for instance, when you doctor asks you about any family history of heart attack, stroke, cancer. But do you want your health care decisions based on how well you distant cousins pay their medical bills?

The chances are significantly greater in a metropolitan area that another driver will rear end your car and then either drive away or file a bogus lawsuit, leaving YOUR insurance company to pay the bill for an accident that was never your fault in the first place. You've simply moved into a more expensive risk group in general.

So my record of good driving, and my history of having ALREADY paid for covering my risk is now worthless. My coverage is only good as long as I don't use it. Whoop-ti-doo! That's REALLY 'artificial'.

Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)

Group: General Forum Members
Points: 907033 Visits: 48690
Rod at work - Thursday, January 10, 2019 2:56 PM
Eric M Russell - Thursday, January 10, 2019 2:16 PM
Personally, I wouldn't work for an organization that pre-screens candidates based on Credit / BMI / Social Media score or an AI. That doesn't serve the interests of qualified candidates or qualified hiring managers.


I agree with you. However, playing devil's advocate for a moment, I can understand why large companies do use some sort of AI. If you're getting thousands of resumes (CV) a day hiring the personnel staff to go through them by hand becomes very daunting, if not impossible. You've got to do something to try and cut down the mountain of resumes to be reviewed.


How about knowledge then? Wink

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

When you put the right degree of spin on it, the number 318 is also a glyph that describes the nature of a DBAs job. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Eric M Russell
Eric M Russell
SSC Guru
SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)

Group: General Forum Members
Points: 113243 Visits: 15180
skeleton567 - Thursday, January 10, 2019 6:12 PM

So my record of good driving, and my history of having ALREADY paid for covering my risk is now worthless. My coverage is only good as long as I don't use it. Whoop-ti-doo! That's REALLY 'artificial'.

In terms of risk; living in a zip code with a higher prevalence of bad drivers (careless drivers, uninsured drivers, driving while on the phone) is equivalent to living in a hurricane hazard zone. The bad drivers themselves pay the highest premiums, but many of them simply choose to drive uninsured.



"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
xsevensinzx
xsevensinzx
SSC-Insane
SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)

Group: General Forum Members
Points: 22815 Visits: 6089
Jeff Moden - Thursday, January 10, 2019 9:31 AM


My point is that the AI/Machine learning cited me as a potential buyer AFTER I "bought" a vehicle without understanding that I just "bought" a vehicle and I'm not going to be in the market for at least another 36 months when the lease runs out. That's means that the failed miserably in identifying the nature of the source of data they're using. It was never a "lead" because it arrived already frozen. It's just stupid.

Ah, this is because cookies on ads that you see are all not tied to the conversion you made. In meaning, ads are broken down into clicks, impressions, and floodlights. The clicks and impressions generate the cookies where you wear "searching" for a car. The floodlight, which can also generate a cookie, happens when you land on the website and browse around for goods. When you make a purchase on the site, this leads to a conversion floodlight.

Thus, when you are just browsing, Advertiser A, B, and C will see you looking. When you make the purchase on a website, only Advertiser C may know, but A and B will not know because you did not purchase off their ads. Thus, A and B will continue to advertise to you where C may remarket/retarget you.

Being you made the purchase likely at a dealer and not a website, A, B, and C prob still don't know you converted. They just have your clicks and impressions. I would imagine it's extremely hard to tie a car purchased offline to online ads on top of the fact advertisers do not tell other advertisers you purchased.

Eric M Russell
Eric M Russell
SSC Guru
SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)SSC Guru (113K reputation)

Group: General Forum Members
Points: 113243 Visits: 15180
Rod at work - Thursday, January 10, 2019 2:56 PM
Eric M Russell - Thursday, January 10, 2019 2:16 PM
Personally, I wouldn't work for an organization that pre-screens candidates based on Credit / BMI / Social Media score or an AI. That doesn't serve the interests of qualified candidates or qualified hiring managers.

I agree with you. However, playing devil's advocate for a moment, I can understand why large companies do use some sort of AI. If you're getting thousands of resumes (CV) a day hiring the personnel staff to go through them by hand becomes very daunting, if not impossible. You've got to do something to try and cut down the mountain of resumes to be reviewed.


The problem with AI and Data Science is that it relies on quantitative analysis, meaning metrics that are easily available and can be measured numerically. But when evaluating people, it's qualitative attributes that matter most. Rather than relying an algorithm to whittle down a list of 1,000 candidates, you may have better luck simply filtering on keywords like "SQL Server", manually reviewing the 100 most recently submitted resumes, and then lining up in person interviews with the 10 candidates that look the most promising. The DBA team themselves can set aside some time to review resumes. They know what to look for and have a vested interest in getting someone who's a good fit.



"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
xsevensinzx
xsevensinzx
SSC-Insane
SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)

Group: General Forum Members
Points: 22815 Visits: 6089
patrickmcginnis59 10839 - Thursday, January 10, 2019 10:02 AM

The same happened to me but its completely reasonable to expect this in my case, I was most certainly tracked by searches pertaining to vehicles as I was shopping around. The actual purchase I would imagine should NOT show up in the same datasets as it should instead be limited to the companies that were actually involved in the purchase. Given that the purchase of a new vehicle is significant enough that folks might put effort over a period of time evaluating vehicles, it makes sense that ad folks who see these analytics would roll the dice and hope to hit me up as its statistically likely that I have not immediately purchased a vehicle within such a narrow timeframe relative to initiating my web searches regarding this purchase.


Yeppers. It would not be in the same dataset for sure. We have no idea you made the purchase. We just know you searched for it.

Even if you did make a purchase for a brand and the advertiser knew you made the purchase, it doesn't mean the brand has more than one advertiser working with them, where you still get ads for that brand when you know THEY know you made the purchase. They just may have 2 advertisement companies handling different channels of marketing and not talking to one another on who purchased (i.e.: social media advertising versus Google search).

robert.sterbal 56890
robert.sterbal 56890
SSCrazy Eights
SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)

Group: General Forum Members
Points: 9558 Visits: 1723
Jeff Moden - Thursday, January 10, 2019 9:54 PM


How about knowledge then? Wink

What percentage of jobs at large companies are filled by the screening process?

Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)SSC Guru (907K reputation)

Group: General Forum Members
Points: 907033 Visits: 48690
robert.sterbal 56890 - Friday, January 11, 2019 7:53 AM
Jeff Moden - Thursday, January 10, 2019 9:54 PM
Rod at work - Thursday, January 10, 2019 2:56 PM
Eric M Russell - Thursday, January 10, 2019 2:16 PM
Personally, I wouldn't work for an organization that pre-screens candidates based on Credit / BMI / Social Media score or an AI. That doesn't serve the interests of qualified candidates or qualified hiring managers.


I agree with you. However, playing devil's advocate for a moment, I can understand why large companies do use some sort of AI. If you're getting thousands of resumes (CV) a day hiring the personnel staff to go through them by hand becomes very daunting, if not impossible. You've got to do something to try and cut down the mountain of resumes to be reviewed.


How about knowledge then? Wink

What percentage of jobs at large companies are filled by the screening process?


Heh... according to what I've seen, the screening process is actually failing. Many throw the baby out with the bath water while letting the poop stick to the sides of the tub. BigGrin

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

When you put the right degree of spin on it, the number 318 is also a glyph that describes the nature of a DBAs job. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Rod
Rod
One Orange Chip
One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)

Group: General Forum Members
Points: 29879 Visits: 2809
Eric M Russell - Friday, January 11, 2019 7:19 AM


The problem with AI and Data Science is that it relies on quantitative analysis, meaning metrics that are easily available and can be measured numerically. But when evaluating people, it's qualitative attributes that matter most. Rather than relying an algorithm to whittle down a list of 1,000 candidates, you may have better luck simply filtering on keywords like "SQL Server", manually reviewing the 100 most recently submitted resumes, and then lining up in person interviews with the 10 candidates that look the most promising. The DBA team themselves can set aside some time to review resumes. They know what to look for and have a vested interest in getting someone who's a good fit.


I agree with you, Eric. However, I'd like to point out that filtering for "SQL Server" is just manually doing what an AI would likely do.

Kindest Regards,Rod
Connect with me on LinkedIn.
Rod
Rod
One Orange Chip
One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)

Group: General Forum Members
Points: 29879 Visits: 2809
Jeff Moden - Friday, January 11, 2019 8:05 AM


Heh... according to what I've seen, the screening process is actually failing. Many throw the baby out with the bath water while letting the poop stick to the sides of the tub. BigGrin


Really? Interesting. I wonder why they stick with it, then?

Kindest Regards,Rod
Connect with me on LinkedIn.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search