Tech has a white dude problem, and it doesn't get better by not talking about it

The organisers of the British Ruby Conference have cancelled the event due to their failure to invite a diverse speaker line-up.

The British Ruby Conference announced, last night, that the 2013 event would be cancelled, because of a furore stemming from one developer's reaction:

Ruby is a programming language, developed in the mid-1990s, which has gained a lot of popularity in recent years as the basis of a framework used for building web applications. As with programming in general, the Ruby community undoubtedly skews heavily male, and the conference – known as "BritRuby" – cites that in its defence.

In their official explanation for why the decision was made to not put on the 2013 event, the BritRuby organisers write:

We wanted innovative ideas and we whole-heartedly pushed everyone that submitted a proposal to think outside the box. Our selection process was the content and nothing more. Not the individuals gender, race, age or nationality. It’s about community…

The Ruby community has been battling with issues of race and gender equality. We at Brit Ruby were well aware of this fundamental and important issue. This was one of the reasons why we encouraged everyone to submit a speaker proposal.

It is often the case with situations like this that those under attack cite the belief that they picked the line-up based entirely on quality. For instance, it remains true that orchestras are dominated by men, and for years, explanations were given about how only men had the strength, or control, or innate musicality to play certain instruments, and so on.

Yet as orchestras gradually introduced blind auditions – actually picking the line-up based purely on quality – the gender balance shifted. And it appears much the same may be true of technology. Josh Susso, the developer whose tweet sparked the whole discussion which ended up leading to the conference being pulled, ran his own ruby conference in San Francisco, GoGaRuCo, which had a completely blind selection process.

As a result of that, and explicitly reaching out to women's programming groups, the slate of speakers was a quarter women. Even though it may be easier in a city like San Francisco, it is possible.

Sadly, the debate around BritRuby's monoculture led, according to the statement, to their sponsors getting spooked after accusations of sexism and racism threatened to toxify the brand. With uncertain sponsorship and personal liabilities, the organisers were forced to cancel.

They did not go out in a blaze of glory.

Sean Handley, who has run previous conventions with the BritRuby team but was not involved in this one, posted his own take on the situation which is slightly more self-pitying than the official one:

Yes, gender equality and racial equality are important. But the team's motives were to get the best speakers who were able to make it to Manchester. Turns out, a lot of the famous Rubyists are white guys and all of the ones who said they'd like to come were, indeed, white guys.

Making an issue out of that is, frankly, misguided. Adding a token minority speaker is offensive to that speaker, it says "You're here because you tick a box - not because you're skilled." It doesn't matter who speaks at a conference, as long as they're capable, interesting and relevant. That's what matters: content, not style.

Even that defence starts getting a bit uncomfortable in the end. If you are defending your all-white, all-male speaker line-up by saying that you only wanted the "best speakers", it's hard for non-white, non-male people to not infer that they are considered sub-par. Saying that the only way to fix the problem would be to add "token" speakers makes it sound like there are no non-token speakers worth inviting.

And saying that "it doesn't matter who speaks at a conference, as long as they're capable, interesting and relevant" is plainly untrue: it does matter, to a hell of a lot of people, and if you set out to be a leading voice in your community, you owe it to yourself and that community to try and make it a better group to be in.

Some – not all – elements of that community sorely need help, judging by the comments beneath Handley's post.

The whole event ruined for everyone but a few narrow minded individuals.

Yes. The people who want not all-white-male-speakers are narrow minded.

Next thing would be people complaining about the lack of Unicorns on the conferences.

Women in tech: Literally Imaginary, apparently.

[Quoting an earlier commenter] I feel this needs to happen more and more so Conference organizers are forced to start considering diversity from the beginning and initiate programs or reach out to more non-white-males to speak

While we're at it, let's make sure to throw in a few over-50s, a disabled woman and a couple of homosexuals. We need to focus on diversity after-all.

Where is the line?

Oh no! Gay people might be at the conference?!

Seriously, this whole equality crap is… crap! One thing is when there are cases where women are not treated fairly (not good) or abused (very bad), but equality is a non-issue for most of us in the Western world. In cases where exploitation or abuse are confirmed, society should act for sure, but the reality is men and women are not equal in many ways. It's not that one is better and the other is worse is that, quite simply, we're different. I see plenty of "Women Seminars" (not very "Men Seminars" I should add) and I don't see anyone rushing those asking for "equality" or "lack of men on these".

I'm done here.

Update: Changed the headline slightly, and corrected the reference to Sean Handley

Photograph: 2013.britruby.com

Alex Hern is a technology reporter for the Guardian. He was formerly staff writer at the New Statesman. You should follow Alex on Twitter.

Getty
Show Hide image

How hackers held the NHS to ransom

NHS staff found their computer screens repleaced by a padlock and a demand for money. Eerily, a junior doctor warned about such an attack days earlier. 

On Friday, doctors at Whipps Cross Hospital, east London, logged into their computers, but a strange red screen popped up. Next to a giant padlock, a message said the files on the computer had been encrypted, and would be lost forever unless $300 was sent to a Bitcoin account – a virtual currency that cannot be traced. The price doubled if the money wasn’t sent within six days. Digital clocks were counting down the time.

It was soon revealed Barts Health Trust, which runs the hospital, had been hit by ransomware, a type of malicious software that hijacks computer systems until money is paid. It was one of 48 trusts in England and 13 in Scotland affected, as well as a handful of GP practices. News reports soon broke of companies in other countries hit. It affected 200,000 victims in 150 countries, according to Europol. This included the Russian Interior Ministry, Fedex, Nissan, Vodafone and Telefonica. It is thought to be the biggest outbreak of ransomware in history.

