Slashdot Mirror


How Responsible Are App Developers For Decisions Their Users Make?

itwbennett writes: In a blog post, Rado Kotorov, Chief Innovation Officer at Information Builders asserts that the creators of enterprise apps implicitly assume some of the responsibility for other people's decision making. He says it's not just developers, but anyone who is involved, from defining the concept, to requirements gathering, to final implementation. Thus, the creators of the app have an ethical obligation to ensure that people can reach the right conclusions from the facts and the way they are presented in the app.

152 comments

  1. There I fixed it for you... by jbrandv · · Score: 1

    The creators of the app have an ethical obligation to ensure that people reach the same conclusions as the developers.

    1. Re:There I fixed it for you... by hsmith · · Score: 4, Informative

      Good luck with that. They keep building better idiots.

    2. Re:There I fixed it for you... by Jamu · · Score: 4, Insightful

      Users are responsible for their own decisions. If developers have an ethical obligation, then it's to inform and train users, so that they can make better decisions.

      --
      Who ordered that?
    3. Re:There I fixed it for you... by Anonymous Coward · · Score: 1

      Users are responsible for their own decisions. If developers have an ethical obligation, then it's to inform and train users, so that they can make better decisions.

      It's just the ongoing effort to destroy and bury the concept of personal responsibility. That's all. The rest is just window dressing.

      It's amazing how much happier and more satisfied someone is when they're not perpetually someone else's victim, when victimhood status is reserved for those who suffer through no fault of their own.

    4. Re:There I fixed it for you... by Gr8Apes · · Score: 3, Insightful

      A company designs and builds a car to safely drive at 70 mph.

      You drive at 140mph in the rain, hydroplane and lose control hitting a bridge column, and die. I'd say the fault lies with the driver. What about you?

      Said company puts in an ignition switch that's faulty and disconnects the entire control system while driving at 70mph and ignores reports of this problem for a decade. That would not only be the fault of said company, but adds layers of premeditation still to be decided.

      --
      The cesspool just got a check and balance.
    5. Re:There I fixed it for you... by Anonymous Coward · · Score: 0

      I don't pay developers to hink. I pay them to code to the design document. Asking them to think is a slippery slope that leads to going over budget.

    6. Re:There I fixed it for you... by FranTaylor · · Score: 1, Troll

      if there is a pedestrian on the bridge, is he responsible for his own death? after all it is well known that people get hit by cars when they decide to walk near the road

      if the car has a speedometer that goes to 140 mph, can the driver assume that the car can be driven at that speed?

      if the owner of a car knows full well that their ignition switch is acting strange and they keep driving the car anyway, are they responsible for the resulting deaths?

    7. Re:There I fixed it for you... by rjstanford · · Score: 1

      A company designs and builds a car to safely drive at 70 mph.

      You drive at 140mph in the rain, hydroplane and lose control hitting a bridge column, and die. I'd say the fault lies with the driver. What about you?

      Said company puts in an ignition switch that's faulty and disconnects the entire control system while driving at 70mph and ignores reports of this problem for a decade. That would not only be the fault of said company, but adds layers of premeditation still to be decided.

      Alternately:

      A company designs and builds a car to safely drive at 70mph.

      They spend lots of time and money showing pictures of the car on a race track and design the interior to make it feel like a race car.

      The default position of the gearshift when pulled down disables all of the speed limiters and briefly flashes a "Race mode" light that, if you read your owners' manual, indicates that you agree to not hold them responsible for anything.

      A complex procedure drops you into "street mode" which baffles the exhaust to legal levels and enables traction control.

      When someone drives at 80mph and wrecks, the car developers act surprised and alarmed that anyone would be so irresponsible.

      --
      You're special forces then? That's great! I just love your olympics!
    8. Re:There I fixed it for you... by Anonymous Coward · · Score: 0

      This is another way of saying that if you develop a climate modeling app and it is used to invalidate AGW claims, you are ethically at fault. So, no matter what the input data is, the answer has been predetermined. The debate is over.

    9. Re:There I fixed it for you... by Anonymous Coward · · Score: 0

      if the car has a speedometer that goes to 140 mph, can the driver assume that the car can be driven at that speed?

      If a driver assumes that the markings on the speedometer are the only thing that matters when determining the safe operational speed of the vehicle, can I assume the driver is a fucking moron?

    10. Re:There I fixed it for you... by cayenne8 · · Score: 5, Interesting

      Good luck with that. They keep building better idiots.

      Yep, to this day, I"m still amazed that we have to have warning tags on hair blow dryers, that not only have it in print, but also with cartoon like diagrams warning you to NOT use the blow dryer while in the bathtub filled with water.

      Seriously, I wonder if the depth of our litigious society has started to seriously interfere with natural selection, by keeping idiot genes in the pool when they should have weeded themselves out years ago.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    11. Re:There I fixed it for you... by cayenne8 · · Score: 4, Interesting

      if there is a pedestrian on the bridge, is he responsible for his own death? after all it is well known that people get hit by cars when they decide to walk near the road

      if the car has a speedometer that goes to 140 mph, can the driver assume that the car can be driven at that speed?

      if the owner of a car knows full well that their ignition switch is acting strange and they keep driving the car anyway, are they responsible for the resulting deaths?

      I think I can answer these all with one of two responses. You pick the correct one:

      1. Shit Happens

      2. Use common sense (what happened to this option over the years?).

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    12. Re:There I fixed it for you... by Oligonicella · · Score: 1

      Did the pedestrian knowingly walk or jump in front of the vehicle?

      Yes they can. Did the driver do so in intelligent conditions (appropriately constructed and marked road?) or in a residential area?

      The last one is at least less vague. They bear responsibility for external persons but did the driver warn the passengers of their dereliction of safety? Those are less clear cut.

      I can walk you down to the details of any example you choose to ignore the context of.

    13. Re:There I fixed it for you... by Oligonicella · · Score: 1

      I notice that you make the speedster mode easy and then arbitrarily make returning to normal difficulty difficult. You purposely loaded your example why?

    14. Re:There I fixed it for you... by iamgnat · · Score: 4, Insightful

      This whole argument is stupid. It's not the hammer, baseball bat, knife, gun, ... manufacturer's responsibility if you use their product to produce inappropriate results. It's their responsibility to make sure that it can be used safely for it's intended purpose, but not guard against every possible misuse the average idiot can come up with. Is it irresponsible of the manufacturer that I can swing my hammer at my toe? Should all hammers be built so that they will only swing when the target is an approved force receptacle?

      if there is a pedestrian on the bridge, is he responsible for his own death? after all it is well known that people get hit by cars when they decide to walk near the road

      If it was a "simple" accident through no egregious fault of the driver, manufacturer of the car, engineer that designed the bridge, builder of the bridge, or the pedestrian, then yes shit happens and it sucks. Life isn't pretty and bad things happen all the time.

      If, however, there is demonstrable fault on any of the related parties (maybe the pedestrian was naked and distracted the driver...) then the offending parties should be held accountable.

      What this means in terms of TFA is that if an engineer inputs bad/incomplete data to a CAD system and the result is a bridge that is not suited for the location that it is actually being built for, then the fault is with the person using the program and not that of the developer. If, on the other hand, the user inputs all the data and it is all correct but the program outputs a bad design, then the software maker has some responsibility (though the users have a responsibility to check the output too).

      if the car has a speedometer that goes to 140 mph, can the driver assume that the car can be driven at that speed?

      When there are contradicting variables (speed limit, driver skill, weather, visibility, etc..), no and it's the driver's responsibility if they do so.

      If you want to take it to a safe location (track) to try to do that, then more power to you and it's mostly on your own head.

      Porsche isn't responsible for someone taking their 991 GT3 out to the track, misjudging their apex, and running into the wall. They are, however, responsible for a design flaw that caused some engines to catch fire while being appropriately operated in normal driving conditions.

      if the owner of a car knows full well that their ignition switch is acting strange and they keep driving the car anyway, are they responsible for the resulting deaths?

      If you know something is dangerous and do not take measures to address it (fixing it yourself, not driving it, etc..), then yes you are 100% responsible for your actions and the results. I know the engine in one of my cars has a couple of design flaws that can lead to a catastrophic engine failure in a measurable percentage of cars. I also know that the manufacturer failed to acknowledge the issue and address it. I am also aware that there are now after market solutions that address most of these problems. Finally I am also aware that it is fully on my head that I continue to drive the car with the risk of losing my engine because I currently opt not to proactively address the items at this time.

      The problem with this particular argument which you fail to grasp is that while GM knew of the problem for a long time, they made light of it at best (telling people not to use a keychain) and actively hid it at worst (never issuing a recall or warning to owners, you only got the keychain response IF it had failed and you complained). I also believe that even in those cases where people experienced the failure and got the keychain BS, they weren't informed that their airbag was being disabled at the same time. If that is indeed the case, then GM is doubly responsible as it not only told them not using a keychain solved the problem, but it also implied that the vehicle was otherwise safe and operating as expected (the average person does not understand that the airbag is tied to the ignition).

    15. Re:There I fixed it for you... by Krishnoid · · Score: 2

      Or, alternatively, the author of the article has a similar ethical obligation that the readers reach the same conclusion as the author.

    16. Re:There I fixed it for you... by oh_my_080980980 · · Score: 0

      You do realize it doesn't work that way.

    17. Re:There I fixed it for you... by oh_my_080980980 · · Score: 1

      Wait...developers inform and train users??? Are you fucking kidding me. You can't even get them to write coherent documentation. Inform and train users my ass.

    18. Re:There I fixed it for you... by iamhassi · · Score: 2

      Who? Rado Kotorov is just trolling, who cares what he says, not like he's a judge or senator that can make a difference. So tired of "omg look this guy that doesn't matter said this thing on a blog, we should all care!"

      --
      my karma will be here long after I'm gone
    19. Re:There I fixed it for you... by oh_my_080980980 · · Score: 1

      They don't chose to drive a car with a faulty ignition system either http://www.nytimes.com/2015/05....

    20. Re:There I fixed it for you... by Pseudonym+Authority · · Score: 1

      Because a strawman can't fight back.

    21. Re:There I fixed it for you... by Anonymous Coward · · Score: 0

      Were you born this stupid, or did it take practice?

    22. Re:There I fixed it for you... by gnasher719 · · Score: 1

      Yep, to this day, I"m still amazed that we have to have warning tags on hair blow dryers, that not only have it in print, but also with cartoon like diagrams warning you to NOT use the blow dryer while in the bathtub filled with water.

      I'm not amazed at all. People who put their pets into the microwave to dry them will complain to the microwave manufacturer. People who use a hair dryer in the bathtub filled with water don't complain afterwards.

    23. Re:There I fixed it for you... by Hognoxious · · Score: 1

      As a warning. Because if the UXtards aren't working on cars now, they soon will be.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    24. Re:There I fixed it for you... by Anonymous Coward · · Score: 0

      The point is that people use apps to make decisions. E.g. navigation apps to decide which way to drive, comparative shopping apps to decide where to buy something. In that case, the quality of the user's decision is limited by the quality of information provided by the app.

      If the app tells me that the quickest route from home to Auntie May's is to take New Road, and I trustingly navigate to New Road only to find that it's not actually open to traffic yet, then I've made a bad decision and wasted my time based on bad information. If there exists a way by which the app could have known that the road was not yet open, but the developers didn't bother to incorporate that function, then - yes, I'd say they're at least partly responsible for that waste. (On the other hand, if someone else fscked up - e.g. by failing to update the opening date in a database somewhere - then the devs are off the hook, it's the fault of whoever should have updated it but didn't.)

      Of course, "ethical obligation" means jack anyway. Good luck suing them on that basis.

    25. Re:There I fixed it for you... by Anonymous Coward · · Score: 0

      It absolutely does.

    26. Re:There I fixed it for you... by Gr8Apes · · Score: 1

      I'm assuming your next Yaris will come this way?

      --
      The cesspool just got a check and balance.
    27. Re:There I fixed it for you... by david_thornley · · Score: 1

      Also, doesn't that expose developers to user cooties?

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    28. Re:There I fixed it for you... by rjstanford · · Score: 1

      Because that paralleled the concepts in the article, as a way of pointing out that the UI decisions people make do in fact have a tendency to influence the behavior of the users of the products (physical or digital) that they create. People build things to suggest that a certain behavior or set of decisions is "normal", "obvious", "easy", and "correct" all the time, and some times doing that sloppily or incorrectly has serious consequences.

      --
      You're special forces then? That's great! I just love your olympics!
    29. Re:There I fixed it for you... by davester666 · · Score: 1

      So, we have to make bigger microwaves, so the person can get in there with their pet and they both can be dried at the same time.

      --
      Sleep your way to a whiter smile...date a dentist!
    30. Re:There I fixed it for you... by Anonymous Coward · · Score: 0

      Yep, to this day, I"m still amazed that we have to have warning tags on hair blow dryers, that not only have it in print, but also with cartoon like diagrams warning you to NOT use the blow dryer while in the bathtub filled with water.

      Do not be alarmed, you probably just live in a dumdum area of the planet. I've never even seen a hair drier with a warning label. Perhaps on the packaging?

  2. App appers app apps that other appers app! by Anonymous Coward · · Score: 0

    Apps!

  3. Just Be Professional About It. by Anonymous Coward · · Score: 0

    Everyone is on the same team, working towards ensuring the company is successful and profitable. Anyone who wants to sit back and say, "It's Not My Fault", needs to be removed.

    1. Re: Just Be Professional About It. by Anonymous Coward · · Score: 3, Insightful

      Thinking that is why you will never make it to the ranks of upper management. Upper management knows it's all about building their own personal fiefdom and nothing else. That's why upper management thinks techies are idiots and vice versa. Our goals are 180 degrees from each other.

    2. Re:Just Be Professional About It. by Anonymous Coward · · Score: 0

      Anyone who wants to sit back and say, "It's Not My Fault", needs to be removed.

      So upper management and executives, gotcha. Gotta warn you though, they're skittish little critters, first sign of trouble and they're out the door clutching their golden parachute.

  4. So then by fustakrakich · · Score: 1

    I can sue Ford if I get run down by one?

    --
    “He’s not deformed, he’s just drunk!”
    1. Re:So then by Anonymous Coward · · Score: 5, Insightful

      No, but if Ford put a turn signal in a non-standard place or labeled the signal 'apparatus for signifying intention to create a curve' it would definitely confuse and possibly lead to accidents. Or if the factory tires weren't tested and fell off after 1 day, then your analogy would work.

    2. Re:So then by fustakrakich · · Score: 1

      No, but if Ford put a turn signal in a non-standard place or labeled the signal 'apparatus for signifying intention to create a curve' it would definitely confuse and possibly lead to accidents.

      Well, yes, that is assuming previous experience with a 'standard' car. A neophyte wouldn't know the difference. And besides, I don't believe we are talking about 'accidents' here. This is somebody doing something intentional, and somebody out there is trying to blame the tools and their makers just because they facilitate the 'crime', another variation of a very old argument, and it doesn't stick any more now than it ever did. Or I can put it another way. Do we hold Ford responsible for making my getaway car?

      --
      “He’s not deformed, he’s just drunk!”
    3. Re:So then by FranTaylor · · Score: 1

      Well, yes, that is assuming previous experience with a 'standard' car. A neophyte wouldn't know the difference.

      in most civilized countries you have to take driver's education class in a normal car before you can get your driver's license, so these people you speak of will not have driver's licenses

    4. Re:So then by fustakrakich · · Score: 1

      Key word: normal car. They are reasonably standardized. If that is all that is being called for from the developers, fine. But if the user does something 'bad' with the program, it is not the developer's fault. The original question is, How responsible are app developers for the decisions the user makes? (easy, short answer; 0, zilch, not at all) It is not asking if the apps fail, crash your computer, or erase your drive by accident.

      --
      “He’s not deformed, he’s just drunk!”
    5. Re:So then by david_thornley · · Score: 1

      Have you noticed that, in any Slashdot article that mentions C++, there will be several arguments (not all well-informed) about whether the language is instrumental in causing bugs, or whether they can be avoided by proper use. Do you tend towards the camp that says that C++ can be used safely?

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    6. Re:So then by fustakrakich · · Score: 1

      Do you tend towards the camp that says that C++ can be used safely?

      A nuclear bomb can be used safely, anything can.

      --
      “He’s not deformed, he’s just drunk!”
  5. an ethical obligation by royallthefourth · · Score: 2

    In the real world "an ethical obligation" is no obligation at all. Nice circlejerk of an article, though.

    1. Re:an ethical obligation by Anonymous Coward · · Score: 0

      Of course there are consequences to going around ignoring what other people consider to be 'ethical' and throwing homophobic slurs at people.

    2. Re:an ethical obligation by ShanghaiBill · · Score: 1

      In the real world "an ethical obligation" is no obligation at all.

      That is not necessarily true. If you sell a product to the public, and it harms someone, you can still be held responsible even if you followed all legal requirements, if a plaintiff can show that you failed to follow common best practices, or made a design decision that was different than what most conscientious engineers would do.

    3. Re:an ethical obligation by FranTaylor · · Score: 2

      In the real world "an ethical obligation" is no obligation at all.

      That is not necessarily true. If you sell a product to the public, and it harms someone, you can still be held responsible even if you followed all legal requirements, if a plaintiff can show that you failed to follow common best practices, or made a design decision that was different than what most conscientious engineers would do.

      my guess is that he's a cop

    4. Re:an ethical obligation by oh_my_080980980 · · Score: 1

      So you're saying the developer isn't responsible for making sure the data presented to the user is "accurate” and “data complete.” Nice.

  6. Usability 101 by Anonymous Coward · · Score: 5, Insightful

    Jeesh. Why is this even a question?

    Anyone who has ever done any reading on usability knows that we need to craft the interface to the user.

    That usually means different interfaces for different cultures.

    For example, Japan and Germany have general populations that are far more used to multi-choice, complex UIs than the US and UK. They tend to prefer their UX to be a bit more technical than other cultures.

    Engineers tend to design for themselves; not for others.

    Read The Design of Everyday Things. It's quite life-changing.

    1. Re:Usability 101 by NotDrWho · · Score: 0

      That must be why every Japanese videogame is on-rails and looks like every other Japanese videogame, because the Japanese are so used to choices.

      --
      SJW's don't eliminate discrimination. They just expropriate it for themselves.
    2. Re:Usability 101 by Anonymous Coward · · Score: 1

      Who cares about videogames? I suspect they use templates.

      Try some of the apps they use for other stuff.

      There's some very neat, very geeky stuff out there that I (as an engineer) like, but most folks don't.

      However, it ain't just those cultures. That was just a strawman.

      Here's a very cool app, designed by a brilliant chap.

      It's a well-done, awesome app that most folks wouldn't even be able to begin to use.

      It's not designed for them. That's fine. However, there's lots of apps with similar complexity that are designed for regular mensch, and that have a similar level of complexity.

    3. Re:Usability 101 by JaredOfEuropa · · Score: 2

      Engineers tend to design for themselves; not for others

      Some engineers design for Satan. Ever used SAP?

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    4. Re:Usability 101 by Anonymous Coward · · Score: 0

      :)

      Satan's App Punishment?

      That's a German company, right?

    5. Re:Usability 101 by Anonymous Coward · · Score: 0

      Just like any engineer, you completely missed the obvious point. Empirical evidence shows that the general population of Japan is the opposite of what you, or rater the reading material, suggests. Just because "some of the apps they use for other stuff" is different does not change the population. Some of the apps they use for specific other stuff is a terribly biased sample. You could use the exact same sampling method on the American population and come up with the exact same answer. Some of the apps some Americans use for stuff that is not simple is, in fact, very complex. Therefore all of the American population is used to complex multi-choice UI.

      The original point about the Japanese general population is patently, empirically wrong. Now that it has been covered. What is the ideal UI complexity? Obviously the referenced work is wrong.

    6. Re:Usability 101 by WarJolt · · Score: 2

      Engineers tend to design for themselves; not for others.

      Engineers tend to design to the specification, which ideally should be designed by an HCI expert. They design for themselves because the specification is sorely lacking.

    7. Re:Usability 101 by Anonymous Coward · · Score: 1

      So, how often are you in Japan?

      I've been traveling there for twenty years, and designing software for dozens of different cultures. Some, in concert with marketing organizations that have taken a stubbornly monocultural approach to their software.

      Not all of it successful, either. LOTS of mistakes.

      I've actually had most of the arrogance knocked out of me by falling on my face. A LOT.

      "Good judgment comes from experience. Experience comes from bad judgment."

    8. Re:Usability 101 by Anonymous Coward · · Score: 0

      I care about videogames

    9. Re:Usability 101 by avandesande · · Score: 1

      That's what I thought about the article too. It's not an issue if there are good requirements, unfortunately we are usually trying to cobble something together that makes sense by channeling a customer's insane wishes.

      --
      love is just extroverted narcissism
  7. Rado Kotorov, Chief Innovation Officer at Informat by Anonymous Coward · · Score: 0

    "Rado Kotorov, Chief Innovation Officer at Information Builders"

    Who? That pretty much sums it up. "Chief Innovation Officer"? Give me a break.

  8. Bullshit. Pure. Simple. Bullshit. by Anonymous Coward · · Score: 5, Insightful

    "In a blog post, Rado Kotorov, Chief Innovation Officer at Information Builders asserts that the creators of enterprise apps implicitly assume some of the responsibility for other people's decision making. He says it's not just developers, but anyone who is involved, from defining the concept, to requirements gathering, to final implementation. Thus, the creators of the app have an ethical obligation to ensure that people can reach the right conclusions from the facts and the way they are presented in the app."

    I call bullshit. This is simply another step down a slippery slope that removes more personal responsibility.

    This is the very definition of the nanny State.

    1. Re:Bullshit. Pure. Simple. Bullshit. by Shoten · · Score: 5, Informative

      "In a blog post, Rado Kotorov, Chief Innovation Officer at Information Builders asserts that the creators of enterprise apps implicitly assume some of the responsibility for other people's decision making. He says it's not just developers, but anyone who is involved, from defining the concept, to requirements gathering, to final implementation. Thus, the creators of the app have an ethical obligation to ensure that people can reach the right conclusions from the facts and the way they are presented in the app."

      I call bullshit. This is simply another step down a slippery slope that removes more personal responsibility.

      This is the very definition of the nanny State.

      RTFA.

      If you look at the article, you'll see just how blatantly Slashdot has mislead us with their summary of the article. The article isn't about "apps" or even just "enterprise apps." It's specifically and only about business intelligence (BI) applications, which are intended to lead their users to make decisions and conclusions. What he's saying, fundamentally, is that "as the makers of business intelligence applications, we have a responsibility to actually not make apps that suck, since the conclusions our users will come to have major ramifications." I agree with him, in that context.

      Take it and apply it to a specific situation like cancer research, and the difference between meeting his ethical standard and failing it is the difference between saving lives or losing them. And this is actually a real example; recent cancer research has largely focused upon big-data mining and BI around specific characteristics of various forms of cancer, and matching up with an incredible degree of precision which combinations of treatments work best on certain kinds of cancer. They go so far as to actually examine the genome of tumors...it's fucking cool. This is the kind of use that a BI system can fulfill, if it works. But if it doesn't work, everyone can go down a bunch of rabbit holes and it takes years to figure out that they've been chasing the wrong approaches all along.

      --

      For your security, this post has been encrypted with ROT-13, twice.
    2. Re:Bullshit. Pure. Simple. Bullshit. by Krishnoid · · Score: 1

      But if it doesn't work, everyone can go down a bunch of rabbit holes and it takes years to figure out that they've been chasing the wrong approaches all along.

      1. Come up with a thousand approaches to a problem
      2. Crowdsource incorrect approaches
      3. Simultaneously discover 999 things that don't work
      4. Success!
    3. Re:Bullshit. Pure. Simple. Bullshit. by Kjella · · Score: 3, Insightful

      I call bullshit. This is simply another step down a slippery slope that removes more personal responsibility. This is the very definition of the nanny State.

      Well, the article is just a fluff piece saying that how you build the interface affects the results and that this can have consequences. Which is actually not such an unreasonable thing to say, as long as you don't take the concept too far. For one concrete example I know of from a hospital system, the software said pretty much "Nothing more to register so closing healthcare contact" when it actually meant to say "Warning, hospital visit registered but no further patient follow-ups scheduled. If you proceed the patient's treatment will end and case will be closed."

      This was in production code found in a review trying to find how the hospital could "lose" patients. The message was technically correct, but it was also extremely misleading when the nurse had forgot to register a follow-up. One seemingly harmless confirmation and the patient could end up not getting chemo for their cancer unless the doctor noticed the patient was missing or the patient followed up himself. So the developers of the system should absolutely take some responsibility for making sure the system makes it easy to do the right thing and very hard to do the wrong thing, not just technically correct.

      Another much hotly debated topic is defaults, because people have a tendency to overuse defaults. The problem is when 99.9% are the default but the 0.1% is actually important to register. Did you skip past the point with allergies when the patient actually is hyperallergic to peanuts? Ouch. People are not machines, they hate doing things that are 99.9% unnecessary even if you tell them that you checking that box is their proof that you remembered to ask the patient and a default won't do that. Like security, completeness and correctness often comes at a cost in usability too. It all depends on what matters more.

      --
      Live today, because you never know what tomorrow brings
    4. Re:Bullshit. Pure. Simple. Bullshit. by paulpach · · Score: 1

      ... the system makes it easy to do the right thing and very hard to do the wrong thing, not just technically correct.

      This is an obvious thing to strive for, and something most developers aim for regardless of legal or ethical frameworks.
      But hindsight is 20/20, I bet that in your example, it did not even occur to the developer that the message could be misleading. Any software is going to have stuff like that, and you just have to do usability testing from time to time to find these usability bugs (I would call this a bug, but you can call it whatever you like).

      There is a slippery slope in the "take some responsibility" language. Does it mean that the developer is bound to fix bugs (usability bugs or otherwise) for ever even if he is not paid for it? Does it mean that the developer is legally liable for any damage the bug might have caused and can be sued? What if the developer released free software with a defect and it causes damage to someone? What exactly does "take responsibility" mean to you?

      The solution to this is simple: put it in the contract. In your example, the developer and hospital owners should have engaged in a voluntary agreement before the work started and clearly state what each party had to do in the case of a bug like this. Typically, the hospital would have agreed to pay him some money for ongoing maintenance, and in exchange he would commit to resolve these kinds of issues within some reasonable time. The extent of his responsibility would be defined by the agreement (contract) and nothing else. If the hospital decided to go cheap and don't pay for maintenance (or for example got a free license), then the developer would have no responsibility whatsoever over the problem, and it would be nothing more than a personal preference whether he chooses to resolve it.

    5. Re:Bullshit. Pure. Simple. Bullshit. by tomhath · · Score: 1

      Suppose your application says "20% of Americans can't find the United States on a map of the world.

      You really should help the user understand what that means:
      20% of Americans are too stupid to find the US on a map
      20% didn't speak English well enough to understand the question
      20% of the sample were infants, blind or otherwise had no chance of reading a map

    6. Re:Bullshit. Pure. Simple. Bullshit. by Hognoxious · · Score: 1

      If that's what he's saying then it doesn't need to be said, so why is he saying it?

      Coming up after the break, how inaccurate rulers mean that shit won't fit.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    7. Re:Bullshit. Pure. Simple. Bullshit. by Shoten · · Score: 1

      But if it doesn't work, everyone can go down a bunch of rabbit holes and it takes years to figure out that they've been chasing the wrong approaches all along.

      1. Come up with a thousand approaches to a problem
      2. Crowdsource incorrect approaches
      3. Simultaneously discover 999 things that don't work
      4. Success!

      Come up with a thousand approaches to a problem.
      Try all of them at once.
      Discover that you just broke your statistically-valid group that has the problem into a thousand groups so small that you can no longer detect the difference between success and failure for any one group.
      Also realize that you just doomed 99.9% of the total test population to failure...and in my example, these are cancer patients, so you also just got yourself barred from practicing medicine. What are you, Dr. Mengele?
      Fail!

      --

      For your security, this post has been encrypted with ROT-13, twice.
    8. Re:Bullshit. Pure. Simple. Bullshit. by Shoten · · Score: 1

      If that's what he's saying then it doesn't need to be said, so why is he saying it?

      Coming up after the break, how inaccurate rulers mean that shit won't fit.

      I asked myself that same question, but I think there's an answer. If you write a version of Angry Birds that sucks, then meh...some people waste a buck each on a crappy game, give it a bad review, and life goes on. If (as actually happened) you radically change the UI on a ubiquitous application *cough*Microsoft Word*cough* then it frustrates a lot of people and wastes a lot of time, but still not necessarily the end of the world. But BI apps drive decision making at a scale that boggles the mind. Things like epidemiology (containing Ebola in West Africa, or trying to reduce HIV infection rates), cancer research (listed up above, and from personal recent experience I can tell you, they're doing some incredible fucking stuff with this), and even decisions that impact negotiations between nation-states all rely upon BI. Because of the cost of the solutions and the effort needed to implement them, no decision they support is really small; nearly all of them have massive impact and thus huge ramifications if the BI solutions drive people in the wrong direction. So while he didn't quite say it this way, I think the point is that BI apps bear a greater moral burden to be effective than most apps because of the impact (good or bad) that they have.

      What I wonder about is why he didn't touch upon the other moral issue of BI: usage. One of the first big BI implementations was in Germany, for example. It was used to do number-crunching to manage and provide efficiency of scale for their overall program of concentration camps. (And no, this isn't Godwin's Law in effect...I'm not comparing anyone to Hitler, just raising an interesting historical fact.) IBM designed, built, and supported the solution...this was far, far beyond just making an app that someone else bought and did something bad with, without direct involvement by the app's creator. BI solutions aren't "buy it, install it, use it" products; they need a metric assload of support and consulting services to get them off the ground, and they are purpose-built to the customer's needs. So what are the ethics around what the customer intends to do, and where do you draw the line and say "No, I'm not going to sell you my product or services to help you do that"?

      --

      For your security, this post has been encrypted with ROT-13, twice.
    9. Re:Bullshit. Pure. Simple. Bullshit. by Hognoxious · · Score: 1

      I get what you're saying. But is BI different to stuff that controls whizzy bangy things? Or is it really the general case where the bigger the consequences of it being wrong, the less likely to be wrong it should be; that's common sense, isn't it?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  9. Waste of money by Dog-Cow · · Score: 1

    Information Builders is not getting their money's worth out of this idiot.

    Thus, the creators of the app have an ethical obligation to ensure that people can reach the right conclusions from the facts and the way they are presented in the app.

    Who decides what the right conclusion is? Why waste time and money creating an app if you already know the "right" conclusion; just send it to all employees via a one-time email.

    1. Re:Waste of money by oh_my_080980980 · · Score: 1

      RTFA: "The two basic questions to ask are, “is the data accurate?” and “is the data complete?” "

  10. Philosophy by Translation+Error · · Score: 2

    From a philosophical or pure cause and effect approach, sure, the makers of an app have some responsibility for the effect it has on people and what they do as a result. From a legal/liability standpoint, generally not.

    The article writer is just saying to keep in mind that how your app behaves, how it looks, how it presents data, can have a real effect on its users, so you should consider the implications of your decisions.

    --
    When someone says, "Any fool can see ..." they're usually exactly right.
    1. Re:Philosophy by MtHuurne · · Score: 1

      The more I think about the article, the less sense it makes.

      Data accuracy and completeness are of course important issues, but if you're going to add measures to improve data quality, that should be done when acquiring and processing the data, not when presenting it. So an app sounds like the wrong place to start worrying about the integrity of the data.

      Doing statistics properly is not easy: it's not an intuitive subject and it requires a good mathematical background, a lot of care and some common sense. Here at least the article has a concrete proposal: a review and sign off process. Whether that actually helps depends on the quality of the review: does the reviewer master statistics and is there enough time budgetted to do a thorough review?

      I have some doubts about painting data presentation as an ethical issue. While I completely agree that clarity is more important than prettyness, overly flashy presentation is far from the only reason why data might be misinterpreted. Perhaps the app developer doesn't understand the domain well enough; hands-on testing with end users would help in that case. Perhaps the end user doesn't understand the data or the processes the data comes from well enough to be able to interpret it accurately no matter how the app presents it. Perhaps the data is so complex that it is not possible to present it accurately in an app format.

    2. Re:Philosophy by Anonymous Coward · · Score: 0

      "Some" is very vague. Though it must be vague. If you make an app for which the obvious primary use case is something illegal, I don't think you can say "user's fault, not mine" and absolve yourself of all responsibility. But if you make something that has legitimate uses, and users do something harmful with it, those users can't say "well they made this thing, so what I did with it is their fault."

      This applies to all inventions, software or otherwise.

      Inventing nuclear power doesn't make the scientist responsible for all the people who died via atomic bombs. Building atomic bombs with the intent of protecting innocent people is not the same thing as choosing to drop those bombs on innocent people. On the other hand, engineering a chemical or viral weapon that has no scientific or economic value apart from causing horrible, agonizing death is pretty hard to justify on "protect the innocent" logic.

      When we invent warp drive, the utility of being able to travel to other planets justifies it, even if some evil people use it to destroy a few planets or planetary systems.

    3. Re:Philosophy by oh_my_080980980 · · Score: 1

      If you don't think UI doesn't matter, you've been huffing glue. And the information presented to the user matter in that you better damn well be sure you are presenting the correct information that the user requested, something that is within the control of the developer. The actual data, no, but the information requested and the its' presentation, yes.

      It's not rocket science but its clear people failed basic reading comprehension skills and focused on a single word "ethical" and got their panties in a twist. Sack up ladies and learn to read.

  11. Honesty by penguinoid · · Score: 2

    If the description of the app were "this is buggy adware that crashes all the time and steals all your personal info and can barely fulfill its nominal function" then more people would be able to reach the right conclusions.

    --
    Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
    1. Re:Honesty by FranTaylor · · Score: 1

      so you assert that the old adage "let the buyer beware" doesn't apply to software?

      you sound like the the police captain in casablanca, "I am shocked, shocked to see anything less than perfect bug free products"

    2. Re:Honesty by david_thornley · · Score: 1

      The old adage "let the buyer beware" doesn't apply in lots of areas. Lying about a product in order to sell it is normally illegal. Mislabeling a product is normally illegal. There are often warranties, either legally required or used as selling points, and those have to be honored.

      The legal system doesn't care what you pay for something or what you buy, as long as you're a competent adult. It does care that you have the ability to know what you're buying.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  12. Article heading by Anonymous Coward · · Score: 0

    "How Responsible Are government officials For Decisions The people Make?"

    Honestly, why would anyone be held more accountable for the result of their actions than government officials? App developers are slightly more important in a society than toy-makers, and yet we have these articles.

    1. Re:Article heading by Hognoxious · · Score: 1

      App developers are slightly more important in a society than toy-makers

      There's a considerable degree of overlap.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  13. For you wondering what he "right conclusions" are by NotDrWho · · Score: 1

    They're the conclusions that *I* have come to!

    --
    SJW's don't eliminate discrimination. They just expropriate it for themselves.
  14. foolish assertion Rado by Anonymous Coward · · Score: 0

    People who are too far up-front of the chain will not encounter the situations that develop down the line and can not possibly foresee the many business requirements that the users of the software will face.

    Second, attempts to 'control' the facts much like big media in America are really going to piss off users! The tool should stick to the facts as they are and not try to spin them.

  15. Summary is Misleading by captnjohnny1618 · · Score: 2

    First off, I think what the author is claiming is bullshit. He's just reiterating stuff that we already have laws and protections for. We don't need a new bank of BS intellectual property laws, or CEO protection laws to throw at developers when the first thing doesn't go correctly.

    Now on to my main point:

    The summary makes it sound like the author was talking about ALL apps and app developers, however after reading the article, it's clear that he's referring to business analytics and applications that people would use to gather data and make business decisions. There is a little bit of language that makes it sound like he might secretly wish that it applied to all app developers, but that's not really the takeaway from the article.

    His claims are still completely moronic: if an app pretends to offer a service and then can't deliver, or provides data that leads to bad decisions, then (1) people will stop using it once this is discovered and (2) we have consumer protection laws if it is found that the developers did this intentionally and then deliberately misrepresented what they had to offer, would protect the people they screwed.

    This isn't a question of "apps" or "applications" or "data," this is an old idea that has been around for literally ages and someone wrote an article while masturbating to the words "big data," "analytics," and "apps."

    What scares me is that idiot politicians and business majors will see this and think "hey, yeah! I don't have to be responsible for bad business decisions in a new way!" Fucking idiots. How much lower can we go on the idiot totem pole?

    1. Re:Summary is Misleading by Anonymous Coward · · Score: 0

      Everyone's so quick to call "moron" on Slashdot. His main point is completely valid. Take the UK election, we had exit polls predicting 315 seats for the Tory party. That's 25 more than anyone predicted in the pre-election polls. But we just had that one number - 315. In fact the margin of error must have been at least +/-20, because the final number was 329 which was *way* more than anyone predicted earlier. But from the exit poll it could have been as low as 295. The consequences of these two numbers may not be clear - with 295, there would have been no clear majority in the house, and a coalition would have had to be formed. With 329, there is a clear majority in the house. So the margin of error in the exit poll was large enough that you simply could not predict who would form the next government. And yet, with no margin of error given, the news coverage repeatedly and obnoxiously called the entire election while the votes were still being counted, based on an exit poll that as far as the viewers knew was supposed to be *exact*, because no margin of error was given. And the errors happened to fall the "right" way, so the coverage is apparently vindicated after the fact. Ugh.

      OK so that makes for poor news coverage, big deal, but a similar situation in a business analytics app could be catastrophic. If you get a number which suggests situation B, but the actual data including margins of errors means that actually situations A, B and C are equally likely ... so you plump for action [B] thinking it has 100% chance of success, when really it only has 33% chance of success. That's not what you want, and you might well assume that the app developer is going to be clued up enough to not let you do this. Caveat emptor; this guy is obviously saying "our business is on top of this issue, so buy our stuff".

      How you get from these simple facts to calling people morons and talking about an idiot totem pole is beyond me. Often, thinking harder about a subject helps.

    2. Re:Summary is Misleading by captnjohnny1618 · · Score: 1

      You're right: we are too quick to call moron on Slashdot. If you can believe it I was even more fired up prior to reading the actual article!

      I get frustrated when people try to impose more restrictions and laws on folks and to me, this seems like one of those situations. The author also seems like someone who knows a lot of buzz words about the development field, but has done little to no development himself (see http://www.informationbuilders...), and it drives me INSANE when people like that want to start coming after my field. He's probably not a moron, but I did find his article moronic.

      I completely agree with everything that you wrote. Full stop.

      To clarify my point a bit, I'm a strong believer that the user/purchaser needs to fully understand the limitations of the product they purchase. In your second example, the app developer misrepresented the accuracy of their predictions: I 100% agree that in this situation, they are the responsible party. This is not something that we need "app" or "data" specific laws for. I'm pretty sure they offered a product and lied about what it could do.

      To put new laws on the books that app developers are somehow responsible for what people choose to do with their apps (as the summary indicates and to a lesser extent, the article) is pushing into a weird and I feel dangerous place legally for developers.

      If I order an uber using the uber app and get that uber to take me to a bank and tell them to wait outside, and then I go in a rob the bank and come back out without the uber ever knowing what happened, does that make him my getaway driver and uber an accomplice to my robbery because I used an app? No! That's absurd! I don't have enough faith that they can craft a law expressing developer accountability over their apps that we wouldn't run into some absurd situations like this and make the environment a little riskier for developers.

      Should we hold Blizzard responsible for lost wages, poor health, etc. that develop as a result of overindulging in WoW? Why would we let cigarette, fast food, soda, alcohol, guns, etc. all get away with the "caveat emptor" argument and not apps?

      THAT is why I think this point is moronic.

    3. Re:Summary is Misleading by Anonymous Coward · · Score: 0

      The point isn't moronic from his employer's point of view.

      What's the barrier to entry for software? Approximately zero.
      What do big companies want to do? Raise the barriers to entry.

      If you are now legality responsible for the idiocy of your users you will need a phalanx of lawyers. Instant barrier to entry, competition averted!
       

    4. Re:Summary is Misleading by Qzukk · · Score: 1

      if an app pretends to offer a service and then can't deliver, or provides data that leads to bad decisions

      It's more than that. How about an app that offers the ability for a doctor to purge the record of a certain bad decision? How about a financial app that allows double bookkeeping, if someone was so inclined to hide their embezzlement? How about a default password of 12345, after all it's the user's responsibility to fix it?

      There are plenty of ways to make apps that do the wrong thing, correctly.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
  16. Re:Philophantasy by tiberus · · Score: 2

    Yet the only way I can imagine meeting that goal is to have a self-aware AI that can in real time (actually it might have to be prescient) determine the users thought process so that it can morph the UI into a state that will present the information to the user in a manner that will lead them to the right conclusion. We can now move on to a discussion of perception and truth.

  17. Replace by Anonymous Coward · · Score: 0

    Replace developers with "article writers" and see if you, the writer of this article, still agree. I can hear "free speech!" piercing my eardrums right about now.

  18. App developers aren't special by mwvdlee · · Score: 1

    App developers aren't some special magical people that have extraordinary powers to influence users.
    They have a moral responsibility not less or more than that of a store clerk, a fashionmodel, a garbage collector or pretty much everyone else.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    1. Re:App developers aren't special by oh_my_080980980 · · Score: 1

      And the author isn't saying that. He's saying that the developer knows what the fuck he is doing and not some drooling moron who doesn't give a flying fig if the information presented to the user is accurate and complete.

  19. Visual effects by Fortran+IV · · Score: 4, Insightful
    From TFA:

    The goal is absolute clarity and lack of ambiguity so that decisions can be made quickly. Visual effects can obscure the facts and misrepresent proportions and ratios, thus leading to incorrect conclusions.

    Of course! That's why every damn application I use these days has its own "skins" and its own custom layout. Using a standard, familiar window layout would allow me to actually get some work done without having to search for the menus and buttons. Can't have that, can we?

    --
    I figure by 2030 or so my 6-digit UID will be something to brag about.
    1. Re:Visual effects by Anonymous Coward · · Score: 0

      Skins. Emojis. That's what sells apps. Their core function? Nobody cares.

  20. Author's bio show how seriously to consider his... by captnjohnny1618 · · Score: 1

    ... opinion.

    Just walk away everyone. Nothing to see here. (Taken from: http://www.informationbuilders...)

    "Dr. Rado Kotorov is vice president of Product Marketing for Information Builders and works both with the Business Intelligence and the iWay product divisions to provide thought leadership, analyze market and technology trends, aid in the development of innovative product roadmaps, and create rich programs to drive adoption of BI, analytics, data integrity, and integration technologies. He strives to make BI and business analytics more accessible, intuitive, and collaborative through the adoption of innovative Web 2.0, advanced visualization, predictive modeling, search, and mobile technologies. Prior to his current role, Dr. Kotorov, was executive director of Strategic Product Management and Competitive Strategy. Active Technologies, InfoAssist, Magnify, RStat, Enable, Mobile Favorites, and the BI Portal are just a few of the products that have been developed and launched by his team."

    "Dr. Rado Kotorov has a Ph.D. in Decision and Game Theory, and institutional economics from Bowling Green State University. He has also published various papers and articles on business processes, emerging technologies, intellectual property rights, CRM, KM, innovation, and entrepreneurship."

  21. What a Load of Crap by l0ungeb0y · · Score: 1

    If you are a Decision Maker you are the sole person with any ethical responsibility regarding the decisions you make. You, as a user are the sole party responsible for ensuring the completeness and accuracy of the Data Sets provided and to ensure that you understand how the software you use for your job works. Anyone who does not act on their own to proof their Data Sets and to completely understand how their Software works is acting negligently and is the sole party responsible for any issues that arise. It is not up to the Developer to do anything more than provide Software that produces output that is as accurate as possible. To demand they somehow be psychic, to know what the user thinks or do anything more than simply provide a tool for people to use is disingenuous and smacks as an attempt to allow incompetent managers to shed personal responsibility and blame others for their own failings.

    1. Re:What a Load of Crap by Anonymous Coward · · Score: 0

      That's simply not true. Put simply, your model of this assumes that, as you go higher up the corporate ladder, people's brains double in size. But they don't. Therefore, anyone near the top has to delegate responsibility for some things. This is a simple mathematical fact. Unfortunately it is completely at odds with your dogmatic views on decision making, which I suspect are received rather than internally generated. I suggest reading some decision theory. It's no coincidence that the author has a PhD in that.

    2. Re:What a Load of Crap by captnjohnny1618 · · Score: 1

      Then wouldn't that make the person to whom you delegated the task responsible for understanding the extent and limitations of the software? So long as the developer did not intentionally misrepresent or withhold information about what their software could and could not do, why should they be the ones held responsible?

    3. Re:What a Load of Crap by oh_my_080980980 · · Score: 1

      "So long as the developer did not intentionally misrepresent or withhold information"

      Which is exactly what he said. RTFA. His only point was making sure the information provided to the user was accurate and complete. He did not say the developer was responsible for the data.

    4. Re:What a Load of Crap by david_thornley · · Score: 1

      The decision maker has responsibility for the decision, and this includes selecting people and software to gather information and project the future. This doesn't mean that nobody else has responsibility. The decision maker isn't going to proof the data sets, audit the reports, and debug the software, but has to trust other people to do their jobs. Everybody who has input into the process has responsibilities involving their own job.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  22. Decision-making apps by Anonymous Coward · · Score: 0

    They seem to focus on those apps that replace corporate drone brains. "My job is to do what the app tells me to do." So if the app tells you to fire your best customer because that's what its logic concluded, and you actually do it, who is responsible? Most likely your boss, who just yelled at you to stop bothering him and just do as the app says.

  23. Response from Edward Tufte by Anonymous Coward · · Score: 0
  24. Cloudy responsibility by userw014 · · Score: 1

    This is another way of saying that "everyone's responsible" (and therefore no-one's responsible.)

    Insuring that a tool (app) suits a business process (and vice versa) can be a non-trivial process - but is one that the business itself is ultimately responsible for.

  25. Re:Author's bio show how seriously to consider his by Anonymous Coward · · Score: 0

    It shows we should take it fairly seriously because he has a PhD in decision and game theory?

    What's your point? Do you have two PhDs in decision and game theory or something?

  26. Re:Philophantasy by FranTaylor · · Score: 1

    apparently software developers are stupid dolts incapable of actually doing their jobs and so we need AI systems to do their work for them

    who programs these AI systems again?

  27. tldr: User Interface Design is important by Anonymous Coward · · Score: 0

    What a stupid buzzword-article only to say that.

  28. Develop like you are... by Kwyj1b0 · · Score: 1

    ... but put in a EULA that you are not.

    I think application developers should try to design things as if they are driving the final users decisions - and in their own minds should feel like they are responsible for bad decisions. I have seen way too many apps that are slapped together by a code-monkeys who ignores to understand the importance of clarity (such as units and legends on a graph - "Put in a feature request, and we'll see if we can get it in the next sprint; it is not a critical bug."), or designs like a programmer ("I can just reuse the old UI if I treat X as Y"). Poorly designed documentation ("help is under Options which comes up if you swipe just so") with arbitrary changes to normal behavior and hidden nuggets ("everyone knows that Ctrl+C is copy, so let me disable the context menu and edit menu") are other problems.

    No one is suggesting that developers become legally responsible for users decisions. But it would sure help if creators designed their application expecting a child to make a decision using their app.

    1. Re:Develop like you are... by FranTaylor · · Score: 1

      people get what they pay for, if you pay crappy developers to write crappy code... if you sign a development contract that doesn't stipulate a working solution...

      if users are incapable of communicating their desires to developers then they can't really complain about what they get

      the onus of responsibility for a quality product lies in the consumer. there will always be snake oil salesmen selling snake oil, and it will always be up to the consumer to figure it out

  29. This is a dangerous path of thought by Anonymous Coward · · Score: 0

    About 20 years ago, when I got my Ph.D in computer science, Texas was defining a licensing for software engineering. The idea that there would be a certified profession. As my Ph.D. would have automatically qualified me for this, I considered it. And then considered not. The problem is that it would shift accountability to the professional software engineer for any issues. However, there would be extreme pressure from the business entities to dictate design decisions. A situation similar to when HMOs started to tell Physicians which procedures they could do based, not on medial needs, but financial needs. Of course, the doctors neck would be on the line. So, if you go down this path of thinking you suggest, you'll be asking to have accountability heaped upon your head for other peoples miss-deeds and then also be in an environment where your bosses (who rarely have much technical knowledge or skill) will be dictating how you design your software. I say no thanks.

  30. Does the inverse of this apply by MooseTick · · Score: 1

    Can I then say that an app led me to make bad decisions and I am no longer responsible?

    I'm sorry that I drank 2 bottles of whiskey and ran over that family of 4, judge. That free app I downloaded said it would be ok.

    1. Re:Does the inverse of this apply by FranTaylor · · Score: 1

      the bad decision was deciding to use the app in the first place, everything after that is ripple effect

  31. Just another reason... by captnjohnny1618 · · Score: 1

    Just another reason to GPL everything you create.

    1. Re:Just another reason... by Anonymous Coward · · Score: 0

      Anyone can say they aren't liable, no need to use a whole pre-written license.
      This is about forcing liability, thereby making that segment of the GPL (and other licenses) invalid.

    2. Re:Just another reason... by captnjohnny1618 · · Score: 1

      Which is precisely my fear of people saying stuff like that. And would be a play to hinder development of free software (e.g. some "security" company decides to use an open source project, finds a bug, claims it ruins their business, and then sues the developers into the ground only to then offer their product to everyone who previously was using the open source tool).

      At least for right now, the GPL holds up and I think if they tried to invalidate that claim, it would come to a free speech issue. "You're telling me I can't post my code? That's just how I talk and I'm expressing my opinions on an efficient means of running md5 hashes!" ;-)

    3. Re:Just another reason... by david_thornley · · Score: 1

      The right way to handle liability is to hold the end users liable for the damage they do to people, a step that's often skipped. If a company was fined for data leaks, or had automatic civil liability, or any other method to internalize costs normally fobbed off on the customers, the company would either take security seriously or go out of business. The company could buy insurance, but insurance companies price their insurance based on the likelihood of a bad thing happening. A company with good security might find the insurance cheap, and a company with bad security might find the insurance unaffordable. Insurance doesn't eliminate risk, but rather gives it a tangible cost.

      The company would be completely free to handle its own data security, using whatever software it wanted. Some software would doubtless come with some sort of warranty or indemnification, and there'd be no reason another company couldn't take something GPLed and sell it with a warranty; alternately, the original company could choose to use something GPLed with the understanding that there is no warranty, but figuring it was the best way for them to go.

      Assuming the original liability can be enforced, this would put liability more or less where it belongs, without affecting the "no warranty" status of most F/OSS.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  32. Oh my by DarkOx · · Score: 1

    Nobody can just own anything any more can they, nor can they accept we live in an imperfect world where mistakes happen.

    An app developer should do their best to provide users with concise, but complete, accurate, and timely information to the extent the technology allows. Perhaps developers/vendors have some responsibility to set realistic expectation about the quality of the information, but that is as far is can possibly go.

    Beyond that people/users just have to make decisions and bear the responsibility. If your counter terrorism intelligence app does face recognition and determines Jim on camera is really Oliver Public Enemy No.1, and Mr.Policeman shoots Jim, its Mr.Police man who is at fault unless your application was deliberately misleading or you mislead Mr. Policeman about the accuracy and confidence possibly with your app.

    --
    Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
  33. comment subject goes here by Falos · · Score: 1

    This is imaginary thoughtcrime again. Good luck prosecuting (sorry, "holding responsible") someone who's been long dead.

    The culprit obtained, kept, and operated the tool, device, machination, etc. that's pertinent. MAYBE the operator caused the events unknowingly, in cases where they were unaware of a strange or faulty capacity (the latter is pre-t-t-y hard to predict the first time), but that affects the measure of intent, which some areas of law are rational enough to outright forgive.

    What it doesn't affect is blame shifting up some abstract chain of causation leading from the inventor's guilty parents to the guilty Big Bang.

  34. 0% by Anonymous Coward · · Score: 0

    0%

  35. Hammer designers are not murderers by Anonymous Coward · · Score: 0

    If I design a tool like a hammer, and sell 100 of them and all 100 of them are used to build houses - but one of the builders also uses it to kill his wife - I am not a murderer. The killer is responsible for his actions. This is the rule of simple tools. However, this responsibility should change with regard to weapons development (I design a nuclear bomb and make it available to anyone and everyone) or creating AI systems and functionality. Asimov's three laws of robotics would be one way of responsibly addressing the AI issue.

  36. Unbelievable! by Anonymous Coward · · Score: 0

    It's hard to believe that this is controversial. The whole idea of applications is to make someone's job easier, not to booby-trap them. If you think your job is to crank out some piece of shit and get on with your life, you are in the wrong business.

  37. "Reasonably foreseeable abuse" doctrine by Anonymous Coward · · Score: 0

    From a legal/liability standpoint, generally not.

    If you're a lawyer, you suck miserably. In product liability cases, some jurisdictions allow the manufacturer to be held liable for "reasonably foreseeable misuse", e.g. use of a product that is not within the scope of what the product is defined to do but that nevertheless a normal user would commonly do. An example is a person standing on a chair to change a lightbulb; if the chair breaks while the person is standing on it and the person is injured, the manufacturer can not get away with saying "a chair is only for sitting in, not standing on, so we're not liable."

    What the article is talking about is basically the same thing, except for software.

    (I am not a lawyer and this is not legal advice.)

    1. Re:"Reasonably foreseeable abuse" doctrine by Anonymous Coward · · Score: 0

      From a legal/liability standpoint, generally not.

      If you're a lawyer, you suck miserably. In product liability cases, some jurisdictions allow the manufacturer to be held liable for "reasonably foreseeable misuse", e.g. use of a product that is not within the scope of what the product is defined to do but that nevertheless a normal user would commonly do. An example is a person standing on a chair to change a lightbulb; if the chair breaks while the person is standing on it and the person is injured, the manufacturer can not get away with saying "a chair is only for sitting in, not standing on, so we're not liable."

      What the article is talking about is basically the same thing, except for software.

      (I am not a lawyer and this is not legal advice.)

      Oh and, by the way, a reasonably good summary of how "reasonably foreseeable abuse" works can be found at: http://www.productliabilityprevention.com/images/DRI_Foreseeable_Spring_2009_KRoss_.pdf

  38. NO! Legal Definition. by DarthVain · · Score: 1

    OK, IMNAL... However we have all heard about:

    A) The definition of insanity is performing the exact same action multiple times but expecting different results, and
    B) The courts hold that if proven insane, they are not legally responsible for their actions.

    I manage several enterprise applications. I have personally seen users, incorrectly doing something which makes a mess out of data, then attempting to fix it using the exact same method, then doing it again, and again, and again, etc...

    Clearly if the user can't be held responsible because technically they are all insane, how can a developer be held accountable for some insane persons actions. Poppycock! If you start talking about the design and the requirements analysis, I will point out that users don't just start being insane when they start to use applications, that is their steady state of being. Requirements that are essentially mutually exclusive for example. A reasonable person would say that isn't rational. Anyway, at best we can care for them, and try to do our best to steer their drunken keyboard mashing into something that resembles productivity. However true responsibility for user actions? You must be a user (i.e. insane).

    1. Re:NO! Legal Definition. by FranTaylor · · Score: 1

      I have personally seen users, incorrectly doing something which makes a mess out of data, then attempting to fix it using the exact same method, then doing it again, and again, and again, etc...

      so when the instructions don't work, should the employees strike out on their own and start inventing stuff to do?

      if the server is down and the user tries five times to enter the data, is it insanity when they try the same thing again for the sixth time when the server is back up again?

  39. Re:Author's bio show how seriously to consider his by captnjohnny1618 · · Score: 1

    Ok. That's on me. Haha.

    I guess my point is, yes, we should consider his points comprising how folks look at data to make decisions. These are things that any good app developer knows (at least insofar as user interfaces are concerned) and anyone dabbling in the world of enterprise data analytics should ABSOLUTELY be familiar with.

    My point was that it sounds like may talk a lot about app development without ever building anything himself. It seems off-base to then turn around and say that app developers should be held responsible for what their customers are doing with their apps. It feels like a play to absolve the users of software from bad decisions or not understanding the product they purchased and/or are using.

    I've said it maybe three other times in these comments, so long as the app developer did not intentionally mislead or misrepresent their product (through misadvertising or withholding information), the responsibility lies with the user, not the developer.

  40. T his is nothing new by houghi · · Score: 1

    Adding "for apps" seems to be the new "on the Internet". Replace it "with cars" or "with tools" and then it becomes obvious that SOME precautions should be taken. e.g. you nake seatbelts that are not too hard to use. You add some safety on a chainsaw.

    You indicate what weight something can carry if it can carry anything.

    So the answer should be "DUH!" The real question is how much is reasonable. If you put a warning in font size 4 in white on a white background it is not enough.

    The discussion could even be about what the dault is for a button and what the questioning is. That in such a way that each time yoy select "No" the No is on the right and it will stop whatever you want. Not Yes/No and then No/Yes and then again No/Yes where the first you must answer Yes, then NO and then Yes to go through.

    There wil be a lot of other things possible. Most could be answered by 'ease of use' and 'ergonomics'.

    Does that mean that there will be no problems? No, but if you show some reasonable efford, you get very far already.

    --
    Don't fight for your country, if your country does not fight for you.
  41. Re:Author's bio show how seriously to consider his by Anonymous Coward · · Score: 0

    So after zeroing out all the meaningless bullshit buzzwords, that was your takeaway too?

  42. Bad summary. This is about BI. by SecurityGuy · · Score: 1

    No, in the general case you're not responsible for making sure your users make the right decisions. Imagine doing that for a dating app. Should you date this person? How should I know? All I can do is present you with information.

    The article, though, is about software that specifically exists to help businesses make better decisions. So yeah, if you're writing software that's supposed to help people make better decisions, you do have some ethical duty to write software that leads people to make better decisions. If you're writing such software that DOESN'T do so, why?

    This is just a specific instance of the general idea that if you write software to do a thing, it should actually do that thing.

  43. How Responsible? by dcw3 · · Score: 1

    1.How responsible is Craftsman if someone uses a hammer to murder someone?
    2.How responsible is Smith & Wesson?
    3.How responsible is the tool creator when a tool is used by someone for a purpose that it wasn't designed for?

    Now, I know people will come in on different sides for all of those questions. My own $.02 is that the tool creator would only be responsible for the tool failing...exploding Pintos for example. I'm guessing that many of you aren't old enough to remember Ford's issue with that model though.

    --
    Just another day in Paradise
    1. Re:How Responsible? by FranTaylor · · Score: 1

      I doubt that there has ever been a single case in recorded history where a customer has been able to actually write a proper specification for the software that they want.

      So therefore there has never been a single case in recorded history where software developers have known what they needed to know to do their jobs. How can you POSSIBLY expect them to do the job right?

    2. Re:How Responsible? by Anonymous Coward · · Score: 0

      Nope, I remember the hype...

      http://message.snopes.com/showthread.php?t=26785

    3. Re:How Responsible? by Anonymous Coward · · Score: 0

      This was what made Steve Jobs so unique.

      He was able to craft a UI that fit the user before the user knew they wanted it.

      He had a lot of misses along the way, but a few (very notable) successes.

      Jony Ive is a superb designer, but I don't think he has that predictive capability that Steve Jobs had.

    4. Re:How Responsible? by gnasher719 · · Score: 1

      I doubt that there has ever been a single case in recorded history where a customer has been able to actually write a proper specification for the software that they want.

      So therefore there has never been a single case in recorded history where software developers have known what they needed to know to do their jobs. How can you POSSIBLY expect them to do the job right?

      In a reasonable world, you pick the right person to do the right job. Gathering requirements and turning them into a proper specification needs a lot of talent, practice, and hard work. Your customer is very unlikely to have the talent or practice. That's the job of the company producing the software to supply the person who can do it.

      The job of the software developer is to recognise rubbish specs, push back when the specs are rubbish, and otherwise implement the spec. It's not that difficult.

    5. Re:How Responsible? by david_thornley · · Score: 1

      Some users know enough to write a proper specification, particularly in conceptually simple fields like accounting. My wife does business software, and always liked working with Accounting.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  44. Huh? This doesn't make sense by argStyopa · · Score: 1

    I don't write apps, so perhaps I'm missing something, but it seems patently unfair to hold someone writing an app for the moral choices made by someone using that tool?

    I mean, are we going to hold hammer-makers responsible if someone murders someone else with a hammer?
    I even think it's ridiculous to hold gun manufacturers responsible for the misuse of their products.

    --
    -Styopa
  45. Re:Huh? This doesn't make sense by FranTaylor · · Score: 1

    Iit seems patently unfair to hold someone writing an app for the moral choices made by someone using that tool?

    If the patient monitoring equipment gives faulty information to the doctor, it's the doctor's fault for trusting the equipment? The doctor makes moral choices depending on what the equipment tells him.

  46. Re:Huh? This doesn't make sense by argStyopa · · Score: 1

    That's hardly a moral choice, and that's simply an error. If a developer programs an app and there's a MISTAKE in it, then of course he/she's liable.

    If a medical device tells the doctor that a patient's heart has stopped, accurately, the doctor has to make a moral choice about whether to restart it or not. Delivering that news to the doctor accurately CANNOT be implicated logically if the doctor decides then to kill the patient.

    Nevertheless: if you expect to live in a world that works 100% of the time, I promise that you're going to be disappointed.

    --
    -Styopa
  47. FDA doesn't agree, thank goodness by Anonymous Coward · · Score: 0

    The FDA is not sympathetic with that point of view with regard to medical devices. You all should be thankful for that.

  48. Re:Philophantasy by tiberus · · Score: 1

    Hmm, I was merely suggesting that they are not likely to be omniscient.

  49. Anyone Ever Read Tufte? by Anonymous Coward · · Score: 0

    Interesting chap.

    I don't agree with him on everything, but he's rich and famous on his merits, and I'm not, so I guess it's all sour grapes on my part...

    In any case, he's all about developing UX to present complex data in a manner that provides a strong "signal to noise ratio," and that helps to afford the correct interpretation of data.

    I'd say that BI data fits that profile pretty well, as it can mean billions of pounds/dollars/yen/ruble, and thousands of jobs.

    I see that someone posted his attack on PowerPoint, but some of the other work he's done is pretty relevant to this discussion.

  50. Making Mistakes Impossible by nathana · · Score: 1

    Have not RTFA yet, but this sounds a lot like Matt Gemmell's talk on "Making Mistakes Impossible", which is really good and which you can view here: https://vimeo.com/84322659

    -- Nathan

  51. MS Rant #47 (Re:Visual effects) by Tablizer · · Score: 1

    Using a standard, familiar window layout would allow me to actually get some work done without having to search for

    Microsoft Office added PDF-generating functionality which is good, BUT they put it under File -> Export instead of File -> Save-As, which is where everybody goes to look for it. I've seen this trip several users already.

    (If they had put it under both, that would be acceptable. Unnecessary redundancy is usually a smaller UI sin than misplacement.)

    WTF were you thinking, Microsoft? I'd really like to hear the "rationale" as a study in human decision mental failures. That is, PHBiology.

    1. Re:MS Rant #47 (Re:Visual effects) by Anonymous Coward · · Score: 1

      WTF were you thinking, Microsoft?

      That's an easy one. They were thinking "Microsoft Office can't read in PDFs. It's a write-only format. "Save as" implies that you'll be able to close the program and open the file back up later and continue editing it. "Export" better conveys that the data is being written out of the program in a way that the program will not be able to read back in."

      It's a very technical distinction, made by people who are very technically oriented, and are ultra-aware of how the program works and it's limitations and internal distinctions.

      On the other hand, users don't care about such a distinction. They think "I'm saving, and I'm saving it as a different format, so I want "Save As". They only care about not being able to re-import it when it comes back to bite them later.

      So it really is a difference in viewpoint between the view of developers and the view of users ... which kinda goes back to the main topic that developers should be aware of how users actually will use their software, and should make efforts such that users will "do the right thing", even if the way developers want to do it is "technically" correct.

    2. Re:MS Rant #47 (Re:Visual effects) by Anonymous Coward · · Score: 1

      My guess is that they were thinking, "Save as" is for documents which you might wish to edit later (including those formats not native to office and would require re-importing, but which are implicitly editable), and PDF is generally used as a final form for a document, after which no more editing is desired.

    3. Re:MS Rant #47 (Re:Visual effects) by Tablizer · · Score: 1

      That's an interesting perspective I haven't considered. But, a company as large as Microsoft should have plenty of "usability" experts to point that out and actual user testing. They have the experts and resources to know better, more so than a vast majority of orgs.

      Incidentally, GIMP made a similar snafu. Are they both copying some other vendor, or copying each other? Who started this fad?

      Also, it is possible to re-import most PDF's into Word, Excel, etc.; it's just lossy. But many other existing Save-As's are also lossy, such as CSV which cuts out formatting info. Thus, "re-importable" is a continuum. Only the single native format typically has any guarantee of not being lossy.

    4. Re:MS Rant #47 (Re:Visual effects) by Anonymous Coward · · Score: 1

      Simple, if you save something in another format such as OpenDocument, you can then load it back into Word. However, when you export something, it's not reversible, you can not load a PDF into word and edit the text anymore.

    5. Re:MS Rant #47 (Re:Visual effects) by Anonymous Coward · · Score: 0

      That would be a decent rant if you weren't totally wrong.

      There's a little drop down box labeled "Save as type:" in the Save As dialog. Change it to "PDF (*.pdf)" and guess what! You've got exactly what you're bitching about right there.

      Directions for Word 2007
      Directions for Word 2010-2013

    6. Re:MS Rant #47 (Re:Visual effects) by Tablizer · · Score: 1

      Some users don't have that for some reason. I don't know why. Maybe it depends on installation of some other MS app. Or a bug?

  52. They're not! by Toshito · · Score: 1

    Next question?

    --
    Try it! Library of Babel
  53. App developers responsible for User Decisions? by nickweller · · Score: 1

    "How Responsible Are App Developers For Decisions Their Users Make?"

    Not at all, once the App leaves the developer then the end user is totally responsible for the decisions.

  54. built for retention and ads by gl4ss · · Score: 1

    that's the dilemma really.

    the developers don't try to make the right choice for the _user_ they try to make the user choose the right choice for the _company_.

    like with windows 8/8.1. it tries to make the choice for you to create a microsoft account to use the computer with - you can create a local account but the UI is made so that you don't consider it even as an option if you don't know you can do it beforehand.

    also consider tickboxes for optional things. are they ticked for you already or not? most often they're already ticked for you when it's detrimental for you and beneficial for the company(like installing adware, browser expansions etc when you install just regular software, changing your homepage to their "portal" or whatever).

    when a software tries to take the users side, what is beneficial for the software user, it's like a breath of fresh air nowadays.

    --
    world was created 5 seconds before this post as it is.
  55. Just Wait Until Judgement Day by tmjva · · Score: 1

    The contract developer writes the app that drives the doomsday device. He hands it over to his government, which in turn uses the app and destroys the world.

    So, on judgement day who gets thrown into hell first? The developer or the head of state that pushed the "Accept" button on the app?

    (Which was no doubt, followed by the "Are you sure?" button.)

    I guess that's why they call it the "kill chain" these days. From forward observer back to Pentagon down to shooter they are all ubiquitously linked.

    --
    Tracy Johnson
    Old fashioned text games hosted below:
    http://empire.openmpe.com/
    BT