Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 10 submissions in the queue.
posted by CoolHand on Thursday May 21 2015, @02:02PM   Printer-friendly
from the oh-the-inhumanity-of-it-all dept.

Algorithms tell you how to vote. Algorithms can revoke your driver’s license and terminate your disability benefits. Algorithms predict crimes. Algorithms ensured you didn’t hear about #FreddieGray on Twitter. Algorithms are everywhere, and, to hear critics, they are trouble. What’s the problem? Critics allege that algorithms are opaque, automatic, emotionless, and impersonal, and that they separate decision-makers from the consequences of their actions. Algorithms cannot appreciate the context of structural discrimination, are trained on flawed datasets, and are ruining lives everywhere. There needs to be algorithmic accountability. Otherwise, who is to blame when a computational process suddenly deprives someone of his or her rights and livelihood?

But at heart, criticism of algorithmic decision-making makes an age-old argument about impersonal, automatic corporate and government bureaucracy. The machine like bureaucracy has simply become the machine. Instead of a quest for accountability, much of the rhetoric and discourse about algorithms amounts to a surrender—an unwillingness to fight the ideas and bureaucratic logic driving the algorithms that critics find so creepy and problematic. Algorithmic transparency and accountability can only be achieved if critics understand that transparency (no modifier is needed) is the issue. If the problem is that a bureaucratic system is impersonal, unaccountable, creepy, and has a flawed or biased decision criteria, then why fetishize and render mysterious the mere mechanical instrument of the system’s will ?

http://www.slate.com/articles/technology/future_tense/2015/05/algorithms_aren_t_responsible_for_the_cruelties_of_bureaucracy.single.html

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Interesting) by krishnoid on Thursday May 21 2015, @06:56PM

    by krishnoid (1156) on Thursday May 21 2015, @06:56PM (#186151)

    "The computer/network is down, so:

    • I can't let you purchase this item
    • I can't give you an estimate based on yesterday's data which we cache at our local site/PC
    • I can't process or even collect a written request for our services
    • I can't release something to you based on your ID and a couple questions"

    An algorithm could be considered simply as a computer implementation of human/business processes, in which case they're both mechanisms of the same underlying issue -- which may be that front-line employees don't have the authority/flexibility/scoping/instruction to go off-script and operate against a division-wide understanding of a central goal.

    If they could, they could use the processes and algorithms as advisories and guidelines towards that goal, and work with customers and other organizations in that light. Otherwise, meat or silicon implementing the rules wouldn't seem to make that much of a difference. They do seem to work well together when working against the customer, however.

    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3