Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Submission Summary: 0 pending, 6 declined, 2 accepted (8 total, 25.00% accepted)

Submission + - Would you refuse a job involving AI?

Nemosoft Unv. writes: En email from a recruiter landed in my inbox today, looking for a developer (or what they called a Data Scientist) with a lot of experience with GenAI, machine learning, large language models, etc. Their goal was to "improve the way call center agents support their customers: faster, smarter and with optimal service". They also wanted "assurances that the AI solution has measurable impact". As is typical with such emails I don't know who the end customer is but they are located in a major city so must be not a small company.

The job doesn't fit my current skillset but even if it did, I would not want to take it for two reasons. First, the job description implies that they want to keep to number of humans working there to a minimum or stow more work on the remaining agents. I have no desire to put someone out of a job or cause burnout, even if it's for a call center.

And that's reason number two: by the time I reach for the phone to call a company, I want to talk to an actual human. Things usually have already progressed to a state where emails or online forms haven't worked, so human intervention is needed. All of us already dread call centers with their menus and "type your insurance number after the beep and finish with a #" nonsense. I don't want have to "talk" first to either a chatbot or voiceprompt, then only to be finally transfered to a real human after much finagling. I have no desire to dump more of this misery on my fellow Earthlings.

So my question: would you refuse a job where the intent (real or apparent) is to replace humans with AI? If not, what are you considerations to take it?

Submission + - Cyanogen Pulls The Plug

Nemosoft Unv. writes: A very brief post on Cyanogen's blog says it all really:

As part of the ongoing consolidation of Cyanogen, all services and Cyanogen-supported nightly builds will be discontinued no later than 12/31/16. The open source project and source code will remain available for anyone who wants to build CyanogenMod personally.

Of course, with no focussed team behind the CyanogenMod project it's effectively dead. Building an Android OS from scratch is no mean feat and most users won't be able to pull this off, let alone make fixes and updates. So what will happen next? And what do they mean by "ongoing consolidation"?

Submission + - Have your iPhone 6 repaired, only to get it bricked by Apple (theguardian.com) 1

Nemosoft Unv. writes: In case you had a problem with the fingerprint sensor or some other small defect on your iPhone 6 and had it repaired by a non-official (read: cheaper) shop, you may be in for a nasty surprise: error 53.

What happens is that during an OS update or re-install the software checks the internal hardware and if it detects a non-Apple component, it will display an error 53 and brick your phone. Any photos or other data held on the handset is lost – and irretrievable.
Thousands of people have flocked to forums to express their dismay at this. What's more insiduous is that the error may only appear weeks or months after the repair.

Increduously, Apple says this cannot be fixed by any hard- or software update, while it is clearly their software that causes the problem in the first place.

And then you thought FTDI was being nasty...

Slashdot Top Deals

Money is the root of all wealth.

Working...