WEBVTT 00:00.000 --> 00:02.000 You 00:30.000 --> 00:32.000 You 01:00.000 --> 01:02.000 You 01:30.000 --> 01:32.000 You 01:40.000 --> 01:42.000 You 02:00.000 --> 02:02.000 You 02:30.000 --> 02:53.000 All right. 02:53.000 --> 02:58.000 Can you hear me? 02:58.000 --> 03:08.000 All right. 03:08.000 --> 03:09.000 All right. 03:09.000 --> 03:11.000 I'm going to start with our next talk. 03:11.000 --> 03:12.000 We have Veronica here. 03:12.000 --> 03:15.000 She's going to tell us a little bit about breaking the gap 03:15.000 --> 03:18.000 and about how classical software development can really be used 03:18.000 --> 03:21.000 a lot and important. 03:21.000 --> 03:23.000 Hi Veronica. 03:23.000 --> 03:24.000 Thank you for being here. 03:24.000 --> 03:26.000 I'm so happy and honored to be here. 03:26.000 --> 03:31.000 Awesome has been probably my favorite conference for many years. 03:31.000 --> 03:36.000 So very happy to present in this room. 03:36.000 --> 03:37.000 So who am I? 03:37.000 --> 03:41.000 I am Veronica Lopizama Distributed Systems Engineer, 03:41.000 --> 03:44.000 but originally I studied physics first. 03:44.000 --> 03:49.000 And then for many personal reasons, I switched into the computer world 03:49.000 --> 03:54.000 or although to be fair, even when I was in the physics world, 03:54.000 --> 04:00.000 I was always spending most of my time on computer land with simulations, 04:00.000 --> 04:03.000 with foretron, then with Python. 04:03.000 --> 04:06.000 And I always gravitated towards there, 04:06.000 --> 04:09.000 but then when I made the decision to switch, 04:09.000 --> 04:12.000 it became mostly computers. 04:12.000 --> 04:17.000 So this was still my student level, 04:17.000 --> 04:20.000 was graduate type of courses. 04:20.000 --> 04:26.000 So as I said, I would look for all the intersections 04:26.000 --> 04:30.000 between physics, maps, and actual computers. 04:30.000 --> 04:34.000 So one time I came across quantum computing. 04:34.000 --> 04:36.000 This was a long time ago. 04:36.000 --> 04:39.000 People usually tell me that I look younger than I am, 04:39.000 --> 04:43.000 so this was over 12 years ago. 04:43.000 --> 04:49.000 So it was very interesting for me that I started exploring 04:49.000 --> 04:52.000 quantum computing from the physics side, 04:52.000 --> 04:56.000 and I'll go back to this. 04:56.000 --> 05:00.000 That the focus and physics from the physics side 05:00.000 --> 05:06.000 was mostly the maps, the logic gates, 05:06.000 --> 05:11.000 all the theory, all the quantum theory. 05:11.000 --> 05:16.000 And then the computing part was like an afterthought. 05:16.000 --> 05:20.000 And then when I switched to computer science, 05:20.000 --> 05:21.000 it was the other way around. 05:21.000 --> 05:25.000 I would still attend the courses and read the papers, 05:25.000 --> 05:28.000 sit the tests, but the focus was completely different. 05:28.000 --> 05:32.000 They did not care that much about the maps. 05:32.000 --> 05:37.000 It was intensive algorithm studies, et cetera, 05:37.000 --> 05:41.000 and just some maps to understand the papers. 05:41.000 --> 05:44.000 But yeah, I think you get the picture. 05:44.000 --> 05:48.000 So it became really evident for me 05:48.000 --> 05:52.000 that whoever would master this area. 05:52.000 --> 05:55.000 I mean, this is in the mind of a silly young students. 05:55.000 --> 05:59.000 Whoever would master this area at some point in time 05:59.000 --> 06:03.000 would have to be good at both disciplines. 06:03.000 --> 06:06.000 Or at least now, in hand side, 06:06.000 --> 06:09.000 I don't think that to be good at quantum computing, 06:09.000 --> 06:11.000 you have to be an expert on both sides, 06:12.000 --> 06:16.000 but at least having notions of what is happening 06:16.000 --> 06:19.000 on the other side of the world. 06:19.000 --> 06:26.000 So going a little bit back, all of the story 06:26.000 --> 06:30.000 and personal anecdotes are literally the thread of this talk. 06:30.000 --> 06:34.000 So bear with me, I have points. 06:34.000 --> 06:38.000 So I'm also a certified young instructor, 06:38.000 --> 06:41.000 and this is very important for all of this 06:41.000 --> 06:45.000 because I am obsessed with interconnectedness 06:45.000 --> 06:51.000 of systems, of particles, of quantum things, of people, 06:51.000 --> 06:56.000 and how some know here, a Kubernetes, 06:56.000 --> 07:00.000 will affect the notes here that we didn't know about. 07:00.000 --> 07:04.000 So that is basically distributed computing. 07:04.000 --> 07:07.000 So fast forward to many years later 07:07.000 --> 07:10.000 that I became a computer scientist 07:10.000 --> 07:13.000 and I started having jobs. 07:13.000 --> 07:18.000 I got very interested in distributed systems. 07:18.000 --> 07:22.000 So that has been my main area. 07:22.000 --> 07:26.000 Nowadays, I work at a company called AudZed. 07:26.000 --> 07:29.000 We have this tool called SpicyB. 07:29.000 --> 07:32.000 Then I'm going to talk about it later. 07:33.000 --> 07:40.000 So this is a bit of the background combined in all these things. 07:40.000 --> 07:51.000 So from time to time, obviously I assume I do not work with 07:51.000 --> 07:56.000 Kubernetes, I do not work with quantum things 07:56.000 --> 08:00.000 directly, at least, but it has always been a passion of mine 08:00.000 --> 08:04.000 to still belong to this world, at least from the sidelines. 08:04.000 --> 08:07.000 So from time to time, I still have all my subscriptions 08:07.000 --> 08:09.000 to the journals and stuff. 08:09.000 --> 08:11.000 So when I am waiting for things to compile, 08:11.000 --> 08:15.000 I go and read little bits of nature and stuff. 08:15.000 --> 08:19.000 So in the past couple of years, 08:19.000 --> 08:22.000 there have been different achievements 08:22.000 --> 08:25.000 and the quantum world, quantum computing world, 08:25.000 --> 08:27.000 especially from Google. 08:27.000 --> 08:32.000 So every time that there is a new milestone 08:32.000 --> 08:34.000 and a new achievement, the way it's communicated 08:34.000 --> 08:36.000 is that, oh, it's this new thing. 08:36.000 --> 08:38.000 I don't even have the words, you know, 08:38.000 --> 08:40.000 but they have to make it sound grand. 08:40.000 --> 08:44.000 For good purposes, but also sometimes it sounds 08:44.000 --> 08:46.000 a bit too pompous. 08:46.000 --> 08:50.000 So I say this with love, 08:50.000 --> 08:55.000 so my colleagues and people that are science 08:55.000 --> 08:58.000 adjacent, meaning that our technical enough 08:58.000 --> 09:01.000 to understand some concepts but who do not have 09:01.000 --> 09:03.000 a background in physics, 09:03.000 --> 09:08.000 usually tend to go by what the marketing 09:08.000 --> 09:10.000 of those announcements go by. 09:10.000 --> 09:13.000 This is important because I'm relevant to this 09:13.000 --> 09:16.000 because every time that there is a new announcement 09:16.000 --> 09:19.000 of quantum computing milestone, people ask me, 09:19.000 --> 09:22.000 oh, is it true that now they prove 09:22.000 --> 09:25.000 that there are multiple universes 09:25.000 --> 09:27.000 existing at the same time? 09:27.000 --> 09:31.000 Is it true that in a certain, 09:31.000 --> 09:34.000 they created a black hole 09:34.000 --> 09:37.000 that people don't know about? 09:37.000 --> 09:40.000 No. 09:40.000 --> 09:44.000 So it's cool when people ask me. 09:44.000 --> 09:47.000 And so then I can go on and tell them, 09:47.000 --> 09:50.000 oh no, I see where you come from, but that's not. 09:50.000 --> 09:54.000 But the issue comes when someone shares 09:54.000 --> 09:58.000 the news article, and I don't know slack, 09:58.000 --> 10:00.000 or whatever, affirming like, 10:00.000 --> 10:03.000 well, see guys, the multiple universe, 10:03.000 --> 10:08.000 theories, proven love, and then I am like, 10:08.000 --> 10:12.000 and sometimes I have the will to explain 10:12.000 --> 10:14.000 most of the time I don't. 10:14.000 --> 10:17.000 So whenever I see things like that, 10:17.000 --> 10:20.000 it prompts me to go and do, 10:20.000 --> 10:23.000 and I don't know, like, do my research again. 10:23.000 --> 10:27.000 So, with all of this, I'm trying to say that 10:27.000 --> 10:30.000 this talk is about my very informed 10:30.000 --> 10:34.000 but still my opinion. 10:34.000 --> 10:38.000 So what I want you to take away from this 10:38.000 --> 10:43.000 is that people from all walks 10:43.000 --> 10:47.000 of technical life can contribute 10:47.000 --> 10:51.000 to the quantum computing world. 10:51.000 --> 10:55.000 Layers of the civilization, like in the classical 10:55.000 --> 10:57.000 computing world, I need it. 10:57.000 --> 11:00.000 So it's okay if you're not good at maths, 11:00.000 --> 11:05.000 but be aware of that you need linear algebra. 11:05.000 --> 11:09.000 Now it's very popular because AI and crypto and all those things. 11:09.000 --> 11:11.000 So learn your AI. 11:11.000 --> 11:13.000 You're linear algebra. 11:13.000 --> 11:15.000 Sorry. 11:15.000 --> 11:19.000 But you don't have to be an expert. 11:19.000 --> 11:22.000 So quantum computing is an isn't 11:22.000 --> 11:25.000 an isolated quantum bubble anymore. 11:25.000 --> 11:29.000 Right now, it's not as if we are going to wake up in 11:29.000 --> 11:34.000 2027 and suddenly say, you know what, guys? 11:34.000 --> 11:36.000 Computers are obsolete now. 11:36.000 --> 11:40.000 We now have to use quantum computers from now on 11:40.000 --> 11:43.000 and whoever does not know the shores algorithm 11:43.000 --> 11:45.000 won't have a job anymore. 11:45.000 --> 11:49.000 I think as the previous talks and the upcoming ones 11:49.000 --> 11:51.000 will explain to you, 11:51.000 --> 11:56.000 that we are already in the middle of a quantum revolution 11:56.000 --> 12:02.000 in computer land where some bits are already in use. 12:02.000 --> 12:05.000 There are some companies in the real world 12:05.000 --> 12:09.000 and Silicon Valley too that are hiring 12:09.000 --> 12:14.000 software engineers for regular software engineering jobs, 12:14.000 --> 12:17.000 for Kubernetes stuff, for database stuff, 12:17.000 --> 12:18.000 for performance stuff. 12:18.000 --> 12:22.000 That don't necessarily require you to have a background 12:22.000 --> 12:25.000 in physics or advanced maths. 12:25.000 --> 12:29.000 So that's a really nice gateway to start there. 12:29.000 --> 12:32.000 I think I would have done that. 12:32.000 --> 12:37.000 And those options been possible back when I was young. 12:37.000 --> 12:41.000 So this is a very silly example for you to understand what I mean 12:41.000 --> 12:43.000 with, this is that continuum. 12:43.000 --> 12:47.000 So for example, IBM Quantum Organizes multiple users jobs 12:47.000 --> 12:49.000 based on priority and availability. 12:49.000 --> 12:53.000 So though the execution is quantum computing, 12:53.000 --> 12:57.000 the priorization of the jobs is handled by an algorithm, 12:57.000 --> 13:00.000 a classical priorization algorithm, you know, 13:00.000 --> 13:01.000 shorting algorithm. 13:01.000 --> 13:05.000 So your job as a software engineer is understanding priorities 13:05.000 --> 13:07.000 like any other system. 13:07.000 --> 13:10.000 Example two, aggregation of results. 13:10.000 --> 13:16.000 Again, how you, in this era, even in classical computing, 13:16.000 --> 13:22.000 having good visualizations, knowing what data is signal, 13:22.000 --> 13:26.000 what data is noise, all that you have to be attuned 13:26.000 --> 13:29.000 to what's important in your system. 13:29.000 --> 13:33.000 So it's no different in a quantum computing system. 13:33.000 --> 13:37.000 And it's even more important because in quantum land, 13:37.000 --> 13:42.000 we will get where more data, way more noise, way more results 13:42.000 --> 13:45.000 that are many times full of noise. 13:45.000 --> 13:48.000 So with your training as a software engineer, 13:48.000 --> 13:53.000 you can actually not only help but tell scientists 13:53.000 --> 13:57.000 how to discern from this thing. 13:57.000 --> 13:58.000 So I have other examples. 13:58.000 --> 14:02.000 But the most important part, and that I took from distributed systems, 14:02.000 --> 14:05.000 is to design for failure. 14:05.000 --> 14:08.000 Because things will fail. 14:08.000 --> 14:13.000 It does not matter how good we are, how many PhDs we have, 14:13.000 --> 14:18.000 how long we've been coding from six years old, whatever. 14:18.000 --> 14:21.000 So this was a critical mindset for me at least, 14:21.000 --> 14:24.000 because I started coding as a scientist, 14:24.000 --> 14:28.000 which meant that my code had to be perfect for the journals, 14:28.000 --> 14:30.000 perfect for the experiments, like one shot. 14:30.000 --> 14:34.000 You had one shot at very sophisticated computers. 14:34.000 --> 14:39.000 I think right now it's a bit like that for like quantum computing 14:39.000 --> 14:42.000 time, it's so precious this day. 14:42.000 --> 14:47.000 But that meant at least in my side of science, 14:47.000 --> 14:50.000 that those algorithms, that code, 14:50.000 --> 14:52.000 we're not always the most efficient, 14:52.000 --> 14:56.000 we're not always the cleanest, we're not always the fastest, 14:56.000 --> 14:58.000 but they had to be accurate. 14:58.000 --> 15:03.000 So when I transitioned into software engineering, 15:03.000 --> 15:08.000 I would try to have a code that was perfect 15:08.000 --> 15:10.000 in terms of like accurate. 15:10.000 --> 15:13.000 But it took me a while to have that. 15:13.000 --> 15:16.000 And if you work in software engineering, 15:16.000 --> 15:17.000 you know like ship ship ship ship, 15:17.000 --> 15:20.000 and I started working in Silicon Valley. 15:20.000 --> 15:23.000 I was like, no, it does not matter if it's horrible, 15:23.000 --> 15:25.000 but it has to. 15:25.000 --> 15:28.000 You have to ship things fast. 15:28.000 --> 15:33.000 So that means that you will fail a lot, 15:33.000 --> 15:35.000 but because of human errors, 15:35.000 --> 15:37.000 but also because distributed systems work like that. 15:37.000 --> 15:40.000 I won't emphasize that more. 15:40.000 --> 15:43.000 So I think that in quantum land, 15:43.000 --> 15:46.000 this is super, super important. 15:47.000 --> 15:51.000 You will see in this life that I'm giving more examples about that. 15:51.000 --> 15:59.000 But the main topic or sub topic about this idea of full tolerance 15:59.000 --> 16:04.000 comes or at least to me comes from the quantum error correction. 16:04.000 --> 16:08.000 That is one of the hardest problems to solve these days, 16:08.000 --> 16:10.000 as you might not or not, 16:10.000 --> 16:13.000 but this can span its own conference. 16:14.000 --> 16:16.000 And with quantum computing, 16:16.000 --> 16:19.000 it's basically the way I see it. 16:19.000 --> 16:22.000 Failure with more errors, 16:22.000 --> 16:26.000 it is very expensive to not only in cash, 16:26.000 --> 16:30.000 but in time and in qubits and stuff to correct this things. 16:30.000 --> 16:36.000 So your experience as a software engineer helps with that. 16:36.000 --> 16:39.000 Last but not least, security. 16:39.000 --> 16:44.000 So every fortnight, we host session on YouTube, 16:44.000 --> 16:48.000 33 from my company, 16:48.000 --> 16:50.000 where people ask different things. 16:50.000 --> 16:52.000 So one, not one time. 16:52.000 --> 16:54.000 A few times people have asked us 16:54.000 --> 16:59.000 if quantum encryption will make our tool obsolete 16:59.000 --> 17:01.000 or similar tools obsolete. 17:01.000 --> 17:03.000 The answer is no. 17:03.000 --> 17:05.000 Well, by the way, 17:05.000 --> 17:09.000 it provides role-based access control. 17:09.000 --> 17:11.000 It's open source. 17:11.000 --> 17:14.000 And we have an annotated paper, 17:14.000 --> 17:17.000 because it's based on Sansubar, 17:17.000 --> 17:18.000 the Google paper, 17:18.000 --> 17:20.000 but since Sansubar, 17:20.000 --> 17:22.000 the code is closed source, 17:22.000 --> 17:25.000 we have to figure out how they did it. 17:25.000 --> 17:29.000 So we have a paper with our annotations, 17:29.000 --> 17:31.000 I recommend you to read it. 17:31.000 --> 17:33.000 So this is just an angel, 17:33.000 --> 17:35.000 but important for my point of, 17:35.000 --> 17:38.000 we'll quantum encryption 17:38.000 --> 17:40.000 make our solutions obsolete. 17:40.000 --> 17:42.000 And the answer is no. 17:42.000 --> 17:44.000 I'm not just because I'm selling that. 17:44.000 --> 17:45.000 Really? 17:45.000 --> 17:49.000 Because we will still have to have role-based access control. 17:49.000 --> 17:53.000 We will still have to need encryption of all sorts. 17:53.000 --> 17:57.000 So what we need to do is evolve with the systems. 17:57.000 --> 18:01.000 Like, adapt the existing algorithms in the classical ones 18:01.000 --> 18:03.000 to interact. 18:03.000 --> 18:06.000 And I have a word that I don't remember, 18:06.000 --> 18:10.000 but converge with the quantum ones. 18:10.000 --> 18:12.000 And eventually, 18:12.000 --> 18:15.000 one of my colleagues likes to say that 18:15.000 --> 18:17.000 as a definition of success in our jobs 18:17.000 --> 18:22.000 is to, when we manage to automate ourselves out of a job. 18:22.000 --> 18:24.000 So, because that meant that we really 18:24.000 --> 18:27.000 understood the assignment we were efficient, 18:27.000 --> 18:29.000 we executed, and we do well. 18:29.000 --> 18:31.000 So, we can only dream of the day 18:31.000 --> 18:34.000 where quantum computing tasks are 18:34.000 --> 18:38.000 automatable and not without errors, 18:38.000 --> 18:41.000 but managed errors so that they can grow 18:41.000 --> 18:47.000 and have real usage in the world at scale. 18:47.000 --> 18:51.000 So, I hope you found this useful. 18:51.000 --> 18:53.000 If you have any questions, 18:53.000 --> 18:55.000 I am on Blue Sky. 18:55.000 --> 18:58.000 Also, you can write me an email. 18:58.000 --> 19:00.000 And if you have the time and you like it, 19:00.000 --> 19:02.000 please give us a star and spy ZB. 19:02.000 --> 19:04.000 And I'm happy to chat here 19:04.000 --> 19:06.000 or afterwards on the internet. 19:06.000 --> 19:08.000 Thank you very much. 19:08.000 --> 19:09.000 Thank you very much. 19:15.000 --> 19:17.000 I have time for one question. 19:17.000 --> 19:20.000 Or, yeah, one question? 19:20.000 --> 19:21.000 No. 19:21.000 --> 19:22.000 Yeah, hope it there. 19:24.000 --> 19:26.000 There is no microphone. 19:50.000 --> 19:51.000 Thank you. 19:53.000 --> 19:55.000 I'm a general manager. 19:55.000 --> 19:59.000 So, what would you suggest to get started 19:59.000 --> 20:01.000 in programming some basic 20:01.000 --> 20:04.000 future for older languages? 20:04.000 --> 20:05.000 Yeah, in the slides.