Summing up the AI summit

The end of the year is approaching fast, with Christmas now barely two weeks away, but I managed to fit in one more virtual event to top off this year of virtual events: the Tortoise Global AI Summit. To be quite honest, I wasn’t actually planning to attend – didn’t even know it was happening – but a colleague messaged me the previous day, suggesting that it might be relevant to my interests and also that the top brass would appreciate some kind of executive summary for the benefit of the Faculty. Despite the short notice I had most of the day free from other engagements, and since the agenda did indeed look interesting, I decided to register and check it out – hope this blog post is close enough to what the Dean had in mind! 

I liked the format of the event, a series of panel discussions rather than a series of presentations. Even the opening keynote with Oxford’s Sir Nigel Shadbolt was organised as a one-on-one chat between Sir Nigel and Tortoise’s James Harding, which felt more natural in an online environment than the traditional “one person speaks, everyone else listens, Q&A afterward” style. Something that worked particularly well was the parallel discussion on the chat, to which anyone attending the event could contribute and from which the moderators would from time to time pick questions or comments to be discussed with the main speakers. Overall, I was left with the feeling that this is the way forward with virtual events: design the format around the strengths of online instead of trying to replicate the format of an offline event using tools that are not (yet) all that great for such a purpose. 

The keynote set the tone for the rest of the event, bringing up a number of themes that would be discussed further in the upcoming sessions: the hype around AI versus the reality, transparency of AI algorithms and AI-based decision making, AI education – fostering AI talent in potential future professionals and data/algorithm literacy in the general populace – and the need for data architectures designed to respect the ethical rights of data subjects. Unhealthy power concentrations and how to avoid them was a topic that resonated with the audience, and it shouldn’t be too hard to think of a few examples of such concentrations. The carbon footprint of running AI software was brought up on the chat. Perhaps my favourite bit of the session was Sir Nigel’s point that there is a need for institutional and regulatory innovations, which he illustrated by way of analogy by mentioning the limited company as a historical example of an institutional innovation. Such innovations are perhaps more easily overlooked than scientific and technological ones, but one can hardly deny that they, too, have changed the world and will continue to do so.

The world according to Tortoise

The second session was about the new edition of the Tortoise Global AI Index, which ranks 62 countries of the world on their strength in AI capacity, defined as comprising the three pillars of implementation, innovation and investment. These are further divided into the seven sub-pillars of talent, infrastructure, operating environment, research, development, government strategy and commercial, and the overall score of each country is based on a total of 143 individual indicators. The scores are normalised such that the top country gets an overall score of 100, and it’s no big surprise that said country is the United States, as it was last year when the index was launched. China and the United Kingdom similarly retain their places as no. 2 and no. 3, respectively. China has closed some of the gap with the US but is still quite far behind with a score of 62, while the UK, sitting at around 40, has lost some of its edge over the challengers. Canada, Israel, Germany, the Netherlands, South Korea, France and Singapore complete the top 10. 

Finland is just out of the top 10 but rising, up three places from 14th to 11th. According to the index, Finland’s particular forte is government strategy, comprising indicators such as the existence of a national AI strategy signed by a senior member of government and the amount of dedicated spending aimed at building AI capacity. In this particular category Finland is ranked 5th in the world. Research (9th) and operating environment (11th) can also be counted among Finland’s strengths, and all of its other subrankings (talent – 16th, commercial – 19th, infrastructure – 21st, development – 22nd) are solidly above the median as well. Interestingly, the US, while being ranked 1st in four categories and in the top 10 for all but one, is only 44th on operating environment. The most heavily weighted indicator here is the level of data protection legislation, giving countries covered by the GDPR a bit of an edge; 7 of the top 10 in this category are indeed EU countries, but there is also, for instance, China in 6th place, so commitment to privacy is clearly not the whole story. 