Trusts worked all through the weekend and are now back to business as usual. But the attack revealed how easy it is to bring a hospital to its knees. Patients are rightly questioning if their medical records are safe. Others fear hackers may strike again and attack other vital systems. Defence minister Michael Fallon was forced to confirm that the Trident nuclear submarines could not be hacked.

So how did this happen? The virus, called WannaCry or WannaDecrypt0r, was an old piece of ransomware that had gained a superpower. It had been combined with a tool called EternalBlue which was developed by US National Security Agency spies and dumped on the dark web by a criminal group called Shadow Brokers. Computers become infected with ransomware when somebody clicks on a dodgy link or downloads a booby-trapped PDF, but normally another person has to be fooled for it to harm a different computer. EternalBlue meant the virus could cascade between machines within a network. It could copy itself over and over, moving from one vulnerable computer to the next, spreading like the plague. Experts cannot trace who caused it, whether a criminal gang or just one person in their bedroom hitting "send".

Like a real virus, it had to be quarantined. Trusts had to shut down computers and scan them to make sure they were bug-free. Doctors – not used to writing anything but their signature – had to go back to pen and paper. But no computers meant they couldn’t access appointments, referral letters, blood tests results or X-rays. In some hospitals computer systems controlled the phones and doors. Many declared a major incident, flagging up that they needed help. In Barts Health NHS Trust, ambulances were directed away from three A&E departments and non-urgent operations were cancelled.

The tragedy is that trusts had been warned of such an attack. Dr Krishna Chinthapalli, a junior doctor in London, wrote an eerily premonitory piece in the British Medical Journal just two days earlier telling hospitals they were vulnerable to ransomware hits. Such attacks had increased fourfold between 2015 and 2016, he said, with the money being paid to the criminals increased to $1bn, according to the FBI. NHS trusts had been hit before. A third reported a ransomware attack last year, with Imperial College London NHS Trust hit 19 times. None admitted to paying the ransom.

Hospitals had even been warned of this exact virus. It exploited a vulnerability in Microsoft Windows operating systems – but Microsoft had been tipped off about it and raised the red flag in March. It issued a patch – an update which would fix it and stop systems being breached this way. But this patch only worked for its latest operating systems. Around 5 per cent of NHS devices are still running the ancient Windows XP, the equivalent of a three-wheeled car. Microsoft said it would no longer create updates for it two years ago, rendering it obsolete.

There are many reasons why systems weren’t updated. Labour and the Lib Dems were quick to blame the attack on lack of Tory funding for the NHS. It is clear cost was an issue. Speaking on BBC Radio 4’s PM programme on Saturday, ex-chief of NHS Digital Kingsley Manning estimated it would take £100m a year to update systems and protect trusts against cyber attacks. Even if that money was granted, there is no guarantee cash-strapped trusts would ringfence it for IT; they may use it to plug holes elsewhere.

Yet even with the money to do so updating systems and applying patches in hospitals is genuinely tricky. There is no NHS-wide computer system – each trust has its own mix of software, evolved due to historical quirk. New software or machines may be coded with specific instructions to help them run. Changing the operating system could stop them working – affecting patient care. While other organisations might have time to do updates, hospital systems have to be up and running 24 hours a day, seven days a week. In small hospitals, it’s a man in a van manually updating each computer.

Some experts believe these are just excuses; that good digital hygiene kept most trusts in the UK safe. "You fix vulnerabilities in computers like you wash your hands after going to the toilet," said Professor Ross Anderson, a security engineering expert at Cambridge University. "If you don't, and patients die, excuses don't work and blame shifting must not be tolerated."

It is not known yet if any patients have died as a result of the attack, but it certainly raised fears about the safety of sensitive medical records. This particular virus got into computer files and encrypted them – turning them into gooble-de-gook and locking doctors out. Systems were breached but there have been no reports of records being extracted. Yet the scale of this attack raises fears in future the NHS could be targeted for the confidential data it holds. "If it’s vulnerable to ransomware in this way, it could be vulnerable to other attacks," said Professor Alan Woodward security expert at the University of Surrey's department of computing.

In the US, there have been examples where ransomware attacks have led to patient data being sucked out, he said. The motivation is not to embarrass people with piles or "out" women who have had an abortion, but because medical information is lucrative. It can be sold to criminals for at least $10, a price 10 times higher than can be earned by selling credit card details. Dossiers with personal identification information – known as "fullz" on the dark web – help crooks commit fraud and carry out scams. The more personal details a conman knows about you the more likely you are to fall for their hustle.

Hospital data is backed up at least hourly and three copies are kept, one offsite, so it is unlikely any medical records or significant amounts of data will have been lost – although the hack will cost the NHS millions in disruption. A British analyst, who tweets under the name Malware Tech, became an unlikely hero after accidentally finding a killswitch to stop the virus replicating. He registered a website, whose presence signalled to the virus it should stop. Yet he admits that a simple tweak of the code would create a new worm able to infect computers.

Experts warn this event could trigger a spate of copycat attacks. Hacker may turn their eyes to other public services. Dr Brian Gladman, a retired Ministry of Defence director, and ex-director of security at Nato, points out that our entire infrastructure, from the national grid, food distribution channels to the railways rely on computer systems. We now face an arms race – and criminals only have to get lucky once.

"We’re going to get more attacks and more attacks and it’s going to go on," he said. "We’ve got to pay more attention to this."

Madlen Davies is a health and science reporter at The Bureau of Investigative Journalism. She tweets @madlendavies.

0800 7318496