schaunwheeler

9 ms·

31.
by schaunwheeler 9y ago
Exactly. The cost of fixing a bug after the product is out the door is much higher when the bug is ethical rather than technical. Therefore, don't move the product out the door so quickly. Ethical QA takes time.
32.
by schaunwheeler 9y ago
I don't think training and sharing of knowledge is the problem. The problem is creating an appropriate incentive structure for maintaining trust in individual practitioners' competency. That doesn't happen in a top-down way.
33.
by schaunwheeler 9y ago
I agree with this. There comes a point (much sooner than most people like to recognize) when quality and safety get sacrificed to just getting things done. However, I think that's a manageable risk. Most focus - and tooling - centered
34.
by schaunwheeler 9y ago
A think a governing body solves the wrong problem. Most of the ethical issues that have arisen around data science in particular are actually competency issues. It's not that someone deliberately set out to target already-vulnerable po
35.
by schaunwheeler 9y ago
I find that people in tech, especially in my own field of data science, treat ethics as a relatively simple problem. If they were building a technical product, they would at least make an appearance of checking assumptions, and worrying abo
36.
by schaunwheeler 9y ago
A lot of people in this thread are focusing on technical tools, which is normal for a discussion of this type, but I think that focus is misplaced. Most technical tools are easily learnable and are not the limiting factor is creating good d