Please note there are MANY updates below, and a separate post following DataCamp’s April 24th announcement.
Last week (April 4, 2019) DataCamp published a blog post stating that “one of DataCamp’s executives danced inappropriately and made uninvited physical contact with another employee,” an action meeting many definitions of sexual assault. While the post makes the claim that DataCamp does not condone this behavior, it also makes clear that the disciplinary actions against the executive were limited to “sensitivity training, personal coaching, and a strong warning.”
DataCamp’s post came one day after a group of 100 DataCamp instructors, including me, signed a letter to DataCamp leadership. Having learned of the incident, several instructors had been engaged with DataCamp to try to get the company to act in a way that appropriately disciplined the executive and assured a safe working environment for DataCamp employees and instructors. Inaction led those leaders to encourage more of us to get involved. DataCamp’s responses to our questions and comments were largely along the lines of the letter. In short: He got a warning, we have great policies and diversity initiatives now, this matter is closed.
Many others have eloquently described how this response is grossly inadequate:
this post is nauseating. it can barely bother to be contrite. missing from the list of actions the company has taken are:--- just moomin 🏳️ 🌈🏴 (@no_reply) April 4, 2019
- any consequences for the perpetrator/executive
- anything the company has done to make things right for the employee.#Python #rstats #datascience #MeToo
They could start by firing the guy who can't keep his hands to himself.— Jesse Mostipak (@kierisi) April 4, 2019
And by writing a responsible incident report...all the extra detail is on the behalf of the perpetrator. I don't care if it was at a Bull Fight in Cuba at 4pm, or at 8am in the copy room. I don't care if it was reported 20 minutes later, or at the start of the next fiscal quarter. pic.twitter.com/2XLtURDDfc--- Mara Averick (@dataandme) April 4, 2019
I've supported D.C. publicly, been on their podcast & pay for their service. I'm VERY displeased with how this was handled. This blog post is bullshit. The post spins a bunch of detail that casts shade / doubt on the victim.--- JD Long (@CMastication) April 5, 2019
This is wrong.
Do better, y'all. https://t.co/NpR9G6aKQG
@skeptycal ha a particularly sharp analysis of just how this statement fails so completely.)
I was, probably credulously, shocked at the statement DataCamp put out. After 100 instructors told them that they couldn’t just leave it at that, they wrote a public statement to leave it at that. We got no message like “we are making a statement, and something more robust is coming.” Nor did DataCamp give the target any warning that they would make the incident public by releasing a statement.
The last part was especially galling given how cautious the instructors who organized us were about avoiding blowback to other parties. The instructors who led the effort were patient, despite months of frustrating conversations with DataCamp. They kept the matter private to avoid dragging the target of the incident into the fray. They kept the focus on DataCamp leadership and policy to avoid putting other employees in an awkward place. They gave DataCamp every opportunity to explain themselves, change course, and own the public narrative. A company should count itself lucky to have such constructive critics.
It’s clear that without enormous public pressure, DataCamp will not take sufficient disciplinary action against the executive. And it is necessary that they do. It must be made very clear to men, from teenage boys to CEOs, that when they choose to violate women’s space, they are risking their jobs. When they decide to abuse their power as bosses, their careers, their VC funding, their tenure, their board seats, their reputation, and their friends, should all be on the line.
I guarantee you that women who are targets of such predation weigh the consequences of every subsequent action. Do they choose to leave their jobs? Do they report the incident and let it upend their career? Do they pursue criminal charges and let it consume their lives, with little chance of success? Do they stay quiet but carefully plan every day to avoid being alone in the room with their predator? Do they laugh it off and risk reprisal when this is interpreted as permission and they reject further advancement?
Let men who can’t keep their hands to themselves live their lives questioning every decision.
The way to make men face consequences for their decisions is to force reprecussions via companies and institutions. So I hope you don’t take my DataCamp course. I hope you will stop using DataCamp and let them know this is why. I hope if your company uses DataCamp you convince them to stop buying licenses. I hope if you invest in or advertise with or accept sponsorships from DataCamp you stop.
If enough pressure is brought on the company to make investors worry about their money and other executives about their jobs, we might see some meaningful action. Scolding DataCamp while continuing to pay them, because it’s a nice platform, is like sensitivity training for a “nice guy.”
My course on DataCamp is Nonlinear Modeling in R with GAMs. It’s about Generalized Additive Models, tools I find quite handy and that I’d love to teach you more about. My contract with DataCamp gives them license to keep using it. Please don’t take my course. Don’t give DataCamp your money and send the message that sexual misconduct doesn’t have consequences. I’ve collected some other resources on GAMs on this page. I hope to convert my course to an open-source format soon, but for now these will more than do. Others are at least skilled as explaining the topic as I am.
Significant Updates (2019-04-24)
DataCamp issued a statement from it’s board and an apology from the CEO. In short, the CEO will be stepping down “indefinitely,” and there is to be an investigation by outside counsel and the creation of instructor review board. There’s an article in Computer World about it, including my and Julia Silge’s reactions.
New stories from Business Insider, which names the CEO as the executive, and Motherboard, which features the large numbers of instructors leaving.
Even More updates (2019-04-17)
A news story about all this in Computer World, by Sharon Machlis.
Yet More updates (2019-04-16)
Read Julia Silge’s thoughtful post on how DataCamp lost her trust.
More updates (2019-04-15)
The SatRdays organization has put out a statement that they are dropping DataCamp sponsorship from their events.
Two former DataCamp employees, Dhavide Aruliah and Greg Wilson, were fired in mid-2018 after complaining to management about handling of sexual harassment. Here are statements from Dhavide and Greg (and some other relevant posts from Greg: 1, 2). Both say that DataCamp claimed their firings were due to poor performance. I find that aburd, as their stamp is all over DataCamp’s products. I tweeted a brief thread about this here.
RStudio announced they will stop working with DataCamp in this tweet thread
Some updates (2019-04-13)
People have asked whether instructors have the right to pull their content off of DataCamp:
In general, no. Contract terms vary a bit, but for me: I retain IP and the right to post it elsewhere, but grant DC a perpetual, non-exclusive license to the course material in return for royalties. I've requested breaking the contract by mutual consent, have not heard back.— Noam Ross (@noamross) April 13, 2019
(Update 2019-04-22: I have heard back and DataCamp opted to keep my course up.)
There are statements from R-Ladies and Women+ in Machine Learning & Data Science comdemning DataCamp. Lots of other instructors are and other DataCamp partners disassociating themselves from the DataCamp and putting their materials somewhere else for learners to use. I expect many more to come. All these people are giving up income. Support them, their organizations and projects as you can.
I created a project for @DataCamp last year. DataCamp has shown poor handling of sexual harassment, so I don't recommend that you use my project on DataCamp. Instead, try it for free on GitHub! (Do left-handed people really die young? Spoiler: no.) https://t.co/oIuBeRkTWD— Madeleine Bonsma-Fisher (@mbonsma) April 24, 2019
My course recently launched. Please don’t take it, not until DataCamp regains our trust. (4/4)— Marc Dotson (@marcdotson) April 17, 2019
🗣 Please don't take my @DataCamp course, as @noamross put it in his post today, there must be consequences for sexual assault. https://t.co/3G1TkfZpK1— 𝓛𝓾𝓬𝔂::postdoc🌻 (@LucyStats) April 12, 2019
Here is a shinydashboard course you can take instead:https://t.co/SNUfY6zdnD
Greg was one of the reasons I developed my course with DataCamp. After he was fired for "performance", they tried to bribe him with a month's pay if he signed a non-disparagement agreement. This company is rotten to the core. https://t.co/qULEffAZ3Y— Dr. Alex Hanna (@alexhanna) April 15, 2019
FWIW I don't feel in an awkward position. By which I mean it's easy for me to state: I would encourage everyone NOT to take or pay for my Bokeh course on DC (or any others). Very sorry this happened to you and very disappointed in DC leadership.— 🔴 (@bigreddot) April 12, 2019
I'm with Noam here, very well said! @DataCamp need to be held accountable - do not take my course, I will be working on getting the content available in another medium soon, hopefully by mid year. https://t.co/02haKPYJE4— Nicholas Tierney (@nj_tierney) April 13, 2019
tl;dr: please don’t take my course on @DataCamp.— Romain François 🧩 (@romain_francois) April 14, 2019
I can not in good faith encourage anyone to take my #rstats and #python #dataviz DataCamp courses given their recent horrific handling of the (not at all recent) sexual assault of a team member. See https://t.co/67Y8vkIcTg and https://t.co/VSpohatmfG and many more.— Nick Strayer (@NicholasStrayer) April 15, 2019
I terminated my #DataCamp course contract this week to stand in support with my #rstats community against DataCamp’s poor handling of sexual misconduct. https://t.co/pzZy3wghWv I cannot support any organisation who does not value the people who make the R community great! #MeToo— Alice Data (@alice_data) April 25, 2019
Like many of you, I'm incredibly disappointed by DataCamp. I wanted to make a free version of my spaCy course so you don't have to sign up for their service – and ended up building my own interactive app. Powered by the awesome @mybinderteam & @gatsbyjs 💖 https://t.co/2QOuDPoZEX— Ines Montani 〰️ (@_inesmontani) April 17, 2019
I was developing a course, but have indefinitely suspended development until the leadership makes a big change in their behavior. More honesty, transparency, and accountability are what I asked for before resuming development. @DataCamp #python #rstats— Nate George (@_tetration_) April 18, 2019
I stopped developing my @DataCamp course on data cleaning in #sql #postgresql. Requested contract termination ASAP. Course will be available on another platform. My gratitude to all that brought the situation to light. Post by @noamross speaks volumes: https://t.co/VX1ayxLmhH— Casey Bates (@_casey_bates) April 17, 2019
Until real change happens, please do not take my @DataCamp course. @noamross said this better than I could: https://t.co/pmJkGDucGV— James Lamb (@_jameslamb) April 14, 2019
Like many others, I am encouraging people to not take my #DataCamp course, due to their unacceptable handling of sexual assault. There are many other places to learn about Bayesian regression modeling. Here are a few using the same packages as my course:— Jake Thompson (@wjakethompson) April 14, 2019
I *can* say it's unlikely I'll ever use or recommend @DataCamp again. They have, through their own arrogance, selfishness, & shortsightedness irrevocably lost the trust & respect of the very community they rely on to build content. (2/2)#MeTooSTEM— Dhavide Aruliah (@dhavidearuliah) April 15, 2019
1. Some of you may know of my course on R programming at @DataCamp. Sadly, the company has failed to properly handle credible allegations of sexual assault perpetrated by a C-lvl exec. Please don’t take my course until they issue a proper remedy. #TimesUp.— G. Elliott Morris (@gelliottmorris) April 16, 2019
This means:— Mine CetinkayaRundel (@minebocek) April 23, 2019
1. My @Coursera course no longer offers option for #rstats labs via @DataCamp.This years-long collaboration represents hard work by @DukeLearning+DataCamp staff to provide browser-based R access for thousands of learners,fruits of this effort will now go unused(2/5)
Please do not take my @DataCamp course. I'm disappointed by the incident, but I'm dumbfounded by recent actions. The: response to instructors, 'no-index' tag on blog, and `3rd party not involved in day-to-day` for investigation speaks volumes. Do not support DataCamp. https://t.co/76qp1wmPfS— Jo Hardin (@jo_hardin47) April 23, 2019
I was so proud & excited to be mere *days* away from my 1st #DataCamp course being hard-launched! After learning about the organization's actions 🤬I have asked for my course to be withdrawn & my contract terminated. I'm waiting for a response & very unsure of the legalities.— Danielle Quinn (@daniellequinn88) April 15, 2019
[...] I'll remove all references to my two @DataCamp courses and refrain from encouraging people to take them. This is really sad and I feel deeply sorry for the good people at the company that I had the pleasure to work with. Background: https://t.co/ybwoa9eSNc #rstats #SQL— Timo Grossenbacher (@grssnbchr) April 17, 2019
"What I do need to maintain a continuing relationship with a company and/or people is trustworthiness and accountability." @juliasilge explains it perfectly. You've lost my trust @DataCamp https://t.co/inMQJfHGlK— Charlotte Wickham (@CVWickham) April 17, 2019
Most of us signed an open letter telling datacamp to go fuck themselves over this. Boycott away!— Os (@farbandish) April 5, 2019
I applaud @noamross's stance and I stand in full support of his position. Please do not pay for or take my @DataCamp course. I'll be releasing an open book this summer that includes equivalent content and more for those of you who are using those resources. https://t.co/uo4O7CmqBG— Kyle Walker (@kyle_e_walker) April 12, 2019
It's incredibly disappointing how DataCamp has dealt with this situation. I will not be developing any more courses with them. https://t.co/G9lvBuRHwX— Sarah Guido (@sarah_guido) April 5, 2019
I have two courses under development at @DataCamp. I have ceased development on both and will not complete them. Outrageous. https://t.co/9vtBUSzp4A— Chris Fonnesbeck (@fonnesbeck) April 15, 2019
Finally, when I was originally writing this post, I discovered that DataCamp’s
blog post describing the event contained a piece of code,
<meta name="robots" content="noindex" class="next-head">
which effectively makes the page invisible to search engines.
@no_reply and Bob Rudis
both give more elaborate explanations. DataCamp doesn’t do this for any of their other blog
If you think @DataCamp deserves credit for a public post that they did not discipline an executive for sexual misconduct, consider that they put this code in the HTML, so no search engines would index it. I don't see it anywhere else on their blog. #rstats #python #datasci #metoo pic.twitter.com/xbQoSaQl5J— Noam Ross (@noamross) April 12, 2019
(Edit 2019-04-17: On April 17th the
noindex tag was removed. Here is the page archived
on the 16th and
on the 17th.)