There was some good discussion on the methodology of the AI index, such as the selection of indicators. For example, one could question the rather heavy bias toward LinkedIn as a source of indicators for AI talent. Another interesting point raised was that while we tend to consider academics mainly in terms of their affiliation, it might also be instructive to look at their nationality. Indeed, the hows and whys of the compilation of the index would easily make for a dedicated blog post, or even a series of posts, but I’ll leave it for others to produce a proper critique. For those who are interested, a methodology report is available online. 

From the Global AI Index the conversation transitioned smoothly into the next session on the geopolitics of AI, where one of the themes discussed was if countries should be viewed as competing against one another in AI, or if AI should rather be seen as an area of international collaboration for the benefit of citizens everywhere. Is there an AI race, like there once was a space race? Is mastery of AI a strategic consideration? Benedict Evans advocated the position that to talk about AI strategy is to adopt a wrong level of abstraction, and that AI (or rather machine learning) is just a particular way of creating software that in about ten years’ time will be like relational databases are today: so ubiquitous and mundane that we hardly pay any attention to it. This was in stark contrast to the view put forward in the beginning of the session that AI is a general-purpose technology akin to electricity, with comparable potential to revolutionise society. The session was largely dominated by this dialectic, but there was still time for other themes as well, such as the nature of AI clusters in a world where geographically limited technology clusters are becoming an outdated concept, and the role of so-called digital plumbing in providing the essential foundation for the success of today’s corporate AI power players.

Winners and losers

The next session, titled “AI’s ugly underbelly”, started by taking a look at an oft-forgotten part of the AI workforce, the people who label data so that it can be used to train machine learning models. It’s been estimated that data labelling accounts for 25% of the total project time in an ML project, but the labellers are, from the perspective of the company running the project, an anonymous mass employed through crowdsourcing platforms such as MTurk. In academic research the labellers are often found closer to home – the job is likely to be done by your students and/or yourself, and when crowdsourcing is used, people may well be willing to volunteer for the sake of contributing to science, such as in the case of the Zooniverse projects. In business it’s a different story, and there is some money to be made by labelling data for companies, but not a lot; it’s an unskilled job that obeys the logic of the gig economy, where the individual worker must buy their own equipment and has very little in the way of job security or career prospects. 

The subtitle of this session was “winners and losers of the workforce”, the winners of course being the highly skilled professionals who are in increasingly high demand and therefore increasingly highly paid. There was a good deal of discussion on the gender imbalance among such people, reflecting a similar imbalance in the distribution of the sort of hard (STEM) skills usually associated with tech jobs. In labelling the gap is apparently much narrower, in some countries even nonexistent. It was argued that relevant soft skills and potential AI talent are distributed considerably more evenly, and that companies trying to find people for AI-related roles may want to look beyond the traditional recruiting pathways for such roles. A minor point that I found thought-provoking was that recruiting is one of the application domains of AI, so the AI of today is involved in selecting the people who will build the AI of tomorrow – and we know, of course, that AI can be biased. One of the speakers brought up the analogy that training an AI is like training a dog in that the training may appear to be a success, but you cannot be sure of what it is that you’ve actually trained it to respond to. 

There was more talk about AI bias in the “AI you can trust” session, starting with what we mean by the term in the first place. We can all surely agree that AI should be fair, but can we agree on what kind of fairness we want – does it involve positive discrimination, for example? Bias in datasets is a relatively straightforward concept, but beyond that things get less tidy and more ambiguous. There is also the question of how we can trust that an AI is not biased, provided that we can agree on the definition; a suggested solution is to have algorithms audited by a third party, which could provide a way to strike a balance between the right of individuals to know what kind of decision-making processes they are being subjected to and the right of organisations to keep their algorithms confidential. An idea that I found particularly interesting, put forth by Carissa Véliz of the Institute for Ethics in AI, was that algorithms should be made to undergo a randomised controlled trial before they are allowed to make decisions that have a serious, potentially even ruinous, effect on people’s lives. 

