Let's not make this a witch hunt. Yes, the company should be ostracised, but don't ask for every little person remotely involved with them to pay the price of a stupid lead decision.
I don't know much about this particular case, so I don't have an opinion on the comments above, but the argument that employees shouldn't be punished for participating in an unethical for-profit scheme doesn't really make sense to me.
Well, there is also the question of actual participation:
Let's say [A]dam thinks they're not getting enough data and had this stupid idea to fix the problem, bought a bunch of repos when he had the chance, and told programmer [B]en to patch this in, while [C]hloe in another room is working on the website or tweaks the ML algorithm. How much is she at fault and involved here? What about [D]elilah and [E]ric in Support? Blaming them all individually and equally harshly for being associated with [A]dam is not really justifyable.
If programming were an engineering proffesion, each engineer would be responsible for ensuring that the code they worked on was ethical at the potential cost of their license. It isn't of course, but there is nothing unusual about demanding personal responsibility for social implications from individual employees like that.
What makes you think that that the coverage of this event to be unbalanced and vindictive?
I think that we all agree that this event should be documented and reported objectively as it's newsworthy proved by this very article here and it deserves a mention in a subsection on their Wiki entry.
The effectiveness of this line of defense hasn't improved since the Nuremberg Trials. And the directly responsible committers are not "every little person".
I hope so. This is the kind of thing where a swift and somewhat brutal response is necessary, I feel. I wouldn't necessarily go as far as digitally tar-and-feathering all the developers involved (I've made mistakes myself that were a result of thoughtlessness), but the people in charge should be sent a message that this is not acceptable, and quite frankly I think public shaming/blacklisting is entirely justified when it comes to them.
Yeah. But this is the thread where two proponents of "sending a message" are using the Nuremberg Trials as a case-study.
So people should quite obviously chill a bit. Even if the pitchfork-people in this thread only wish bad PR upon this company, thousands of people are reading these threads, and it only takes one slightly unstable personality to think he'll be a hero for the community if he publishes the CEO's honeymoon photos (or whatever).
Also, to keep this in perspective: they did nothing illegal. Changing the rules is a much better course of action than vigilant justice if you believe this to be wrong.
Let's not make this a witch hunt. Yes, the company should be ostracised, but don't ask for every little person remotely involved with them to pay the price of a stupid lead decision.
I don't know much about this particular case, so I don't have an opinion on the comments above, but the argument that employees shouldn't be punished for participating in an unethical for-profit scheme doesn't really make sense to me.
Well, there is also the question of actual participation: Let's say [A]dam thinks they're not getting enough data and had this stupid idea to fix the problem, bought a bunch of repos when he had the chance, and told programmer [B]en to patch this in, while [C]hloe in another room is working on the website or tweaks the ML algorithm. How much is she at fault and involved here? What about [D]elilah and [E]ric in Support? Blaming them all individually and equally harshly for being associated with [A]dam is not really justifyable.
Completely agree, it's the classic Nuremberg defense.
4 replies →
If programming were an engineering proffesion, each engineer would be responsible for ensuring that the code they worked on was ethical at the potential cost of their license. It isn't of course, but there is nothing unusual about demanding personal responsibility for social implications from individual employees like that.
What makes you think that that the coverage of this event to be unbalanced and vindictive?
I think that we all agree that this event should be documented and reported objectively as it's newsworthy proved by this very article here and it deserves a mention in a subsection on their Wiki entry.
The effectiveness of this line of defense hasn't improved since the Nuremberg Trials. And the directly responsible committers are not "every little person".
Am I the only one alarmed by how quickly this comment chain is escalating?
I hope so. This is the kind of thing where a swift and somewhat brutal response is necessary, I feel. I wouldn't necessarily go as far as digitally tar-and-feathering all the developers involved (I've made mistakes myself that were a result of thoughtlessness), but the people in charge should be sent a message that this is not acceptable, and quite frankly I think public shaming/blacklisting is entirely justified when it comes to them.
Yeah. But this is the thread where two proponents of "sending a message" are using the Nuremberg Trials as a case-study.
So people should quite obviously chill a bit. Even if the pitchfork-people in this thread only wish bad PR upon this company, thousands of people are reading these threads, and it only takes one slightly unstable personality to think he'll be a hero for the community if he publishes the CEO's honeymoon photos (or whatever).
Also, to keep this in perspective: they did nothing illegal. Changing the rules is a much better course of action than vigilant justice if you believe this to be wrong.
2 replies →
I wouldn't make so much fuss for some changes that:
1.They have every right to make (it is open source and they have write access to the repo)
2.I have every right to either fork and reverse, or completely stop using.