Data protection was, of course, another big topic in this session. That personal data should be handled responsibly is again something we can all agree on, but there was a good deal of debate on what is the proper way to regulate companies to ensure that they are willing and able to shoulder that responsibility. Should they be told how to behave in a top-down manner, or is it better to adopt a bottom-up strategy and empower individuals to look after their own interests when it comes to privacy? Is self-regulation an option? The data subject rights guaranteed by the GDPR represent the bottom-up approach and are, in my opinion, a major step in the right direction, but it’s also a matter of having effective means to enforce those rights, and here, I feel, there is still a lot of work to be done. The GDPR, of course, only covers the countries of the EU and the EEA, and it was suggested that perhaps we need an international organisation for the harmonisation of data protection, a “UN of data” – a tall order for sure, but one worth considering.

Grand finale

The final session, titled “AI: the breakthroughs that will shape your life”, included several callbacks to themes discussed in previous sessions, such as the growth of the carbon footprint of AI as the computational cost of new breakthroughs continues to increase – doubling almost every 3 months according to an OpenAI statistic. The summit took place just days after the announcement of a great advance achieved by DeepMind’s AlphaFold AI in solving the protein folding problem in computational biochemistry, mentioned already in the beginning of the first session and discussed further here. While it was pointed out that the DeepMind solution is not necessarily the end-all it has been hailed as, it certainly serves to demonstrate that the technology is good for tackling serious scientific problems and not just for mastering board games. The subject of crowdsourcing came up again in this context, as the approach has been applied to the folding problem with some success in the form of Folding@home, where the home computers of volunteers are used to run distributed computations, as well as Foldit, a puzzle video game that essentially harnesses the volunteers’ brains to do the computations. 

There was some debate on the place of humans in a society increasingly permeated by AI systems, particularly on where we want to draw the line on AI autonomy and whether new jobs created by AI will be enough to compensate for old ones replaced by AI. Somewhat ironically, data labeller is a job created by AI that may already be on its way to being made obsolete by advances in AI techniques that do not require large quantities of labelled data for training. One of the speakers, Connecterra founder Yasir Khokhar, talked about the role of AI in solving the problem of feeding the world, reminding me of Risto Miikkulainen’s keynote talk at CEC 2019, in which he presented agriculture as one of the application domains of creative AI through evolutionary computation. OpenAI’s GPT-3 was then brought up as another example of a recent breakthrough, leading to a discussion on how we tend to anthropomorphise our Siris and Alexas and to ascribe human thought processes to entities that merely exhibit some semblance of them. There was a callback to AI ethics here when someone asked whether we have the right to know when we are interacting with an AI – if we’re concerned about AI transparency, then arguably being aware that there is an AI is the most basic level of it. Of things that are still in the future, the impact of quantum computing on AI was discussed, as were the age-old themes of artificial general intelligence and rogue AI as existential risk, but in the time available it wasn’t feasible to come to any real conclusions. 

Inevitably, it got harder to stay alert and focused as the afternoon wore on, and I also missed the beginning of one session because I had to attend another (albeit very brief) meeting, but even so, I managed to gather a good amount of interesting ideas and information over the course of the day. I’m particularly happy that I got a lot of material on the social implications of AI that we should be able to use when developing our upcoming AI ethics course, since so far I haven’t been too clear about specific topics related to this aspect of AI that we could discuss in the lectures. This wasn’t a week too soon, I might add – we’re due to start teaching that course in March, so it’s time to get cracking on the preparations!

Sweet freedom

The Midsummer celebrations are over, and the main holiday season is upon us. This is the first time since 2017 that I’m spending the whole summer in Finland, and I have to say it feels pretty sweet so far – they call Ireland the Emerald Isle, but we have plenty of shades of green of our own here, and the weather in June has been mostly gorgeous. Somewhat annoyingly, it looks like we’re due for the return of more traditional Finnish summer weather just as I’m about to start my vacation, but I’ll take it; I certainly prefer it to the sweaty +30°C days I had to endure toward the end of my summer holiday last year. Having access to my bike again has been a great joy, although I do kind of miss taking a commuter train to a random town or village and going exploring like I used to do in Dublin. I have been expanding my territory by trying out new routes and going further afield than before, but it doesn’t quite have the same sense of adventure to it. 

I was actually planning to travel to England this July; a band I became a big fan of during my tour of duty in Ireland was going to play a concert in Aylesbury near London and I bought myself a ticket pretty much as soon as they became available. Since I’ve never been to London, I thought I’d spend some time there, and I was also planning to visit Oxford as well as Bletchley Park in Milton Keynes, the place where Allied codebreakers (among them one Alan Turing) worked during WW2 – a sort of science and technology-themed pilgrimage, if you will. However, because of the pandemic the event has been postponed until an as yet unspecified date in 2021, and besides I don’t think going gallivanting around the UK would be very favourably looked upon anyway, so it’s just as well that I wasn’t an early bird with my travel arrangements. Better luck next year, I hope! 

In Finland the COVID situation seems to be pretty much under control for now, with only a couple dozen people receiving hospital care in the whole country; the figure peaked at just shy of 250 in early April. Life is steadily becoming less restricted, and the nationwide official recommendation to work remotely is being lifted as of the 1st of August. There’s no word yet on how this will affect university policy, but perhaps when July is over, we’ll be going back to the office. Strange thought – working from home really does feel like the new normal already! Of course the pandemic is far from over and there’s no telling when we’re going to be hit by another wave, so better keep that sourdough starter alive for lockdown part two.

The biggest thing I wanted to tick off my to-do list before switching into vacation mode was finishing and submitting the journal paper manuscript that will probably be the last thing I publish on the results of the KDD-CHASER project. With so much else going on, the paper took a while to get into shape for submission, but it’s now in the care of the good people of ACM Transactions on Social Computing, so there’s one thing I (presumably) won’t have to think about until autumn. The notification for my CIKM paper is due on July 17th, but the camera-ready submission deadline is a whole month after that, so if the paper does get accepted, I shouldn’t need to do anything about it while I’m on leave. 

Something that was only very recently set in motion but that I’m quite excited about is a new study course on AI ethics that I’ve started developing with a couple of colleagues after one of them suggested it, knowing that I’m interested in the subject and have some research background in it. I’ll admit I’m slightly worried about exactly how much extra work I’m taking upon myself, but I have a lot of ideas already, and it should make a nice merit to put in my academic CV. The main thing to keep in mind is that we teach engineering, not philosophy, so we want to keep the scope of the course relatively narrow and down-to-earth: we’ll leave debating AI rights to the more qualified and stick to issues that are relevant to today’s practitioners. After two weeks and three meetings we have a pretty good tentative plan already and will get back to the task of fleshing it out in August. 

On the matter of the Academy of Finland September call I’m still undecided. Should I have another go at the Research Fellow grant? I’m not ruling it out yet, but I’m not going to simply rehash the same basic idea, that much seems clear by now. Last year my proposal in a nutshell was “do what I did in Dublin, scaled up”; that made it relatively easy to write, but in retrospect, and other weaknesses aside, it wasn’t a very novel or ambitious plan from the reviewers’ perspective nor even all that exciting from my own perspective. Of course it still makes sense that I’d build on the results of my MSCA fellowship, but I’ll need to do better than follow it up with more of the same. Currently I only have some fairly vague ideas about what that would mean in terms of writing an actual proposal, but there’s still time to find that inspiration, and I’m pretty sure that the upcoming time off is not going to hurt. 

Job security

There’s an old joke about how you can distinguish between theoretical and practical philosophy: if your degree is in practical philosophy, there are practically no jobs available for you, whereas if it’s in theoretical philosophy, it’s not even theoretically possible for you to find a job. I was reminded of this the other day when I was having a lunchtime chat with a colleague who had recently learned of the existence of a vending machine that bakes and dispenses pizzas on request. From this the conversation moved to the broader theme of machines, and particularly artificial intelligence, taking over jobs that previously only humans could perform, such as those that involve designing artefacts.

A specific job that my colleague brought up was architect: how far away are we from the situation where you can just tell an AI to design a building for a given purpose within given parameters and a complete set of plans will come out? This example is interesting, because in architecture – in some architecture at any rate – engineering meets art: the outcome of the process represents a synthesis of practical problem-solving and creative expression, functionality and beauty. Algorithms are good at exploring solution spaces for quantifiable problems, but quantifying the qualities that a work of art is traditionally expected to exhibit is challenging to say the least. Granted, it’s a bit of a cliché, but how exactly does one measure something as abstract as beauty or elegance?

If we follow this train of thought to its logical conclusion, then it would seem that the last jobs to go would be the ones driven entirely by self-expression: painter, sculptor, writer, composer, actor, singer, comedian… Athlete, too – we still want to see humans perform feats of strength, speed and skill even though a robot could easily outdo the best of us at many of them. In a sense, these might be the only jobs that never can be completely taken over by machines, because potentially every human individual has something totally unique to express (unless we eventually give up our individuality altogether and meld into some kind of collective superconsciousness). However, it’s debatable if the concept of a job would any longer have a recognisable meaning in the kind of post-scarcity utopia seemingly implied by this scenario.

Coming back closer to the present day and my own research on collaborative knowledge discovery, I have actually given some (semi-)serious thought to the idea that one day, perhaps in the not-too-far future, some of the partners in your collaboration may be AI agents instead of human experts. As AIs become capable of handling more and more complex tasks independently, the role of humans in the process shifts toward the determination of what tasks need doing in the first place. Applying AI in the future may therefore be less like engineering and more like management, requiring a skill set that’s rather different from the one required today.

So what do managers do? For one thing, they take responsibility for decisions. Why is this relevant? The case of self-driving cars comes to mind. From a purely utilitarian perspective, autopilots should replace human drivers as soon as it can be shown beyond reasonable doubt that they would make roads safer, but while the possibility remains that an autopilot will make a bad call leading to damage or injury, there are other points of view to consider. Being on the road is always a risk, and it seems to me that our acceptance of that risk is at least partially based on an understanding of the behaviour of the other people we share the road with – a kind of informed consent, so to speak. If an increasing percentage of those other people is replaced by AIs whose decision-making processes may differ radically from those of human drivers, does there come a point where we no longer understand the nature of the risk well enough for our consent to be genuinely informed? Would people prefer a risk that’s statistically higher if they feel more confident about their ability to manage it?

On the other side of the responsibility equation there is the question of who is in fact liable when something bad happens. When it’s all humans making the decisions, we have established processes for finding this out, but things get more complicated when there’s algorithmic decision-making involved, and I would assume that the more severe the damage, the less happy people are going to be to accept a conclusion that nobody’s liable because it was the algorithm’s fault and you can’t prosecute an algorithm. In response to these concerns, the concepts of algorithmic transparency and accountability have been introduced, elements of which can already be seen in enacted or proposed legislation such as the GDPR and the U.S. Algorithmic Accountability Act.

This might seem to be pointing toward a rather bleak future where the only “serious” professional role left for humans is taking the blame when something goes wrong, but I’m more hopeful than that. What else do managers do? They set goals, and I would argue that in a human society this is something that only humans can do, no matter how advanced the technology we have at our disposal for pursuing those goals, because it’s a matter of values, not means. Similarly, it’s ultimately determined by human values whether a given course of action, no matter how effective it would be in achieving a goal, is ethically permissible. In science, for example, we may eventually reach a point where an AI, given a research question, is capable of designing experiments, carrying them out and evaluating the results all by itself, but this still leaves vacancies for people whose job it is to decide what questions are worth asking and how far we are willing to go to get the answers.

Perhaps it’s the philosophers who will have the last laugh after all?