>>Hey, everyone. Welcome to the cubes coverage of women in data science, 2022. I'm Lisa Martin. And I'm here with one of the key featured keynotes for this year is with events. So the Aragon, the professor and department of human centered design and engineering at the university of Washington Cecilia, it's a pleasure to have you on the cube. >>Thank you so much, Lisa Lisa, it's a pleasure to be here as well. >>You got an amazing background that I want to share with the audience. You are a professor, you are a data scientist, an aerobatic pilot, and an author with expertise in human centered, data science, visual analytics, aviation safety, and analysis of extremely large and complex data sets. That's quite the background. >>Well, thank you so much. It's it's all very interesting and fun. So, >>And as a professor, you study how people make sense of vast data sets, including a combination of computer science and art, which I love. And as an author, you write about interesting things. You write about how to overcome fear, which is something that everybody can benefit from and how to expand your life until it becomes amazing. I need to take a page out of your book. You were also honored by president Obama a few years back. My goodness. >>Thank you so much. Yes. I I've had quite a journey to come here, but I feel really fortunate to be here today. >>Talk about that journey. I'd love to understand if you were always interested in stem, if it was something that you got into later, I know that you are the co-founder of Latinas in computing, a passionate advocate for girls and women in stem. Were you always interested in stem or was it something that you got into in a kind of a non-linear path? >>I was always interested in it when I was a young girl. I grew up in a small Midwestern town and my parents are both immigrants and I was one of the few Latinas in a mostly white community. And I was, um, I loved math, but I also wanted to be an astronaut. And I remember I, when we were asked, I think it was in second grade. What would you like to be when you grow up? I said, oh, I want to be an astronaut. And my teacher said, oh, you can't do that. You're a girl pick something else. And um, so I picked math and she was like, okay. >>Um, so I always wanted to, well, maybe it would be better to say I never really quite lost my love of being up in the air and potentially space. But, um, but I ended up working in math and science and, um, I, I loved it because one of the great advantages of math is that it's kind of like a magic trick for young people, especially if you're a girl or if you are from an underrepresented group, because if you get the answers right on a math test, no one can mark you wrong. It doesn't matter what the color of your skin is or what your gender is. Math is powerful that way. And I will say there's nothing like standing in a room in front of a room of people who think little of you and you silence them with your love with numbers. >>I love that. I never thought about math as power before, but it clearly is. But also, you know, and, and I wish we had more time because I would love to get into how you overcame that fear. And you write books about that, but being told you can't be an astronaut. You're a girl and maybe laughing at you because you liked Matt. How did you overcome that? And so nevermind I'm doing it anyway. >>Well, that's a, it's a, okay. The short answer is I had incredible imposter syndrome. I didn't believe that I was smart enough to get a PhD in math and computer science. But what enabled me to do that was becoming a pilot and I B I learned how to fly small airplanes. I learned how to fly them upside down and pointing straight at the ground. And I know this might sound kind of extreme. So this is not what I recommend to everybody. But if you are brought up in a way where everybody thinks little of you, one of the best things you can possibly do is take on a challenge. That's scary. I was afraid of everything, but by learning to fly and especially learning to fly loops and rolls, it gave me confidence to do everything else because I thought I appointed the airplane at the ground at 250 miles an hour and waited, why am I afraid to get a PhD in computer science? >>Wow. How empowering is that? >>Yeah, it really was. So that's really how I overcame the fear. And I will say that, you know, I encountered situations getting my PhD in computer science where I didn't believe that I was good enough to finish the degree. I didn't believe that I was smart enough. And what I've learned later on is that was just my own emotional, you know, residue from my childhood and from people telling me that they, you know, that they, that I couldn't achieve >>As I look what, look what you've achieved so far. It's amazing. And we're going to be talking about some of the books that you've written, but I want to get into data science and AI and get your thoughts on this. Why is it necessary to think about human issues and data science >>And what are your thoughts there? So there's been a lot of work in data science recently looking at societal impacts. And if you just address data science as a purely technical field, and you don't think about unintended consequences, you can end up with tremendous injustices and societal harms and harms to individuals. And I think any of us who has dealt with an inflexible algorithm, even if you just call up, you know, customer service and you get told, press five for this press four for that. And you say, well, I don't fit into any of those categories, you know, or have the system hang up on you after an hour. I think you'll understand that any type of algorithmic approach, especially on very large data sets has the risk of impacting people, particularly from low income or marginalized groups, but really any of us can be impacted in a negative way. >>And so, as a developer of algorithms that work over very large data sets, I've always found it really important to consider the humans on the other end of the algorithm. And that's why I believe that all data science is truly human centered or should be human centered, should be human centered and also involves both technical issues as well as social issues. Absolutely correct. So one example is that, um, many of us who started working in data science, including I have to admit me when I started out assume that data is unbiased. It's scrubbed of human influence. It is pure in some ways, however, that's really not true as I've started working with datasets. And this is generally known in the field that data sets are touched by humans everywhere. As a matter of fact, in our, in the recent book that we're, that we're coming out with human centered data science, we talk about five important points where humans touch data, no matter how scrubbed of human influence it's support it's supposed to be. >>Um, so the first one is discovery. So when a human encounters, a data set and starts to use it, it's a human decision. And then there's capture, which is the process of searching for a data set. So any data that has to be selected and chosen by an individual, um, then once that data set is brought in there's curation, a human will have to select various data sets. They'll have to decide what is, what is the proper set to use. And they'll be making judgements on this the time. And perhaps one of the most important ways the data is changed and touched by humans is what we call the design of data. And what that means is whenever you bring in a data set, you have to categorize it. No, for example, let's suppose you are, um, a geologist and you are classifying soil data. >>Well, you don't just take whatever the description of the soil data is. You actually may put it into a previously established taxonomy and you're making human judgments on that. So even though you think, oh, geology data, that's just rocks. You know, that's soil. It has nothing to do with people, but it really does. Um, and finally, uh, people will label the data that they have. And this is especially critical when humans are making subjective judgments, such as what race is the person in this dataset. And they may judge it based on looking at the individual skin color. They may try to apply an algorithm to it, but you know what? We all have very different skin colors, categorizing us into race boxes, really diminishes us and makes us less than we truly are. So it's very important to realize that humans touch the data. We interpret the data. It is not scrubbed of bias. And when we make algorithmic decisions, even the very fact of having an algorithm that makes a judgment say on whether a prisoner's likely to offend again, the judge just by having an algorithm, even if the algorithm makes a recommended statement, they are impacted by that algorithms recommendation. And that has obviously an impact on that human's life. So we consider all of this. >>So you just get given five solid reasons why data science and AI are inevitably human centric should be, but in the past, what's led to the separation between data science and humans. >>Well, I think a lot of it simply has to do with incorrect mental models. So many of us grew up thinking that, oh, humans have biases, but computers don't. And so if we just take decision-making out of people's hands and put it into the hands of an algorithm, we will be having less biased results. However, recent work in the field of data science and artificial intelligence has shown that that's simply not true that algorithmic algorithms reinforce human biases. They amplify them. So algorithmic biases can be much worse than human biases and can greater impact. >>So how do we pull ethics into all of this data science and AI and that ethical component, which seems to be that it needs to be foundational. >>It absolutely has to be foundational. And this is why we believe. And what we teach at the university of Washington in our data science courses is that ethical and human centered approaches and ideas have to be brought in at the very beginning of the algorithm. It's not something you slap on at the end or say, well, I'll wait for the ethicists to weigh in on this. Now we are all human. We can all make human decisions. We can all think about the unintended consequences of our algorithms as we develop them. And we should do that at the very beginning. And all algorithm designers really need to spend some time thinking about the impact that their algorithm may have. >>Right. Do you, do you find that people are still in need of convincing of that or is it generally moving in that direction of understanding? We need to bring ethics in from the beginning, >>It's moving in that direction, but there are still people who haven't modified their mental models yet. So we're working on it. And we hope that with the publication of our book, that it will be used as a supplemental textbook in many data science courses that are focused exclusively on the algorithms and that they can open up the idea that considering the human centered approaches at the beginning of learning about algorithms and data science and the mathematical and statistical techniques, that the next generation of data scientists and artificial intelligence developers will be able to mitigate some of the potentially harmful effects. And we're very excited about this. This is why I'm a professor, because I want to teach the next generation of data scientists and artificial intelligence experts, how to make sure that their work really achieves what they intended it to, which is to make the world a better place, not a worse place, but to enable humans to do better and to mitigate biases and really to lead us into this century in a positive way. >>So the book, human centered data science, you can see it there over Sicily, his right shoulder. When does this come out and how can folks get a copy of it? >>So it came out March 1st and it's available in bookstores everywhere. It was published by MIT press, and you can go online or you can go to your local independent bookstore, or you can order it from your university bookstore as well. >>Excellent. Got to, got to get a copy of, get my hands on that. Got cut and get a copy and dig into that. Cause it sounds so interesting, but also so thoughtful and, um, clear in the way that you described that. And also all the opportunities that, that AI data science and humans are gonna unlock for the world and humans and jobs and, and great things like that. So I'm sure there's lots of great information there. Last question I mentioned, you are keynoting at this year's conference. Talk to me about like the top three takeaways that the audience is going to get from your keynote. >>So I'm very excited to have been invited to wins this year, which of course is a wonderful conference to support women in data science. And I've been a big fan of the conference since it was first developed here, uh, here at Stanford. Um, the three, the three top takeaways I would say is to really consider the data. Science can be rigorous and mathematical and human centered and ethical. It's not a trade-off, it's both at the same time. And that's really the, the number one that, that I'm hoping to keynote will bring to, to the entire audience. And secondly, I hope that it will encourage women or people who've been told that maybe you're not a science person or this isn't for you, or you're not good at math. I hope it will encourage them to disbelieve those views. And to realize that if you, as a member of any type of unread, underrepresented group have ever felt, oh, I'm not good enough for this. >>I'm not smart enough. It's not for me that you will reconsider because I firmly believe that everyone can be good at math. And it's a matter of having the information presented to you in a way that honors your, the background you had. So when I started out my, my high school didn't have AP classes and I needed to learn in a somewhat different way than other people around me. And it's really, it's really something. That's what I tell young people today is if you are struggling in a class, don't think it's because you're not good enough. It might just be that the teacher is not presenting it in a way that is best for someone with your particular background. So it doesn't mean they're a bad teacher. It doesn't mean you're unintelligent. It just means the, maybe you need to find someone else that can explain it to you in a simple and clear way, or maybe you need to get some scaffolding that is Tate, learn extra, take extra classes that will help you. Not necessarily remedial classes. I believe very strongly as a teacher in giving students very challenging classes, but then giving them the scaffolding so that they can learn that difficult material. And I have longer stories on that, but I think I've already talked a bit too long. >>I love that. The scaffolding, I th I think the, the one, one of the high level takeaways that we're all going to get from your keynote is inspiration. Thank you so much for sharing your path to stem, how you got here, why humans, data science and AI are, have to be foundationally human centered, looking forward to the keynote. And again, Cecilia, Aragon. Thank you so much for spending time with me today. >>Thank you so much, Lisa. It's been a pleasure, >>Likewise versus silly Aragon. I'm Lisa Martin. You're watching the cubes coverage of women in data science, 2022.

(energetic music) >> Announcer: Live, from Stanford University in Palo Alto, California, it's The Cube, covering Women in Data Science Conference 2018. Brought to you by Stanford. >> Welcome back to The Cube. We are live at Stanford University at the third annual Women in Data Science Conference. I am Lisa Martin. We've had a really exciting day so far, talking with a lot of female leaders in different parts of STEM fields. And I'm excited to be joined by my next guest, who is a speaker at this year's WIDS 2018 event, Daniela Witten, the Associate Professor of Statistics and Biostatistics at the University of Washington. Daniela, thanks so much for stopping by The Cube. >> Oh, thanks so much for the invitation. >> So here we are at Stanford University. You spent quite a lot of time here. You've got three degrees from Stanford, so it's kind of like coming back home? >> Yeah, I've spent from 2001 to 2010 here. I started with a bachelor's degree in math and biology, and then I did a master's, and finally a PhD in statistics. >> And so now you're up at the University of Washington. Tell us about that. What is your focus there? >> Yeah, so my work is in statistical machine learning, with applications to large scale data coming out of biology. And so the idea is that in the last ten or 20 years, the field of biology has been totally transformed by new technologies that make it possible to measure a person's DNA sequence, or to see the activity in their brain. Really, all different types of measurements that would have been unthinkable just a few years ago. But unfortunately, we don't yet know really how to make sense of these data statistically. So there's a pretty big gap between the data that we're collecting, or rather, the data that biologists are collecting, and then the scientific conclusions that we can draw from these data. So my work focuses on trying to bridge this gap by developing statistical methods that we can use to make sense of this large scale data. >> That sounds exciting. So, WIDS, this is the third year, and they have grown this event remarkably quickly. So, we had Margot Garritsen on the program a little bit earlier, and she had shared 177 regional WIDS events going on today, this week, in 53 countries. And they're expecting to reach 100,000 people. So, for you, as a speaker, what is it that attracted you to participate in the WIDS movement, and share your topic, which we'll get to in a second, what was it that sort of attracted you to that? >> Well, first of all, it's an honor to be invited to participate in this event, which, as you mentioned, is getting live streamed and so many people are watching. But what's really special for me, of course, as a woman, is that there's so many conferences out there that I speak at, and the vast majority have a couple of female speakers, and it's not because there's a lack of talent. There are plenty of very qualified women who could be speaking at these conferences. But often, the conference organizers just don't think of women right away, or maybe add a couple women as an afterthought to their speaker lineups. And so it's really wonderful to be part of a conference where all of the speakers are women, and so we can really see the broad ways in which women are contributing to data science, both in and out of industry. >> And one of the things that Margot shared was, she had this idea with her co-founders only three years ago in 2015, and they got from concept to their first event in six months. >> Daniela: Women know how to get things done. >> We do, don't we? (laughs) But also what it showed, and even in 2015, and we still have this problem in 2018, is there's a massive demand for this. >> Yeah. >> The statistics, speaking of statistics, the numbers show very few women that are getting degrees in STEM subjects are actually working in their field. I just saw this morning, it's really cool, interactive infographic that someone shared with me on Twitter, thank you very much, that showed that 20 percent of females get degrees in engineering, but only 11 percent of them are working in engineering. And you think, "How have we gone backwards in the last 30 years?" But at least now we've got this movement, this phenomenon that is WIDS to start, even from an awareness perspective, of showing we don't have a lot of thought diversity. We have a great opportunity to increase that, and you've got a great platform in order to share your story. >> Yeah. Well, I think that you raise a good point though, as, even though the number of women majoring in STEM fields, at least in some areas of STEM has increased, the number of women making it higher up in the STEM ladder hasn't, for the most part. And one reason for this is possibly the lack of female role models. So being able to attend a conference like this, for young women who are interested in developing their career in STEM, I'm sure is really inspirational and a great opportunity. So it's wonderful for Margot and the other organizers to have put this together. >> It is. Even on the recruiting side, some of the things that still surprise me are when some, whether it's universities or companies that are going to universities to recruit for STEM roles, they're still bringing mostly men. And if there are females at the events, they're, often times they're handing out swag, they're doing more event coordination, which is great. I'm a marketer. There's a lot of females in marketing. But it still shows the need to start from a visibility standpoint and a messaging standpoint alone. They've got to flip this. >> I completely agree with that, but it also works the other way. So, often a company or an academic department might have a few women in a particular role, and those women get asked to do everything. Because they'll say, "Oh, we're going to Stanford to recruit. We need a woman there. We're having some event, and we don't want it to look totally non-diverse, so we need a woman there too." And the small number of women in STEM get asked to do a lot of things that the men don't get asked to do, and this can also be really problematic. Even though the intent is good, to clearly showcase the fact that there's diversity in STEM and in academia, the end outcome can actually be hurtful to the women involved who are being asked to do more than their fair share. So we need to find a way to balance this. >> Right. That balance is key. So what I want to kind of pivot on next is, just looking at the field of data science, it's so interesting because it's very, I like 'cause it's horizontal. We just had a guest on from Uber, and we talk to on The Cube, people in many different industries, from big tech to baseball teams and things like that. And what it really shows, though, is, there's blurred lines, or maybe even lines that have evaporated between demarcated career A, B, C, D. And data science is so pervasive that it's impacting, people that are working in it, like yourself, have the ability to impact every sector, policy changes, things like that. Do you think that that message is out there enough? That the next generation understands how much impact they can make in data science? >> I think there is a lot of excitement from young people about data science. At U-dub, we have a statistics major, and it's really grown a lot in popularity in the last few years. We have a new master's degree in data science that just was started around the same time that WIDS was started, and we had 800 applicants this year. >> Wow. >> For a single masters program. Truly incredible. But I think that there's an element of it that also maybe people don't realize. So data science, there's a technical skill set that comes with it, and people are studying undergrad in statistics, and getting master's in data science in order to get that technical skill set. But there's also a non-technical skill set that's incredibly important, because data science isn't done in a vacuum. It's done within the context of interdisciplinary teams with team members from all different areas. So, for example, in my work, I work with biologists. Your previous guest from Uber, I'm sure is working with engineers and all different areas of the company. And in order to be successful in data science, you need to really not only have technical skills, but also the ability to work as a team player and to communicate your ideas. >> Yeah, you're right. Balancing those technical skills with, what some might call soft skills, empathy, collaboration, the ability to communicate, seems to be, we talked about balance earlier, a scale-wise. Would you say they're pretty equivalent, in terms of really, that would give somebody a great foundation as a data scientist? >> I would say that having both of those skill sets would give you a good foundation, yes. The extent to which either one is needed probably depends on the details of your job. >> True. So, I want to talk a little bit more about your background. Something that caught my eye was that your work has been featured in popular media. Forbes, three times, and Elle magazine, which of course, I thought, "What? I've got to talk to you about that!" Tell me a little bit about the opportunities that you've had in Forbes and in Elle magazine to share your story and to be a mentor. >> Yeah. Well, I've just been lucky to be getting involved in the field of statistics at a time when statistics is really growing in importance and interest. So the joke is, that ten years ago, if you went to a cocktail party, and you said that you were a statistician, then nobody would want to talk to you. (Lisa laughs) And now, if you go to a cocktail party and you say you're a statistician, everyone wants to know more and find out if you know of any job openings for them. >> Lisa: That's pretty cool! >> Yeah. So it's a really great time to be doing this kind of work. And there's really an increased appreciation for the fact that it's not enough to have access to a lot of data, but we really need the technical skills to make sense of that data. >> Right. So share with us a little bit about the session that you're doing here: More Data, More Statistical Problems. Tell us a little bit about that and maybe some of the three, what are the three key takeaways that the audience was hearing from you? >> Yeah. So I think the first real takeaway is, sometimes there's a feeling that, when we have a lot of data, we don't really need a deep understanding of statistics, we just need to know how to do machine learning, or how to develop a black box predictor. And so, the first point that I wanted to make is that that's not really right. Actually, the more data you have, often the more opportunity there is for your analysis to go awry, if you don't really have the solid foundations. Another point that I wanted to make is that there's been a lot of excitement about the promise of biology. So, a lot of my work has biomedical applications, and people have been hoping for many years that the new technologies that have come out in recent years in biology, would lead to improve understanding of human health and improve treatment of disease. And, it turns out, that it hasn't, at least not yet. We've got the data, but what we don't know how to do is how to analyze it yet. And so, the real gap between the data that we have and achieving its promise is actually a statistical gap. So there's a lot of opportunity for statisticians to help bridge that gap, in order to improve human health. And finally, the last point that I want to make is that a lot of these issues are really subtle. So we can try to just swing a hammer at our data and hope to get something out of it, but often there's subtle statistical issues that we need to think about, that could very much affect our results. And keeping in mind sort of the effects of our models, and some of these subtle statistical issues is very important. >> So, in terms of your team at University of Washington, or your classes that you teach, you work with undergrads. >> Yeah, I teach undergrads and PhD students, and I work mostly with PhD students. And I've just been lucky to work with incredibly talented students. I did my PhD here at Stanford, and I had a great advisor and really wonderful mentoring from my advisor and from the other faculty in the department. And so it's really great to have the opportunity now, in turn, to mentor grad students at University of Washington. >> What are some of the things that you help them with? Is it, we talk about inspiring women to get into the field, but, as you prepare these grad students to finish their master's or PhD's, and then go out either into academia or in industry, what are some of the other elements that you think is important for them to understand in terms of learning how to be assertive, or make their points in a respectful, professional way? Is that part of what you help them understand and achieve? >> That's definitely part of it. I would say another thing that I try to teach them, so everyone who I work with, all my students, they're incredibly strong technically, because you don't get into a top PhD program in statistics or biostatistics if you're not technically very strong, so what I try to help my students do is figure out not just how to solve problems, because they can solve any problem they set their mind to, but actually how to identify the problems that are likely to be high impact. Because there's so many problems out there that you can try to solve statistically, and, of course, we should all be focusing our efforts on the ones that are likely to have a really big impact on society, or on health, or whatever it is that we're trying to influence. >> Last question for you. If you look back to your education to now, what advice would you give your younger self? >> Gosh, that's a really great question. I think that I'm happy with many of the career decisions I've made. For example, getting a PhD in statistics, I think is a great career move. But, at the same time, maybe I would tell a younger version of me to take more risks, and not be so worried about meeting every requirement on time, and instead, expanding a little bit, taking more courses in other areas, and really broadening instead of just deepening my skill set. >> We've heard that sentiment echoed a number of times today, and one of the themes that I'm hearing a lot is don't be afraid to get out of your comfort zone. And it's so hard for us when we're in it, when we're younger, 'cause you don't know that, you don't have any experience there. But it's something that I always appreciate hearing from the women who've kind of led the way for those of us and then, the next generation, is, don't be afraid to get comfortably uncomfortable and as you said, take risks. It's not a bad thing, right? Well, Daniela, thanks so much for carving out some time to visit us on The Cube, and we're happy to have given you the opportunity to reach an even bigger audience with your message, and we wish you continued success at U-dub. >> Oh, thanks so much. >> We want to thank you for watching. I'm Lisa Martin live with The Cube at WIDS 2018 from Stanford University. Stick around, I'll be back with my next guest after a short break. (energetic music)

(gentle music) >> Hey! Welcome back to theCUBE's coverage of WiDS 2023, the eighth Annual Women In Data Science Conference. I'm your host, Lisa Martin. We are at Stanford University, as you know we are every year, having some wonderful conversations with some very inspiring women and men in data science and technical roles. I'm very pleased to introduce Tracy Zhang, my co-host, who is in the Data Journalism program at Stanford. And Tracy and I are pleased to welcome our next guest, Rhonda Crate, Principal Data Scientist at Boeing. Great to have you on the program, Rhonda. >> Tracy: Welcome. >> Hey, thanks for having me. >> Were you always interested in data science or STEM from the time you were young? >> No, actually. I was always interested in archeology and anthropology. >> That's right, we were talking about that, anthropology. Interesting. >> We saw the anthropology background, not even a bachelor's degree, but also a master's degree in anthropology. >> So you were committed for a while. >> I was, I was. I actually started college as a fine arts major, but I always wanted to be an archeologist. So at the last minute, 11 credits in, left to switch to anthropology. And then when I did my master's, I focused a little bit more on quantitative research methods and then I got my Stat Degree. >> Interesting. Talk about some of the data science projects that you're working on. When I think of Boeing, I always think of aircraft. But you are doing a lot of really cool things in IT, data analytics. Talk about some of those intriguing data science projects that you're working on. >> Yeah. So when I first started at Boeing, I worked in information technology and data analytics. And Boeing, at the time, had cored up data science in there. And so we worked as a function across the enterprise working on anything from shared services to user experience in IT products, to airplane programs. So, it has a wide range. I worked on environment health and safety projects for a long time as well. So looking at ergonomics and how people actually put parts onto airplanes, along with things like scheduling and production line, part failures, software testing. Yeah, there's a wide spectrum of things. >> But I think that's so fantastic. We've been talking, Tracy, today about just what we often see at WiDS, which is this breadth of diversity in people's background. You talked about anthropology, archeology, you're doing data science. But also all of the different opportunities that you've had at Boeing. To see so many facets of that organization. I always think that breadth of thought diversity can be hugely impactful. >> Yeah. So I will say my anthropology degree has actually worked to my benefit. I'm a huge proponent of integrating liberal arts and sciences together. And it actually helps me. I'm in the Technical Fellowship program at Boeing, so we have different career paths. So you can go into management, you can be a regular employee, or you can go into the Fellowship program. So right now I'm an Associate Technical Fellow. And part of how I got into the Fellowship program was that diversity in my background, what made me different, what made me stand out on projects. Even applying a human aspect to things like ergonomics, as silly as that sounds, but how does a person actually interact in the space along with, here are the actual measurements coming off of whatever system it is that you're working on. So, I think there's a lot of opportunities, especially in safety as well, which is a big initiative for Boeing right now, as you can imagine. >> Tracy: Yeah, definitely. >> I can't go into too specifics. >> No, 'cause we were like, I think a theme for today that kind of we brought up in in all of our talk is how data is about people, how data is about how people understand the world and how these data can make impact on people's lives. So yeah, I think it's great that you brought this up, and I'm very happy that your anthropology background can tap into that and help in your day-to-day data work too. >> Yeah. And currently, right now, I actually switched over to Strategic Workforce Planning. So it's more how we understand our workforce, how we work towards retaining the talent, how do we get the right talent in our space, and making sure overall that we offer a culture and work environment that is great for our employees to come to. >> That culture is so important. You know, I was looking at some anitab.org stats from 2022 and you know, we always talk about the number of women in technical roles. For a long time it's been hovering around that 25% range. The data from anitab.org showed from '22, it's now 27.6%. So, a little increase. But one of the biggest challenges still, and Tracy and I and our other co-host, Hannah, have been talking about this, is attrition. Attrition more than doubled last year. What are some of the things that Boeing is doing on the retention side, because that is so important especially as, you know, there's this pipeline leakage of women leaving technical roles. Tell us about what Boeing's, how they're invested. >> Yeah, sure. We actually have a publicly available Global Diversity Report that anybody can go and look at and see our statistics for our organization. Right now, off the top of my head, I think we're hovering at about 24% in the US for women in our company. It has been a male majority company for many years. We've invested heavily in increasing the number of women in roles. One interesting thing about this year that came out is that even though with the great resignation and those types of things, the attrition level between men and women were actually pretty close to being equal, which is like the first time in our history. Usually it tends on more women leaving. >> Lisa: That's a good sign. >> Right. >> Yes, that's a good sign. >> And we've actually focused on hiring and bringing in more women and diversity in our company. >> Yeah, some of the stats too from anitab.org talked about the increase, and I have to scroll back and find my notes, the increase in 51% more women being hired in 2022 than 2021 for technical roles. So the data, pun intended, is showing us. I mean, the data is there to show the impact that having females in executive leadership positions make from a revenue perspective. >> Tracy: Definitely. >> Companies are more profitable when there's women at the head, or at least in senior leadership roles. But we're seeing some positive trends, especially in terms of representation of women technologists. One of the things though that I found interesting, and I'm curious to get your thoughts on this, Rhonda, is that the representation of women technologists is growing in all areas, except interns. >> Rhonda: Hmm. >> So I think, we've got to go downstream. You teach, I have to go back to my notes on you, did my due diligence, R programming classes through Boeings Ed Wells program, this is for WSU College of Arts and Sciences, talk about what you teach and how do you think that intern kind of glut could be solved? >> Yeah. So, they're actually two separate programs. So I teach a data analytics course at Washington State University as an Adjunct Professor. And then the Ed Wells program is a SPEEA, which is an Aerospace Union, focused on bringing up more technology and skills to the actual workforce itself. So it's kind of a couple different audiences. One is more seasoned employees, right? The other one is our undergraduates. I teach a Capstone class, so it's a great way to introduce students to what it's actually like to work on an industry project. We partner with Google and Microsoft and Boeing on those. The idea is also that maybe those companies have openings for the students when they're done. Since it's Senior Capstone, there's not a lot of opportunities for internships. But the opportunities to actually get hired increase a little bit. In regards to Boeing, we've actually invested a lot in hiring more women interns. I think the number was 40%, but you'd have to double check. >> Lisa: That's great, that's fantastic. >> Tracy: That's way above average, I think. >> That's a good point. Yeah, it is above average. >> Double check on that. That's all from my memory. >> Is this your first WiDS, or have you been before? >> I did virtually last year. >> Okay. One of the things that I love, I love covering this event every year. theCUBE's been covering it since it's inception in 2015. But it's just the inspiration, the vibe here at Stanford is so positive. WiDS is a movement. It's not an initiative, an organization. There are going to be, I think annually this year, there will be 200 different events. Obviously today we're live on International Women's Day. 60 plus countries, 100,000 plus people involved. So, this is such a positive environment for women and men, because we need everybody, underrepresented minorities, to be able to understand the implication that data has across our lives. If we think about stripping away titles in industries, everybody is a consumer, not everybody, most of mobile devices. And we have this expectation, I was in Barcelona last week at a Mobile World Congress, we have this expectation that we're going to be connected 24/7. I can get whatever I want wherever I am in the world, and that's all data driven. And the average person that isn't involved in data science wouldn't understand that. At the same time, they have expectations that depend on organizations like Boeing being data driven so that they can get that experience that they expect in their consumer lives in any aspect of their lives. And that's one of the things I find so interesting and inspiring about data science. What are some of the things that keep you motivated to continue pursuing this? >> Yeah I will say along those lines, I think it's great to invest in K-12 programs for Data Literacy. I know one of my mentors and directors of the Data Analytics program, Dr. Nairanjana Dasgupta, we're really familiar with each other. So, she runs a WSU program for K-12 Data Literacy. It's also something that we strive for at Boeing, and we have an internal Data Literacy program because, believe it or not, most people are in business. And there's a lot of disconnect between interpreting and understanding data. For me, what kind of drives me to continue data science is that connection between people and data and how we use it to improve our world, which is partly why I work at Boeing too 'cause I feel that they produce products that people need like satellites and airplanes, >> Absolutely. >> and everything. >> Well, it's tangible, it's relatable. We can understand it. Can you do me a quick favor and define data literacy for anyone that might not understand what that means? >> Yeah, so it's just being able to understand elements of data, whether that's a bar chart or even in a sentence, like how to read a statistic and interpret a statistic in a sentence, for example. >> Very cool. >> Yeah. And sounds like Boeing's doing a great job in these programs, and also trying to hire more women. So yeah, I wanted to ask, do you think there's something that Boeing needs to work on? Or where do you see yourself working on say the next five years? >> Yeah, I think as a company, we always think that there's always room for improvement. >> It never, never stops. >> Tracy: Definitely. (laughs) >> I know workforce strategy is an area that they're currently really heavily investing in, along with safety. How do we build safer products for people? How do we help inform the public about things like Covid transmission in airports? For example, we had the Confident Traveler Initiative which was a big push that we had, and we had to be able to inform people about data models around Covid, right? So yeah, I would say our future is more about an investment in our people and in our culture from my perspective >> That's so important. One of the hardest things to change especially for a legacy organization like Boeing, is culture. You know, when I talk with CEO's or CIO's or COO's about what's your company's vision, what's your strategy? Especially those companies that are on that digital journey that have no choice these days. Everybody expects to have a digital experience, whether you're transacting an an Uber ride, you're buying groceries, or you're traveling by air. That culture sounds like Boeing is really focused on that. And that's impressive because that's one of the hardest things to morph and mold, but it's so essential. You know, as we look around the room here at WiDS it's obviously mostly females, but we're talking about women, underrepresented minorities. We're talking about men as well who are mentors and sponsors to us. I'd love to get your advice to your younger self. What would you tell yourself in terms of where you are now to become a leader in the technology field? >> Yeah, I mean, it's kind of an interesting question because I always try to think, live with no regrets to an extent. >> Lisa: I like that. >> But, there's lots of failures along the way. (Tracy laughing) I don't know if I would tell myself anything different because honestly, if I did, I wouldn't be where I am. >> Lisa: Good for you. >> I started out in fine arts, and I didn't end up there. >> That's good. >> Such a good point, yeah. >> We've been talking about that and I find that a lot at events like WiDS, is women have these zigzaggy patterns. I studied biology, I have a master's in molecular biology, I'm in media and marketing. We talked about transportable skills. There's a case I made many years ago when I got into tech about, well in science you learn the art of interpreting esoteric data and creating a story from it. And that's a transportable skill. But I always say, you mentioned failure, I always say failure is not a bad F word. It allows us to kind of zig and zag and learn along the way. And I think that really fosters thought diversity. And in data science, that is one of the things we absolutely need to have is that diversity and thought. You know, we talk about AI models being biased, we need the data and we need the diverse brains to help ensure that the biases are identified, extracted, and removed. Speaking of AI, I've been geeking out with ChatGPT. So, I'm on it yesterday and I ask it, "What's hot in data science?" And I was like, is it going to get that? What's hot? And it did it, it came back with trends. I think if I ask anything, "What's hot?", I should be to Paris Hilton, but I didn't. And so I was geeking out. One of the things I learned recently that I thought was so super cool is the CTO of OpenAI is a woman, Mira Murati, which I didn't know until over the weekend. Because I always think if I had to name top females in tech, who would they be? And I always default to Sheryl Sandberg, Carly Fiorina, Susan Wojcicki running YouTube. Who are some of the people in your history, in your current, that are really inspiring to you? Men, women, indifferent. >> Sure. I think Boeing is one of the companies where you actually do see a lot of women in leadership roles. I think we're one of the top companies with a number of women executives, actually. Susan Doniz, who's our Chief Information Officer, I believe she's actually slotted to speak at a WiDS event come fall. >> Lisa: Cool. >> So that will be exciting. Susan's actually relatively newer to Boeing in some ways. A Boeing time skill is like three years is still kind of new. (laughs) But she's been around for a while and she's done a lot of inspiring things, I think, for women in the organization. She does a lot with Latino communities and things like that as well. For me personally, you know, when I started at Boeing Ahmad Yaghoobi was one of my mentors and my Technical Lead. He came from Iran during a lot of hard times in the 1980s. His brother actually wrote a memoir, (laughs) which is just a fun, interesting fact. >> Tracy: Oh my God! >> Lisa: Wow! >> And so, I kind of gravitate to people that I can learn from that's not in my sphere, that might make me uncomfortable. >> And you probably don't even think about how many people you're influencing along the way. >> No. >> We just keep going and learning from our mentors and probably lose sight of, "I wonder how many people actually admire me?" And I'm sure there are many that admire you, Rhonda, for what you've done, going from anthropology to archeology. You mentioned before we went live you were really interested in photography. Keep going and really gathering all that breadth 'cause it's only making you more inspiring to people like us. >> Exactly. >> We thank you so much for joining us on the program and sharing a little bit about you and what brought you to WiDS. Thank you so much, Rhonda. >> Yeah, thank you. >> Tracy: Thank you so much for being here. >> Lisa: Yeah. >> Alright. >> For our guests, and for Tracy Zhang, this is Lisa Martin live at Stanford University covering the eighth Annual Women In Data Science Conference. Stick around. Next guest will be here in just a second. (gentle music)

(gentle music) >> Hello, everyone. Welcome to this Cube Conversation. I'm John Furrier, host of theCUBE here, in our Palo Alto Studios. We're featuring OctoML. I'm with the CEO, Luis Ceze. Chief Executive Officer, Co-founder of OctoML. I'm John Furrier of theCUBE. Thanks for joining us today. Luis, great to see you. Last time we spoke was at "re:MARS" Amazon's event. Kind of a joint event between (indistinct) and Amazon, kind of put a lot together. Great to see you. >> Great to see you again, John. I really have good memories of that interview. You know, that was definitely a great time. Great to chat with you again. >> The world of ML and AI, machine learning and AI is really hot. Everyone's talking about it. It's really great to see that advance. So I'm looking forward to this conversation but before we get started, introduce who you are in OctoML. >> Sure. I'm Luis Ceze, Co-founder and CEO at OctoML. I'm also professor of Computer Science at University of Washington. You know, OctoML grew out of our efforts on the Apache CVM project, which is a compiler in runtime system that enables folks to run machine learning models in a broad set of harder in the Edge and in the Cloud very efficiently. You know, we grew that project and grew that community, definitely saw there was something to pain point there. And then we built OctoML, OctoML is about three and a half years old now. And the mission, the company is to enable customers to deploy models very efficiently in the Cloud. And make them, you know, run. Do it quickly, run fast, and run at a low cost, which is something that's especially timely right now. >> I like to point out also for the folks 'casue they should know that you're also a professor in the Computer Science department at University of Washington. A great program there. This is a really an inflection point with AI machine learning. The computer science industry has been waiting for decades to advance AI with all this new cloud computing, all the hardware and silicon advancements, GPUs. This is the perfect storm. And you know, this the computer science now we we're seeing an acceleration. Can you share your view, and you're obviously a professor in that department but also, an entrepreneur. This is a great time for computer science. Explain why. >> Absolutely, yeah, no. Just like the confluence of you know, advances in what, you know, computers can do as devices to computer information. Plus, you know, advances in AI that enable applications that you know, we thought it was highly futuristic and now it's just right there today. You know, AI that can generate photo realistic images from descriptions, you know, can write text that's pretty good. Can help augment, you know, human creativity in a really meaningful way. So you see the confluence of capabilities and the creativity of humankind into new applications is just extremely exciting, both from a researcher point of view as well as an entrepreneur point of view, right. >> What should people know about these large language models we're seeing with ChatGPT and how Google has got a lot of work going on that air. There's been a lot of work recently. What's different now about these models, and why are they so popular and effective now? What's the difference between now, and say five years ago, that makes it more- >> Oh, yeah. It's a huge inflection on their capabilities, I always say like emergent behavior, right? So as these models got more complex and our ability to train and deploy them, you know, got to this point... You know, they really crossed a threshold into doing things that are truly surprising, right? In terms of generating, you know, exhalation for things generating tax, summarizing tax, expending tax. And you know, exhibiting what to some may look like reasoning. They're not quite reasoning fundamentally. They're generating tax that looks like they're reasoning, but they do it so well, that it feels like was done by a human, right. So I would say that the biggest changes that, you know, now, they can actually do things that are extremely useful for business in people's lives today. And that wasn't the case five years ago. So that's in the model capabilities and that is being paired with huge advances in computing that enabled this to be... Enables this to be, you know, actually see line of sites to be deployed at scale, right. And that's where we come in, by the way, but yeah. >> Yeah, I want to get into that. And also, you know, the fusion of data integrating data sets at scales. Another one we're seeing a lot of happening now. It's not just some, you know, siloed, pre-built data modeling. It's a lot of agility and a lot of new integration capabilities of data. How is that impacting the dynamics? >> Yeah, absolutely. So I'll say that the ability to either take the data that has that exists in training a model to do something useful with it, and more interestingly I would say, using baseline foundational models and with a little bit of data, turn them into something that can do a specialized task really, really well. Created this really fast proliferation of really impactful applications, right? >> If every company now is looking at this trend and I'm seeing a lot... And I think every company will rebuild their business with machine learning. If they're not already doing it. And the folks that aren't will probably be dinosaurs will be out of business. This is a real business transformation moment where machine learning and AI, as it goes mainstream. I think it's just the beginning. This is where you guys come in, and you guys are poised for handling this frenzy to change business with machine learning models. How do you guys help customers as they look at this, you know, transition to get, you know, concept to production with machine learning? >> Great. Great questions, yeah, so I would say that it's fair to say there's a bunch of models out there that can do useful things right off the box, right? So and also, the ability to create models improved quite a bit. So the challenge now shifted to customers, you know. Everyone is looking to incorporating AI into their applications. So what we do for them is to, first of all, how do you do that quickly, without needing highly specialized, difficult to find engineering? And very importantly, how do you do that at cost that's accessible, right? So all of these fantastic models that we just talked about, they use an amount of computing that's just astronomical compared to anything else we've done in the past. It means the costs that come with it, are also very, very high. So it's important to enable customers to, you know, incorporate AI into their applications, to their use cases in a way that they can do, with the people that they have, and the costs that they can afford, such that they can have, you know, the maximum impacting possibly have. And finally, you know, helping them deal with hardware availability, as you know, even though we made a lot of progress in making computing cheaper and cheaper. Even to this day, you know, you can never get enough. And getting an allocation, getting the right hardware to run these incredibly hungry models is hard. And we help customers deal with, you know, harder availability as well. >> Yeah, for the folks watching as a... If you search YouTube, there's an interview we did last year at "re:MARS," I mentioned that earlier, just a great interview. You talked about this hardware independence, this traction. I want to get into that, because if you look at all the foundation models that are out there right now, that are getting traction, you're seeing two trends. You're seeing proprietary and open source. And obviously, open source always wins in my opinion, but, you know, there's this iPhone moment and android moment that one of your investors John Torrey from Madrona, talked about was is iPhone versus Android moment, you know, one's proprietary hardware and they're very specialized high performance and then open source. This is an important distinction and you guys are hardware independent. What's the... Explain what all this means. >> Yeah. Great set of questions. First of all, yeah. So, you know, OpenAI, and of course, they create ChatGPT and they offer an API to run these models that does amazing things. But customers have to be able to go and send their data over to OpenAI, right? So, and run the model there and get the outputs. Now, there's open source models that can do amazing things as well, right? So they typically open source models, so they don't lag behind, you know, these proprietary closed models by more than say, you know, six months or so, let's say. And it means that enabling customers to take the models that they want and deploy under their control is something that's very valuable, because one, you don't have to expose your data to externally. Two, you can customize the model even more to the things that you wanted to do. And then three, you can run on an infrastructure that can be much more cost effective than having to, you know, pay somebody else's, you know, cost and markup, right? So, and where we help them is essentially help customers, enable customers to take machine learning models, say an open source model, and automate the process of putting them into production, optimize them to run with the right performance, and more importantly, give them the independence to run where they need to run, where they can run best, right? >> Yeah, and also, you know, I point out all the time that, you know, there's never any stopping the innovation of hardware silicon. You're seeing cloud computing more coming in there. So, you know, being hardware independent has some advantages. And if you look at OpenAI, for instance, you mentioned ChatGPT, I think this is interesting because I think everyone is scratching their head, going, "Okay, I need to move to this new generation." What's your pro tip and advice for folks who want to move to, or businesses that want to say move to machine learning? How do they get started? What are some of the considerations they need to think about to deploy these models into production? >> Yeah, great though. Great set of questions. First of all, I mean, I'm sure they're very aware of the kind of things that you want to do with AI, right? So you could be interacting with customers, you know, automating, interacting with customers. It could be, you know, finding issues in production lines. It could be, you know... Generating, you know, making it easier to produce content and so on. Like, you know, customers, users would have an idea what they want to do. You know, from that it can actually determine, what kind of machine learning models would solve the problem that would, you know, fits that use case. But then, that's when the hard thing begins, right? So when you find a model, identify the model that can do the thing that you wanted to do, you need to turn that into a thing that you can deploy. So how do you go from machine learning model that does a thing that you need to do, to a container with the right executor, the artifact they can actually go and deploy, right? So we've seen customers doing that on their own, right? So, and it's got a bit of work, and that's why we are excited about the automation that we can offer and then turn that into a turnkey problem, right? So a turnkey process. >> Luis, talk about the use cases. If I don't mind going and double down on the previous answer. You got existing services, and then there's new AI applications, AI for applications. What are the use cases with existing stuff, and the new applications that are being built? >> Yeah, I mean, existing itself is, for example, how do you do very smart search and auto completion, you know, when you are editing documents, for example. Very, very smart search of documents, summarization of tax, expanding bullets into pros in a way that, you know, don't have to spend as much human time. Just some of the existing applications, right? So some of the new ones are like truly AI native ways of producing content. Like there's a company that, you know, we share investors and love what they're doing called runwayyML, for example. It's sort of like an AI first way of editing and creating visual content, right? So you could say you have a video, you could say make this video look like, it's night as opposed to dark, or remove that dog in the corner. You can do that in a way that you couldn't do otherwise. So there's like definitely AI native use cases. And yet not only in life sciences, you know, there's quite a bit of advances on AI-based, you know, therapies and diagnostics processes that are designed using automated processes. And this is something that I feel like, we were just scratching the surface there. There's huge opportunities there, right? >> Talk about the inference and AI and production kind of angle here, because cost is a huge concern when you look at... And there's a hardware and that flexibility there. So I can see how that could help, but is there a cost freight train that can get out of control here if you don't deploy properly? Talk about the scale problem around cost in AI. >> Yeah, absolutely. So, you know, very quickly. One thing that people tend to think about is the cost is. You know, training has really high dollar amounts it tends over index on that. But what you have to think about is that for every model that's actually useful, you're going to train it once, and then run it a large number of times in inference. That means that over the lifetime of a model, the vast majority of the compute cycles and the cost are going to go to inference. And that's what we address, right? So, and to give you some idea, if you're talking about using large language model today, you know, you can say it's going to cost a couple of cents per, you know, 2,000 words output. If you have a million users active, you know, a day, you know, if you're lucky and you have that, you can, this cost can actually balloon very quickly to millions of dollars a month, just in inferencing costs. You know, assuming you know, that you actually have access to the infrastructure to run it, right? So means that if you don't pay attention to these inference costs and that's definitely going to be a surprise. And affects the economics of the product where this is embedded in, right? So this is something that, you know, if there's quite a bit of attention being put on right now on how do you do search with large language models and you don't pay attention to the economics, you know, you can have a surprise. You have to change the business model there. >> Yeah. I think that's important to call out, because you don't want it to be a runaway cost structure where you architected it wrong and then next thing you know, you got to unwind that. I mean, it's more than technical debt, it's actually real debt, it's real money. So, talk about some of the dynamics with the customers. How are they architecting this? How do they get ahead of that problem? What do you guys do specifically to solve that? >> Yeah, I mean, well, we help customers. So, it's first of all, be hyper aware, you know, understanding what's going to be the cost for them deploying the models into production and showing them the possibilities of how you can deploy the model with different cost structure, right? So that's where, you know, the ability to have hardware independence is so important because once you have hardware independence, after you optimize models, obviously, you have a new, you know, dimension of freedom to choose, you know, what is the right throughput per dollar for you. And then where, and what are the options? And once you make that decision, you want to automate the process of putting into production. So the way we help customers is showing very clearly in their use case, you know, how they can deploy their models in a much more cost-effective way. You know, when the cases... There's a case study that we put out recently, showing a 4x reduction in deployment costs, right? So this is by doing a mix optimization and choosing the right hardware. >> How do you address the concern that someone might say, Luis said, "Hey, you know, I don't want to degrade performance and latency, and I don't want the user experience to suffer." What's the answer there? >> Two things. So first of all, all of the manipulations that we do in the model is to turn the model to efficient code without changing the behavior of the models. We wouldn't degrade the experience of the user by having the model be wrong more often. And we don't change that at all. The model behaves the way it was validated for. And then the second thing is, you know, user experience with respect to latency, it's all about a maximum... Like, you could say, I want a model to run at 50 milliseconds or less. If it's much faster than 15 seconds, you're not going to notice the difference. But if it's lower, you're going to notice a difference. So the key here is that, how do you find a set of options to deploy, that you are not overshooting performance in a way that's going to lead to costs that has no additional benefits. And this provides a huge, a very significant margin of choices, set of choices that you can optimize for cost without degrading customer experience, right. End user experience. >> Yeah, and I also point out the large language models like the ChatGPTs of the world, they're coming out with Dave Moth and I were talking on this breaking analysis around, this being like, over 10X more computational intensive on capabilities. So this hardware independence is a huge thing. So, and also supply chain, some people can't get servers by the way, so, or hardware these days. >> Or even more interestingly, right? So they do not grow in trees, John. Like GPUs is not kind of stuff that you plant an orchard until you have a bunch and then you can increase it, but no, these things, you know, take a while. So, and you can't increase it overnight. So being able to live with those cycles that are available to you is not just important for all for cost, but also important for people to scale and serve more users at, you know, at whatever pace that they come, right? >> You know, it's really great to talk to you, and congratulations on OctaML. Looking forward to the startup showcase, we'll be featuring you guys there. But I want to get your personal opinion as someone in the industry and also, someone who's been in the computer science area for your career. You know, computer science has always been great, and there's more people enrolling in computer science, more diversity than ever before, but there's also more computer science related fields. How is this opening up computer science and where's AI going with the computers, with the science? Can you share your vision on, you know, the aperture, or the landscape of CompSci, or CS students, and opportunities. >> Yeah, no, absolutely. I think it's fair to say that computer has been embedded in pretty much every aspect of human life these days. Human life these days, right? So for everything. And AI has been a counterpart, it been an integral component of computer science for a while. And this medicines that happened in the last 10, 15 years in AI has shown, you know, new application has I think re-energized how people see what computers can do. And you, you know, there is this picture in our department that shows computer science at the center called the flower picture, and then all the different paddles like life sciences, social sciences, and then, you know, mechanical engineering, all these other things that, and I feel like it can replace that center with computer science. I put AI there as well, you see AI, you know touching all these applications. AI in healthcare, diagnostics. AI in discovery in the sciences, right? So, but then also AI doing things that, you know, the humans wouldn't have to do anymore. They can do better things with their brains, right? So it's permitting every single aspect of human life from intellectual endeavor to day-to-day work, right? >> Yeah. And I think the ChatGPT and OpenAI has really kind of created a mainstream view that everyone sees value in it. Like you could be in the data center, you could be in bio, you could be in healthcare. I mean, every industry sees value. So this brings up what I can call the horizontally scalable use constance. And so this opens up the conversation, what's going to change from this? Because if you go horizontally scalable, which is a cloud concept as you know, that's going to create a lot of opportunities and some shifting of how you think about architecture around data, for instance. What's your opinion on what this will do to change the inflection of the role of architecting platforms and the role of data specifically? >> Yeah, so good question. There is a lot in there, by the way, I should have added the previous question, that you can use AI to do better AI as well, which is what we do, and other folks are doing as well. And so the point I wanted to make here is that it's pretty clear that you have a cloud focus component with a nudge focused counterparts. Like you have AI models, but both in the Cloud and in the Edge, right? So the ability of being able to run your AI model where it runs best also has a data advantage to it from say, from a privacy point of view. That's inherently could say, "Hey, I want to run something, you know, locally, strictly locally, such that I don't expose the data to an infrastructure." And you know that the data never leaves you, right? Never leaves the device. Now you can imagine things that's already starting to happen, like you do some forms of training and model customization in the model architecture itself and the system architecture, such that you do this as close to the user as possible. And there's something called federated learning that has been around for some time now that's finally happening is, how do you get a data from butcher places, you do, you know, some common learning and then you send a model to the Edges, and they get refined for the final use in a way that you get the advantage of aggregating data but you don't get the disadvantage of privacy issues and so on. >> It's super exciting. >> And some of the considerations, yeah. >> It's super exciting area around data infrastructure, data science, computer science. Luis, congratulations on your success at OctaML. You're in the middle of it. And the best thing about its businesses are looking at this and really reinventing themselves and if a business isn't thinking about restructuring their business around AI, they're probably will be out of business. So this is a great time to be in the field. So thank you for sharing your insights here in theCUBE. >> Great. Thank you very much, John. Always a pleasure talking to you. Always have a lot of fun. And we both speak really fast, I can tell, you know, so. (both laughing) >> I know. We'll not the transcript available, we'll integrate it into our CubeGPT model that we have Luis. >> That's right. >> Great. >> Great. >> Great to talk to you, thank you, John. Thanks, man, bye. >> Hey, this is theCUBE. I'm John Furrier, here in Palo Alto, Cube Conversation. Thanks for watching. (gentle music)

(upbeat music) >> Welcome back, everyone, to theCUBE's coverage here live on the floor at AWS re:MARS 2022. I'm John Furrier, host for theCUBE. Great event, machine learning, automation, robotics, space, that's MARS. It's part of the re-series of events, re:Invent's the big event at the end of the year, re:Inforce, security, re:MARS, really intersection of the future of space, industrial, automation, which is very heavily DevOps machine learning, of course, machine learning, which is AI. We have Luis Ceze here, who's the CEO co-founder of OctoML. Welcome to theCUBE. >> Thank you very much for having me in the show, John. >> So we've been following you guys. You guys are a growing startup funded by Madrona Venture Capital, one of your backers. You guys are here at the show. This is a, I would say small show relative what it's going to be, but a lot of robotics, a lot of space, a lot of industrial kind of edge, but machine learning is the centerpiece of this trend. You guys are in the middle of it. Tell us your story. >> Absolutely, yeah. So our mission is to make machine learning sustainable and accessible to everyone. So I say sustainable because it means we're going to make it faster and more efficient. You know, use less human effort, and accessible to everyone, accessible to as many developers as possible, and also accessible in any device. So, we started from an open source project that began at University of Washington, where I'm a professor there. And several of the co-founders were PhD students there. We started with this open source project called Apache TVM that had actually contributions and collaborations from Amazon and a bunch of other big tech companies. And that allows you to get a machine learning model and run on any hardware, like run on CPUs, GPUs, various GPUs, accelerators, and so on. It was the kernel of our company and the project's been around for about six years or so. Company is about three years old. And we grew from Apache TVM into a whole platform that essentially supports any model on any hardware cloud and edge. >> So is the thesis that, when it first started, that you want to be agnostic on platform? >> Agnostic on hardware, that's right. >> Hardware, hardware. >> Yeah. >> What was it like back then? What kind of hardware were you talking about back then? Cause a lot's changed, certainly on the silicon side. >> Luis: Absolutely, yeah. >> So take me through the journey, 'cause I could see the progression. I'm connecting the dots here. >> So once upon a time, yeah, no... (both chuckling) >> I walked in the snow with my bare feet. >> You have to be careful because if you wake up the professor in me, then you're going to be here for two hours, you know. >> Fast forward. >> The average version here is that, clearly machine learning has shown to actually solve real interesting, high value problems. And where machine learning runs in the end, it becomes code that runs on different hardware, right? And when we started Apache TVM, which stands for tensor virtual machine, at that time it was just beginning to start using GPUs for machine learning, we already saw that, with a bunch of machine learning models popping up and CPUs and GPU's starting to be used for machine learning, it was clear that it come opportunity to run on everywhere. >> And GPU's were coming fast. >> GPUs were coming and huge diversity of CPUs, of GPU's and accelerators now, and the ecosystem and the system software that maps models to hardware is still very fragmented today. So hardware vendors have their own specific stacks. So Nvidia has its own software stack, and so does Intel, AMD. And honestly, I mean, I hope I'm not being, you know, too controversial here to say that it kind of of looks like the mainframe era. We had tight coupling between hardware and software. You know, if you bought IBM hardware, you had to buy IBM OS and IBM database, IBM applications, it all tightly coupled. And if you want to use IBM software, you had to buy IBM hardware. So that's kind of like what machine learning systems look like today. If you buy a certain big name GPU, you've got to use their software. Even if you use their software, which is pretty good, you have to buy their GPUs, right? So, but you know, we wanted to help peel away the model and the software infrastructure from the hardware to give people choice, ability to run the models where it best suit them. Right? So that includes picking the best instance in the cloud, that's going to give you the right, you know, cost properties, performance properties, or might want to run it on the edge. You might run it on an accelerator. >> What year was that roughly, when you were going this? >> We started that project in 2015, 2016 >> Yeah. So that was pre-conventional wisdom. I think TensorFlow wasn't even around yet. >> Luis: No, it wasn't. >> It was, I'm thinking like 2017 or so. >> Luis: Right. So that was the beginning of, okay, this is opportunity. AWS, I don't think they had released some of the nitro stuff that the Hamilton was working on. So, they were already kind of going that way. It's kind of like converging. >> Luis: Yeah. >> The space was happening, exploding. >> Right. And the way that was dealt with, and to this day, you know, to a large extent as well is by backing machine learning models with a bunch of hardware specific libraries. And we were some of the first ones to say, like, know what, let's take a compilation approach, take a model and compile it to very efficient code for that specific hardware. And what underpins all of that is using machine learning for machine learning code optimization. Right? But it was way back when. We can talk about where we are today. >> No, let's fast forward. >> That's the beginning of the open source project. >> But that was a fundamental belief, worldview there. I mean, you have a world real view that was logical when you compare to the mainframe, but not obvious to the machine learning community. Okay, good call, check. Now let's fast forward, okay. Evolution, we'll go through the speed of the years. More chips are coming, you got GPUs, and seeing what's going on in AWS. Wow! Now it's booming. Now I got unlimited processors, I got silicon on chips, I got, everywhere >> Yeah. And what's interesting is that the ecosystem got even more complex, in fact. Because now you have, there's a cross product between machine learning models, frameworks like TensorFlow, PyTorch, Keras, and like that and so on, and then hardware targets. So how do you navigate that? What we want here, our vision is to say, folks should focus, people should focus on making the machine learning models do what they want to do that solves a value, like solves a problem of high value to them. Right? So another deployment should be completely automatic. Today, it's very, very manual to a large extent. So once you're serious about deploying machine learning model, you got a good understanding where you're going to deploy it, how you're going to deploy it, and then, you know, pick out the right libraries and compilers, and we automated the whole thing in our platform. This is why you see the tagline, the booth is right there, like bringing DevOps agility for machine learning, because our mission is to make that fully transparent. >> Well, I think that, first of all, I use that line here, cause I'm looking at it here on live on camera. People can't see, but it's like, I use it on a couple couple of my interviews because the word agility is very interesting because that's kind of the test on any kind of approach these days. Agility could be, and I talked to the robotics guys, just having their product be more agile. I talked to Pepsi here just before you came on, they had this large scale data environment because they built an architecture, but that fostered agility. So again, this is an architectural concept, it's a systems' view of agility being the output, and removing dependencies, which I think what you guys were trying to do. >> Only part of what we do. Right? So agility means a bunch of things. First, you know-- >> Yeah explain. >> Today it takes a couple months to get a model from, when the model's ready, to production, why not turn that in two hours. Agile, literally, physically agile, in terms of walk off time. Right? And then the other thing is give you flexibility to choose where your model should run. So, in our deployment, between the demo and the platform expansion that we announced yesterday, you know, we give the ability of getting your model and, you know, get it compiled, get it optimized for any instance in the cloud and automatically move it around. Today, that's not the case. You have to pick one instance and that's what you do. And then you might auto scale with that one instance. So we give the agility of actually running and scaling the model the way you want, and the way it gives you the right SLAs. >> Yeah, I think Swami was mentioning that, not specifically that use case for you, but that use case generally, that scale being moving things around, making them faster, not having to do that integration work. >> Scale, and run the models where they need to run. Like some day you want to have a large scale deployment in the cloud. You're going to have models in the edge for various reasons because speed of light is limited. We cannot make lights faster. So, you know, got to have some, that's a physics there you cannot change. There's privacy reasons. You want to keep data locally, not send it around to run the model locally. So anyways, and giving the flexibility. >> Let me jump in real quick. I want to ask this specific question because you made me think of something. So we're just having a data mesh conversation. And one of the comments that's come out of a few of these data as code conversations is data's the product now. So if you can move data to the edge, which everyone's talking about, you know, why move data if you don't have to, but I can move a machine learning algorithm to the edge. Cause it's costly to move data. I can move computer, everyone knows that. But now I can move machine learning to anywhere else and not worry about integrating on the fly. So the model is the code. >> It is the product. >> Yeah. And since you said, the model is the code, okay, now we're talking even more here. So machine learning models today are not treated as code, by the way. So do not have any of the typical properties of code that you can, whenever you write a piece of code, you run a code, you don't know, you don't even think what is a CPU, we don't think where it runs, what kind of CPU it runs, what kind of instance it runs. But with machine learning model, you do. So what we are doing and created this fully transparent automated way of allowing you to treat your machine learning models if you were a regular function that you call and then a function could run anywhere. >> Yeah. >> Right. >> That's why-- >> That's better. >> Bringing DevOps agility-- >> That's better. >> Yeah. And you can use existing-- >> That's better, because I can run it on the Artemis too, in space. >> You could, yeah. >> If they have the hardware. (both laugh) >> And that allows you to run your existing, continue to use your existing DevOps infrastructure and your existing people. >> So I have to ask you, cause since you're a professor, this is like a masterclass on theCube. Thank you for coming on. Professor. (Luis laughing) I'm a hardware guy. I'm building hardware for Boston Dynamics, Spot, the dog, that's the diversity in hardware, it's tends to be purpose driven. I got a spaceship, I'm going to have hardware on there. >> Luis: Right. >> It's generally viewed in the community here, that everyone I talk to and other communities, open source is going to drive all software. That's a check. But the scale and integration is super important. And they're also recognizing that hardware is really about the software. And they even said on stage, here. Hardware is not about the hardware, it's about the software. So if you believe that to be true, then your model checks all the boxes. Are people getting this? >> I think they're starting to. Here is why, right. A lot of companies that were hardware first, that thought about software too late, aren't making it. Right? There's a large number of hardware companies, AI chip companies that aren't making it. Probably some of them that won't make it, unfortunately just because they started thinking about software too late. I'm so glad to see a lot of the early, I hope I'm not just doing our own horn here, but Apache TVM, the infrastructure that we built to map models to different hardware, it's very flexible. So we see a lot of emerging chip companies like SiMa.ai's been doing fantastic work, and they use Apache TVM to map algorithms to their hardware. And there's a bunch of others that are also using Apache TVM. That's because you have, you know, an opening infrastructure that keeps it up to date with all the machine learning frameworks and models and allows you to extend to the chips that you want. So these companies pay attention that early, gives them a much higher fighting chance, I'd say. >> Well, first of all, not only are you backable by the VCs cause you have pedigree, you're a professor, you're smart, and you get good recruiting-- >> Luis: I don't know about the smart part. >> And you get good recruiting for PhDs out of University of Washington, which is not too shabby computer science department. But they want to make money. The VCs want to make money. >> Right. >> So you have to make money. So what's the pitch? What's the business model? >> Yeah. Absolutely. >> Share us what you're thinking there. >> Yeah. The value of using our solution is shorter time to value for your model from months to hours. Second, you shrink operator, op-packs, because you don't need a specialized expensive team. Talk about expensive, expensive engineers who can understand machine learning hardware and software engineering to deploy models. You don't need those teams if you use this automated solution, right? Then you reduce that. And also, in the process of actually getting a model and getting specialized to the hardware, making hardware aware, we're talking about a very significant performance improvement that leads to lower cost of deployment in the cloud. We're talking about very significant reduction in costs in cloud deployment. And also enabling new applications on the edge that weren't possible before. It creates, you know, latent value opportunities. Right? So, that's the high level value pitch. But how do we make money? Well, we charge for access to the platform. Right? >> Usage. Consumption. >> Yeah, and value based. Yeah, so it's consumption and value based. So depends on the scale of the deployment. If you're going to deploy machine learning model at a larger scale, chances are that it produces a lot of value. So then we'll capture some of that value in our pricing scale. >> So, you have direct sales force then to work those deals. >> Exactly. >> Got it. How many customers do you have? Just curious. >> So we started, the SaaS platform just launched now. So we started onboarding customers. We've been building this for a while. We have a bunch of, you know, partners that we can talk about openly, like, you know, revenue generating partners, that's fair to say. We work closely with Qualcomm to enable Snapdragon on TVM and hence our platform. We're close with AMD as well, enabling AMD hardware on the platform. We've been working closely with two hyperscaler cloud providers that-- >> I wonder who they are. >> I don't know who they are, right. >> Both start with the letter A. >> And they're both here, right. What is that? >> They both start with the letter A. >> Oh, that's right. >> I won't give it away. (laughing) >> Don't give it away. >> One has three, one has four. (both laugh) >> I'm guessing, by the way. >> Then we have customers in the, actually, early customers have been using the platform from the beginning in the consumer electronics space, in Japan, you know, self driving car technology, as well. As well as some AI first companies that actually, whose core value, the core business come from AI models. >> So, serious, serious customers. They got deep tech chops. They're integrating, they see this as a strategic part of their architecture. >> That's what I call AI native, exactly. But now there's, we have several enterprise customers in line now, we've been talking to. Of course, because now we launched the platform, now we started onboarding and exploring how we're going to serve it to these customers. But it's pretty clear that our technology can solve a lot of other pain points right now. And we're going to work with them as early customers to go and refine them. >> So, do you sell to the little guys, like us? Will we be customers if we wanted to be? >> You could, absolutely, yeah. >> What we have to do, have machine learning folks on staff? >> So, here's what you're going to have to do. Since you can see the booth, others can't. No, but they can certainly, you can try our demo. >> OctoML. >> And you should look at the transparent AI app that's compiled and optimized with our flow, and deployed and built with our flow. That allows you to get your image and do style transfer. You know, you can get you and a pineapple and see how you look like with a pineapple texture. >> We got a lot of transcript and video data. >> Right. Yeah. Right, exactly. So, you can use that. Then there's a very clear-- >> But I could use it. You're not blocking me from using it. Everyone's, it's pretty much democratized. >> You can try the demo, and then you can request access to the platform. >> But you get a lot of more serious deeper customers. But you can serve anybody, what you're saying. >> Luis: We can serve anybody, yeah. >> All right, so what's the vision going forward? Let me ask this. When did people start getting the epiphany of removing the machine learning from the hardware? Was it recently, a couple years ago? >> Well, on the research side, we helped start that trend a while ago. I don't need to repeat that. But I think the vision that's important here, I want the audience here to take away is that, there's a lot of progress being made in creating machine learning models. So, there's fantastic tools to deal with training data, and creating the models, and so on. And now there's a bunch of models that can solve real problems there. The question is, how do you very easily integrate that into your intelligent applications? Madrona Venture Group has been very vocal and investing heavily in intelligent applications both and user applications as well as enablers. So we say an enable of that because it's so easy to use our flow to get a model integrated into your application. Now, any regular software developer can integrate that. And that's just the beginning, right? Because, you know, now we have CI/CD integration to keep your models up to date, to continue to integrate, and then there's more downstream support for other features that you normally have in regular software development. >> I've been thinking about this for a long, long, time. And I think this whole code, no one thinks about code. Like, I write code, I'm deploying it. I think this idea of machine learning as code independent of other dependencies is really amazing. It's so obvious now that you say it. What's the choices now? Let's just say that, I buy it, I love it, I'm using it. Now what do I got to do if I want to deploy it? Do I have to pick processors? Are there verified platforms that you support? Is there a short list? Is there every piece of hardware? >> We actually can help you. I hope we're not saying we can do everything in the world here, but we can help you with that. So, here's how. When you have them all in the platform you can actually see how this model runs on any instance of any cloud, by the way. So we support all the three major cloud providers. And then you can make decisions. For example, if you care about latency, your model has to run on, at most 50 milliseconds, because you're going to have interactivity. And then, after that, you don't care if it's faster. All you care is that, is it going to run cheap enough. So we can help you navigate. And also going to make it automatic. >> It's like tire kicking in the dealer showroom. >> Right. >> You can test everything out, you can see the simulation. Are they simulations, or are they real tests? >> Oh, no, we run all in real hardware. So, we have, as I said, we support any instances of any of the major clouds. We actually run on the cloud. But we also support a select number of edge devices today, like ARMs and Nvidia Jetsons. And we have the OctoML cloud, which is a bunch of racks with a bunch Raspberry Pis and Nvidia Jetsons, and very soon, a bunch of mobile phones there too that can actually run the real hardware, and validate it, and test it out, so you can see that your model runs performant and economically enough in the cloud. And it can run on the edge devices-- >> You're a machine learning as a service. Would that be an accurate? >> That's part of it, because we're not doing the machine learning model itself. You come with a model and we make it deployable and make it ready to deploy. So, here's why it's important. Let me try. There's a large number of really interesting companies that do API models, as in API as a service. You have an NLP model, you have computer vision models, where you call an API and then point in the cloud. You send an image and you got a description, for example. But it is using a third party. Now, if you want to have your model on your infrastructure but having the same convenience as an API you can use our service. So, today, chances are that, if you have a model that you know that you want to do, there might not be an API for it, we actually automatically create the API for you. >> Okay, so that's why I get the DevOps agility for machine learning is a better description. Cause it's not, you're not providing the service. You're providing the service of deploying it like DevOps infrastructure as code. You're now ML as code. >> It's your model, your API, your infrastructure, but all of the convenience of having it ready to go, fully automatic, hands off. >> Cause I think what's interesting about this is that it brings the craftsmanship back to machine learning. Cause it's a craft. I mean, let's face it. >> Yeah. I want human brains, which are very precious resources, to focus on building those models, that is going to solve business problems. I don't want these very smart human brains figuring out how to scrub this into actually getting run the right way. This should be automatic. That's why we use machine learning, for machine learning to solve that. >> Here's an idea for you. We should write a book called, The Lean Machine Learning. Cause the lean startup was all about DevOps. >> Luis: We call machine leaning. No, that's not it going to work. (laughs) >> Remember when iteration was the big mantra. Oh, yeah, iterate. You know, that was from DevOps. >> Yeah, that's right. >> This code allowed for standing up stuff fast, double down, we all know the history, what it turned out. That was a good value for developers. >> I could really agree. If you don't mind me building on that point. You know, something we see as OctoML, but we also see at Madrona as well. Seeing that there's a trend towards best in breed for each one of the stages of getting a model deployed. From the data aspect of creating the data, and then to the model creation aspect, to the model deployment, and even model monitoring. Right? We develop integrations with all the major pieces of the ecosystem, such that you can integrate, say with model monitoring to go and monitor how a model is doing. Just like you monitor how code is doing in deployment in the cloud. >> It's evolution. I think it's a great step. And again, I love the analogy to the mainstream. I lived during those days. I remember the monolithic propriety, and then, you know, OSI model kind of blew it. But that OSI stack never went full stack, and it only stopped at TCP/IP. So, I think the same thing's going on here. You see some scalability around it to try to uncouple it, free it. >> Absolutely. And sustainability and accessibility to make it run faster and make it run on any deice that you want by any developer. So, that's the tagline. >> Luis Ceze, thanks for coming on. Professor. >> Thank you. >> I didn't know you were a professor. That's great to have you on. It was a masterclass in DevOps agility for machine learning. Thanks for coming on. Appreciate it. >> Thank you very much. Thank you. >> Congratulations, again. All right. OctoML here on theCube. Really important. Uncoupling the machine learning from the hardware specifically. That's only going to make space faster and safer, and more reliable. And that's where the whole theme of re:MARS is. Let's see how they fit in. I'm John for theCube. Thanks for watching. More coverage after this short break. >> Luis: Thank you. (gentle music)

(upbeat music) >> Announcer: TheCUBE presents KubeCon and CloudNativeCon Europe, 2022. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partners. >> Welcome to Valencia, Spain, a KubeCon, CloudNativeCon Europe, 2022. I'm your host, Keith Townsend alongside Paul Gillon, Senior Editor, Enterprise Architecture for SiliconANGLE. We are, I think at the half point way point this to be fair we've talked to a lot of folks in open source in general. What's the difference between open source communities and these closed source communities that we attend so so much? >> Well open source is just it's that it's open it's anybody can contribute. There are a set of rules that manage how your contributions are reflected in the code base. What has to be shared, what you can keep to yourself but the it's an entirely different vibe. You know, you go to a conventional conference where there's a lot of proprietary being sold and it's all about cash. It's all about money changing hands. It's all about doing the deal. And open source conferences I think are more, they're more transparent and yeah money changes hands, but it seems like the objective of the interaction is not to consummate a deal to the degree that it is at a more conventional computer conference. >> And I think that can create an uneven side effect. And we're going to talk about that a little bit with, honestly a friend of mine Alex Ellis, founder of OpenFaaS. Alex welcome back to the program. >> Thank you, good to see Keith. >> So how long you've been doing OpenFaaS? >> Well, I first had this idea that serverless and function should be run on your own hardware back in 2016. >> Wow and I remember seeing you at DockerCon EU, was that in 2017? >> Yeah, I think that's when we first met and Simon Foskett took us out to dinner and we got chatting. And I just remember you went back to your hotel room after the presentation. You just had your iPhone out and your headphones you were talking about how you tried to OpenWhisk and really struggled with it and OpenFaaS sort of got you where you needed to be to sort of get some value out of the solution. >> And I think that's the magic of these open source communities in open source conferences that you can try stuff, you can struggle with it, come to a conference either get some advice or go in another direction and try something like a OpenFaaS. But we're going to talk about the business perspective. >> Yeah. >> Give us some, like give us some hero numbers from the project. What types of organizations are using OpenFaaS and what are like the download and stars all those, the ways you guys measure project success. >> So there's a few ways that you hear this talked about at KubeCon specifically. And one of the metrics that you hear the most often is GitHub stars. Now a GitHub star means that somebody with their laptop like yourself has heard of a project or seen it on their phone and clicked a button that's it. There's not really an indication of adoption but of interest. And that might be fleeting and a blog post you might publish you might bump that up by 2000. And so OpenFaaS quite quickly got a lot of stars which encouraged me to go on and do more with it. And it's now just crossed 30,000 across the whole organization of about 40 different open source repositories. >> Wow that is a number. >> Now you are in ecosystem where Knative is also taken off. And can you distinguish your approach to serverless or FaaS to Knatives? >> Yes so, Knative isn't an approach to FaaS. That's simply put and if you listen to Aikas Ville from the Knative project, he was working inside Google and wished that Kubernetes would do a little bit more than what it did. And so he started an initiative with some others to start bringing more abstractions like Auto Scaling, revision management so he can have two versions of code and and shift traffic around. And that's really what they're trying to do is add onto Kubernetes and make it do some of the things that a platform might do. Now OpenFaaS started from a different angle and frankly, two years earlier. >> There was no Kubernetes when you started it. >> It kind of led in the space and and built out that ecosystem. So the idea was, I was working with Lambda and AWS Alexa skills. I wanted to run them on my own hardware and I couldn't. And so OpenFaaS from the beginning started from that developer experience of here's my code, run it for me. Knative is a set of extensions that may be a building block but you're still pretty much working with Kubernetes. We get calls come through. And actually recently I can't tell you who they are but there's a very large telecommunications provider in the US that was using OpenFaaS, like yourself heard of Knative and in the hype they switched. And then they switched back again recently to OpenFaaS and they've come to us for quite a large commercial deal. >> So did they find Knative to be more restrictive? >> No, it's the opposite. It's a lot less opinionated. It's more like building blocks and you are dealing with a lot more detail. It's a much bigger system to manage, but don't get me wrong. I mean the guys are very friendly. They have their sort of use cases that they pursue. Google's now donated the project to CNCF. And so they're running it that way. Now it doesn't mean that there aren't FaaS on top of it. Red Hat have a serverless product VMware have one. But OpenFaaS because it owns the whole stack can get you something that's always been very lean, simple to use to the point that Keith in his hotel room installed it and was product with it in an evening without having to be a Kubernetes expert. >> And that is and if you remember back that was very anti-Kubernetes. >> Yes. >> It was not a platform I thought that was. And for some of the very same reasons, I didn't think it was very user friendly. You know, I tried open with I'm thinking what enterprise is going to try this thing, especially without the handholding and the support needed to do that. And you know, something pretty interesting that happened as I shared this with you on Twitter, I was having a briefing by a big microprocessor company, one of the big two. And they were showing me some of the work they were doing in Cloud-native and the way that they stretch test the system to show me Auto Scaling. Is that they bought up a OpenFaaS what is it? The well text that just does a bunch of, >> The cows maybe. >> Yeah the cows. That does just a bunch of texts. And it just all, and I'm like one I was amazed at is super simple app. And the second one was the reason why they discovered it was because of that simplicity is just a thing that's in your store that you can just download and test. And it was open fast. And it was this big company that you had no idea that was using >> No >> OpenFaaS. >> No. >> How prevalent is that? That you're always running into like these surprises of who's using the solution. >> There are a lot of top tier companies, billion dollar companies that use software that I've worked on. And it's quite common. The main issue you have with open source is you don't have like the commercial software you talked about, the relationships. They don't tell you they're using it until it breaks. And then they may come in incognito with a personal email address asking for things. What they don't want to do often is lend their brands or support you. And so it is a big challenge. However, early on, when I met you, BT, live person the University of Washington, and a bunch of other companies had told us they were using it. We were having discussions with them took them to Kubecon and did talks with them. You can go and look at them in the video player. However, when I left my job in 2019 to work on this full time I went to them and I said, you know, use it in production it's useful for you. We've done a talk, we really understand the business value of how it saves you time. I haven't got a way to fund it and it won't exist unless you help they were like sucks to be you. >> Wow that's brutal. So, okay let me get this right. I remember the story 2019, you leave your job. You say I'm going to do OpenFaaS and support this project 100% of your time. If there's no one contributing to the project from a financial perspective how do you make money? I've always pitched open source because you're the first person that I've met that ran an open source project. And I always pitched them people like you who work on it on their side time. But they're not the Knatives of the world, the SDOs, they have full time developers. Sponsored by Google and Microsoft, etc. If you're not sponsored how do you make money off of open source? >> If this is the million dollar question, really? How do you make money from something that is completely free? Where all of the value has already been captured by a company and they have no incentive to support you build a relationship or send you money in any way. >> And no one has really figured it out. Arguably Red Hat is the only one that's pulled it off. >> Well, people do refer to Red Hat and they say the Red Hat model but I think that was a one off. And we quite, we can kind of agree about that in a business. However, I eventually accepted the fact that companies don't pay for something they can get for free. It took me a very long time to get around that because you know, with open source enthusiast built a huge community around this project, almost 400 people have contributed code to it over the years. And we have had full-time people working on it on and off. And there's some people who really support it in their working hours or at home on the weekends. But no, I had to really think, right, what am I going to offer? And to begin with it would support existing customers weren't interested. They're not really customers because they're consuming it as a project. So I needed to create a product because we understand we buy products. Initially I just couldn't find the right customers. And so many times I thought about giving up, leaving it behind, my family would've supported me with that as well. And they would've known exactly why even you would've done. And so what I started to do was offer my insights as a community leader, as a maintainer to companies like we've got here. So Casting one of my customers, CSIG one of my customers, Rancher R, DigitalOcean, a lot of the vendors you see here. And I was able to get a significant amount of money by lending my expertise and writing content that gave me enough buffer to give the doctors time to realize that maybe they do need support and go a bit further into production. And over the last 12 months, we've been signing six figure deals with existing users and new users alike in enterprise. >> For support >> For support, for licensing of new features that are close source and for consulting. >> So you have proprietary extensions. Also that are sort of enterprise class. Right and then also the consulting business, the support business which is a proven business model that has worked >> Is a proven business model. What it's not a proven business model is if you work hard enough, you deserve to be rewarded. >> Mmh. >> You have to go with the system. Winter comes after autumn. Summer comes after spring and you, it's no point saying why is it like that? That's the way it is. And if you go with it, you can benefit from it. And that's what the realization I had as much as I didn't want to do it. >> So you know this community, well you know there's other project founders out here thinking about making the leap. If you're giving advice to a project founder and they're thinking about making this leap, you know quitting their job and becoming the next Alex. And I think this is the perception that the misperception out there. >> Yes. >> You're, you're well known. There's a difference between being well known and well compensated. >> Yeah. >> What advice would you give those founders >> To be. >> Before they make the leap to say you know what I'm going to do my project full time. I'm going to lean on the generosity of the community. So there are some generous people in the community. You've done some really interesting things for individual like contributions etc but that's not enough. >> So look, I mean really you have to go back to the MBA mindset. What problem are you trying to solve? Who is your target customer? What do they care about? What do they eat and drink? When do they go to sleep? You really need to know who this is for. And then customize a journey for them so that they can come to you. And you need some way initially of funneling those people in qualifying them because not everybody that comes to a student or somebody doing a PhD is not your customer. >> Right, right. >> You need to understand sales. You need to understand a lot about business but you can work it out on your way. You know, I'm testament to that. And once you have people you then need something to sell them that might meet their needs and be prepared to tell them that what you've got isn't right for them. 'cause sometimes that's the one thing that will build integrity. >> That's very hard for community leaders. It's very hard for community leaders to say, no >> Absolutely so how do you help them over that hump? I think of what you've done. >> So you have to set some boundaries because as an open source developer and maintainer you want to help everybody that's there regardless. And I think for me it was taking some of the open source features that companies used not releasing them anymore in the open source edition, putting them into the paid developing new features based on what feedback we'd had, offering support as well but also understanding what is support. What do you need to offer? You may think you need a one hour SLA for a fix probably turns out that you could sell a three day response time or one day response time. And some people would want that and see value in it. But you're not going to know until you talk to your customers. >> I want to ask you, because this has been a particular interest of mine. It seems like managed services have been kind of the lifeline for pure open source companies. Enabling these companies to maintain their open source roots, but still have a revenue stream of delivering as a service. Is that a business model option you've looked at? >> There's three business models perhaps that are prevalent. One is OpenCore, which is roughly what I'm following. >> Right. >> Then there is SaaS, which is what you understand and then there's support on pure open source. So that's more like what Rancher does. Now if you think of a company like Buoyant that produces Linkerd they do a bit of both. So they don't have any close source pieces yet but they can host it for you or you can host it and they'll support you. And so I think if there's a way that you can put your product into a SaaS that makes it easier for them to run then you know go for it. However, we've OpenFaaS, remember what is the core problem we are solving, portability So why lock into my cloud? >> Take that option off the table, go ahead. >> It's been a long journey and I've been a fan since your start. I've seen the bumps and bruises and the scars get made. If you're open source leader and you're thinking about becoming as famous as Alex, hey you can do that, you can put in all the work become famous but if you want to make a living, solve a problem, understand what people are willing to pay for that problem and go out and sell it. Valuable lessons here on theCUBE. From Valencia, Spain I'm Keith Townsend along with Paul Gillon and you're watching theCUBE the leader in high-tech coverage. (Upbeat music)

>>Mhm >>Welcome to the cube where we're celebrating the EC 2/15 birthday anniversary. My name is Dave Volonte and we're joined right now by Sandy carter, Vice President of AWS. Welcome Sandy, it's great to see you again, >>David. So great to see you too. Thanks for having me on the show today. >>Very welcome. We were last physically together. I think it was reinvent 2019. Hopefully I'll see you before 2022. But first happy birthday to EC two. I mean, it's hard to imagine back in 2006, the degree to which EC two would impact our industry. Sandy, >>I totally agree. You know, I joined a W S about 4.5 years ago in EC two and it's, it's even amazing to see what's just happened in the last 4.5 years. So I'm with you. Nobody really expected the momentum, but EC two has really shone brightly in value to our customers. >>You know, we've done the public sector summit, you know, many times. It's a great event. Things are a little different in public sector as you well know. So talk about the public sector momentum with EC two and that journey. What have you seen? >>Yeah, so it's a great question day. So I had to go back in the time vault. You know, public sector was founded in 2010 and we were actually founded by the amazon process writing a paper setting up a two pizza team, which happened to be six people. And that journey really started with a lot of our public sector customers thinking that we don't know about the cloud. So we might want to do a pilot or just look at non mission critical workloads now public sector and I know you know this day but public sector is more than just government, it has education, not for profit healthcare and now space. But everybody at that time was very skeptical. So we had to really work hard to migrate some workloads over. And one of our very first non mission critical workloads was the U. S. Navy. Um and what they did was the Navy Media Services actually moved images over to EC two. Now today that seems like oh that's pretty easy. But back then that was a big monumental reference. Um and we had to spend a lot of time on training and education to win the hearts and souls of our customers. So back then we had half of the floor and Herndon Washington, we just had a few people and that room really became a training room. We trained our reps, we trained our customers um research drive. A lot of our early adopters accounts like Nasa and jpl. And um then when cloud first came out and governments that started with the U. S. A. And we announced Govcloud, you know, things really picked up, we had migration of significant workloads. So if you think back to that S. A. P. And just moving media over um with the Navy, the Navy and S. A. P. Migrated their largest S A P E R P solution to the cloud in that time as well. Um, then we started international. Our journey continued with the UK International was UK and us was us. Then we added a P. J. And latin America and Canada. And then of course the partner team which you know, is very close to my heart. Partners today are about 73% of our overall public sector business. And it started out with some interesting small pro program SVS being very crucial to that, accelerating adoption. And then of course now the journey has continued with Covid. That has really accelerated that movement to the cloud. And we're seeing, you know, use of ec two to really help us drive by the cute power needed for A I N. M. L. And taking all that data in from IOT and computing that data. And are they are. Um, and we're really seeing that journey just continue and we see no end in sight. >>So if we can stay in the infancy and sort of the adolescent years of public sector, I mean, remember, I mean as analysts, we were really excited about, you know, the the the introduction of of of of EC two. But but there was a lot of skepticism in whatever industry, financial services, healthcare concerns about security, I presume it was similar in public sector, but I'm interested in how you you dealt with those challenges, how you you listen to folks, you know, how did you drive that leadership to where it is today? >>Yeah, you're right. The the first questions were what is the cloud? Doesn't amazon sell books? What is this clown thing? Um, what is easy to, what is easy to stand for and then what the heck is an instance? You know, way back when there was one instance, it didn't even have a name. And today of course we have over 400 instant types with different names for each one. Um and the big challenges you asked about challenges, the big challenges that we had to face. Dave were first and foremost, how do we educate? Um we had to educate our employees and then we had to educate our customers. So we created these really innovative hands on training programmes, white boarding um, sessions that we needed. They were wildly popular. So we really have to do that and then also prove security as you know. So you asked how we listen to our customers and of course we followed the amazon way we work backwards from where we were. So at that time, customers needed education. And so we started there um, data was really important. We needed to make customer or data for government more available as well. So for instance, we first started hosting the Census Bureau for instance. Um and that was all on EC two. So we had lots of early adopters and I think the early adopters around EC two really helped us to remember. I said that the UK was our international office for a while. So we had NIH we had a genomes project and the UK Ministry of Justice as well. And we had to prove security out. We had to prove how this drove a structured GovCloud and then we had to also prove it out with our partners with things like helping them get fed ramped or other certifications. I'll for that sort of thing as well. And so we really lead in those early days through that education and training. Um we lead with pilots to show the potential of the possible and we lead with that security setting those security standards and those compliance certifications, always listening to the customer, always listening to the partner, knowing how important the partners we're going to be. So for example, recovery dot gov was the first government wide system that moved to the cloud. Um the recovery transparency board was first overseeing that Recovery act spending, which included stimulus tracking website. I don't know if you remember that, but they hosted the recovery dot gov On amazon.com using EC two. And that site quickly made information available to a million visitors per hour and at that time, that was amazing. And the cost savings were significant. We also launched Govcloud. You'd asked about GovCloud earlier and that federal cloud computing strategy when the U. S. Government came out with cloud first and they had to consider what is really going to compel these federal agencies to consider cloud. They had Public-sector customers had 70 requirements for security and safety of the data that we came out with Govcloud to open up all those great opportunities. And I think Dave we continue to leave because we are customer obsessed uh you know, still supporting more security standards and compliance sort than any other provider. Um You know, now we lead with data not just data for census or images for the US Navy, but we've got now data in space and ground station and data at scale with customers like Finra who's now doing 100 billion financial transactions. Not just that one million from the early days. So it has been a heck of a ride for public sector and I love the way that the public sector team really used and leveraged the leadership principles. Re invent and simplify dive deep. Be obsessed with the customers start where they are. Um and make sure that you're always always always listening to what they need. >>You know, it's interesting just observing public sector. It's not uncommon, especially because of the certifications that some of the services, you know come out after they come out for the commercial sector. And I remember years ago when I was at I. D. C. I was kind of the steward of the public sector business. And that was a time when everybody was trying to focus in public sector on commercial off the shelf software. That was the big thing. And they want to understand, they wanted to look at commercial use cases and how they could apply them to government. And when I dug in a little bit and met with generals and like eight different agencies, I was struck by how many really smart people and the things that they were doing. And I said at the time, you know, a lot of my commercial clients could learn a lot from you. And so the reason I bring that up is because I saw the same thing with Govcloud because there was a lot of skepticism in various industries, particularly regulated industries, financial services, healthcare. And then when Govcloud hit and the CIA deal hit, people said, whoa CIA, they're like the most security conscious industry or organization in the world. And so I feel as though in a way public sector led that that breakthrough. So I'm wondering when you think about EC two today and the momentum that it has in the government, Are there similar things that you see? Where's the momentum today in public sector? >>You are right on target day? I mean that CIA was a monumental moment and that momentum with ever increasing adoption to the cloud has continued in public sector. In fact today, public sector is one of our fastest growing areas. So we've got um, you know, thousands of startups or multiple countries that were helping out today to really ignite that innovation. We have over 4000 government agencies, 9000 education agencies. Um 2000 public sector partners from all over the globe. 24,000 not for profit organizations. And what I see is the way that they're using EC two um is is leading the pack now, especially after Covid, you know, many of these folks accelerated their journey because of Covid. They got to the cloud faster and now they are doing some really things that no one else is doing like sending an outpost postbox into space or leveraging, you know robots and health care for sure. So that momentum continues today and I love that you were the champion of that you know way back when even when you were with I. D. C. >>So I want to ask you, you sort of touched on some interesting use cases, what are some of the more unusual ones and maybe breakthrough use cases that you see? >>Oh so yeah we have a couple. So one is um I mentioned it earlier but there is a robot now that is powered by IOT and EC two and the robot helps to take temperature and and readings for folks that are entering the hospital in latin America really helped during Covid, one of my favorites. It actually blew the socks off of verne or two and you know that's hard to do is a space startup called lunar outpost and they are synthesizing oxygen on mars now that's, that's driven by Ec two. That's crazy. Right? Um, we see state governments like new york, they've got this vision zero traffic and they're leveraging that to prevent accidents all through new york city. I used to live in new york city. So this is really needed. Um, and it continues like with education, we see university of Illinois and Splunk one of our partners, they created a boarding pass for students to get back to school. So I have a daughter in college. Um, and you know, it's really hard for her to prove that she's had the vaccine or that she's tested negative on the covid test. They came out with a past of this little boarding pass, just like you used to get on an airplane to get into different classes and labs and then a couple of my favorites and you guys actually filmed the Cherokee nation. So the Cherokee nation, the chief of the Cherokee nation was on our silicon um show and silicon angles show and the cube featured them And as the chief talked about how he preserves the Cherokee language. And if you remember the Cherokee language has been used to help out the US in many different ways and Presidio. One of our partners helped to create a game, a super cool game that links in with unity To help teach that next generation the language while they're playing a game and then last but not least axle three d out of the UK. Um, they're using easy to, to save lives. They've created a three D imaging process for people getting ready to get kidney transplants and they have just enhanced that taken the time frame down for months. Now today's that they can actually articulate whether the kidney transplant will work. And when I talked to roger their Ceo, they're doing R. O. L return on life's not return on investment. So those are just some of the unusual and breakthrough use cases that we see powered by E. C. To >>Sandy. I'll give you the last word. Your final closing comments. >>Well, my final closing comments are happy birthday to ec two celebrating 15 years. What a game changer and value added. It has been the early days of Ec two. Of course we're about education like what is the cloud? Why is a bookseller doing it. But um, easy to really help to create a new hub of value Now. We've got customers moving so fast with modernization using a I. M and M. L. Containers survivalists. Um, and all of these things are really changing the game and leveling it up as we increased that business connection. So I think the future is really bright. We've only just begun. We've only just begun with EC two and we've only just begun with public sector. You know, our next great moments are still left to come. >>Well, Sandy, thanks so much. Always Great to see you. Really appreciate your time. >>Thank you so much. Dave. I really appreciate it. And happy birthday again to E. C. To keep >>It right there were celebrating Ec 2's 15th birthday right back. >>Mhm.

>>Individuals create developers, translate ideas to code, to create great applications and great applications. Touch everyone. A Docker. We know that collaboration is key to your innovation sharing ideas, working together. Launching the most secure applications. Docker is with you wherever your team innovates, whether it be robots or autonomous cars, we're doing research to save lives during a pandemic, revolutionizing, how to buy and sell goods online, or even going into the unknown frontiers of space. Docker is launching innovation everywhere. Join us on the journey to build, share, run the future. >>Hello and welcome to Docker con 2021. We're incredibly excited to have more than 80,000 of you join us today from all over the world. As it was last year, this year at DockerCon is 100% virtual and 100% free. So as to enable as many community members as possible to join us now, 100%. Virtual is also an acknowledgement of the continuing global pandemic in particular, the ongoing tragedies in India and Brazil, the Docker community is a global one. And on behalf of all Dr. Khan attendees, we are donating $10,000 to UNICEF support efforts to fight the virus in those countries. Now, even in those regions of the world where the pandemic is being brought under control, virtual first is the new normal. It's been a challenging transition. This includes our team here at Docker. And we know from talking with many of you that you and your developer teams are challenged by this as well. So to help application development teams better collaborate and ship faster, we've been working on some powerful new features and we thought it would be fun to start off with a demo of those. How about it? Want to have a look? All right. Then no further delay. I'd like to introduce Youi Cal and Ben, gosh, over to you and Ben >>Morning, Ben, thanks for jumping on real quick. >>Have you seen the email from Scott? The one about updates and the docs landing page Smith, the doc combat and more prominence. >>Yeah. I've got something working on my local machine. I haven't committed anything yet. I was thinking we could try, um, that new Docker dev environments feature. >>Yeah, that's cool. So if you hit the share button, what I should do is it will take all of your code and the dependencies and the image you're basing it on and wrap that up as one image for me. And I can then just monitor all my machines that have been one click, like, and then have it side by side, along with the changes I've been looking at as well, because I was also having a bit of a look and then I can really see how it differs to what I'm doing. Maybe I can combine it to do the best of both worlds. >>Sounds good. Uh, let me get that over to you, >>Wilson. Yeah. If you pay with the image name, I'll get that started up. >>All right. Sen send it over >>Cheesy. Okay, great. Let's have a quick look at what you he was doing then. So I've been messing around similar to do with the batter. I've got movie at the top here and I think it looks pretty cool. Let's just grab that image from you. Pick out that started on a dev environment. What this is doing. It's just going to grab the image down, which you can take all of the code, the dependencies only get brunches working on and I'll get that opened up in my idea. Ready to use. It's a here close. We can see our environment as my Molly image, just coming down there and I've got my new idea. >>We'll load this up and it'll just connect to my dev environment. There we go. It's connected to the container. So we're working all in the container here and now give it a moment. What we'll do is we'll see what changes you've been making as well on the code. So it's like she's been working on a landing page as well, and it looks like she's been changing the banner as well. So let's get this running. Let's see what she's actually doing and how it looks. We'll set up our checklist and then we'll see how that works. >>Great. So that's now rolling. So let's just have a look at what you use doing what changes she had made. Compare those to mine just jumped back into my dev container UI, see that I've got both of those running side by side with my changes and news changes. Okay. So she's put Molly up there rather than mobi or somebody had the same idea. So I think in a way I can make us both happy. So if we just jumped back into what we'll do, just add Molly and Moby and here I'll save that. And what we can see is, cause I'm just working within the container rather than having to do sort of rebuild of everything or serve, or just reload my content. No, that's straight the page. So what I can then do is I can come up with my browser here. Once that's all refreshed, refresh the page once hopefully, maybe twice, we should then be able to see your refresh it or should be able to see that we get Malia mobi come up. So there we go, got Molly mobi. So what we'll do now is we'll describe that state. It sends us our image and then we'll just create one of those to share with URI or share. And we'll get a link for that. I guess we'll send that back over to you. >>So I've had a look at what you were doing and I'm actually going to change. I think that might work for both of us. I wondered if you could take a look at it. If I send it over. >>Sounds good. Let me grab the link. >>Yeah, it's a dev environment link again. So if you just open that back in the doc dashboard, it should be able to open up the code that I've changed and then just run it in the same way you normally do. And that shouldn't interrupt what you're already working on because there'll be able to run side by side with your other brunch. You already got, >>Got it. Got it. Loading here. Well, that's great. It's Molly and movie together. I love it. I think we should ship it. >>Awesome. I guess it's chip it and get on with the rest of.com. Wasn't that cool. Thank you Joey. Thanks Ben. Everyone we'll have more of this later in the keynote. So stay tuned. Let's say earlier, we've all been challenged by this past year, whether the COVID pandemic, the complete evaporation of customer demand in many industries, unemployment or business bankruptcies, we all been touched in some way. And yet, even to miss these tragedies last year, we saw multiple sources of hope and inspiration. For example, in response to COVID we saw global communities, including the tech community rapidly innovate solutions for analyzing the spread of the virus, sequencing its genes and visualizing infection rates. In fact, if all in teams collaborating on solutions for COVID have created more than 1,400 publicly shareable images on Docker hub. As another example, we all witnessed the historic landing and exploration of Mars by the perseverance Rover and its ingenuity drone. >>Now what's common in these examples, these innovative and ambitious accomplishments were made possible not by any single individual, but by teams of individuals collaborating together. The power of teams is why we've made development teams central to Docker's mission to build tools and content development teams love to help them get their ideas from code to cloud as quickly as possible. One of the frictions we've seen that can slow down to them in teams is that the path from code to cloud can be a confusing one, riddle with multiple point products, tools, and images that need to be integrated and maintained an automated pipeline in order for teams to be productive. That's why a year and a half ago we refocused Docker on helping development teams make sense of all this specifically, our goal is to provide development teams with the trusted content, the sharing capabilities and the pipeline integrations with best of breed third-party tools to help teams ship faster in short, to provide a collaborative application development platform. >>Everything a team needs to build. Sharon run create applications. Now, as I noted earlier, it's been a challenging year for everyone on our planet and has been similar for us here at Docker. Our team had to adapt to working from home local lockdowns caused by the pandemic and other challenges. And despite all this together with our community and ecosystem partners, we accomplished many exciting milestones. For example, in open source together with the community and our partners, we open sourced or made major contributions to many projects, including OCI distribution and the composed plugins building on these open source projects. We had powerful new capabilities to the Docker product, both free and subscription. For example, support for WSL two and apple, Silicon and Docker, desktop and vulnerability scanning audit logs and image management and Docker hub. >>And finally delivering an easy to use well-integrated development experience with best of breed tools and content is only possible through close collaboration with our ecosystem partners. For example, this last year we had over 100 commercialized fees, join our Docker verified publisher program and over 200 open source projects, join our Docker sponsored open source program. As a result of these efforts, we've seen some exciting growth in the Docker community in the 12 months since last year's Docker con for example, the number of registered developers grew 80% to over 8 million. These developers created many new images increasing the total by 56% to almost 11 million. And the images in all these repositories were pulled by more than 13 million monthly active IP addresses totaling 13 billion pulls a month. Now while the growth is exciting by Docker, we're even more excited about the stories we hear from you and your development teams about how you're using Docker and its impact on your businesses. For example, cancer researchers and their bioinformatics development team at the Washington university school of medicine needed a way to quickly analyze their clinical trial results and then share the models, the data and the analysis with other researchers they use Docker because it gives them the ease of use choice of pipeline tools and speed of sharing so critical to their research. And most importantly to the lives of their patients stay tuned for another powerful customer story later in the keynote from Matt fall, VP of engineering at Oracle insights. >>So with this last year behind us, what's next for Docker, but challenge you this last year of force changes in how development teams work, but we felt for years to come. And what we've learned in our discussions with you will have long lasting impact on our product roadmap. One of the biggest takeaways from those discussions that you and your development team want to be quicker to adapt, to changes in your environment so you can ship faster. So what is DACA doing to help with this first trusted content to own the teams that can focus their energies on what is unique to their businesses and spend as little time as possible on undifferentiated work are able to adapt more quickly and ship faster in order to do so. They need to be able to trust other components that make up their app together with our partners. >>Docker is doubling down and providing development teams with trusted content and the tools they need to use it in their applications. Second, remote collaboration on a development team, asking a coworker to take a look at your code used to be as easy as swiveling their chair around, but given what's happened in the last year, that's no longer the case. So as you even been hinted in the demo at the beginning, you'll see us deliver more capabilities for remote collaboration within a development team. And we're enabling development team to quickly adapt to any team configuration all on prem hybrid, all work from home, helping them remain productive and focused on shipping third ecosystem integrations, those development teams that can quickly take advantage of innovations throughout the ecosystem. Instead of getting locked into a single monolithic pipeline, there'll be the ones able to deliver amps, which impact their businesses faster. >>So together with our ecosystem partners, we are investing in more integrations with best of breed tools, right? Integrated automated app pipelines. Furthermore, we'll be writing more public API APIs and SDKs to enable ecosystem partners and development teams to roll their own integrations. We'll be sharing more details about remote collaboration and ecosystem integrations. Later in the keynote, I'd like to take a moment to share with Docker and our partners are doing for trusted content, providing development teams, access to content. They can trust, allows them to focus their coding efforts on what's unique and differentiated to that end Docker and our partners are bringing more and more trusted content to Docker hub Docker official images are 160 images of popular upstream open source projects that serve as foundational building blocks for any application. These include operating systems, programming, languages, databases, and more. Furthermore, these are updated patch scan and certified frequently. So I said, no image is older than 30 days. >>Docker verified publisher images are published by more than 100 commercialized feeds. The image Rebos are explicitly designated verify. So the developers searching for components for their app know that the ISV is actively maintaining the image. Docker sponsored open source projects announced late last year features images for more than 200 open source communities. Docker sponsors these communities through providing free storage and networking resources and offering their community members unrestricted access repos for businesses allow businesses to update and share their apps privately within their organizations using role-based access control and user authentication. No, and finally, public repos for communities enable community projects to be freely shared with anonymous and authenticated users alike. >>And for all these different types of content, we provide services for both development teams and ISP, for example, vulnerability scanning and digital signing for enhanced security search and filtering for discoverability packaging and updating services and analytics about how these products are being used. All this trusted content, we make available to develop teams for them directly to discover poll and integrate into their applications. Our goal is to meet development teams where they live. So for those organizations that prefer to manage their internal distribution of trusted content, we've collaborated with leading container registry partners. We announced our partnership with J frog late last year. And today we're very pleased to announce our partnerships with Amazon and Miranda's for providing an integrated seamless experience for joint for our joint customers. Lastly, the container images themselves and this end to end flow are built on open industry standards, which provided all the teams with flexibility and choice trusted content enables development teams to rapidly build. >>As I let them focus on their unique differentiated features and use trusted building blocks for the rest. We'll be talking more about trusted content as well as remote collaboration and ecosystem integrations later in the keynote. Now ecosystem partners are not only integral to the Docker experience for development teams. They're also integral to a great DockerCon experience, but please join me in thanking our Dr. Kent on sponsors and checking out their talks throughout the day. I also want to thank some others first up Docker team. Like all of you this last year has been extremely challenging for us, but the Docker team rose to the challenge and worked together to continue shipping great product, the Docker community of captains, community leaders, and contributors with your welcoming newcomers, enthusiasm for Docker and open exchanges of best practices and ideas talker, wouldn't be Docker without you. And finally, our development team customers. >>You trust us to help you build apps. Your businesses rely on. We don't take that trust for granted. Thank you. In closing, we often hear about the tenant's developer capable of great individual feeds that can transform project. But I wonder if we, as an industry have perhaps gotten this wrong by putting so much emphasis on weight, on the individual as discussed at the beginning, great accomplishments like innovative responses to COVID-19 like landing on Mars are more often the results of individuals collaborating together as a team, which is why our mission here at Docker is delivered tools and content developers love to help their team succeed and become 10 X teams. Thanks again for joining us, we look forward to having a great DockerCon with you today, as well as a great year ahead of us. Thanks and be well. >>Hi, I'm Dana Lawson, VP of engineering here at get hub. And my job is to enable this rich interconnected community of builders and makers to build even more and hopefully have a great time doing it in order to enable the best platform for developers, which I know is something we are all passionate about. We need to partner across the ecosystem to ensure that developers can have a great experience across get hub and all the tools that they want to use. No matter what they are. My team works to build the tools and relationships to make that possible. I am so excited to join Scott on this virtual stage to talk about increasing developer velocity. So let's dive in now, I know this may be hard for some of you to believe, but as a former CIS admin, some 21 years ago, working on sense spark workstations, we've come such a long way for random scripts and desperate systems that we've stitched together to this whole inclusive developer workflow experience being a CIS admin. >>Then you were just one piece of the siloed experience, but I didn't want to just push code to production. So I created scripts that did it for me. I taught myself how to code. I was the model lazy CIS admin that got dangerous and having pushed a little too far. I realized that working in production and building features is really a team sport that we had the opportunity, all of us to be customer obsessed today. As developers, we can go beyond the traditional dev ops mindset. We can really focus on adding value to the customer experience by ensuring that we have work that contributes to increasing uptime via and SLS all while being agile and productive. We get there. When we move from a pass the Baton system to now having an interconnected developer workflow that increases velocity in every part of the cycle, we get to work better and smarter. >>And honestly, in a way that is so much more enjoyable because we automate away all the mundane and manual and boring tasks. So we get to focus on what really matters shipping, the things that humans get to use and love. Docker has been a big part of enabling this transformation. 10, 20 years ago, we had Tomcat containers, which are not Docker containers. And for y'all hearing this the first time go Google it. But that was the way we built our applications. We had to segment them on the server and give them resources. Today. We have Docker containers, these little mini Oasys and Docker images. You can do it multiple times in an orchestrated manner with the power of actions enabled and Docker. It's just so incredible what you can do. And by the way, I'm showing you actions in Docker, which I hope you use because both are great and free for open source. >>But the key takeaway is really the workflow and the automation, which you certainly can do with other tools. Okay, I'm going to show you just how easy this is, because believe me, if this is something I can learn and do anybody out there can, and in this demo, I'll show you about the basic components needed to create and use a package, Docker container actions. And like I said, you won't believe how awesome the combination of Docker and actions is because you can enable your workflow to do no matter what you're trying to do in this super baby example. We're so small. You could take like 10 seconds. Like I am here creating an action due to a simple task, like pushing a message to your logs. And the cool thing is you can use it on any the bit on this one. Like I said, we're going to use push. >>You can do, uh, even to order a pizza every time you roll into production, if you wanted, but at get hub, that'd be a lot of pizzas. And the funny thing is somebody out there is actually tried this and written that action. If you haven't used Docker and actions together, check out the docs on either get hub or Docker to get you started. And a huge shout out to all those doc writers out there. I built this demo today using those instructions. And if I can do it, I know you can too, but enough yapping let's get started to save some time. And since a lot of us are Docker and get hub nerds, I've already created a repo with a Docker file. So we're going to skip that step. Next. I'm going to create an action's Yammel file. And if you don't Yammer, you know, actions, the metadata defines my important log stuff to capture and the input and my time out per parameter to pass and puts to the Docker container, get up a build image from your Docker file and run the commands in a new container. >>Using the Sigma image. The cool thing is, is you can use any Docker image in any language for your actions. It doesn't matter if it's go or whatever in today's I'm going to use a shell script and an input variable to print my important log stuff to file. And like I said, you know me, I love me some. So let's see this action in a workflow. When an action is in a private repo, like the one I demonstrating today, the action can only be used in workflows in the same repository, but public actions can be used by workflows in any repository. So unfortunately you won't get access to the super awesome action, but don't worry in the Guild marketplace, there are over 8,000 actions available, especially the most important one, that pizza action. So go try it out. Now you can do this in a couple of ways, whether you're doing it in your preferred ID or for today's demo, I'm just going to use the gooey. I'm going to navigate to my actions tab as I've done here. And I'm going to in my workflow, select new work, hello, probably load some workflows to Claire to get you started, but I'm using the one I've copied. Like I said, the lazy developer I am in. I'm going to replace it with my action. >>That's it. So now we're going to go and we're going to start our commitment new file. Now, if we go over to our actions tab, we can see the workflow in progress in my repository. I just click the actions tab. And because they wrote the actions on push, we can watch the visualization under jobs and click the job to see the important stuff we're logging in the input stamp in the printed log. And we'll just wait for this to run. Hello, Mona and boom. Just like that. It runs automatically within our action. We told it to go run as soon as the files updated because we're doing it on push merge. That's right. Folks in just a few minutes, I built an action that writes an entry to a log file every time I push. So I don't have to do it manually. In essence, with automation, you can be kind to your future self and save time and effort to focus on what really matters. >>Imagine what I could do with even a little more time, probably order all y'all pieces. That is the power of the interconnected workflow. And it's amazing. And I hope you all go try it out, but why do we care about all of that? Just like in the demo, I took a manual task with both tape, which both takes time and it's easy to forget and automated it. So I don't have to think about it. And it's executed every time consistently. That means less time for me to worry about my human errors and mistakes, and more time to focus on actually building the cool stuff that people want. Obviously, automation, developer productivity, but what is even more important to me is the developer happiness tools like BS, code actions, Docker, Heroku, and many others reduce manual work, which allows us to focus on building things that are awesome. >>And to get into that wonderful state that we call flow. According to research by UC Irvine in Humboldt university in Germany, it takes an average of 23 minutes to enter optimal creative state. What we call the flow or to reenter it after distraction like your dog on your office store. So staying in flow is so critical to developer productivity and as a developer, it just feels good to be cranking away at something with deep focus. I certainly know that I love that feeling intuitive collaboration and automation features we built in to get hub help developer, Sam flow, allowing you and your team to do so much more, to bring the benefits of automation into perspective in our annual October's report by Dr. Nicole, Forsgren. One of my buddies here at get hub, took a look at the developer productivity in the stork year. You know what we found? >>We found that public GitHub repositories that use the Automational pull requests, merge those pull requests. 1.2 times faster. And the number of pooled merged pull requests increased by 1.3 times, that is 34% more poor requests merged. And other words, automation can con can dramatically increase, but the speed and quantity of work completed in any role, just like an open source development, you'll work more efficiently with greater impact when you invest the bulk of your time in the work that adds the most value and eliminate or outsource the rest because you don't need to do it, make the machines by elaborate by leveraging automation in their workflows teams, minimize manual work and reclaim that time for innovation and maintain that state of flow with development and collaboration. More importantly, their work is more enjoyable because they're not wasting the time doing the things that the machines or robots can do for them. >>And I remember what I said at the beginning. Many of us want to be efficient, heck even lazy. So why would I spend my time doing something I can automate? Now you can read more about this research behind the art behind this at October set, get hub.com, which also includes a lot of other cool info about the open source ecosystem and how it's evolving. Speaking of the open source ecosystem we at get hub are so honored to be the home of more than 65 million developers who build software together for everywhere across the globe. Today, we're seeing software development taking shape as the world's largest team sport, where development teams collaborate, build and ship products. It's no longer a solo effort like it was for me. You don't have to take my word for it. Check out this globe. This globe shows real data. Every speck of light you see here represents a contribution to an open source project, somewhere on earth. >>These arts reach across continents, cultures, and other divides. It's distributed collaboration at its finest. 20 years ago, we had no concept of dev ops, SecOps and lots, or the new ops that are going to be happening. But today's development and ops teams are connected like ever before. This is only going to continue to evolve at a rapid pace, especially as we continue to empower the next hundred million developers, automation helps us focus on what's important and to greatly accelerate innovation. Just this past year, we saw some of the most groundbreaking technological advancements and achievements I'll say ever, including critical COVID-19 vaccine trials, as well as the first power flight on Mars. This past month, these breakthroughs were only possible because of the interconnected collaborative open source communities on get hub and the amazing tools and workflows that empower us all to create and innovate. Let's continue building, integrating, and automating. So we collectively can give developers the experience. They deserve all of the automation and beautiful eye UIs that we can muster so they can continue to build the things that truly do change the world. Thank you again for having me today, Dr. Khan, it has been a pleasure to be here with all you nerds. >>Hello. I'm Justin. Komack lovely to see you here. Talking to developers, their world is getting much more complex. Developers are being asked to do everything security ops on goal data analysis, all being put on the rockers. Software's eating the world. Of course, and this all make sense in that view, but they need help. One team. I told you it's shifted all our.net apps to run on Linux from windows, but their developers found the complexity of Docker files based on the Linux shell scripts really difficult has helped make these things easier for your teams. Your ones collaborate more in a virtual world, but you've asked us to make this simpler and more lightweight. You, the developers have asked for a paved road experience. You want things to just work with a simple options to be there, but it's not just the paved road. You also want to be able to go off-road and do interesting and different things. >>Use different components, experiments, innovate as well. We'll always offer you both those choices at different times. Different developers want different things. It may shift for ones the other paved road or off road. Sometimes you want reliability, dependability in the zone for day to day work, but sometimes you have to do something new, incorporate new things in your pipeline, build applications for new places. Then you knew those off-road abilities too. So you can really get under the hood and go and build something weird and wonderful and amazing. That gives you new options. Talk as an independent choice. We don't own the roads. We're not pushing you into any technology choices because we own them. We're really supporting and driving open standards, such as ISEI working opensource with the CNCF. We want to help you get your applications from your laptops, the clouds, and beyond, even into space. >>Let's talk about the key focus areas, that frame, what DACA is doing going forward. These are simplicity, sharing, flexibility, trusted content and care supply chain compared to building where the underlying kernel primitives like namespaces and Seagraves the original Docker CLI was just amazing Docker engine. It's a magical experience for everyone. It really brought those innovations and put them in a world where anyone would use that, but that's not enough. We need to continue to innovate. And it was trying to get more done faster all the time. And there's a lot more we can do. We're here to take complexity away from deeply complicated underlying things and give developers tools that are just amazing and magical. One of the area we haven't done enough and make things magical enough that we're really planning around now is that, you know, Docker images, uh, they're the key parts of your application, but you know, how do I do something with an image? How do I, where do I attach volumes with this image? What's the API. Whereas the SDK for this image, how do I find an example or docs in an API driven world? Every bit of software should have an API and an API description. And our vision is that every container should have this API description and the ability for you to understand how to use it. And it's all a seamless thing from, you know, from your code to the cloud local and remote, you can, you can use containers in this amazing and exciting way. >>One thing I really noticed in the last year is that companies that started off remote fast have constant collaboration. They have zoom calls, apron all day terminals, shattering that always working together. Other teams are really trying to learn how to do this style because they didn't start like that. We used to walk around to other people's desks or share services on the local office network. And it's very difficult to do that anymore. You want sharing to be really simple, lightweight, and informal. Let me try your container or just maybe let's collaborate on this together. Um, you know, fast collaboration on the analysts, fast iteration, fast working together, and he wants to share more. You want to share how to develop environments, not just an image. And we all work by seeing something someone else in our team is doing saying, how can I do that too? I can, I want to make that sharing really, really easy. Ben's going to talk about this more in the interest of one minute. >>We know how you're excited by apple. Silicon and gravis are not excited because there's a new architecture, but excited because it's faster, cooler, cheaper, better, and offers new possibilities. The M one support was the most asked for thing on our public roadmap, EFA, and we listened and share that we see really exciting possibilities, usership arm applications, all the way from desktop to production. We know that you all use different clouds and different bases have deployed to, um, you know, we work with AWS and Azure and Google and more, um, and we want to help you ship on prime as well. And we know that you use huge number of languages and the containers help build applications that use different languages for different parts of the application or for different applications, right? You can choose the best tool. You have JavaScript hat or everywhere go. And re-ask Python for data and ML, perhaps getting excited about WebAssembly after hearing about a cube con, you know, there's all sorts of things. >>So we need to make that as easier. We've been running the whole month of Python on the blog, and we're doing a month of JavaScript because we had one specific support about how do I best put this language into production of that language into production. That detail is important for you. GPS have been difficult to use. We've added GPS suppose in desktop for windows, but we know there's a lot more to do to make the, how multi architecture, multi hardware, multi accelerator world work better and also securely. Um, so there's a lot more work to do to support you in all these things you want to do. >>How do we start building a tenor has applications, but it turns out we're using existing images as components. I couldn't assist survey earlier this year, almost half of container image usage was public images rather than private images. And this is growing rapidly. Almost all software has open source components and maybe 85% of the average application is open source code. And what you're doing is taking whole container images as modules in your application. And this was always the model with Docker compose. And it's a model that you're already et cetera, writing you trust Docker, official images. We know that they might go to 25% of poles on Docker hub and Docker hub provides you the widest choice and the best support that trusted content. We're talking to people about how to make this more helpful. We know, for example, that winter 69 four is just showing us as support, but the image doesn't yet tell you that we're working with canonical to improve messaging from specific images about left lifecycle and support. >>We know that you need more images, regularly updated free of vulnerabilities, easy to use and discover, and Donnie and Marie neuro, going to talk about that more this last year, the solar winds attack has been in the, in the news. A lot, the software you're using and trusting could be compromised and might be all over your organization. We need to reduce the risk of using vital open-source components. We're seeing more software supply chain attacks being targeted as the supply chain, because it's often an easier place to attack and production software. We need to be able to use this external code safely. We need to, everyone needs to start from trusted sources like photography images. They need to scan for known vulnerabilities using Docker scan that we built in partnership with sneak and lost DockerCon last year, we need just keep updating base images and dependencies, and we'll, we're going to help you have the control and understanding about your images that you need to do this. >>And there's more, we're also working on the nursery V2 project in the CNCF to revamp container signings, or you can tell way or software comes from we're working on tooling to make updates easier, and to help you understand and manage all the principals carrier you're using security is a growing concern for all of us. It's really important. And we're going to help you work with security. We can't achieve all our dreams, whether that's space travel or amazing developer products ever see without deep partnerships with our community to cloud is RA and the cloud providers aware most of you ship your occasion production and simple routes that take your work and deploy it easily. Reliably and securely are really important. Just get into production simply and easily and securely. And we've done a bunch of work on that. And, um, but we know there's more to do. >>The CNCF on the open source cloud native community are an amazing ecosystem of creators and lovely people creating an amazing strong community and supporting a huge amount of innovation has its roots in the container ecosystem and his dreams beyond that much of the innovation is focused around operate experience so far, but developer experience is really a growing concern in that community as well. And we're really excited to work on that. We also uses appraiser tool. Then we know you do, and we know that you want it to be easier to use in your environment. We just shifted Docker hub to work on, um, Kubernetes fully. And, um, we're also using many of the other projects are Argo from atheists. We're spending a lot of time working with Microsoft, Amazon right now on getting natural UV to ready to ship in the next few. That's a really detailed piece of collaboration we've been working on for a long term. Long time is really important for our community as the scarcity of the container containers and, um, getting content for you, working together makes us stronger. Our community is made up of all of you have. Um, it's always amazing to be reminded of that as a huge open source community that we already proud to work with. It's an amazing amount of innovation that you're all creating and where perhaps it, what with you and share with you as well. Thank you very much. And thank you for being here. >>Really excited to talk to you today and share more about what Docker is doing to help make you faster, make your team faster and turn your application delivery into something that makes you a 10 X team. What we're hearing from you, the developers using Docker everyday fits across three common themes that we hear consistently over and over. We hear that your time is super important. It's critical, and you want to move faster. You want your tools to get out of your way, and instead to enable you to accelerate and focus on the things you want to be doing. And part of that is that finding great content, great application components that you can incorporate into your apps to move faster is really hard. It's hard to discover. It's hard to find high quality content that you can trust that, you know, passes your test and your configuration needs. >>And it's hard to create good content as well. And you're looking for more safety, more guardrails to help guide you along that way so that you can focus on creating value for your company. Secondly, you're telling us that it's a really far to collaborate effectively with your team and you want to do more, to work more effectively together to help your tools become more and more seamless to help you stay in sync, both with yourself across all of your development environments, as well as with your teammates so that you can more effectively collaborate together. Review each other's work, maintain things and keep them in sync. And finally, you want your applications to run consistently in every single environment, whether that's your local development environment, a cloud-based development environment, your CGI pipeline, or the cloud for production, and you want that micro service to provide that consistent experience everywhere you go so that you have similar tools, similar environments, and you don't need to worry about things getting in your way, but instead things make it easy for you to focus on what you wanna do and what Docker is doing to help solve all of these problems for you and your colleagues is creating a collaborative app dev platform. >>And this collaborative application development platform consists of multiple different pieces. I'm not going to walk through all of them today, but the overall view is that we're providing all the tooling you need from the development environment, to the container images, to the collaboration services, to the pipelines and integrations that enable you to focus on making your applications amazing and changing the world. If we start zooming on a one of those aspects, collaboration we hear from developers regularly is that they're challenged in synchronizing their own setups across environments. They want to be able to duplicate the setup of their teammates. Look, then they can easily get up and running with the same applications, the same tooling, the same version of the same libraries, the same frameworks. And they want to know if their applications are good before they're ready to share them in an official space. >>They want to collaborate on things before they're done, rather than feeling like they have to officially published something before they can effectively share it with others to work on it, to solve this. We're thrilled today to announce Docker, dev environments, Docker, dev environments, transform how your team collaborates. They make creating, sharing standardized development environments. As simple as a Docker poll, they make it easy to review your colleagues work without affecting your own work. And they increase the reproducibility of your own work and decreased production issues in doing so because you've got consistent environments all the way through. Now, I'm going to pass it off to our principal product manager, Ben Gotch to walk you through more detail on Docker dev environments. >>Hi, I'm Ben. I work as a principal program manager at DACA. One of the areas that doc has been looking at to see what's hard today for developers is sharing changes that you make from the inner loop where the inner loop is a better development, where you write code, test it, build it, run it, and ultimately get feedback on those changes before you merge them and try and actually ship them out to production. Most amount of us build this flow and get there still leaves a lot of challenges. People need to jump between branches to look at each other's work. Independence. Dependencies can be different when you're doing that and doing this in this new hybrid wall of work. Isn't any easier either the ability to just save someone, Hey, come and check this out. It's become much harder. People can't come and sit down at your desk or take your laptop away for 10 minutes to just grab and look at what you're doing. >>A lot of the reason that development is hard when you're remote, is that looking at changes and what's going on requires more than just code requires all the dependencies and everything you've got set up and that complete context of your development environment, to understand what you're doing and solving this in a remote first world is hard. We wanted to look at how we could make this better. Let's do that in a way that let you keep working the way you do today. Didn't want you to have to use a browser. We didn't want you to have to use a new idea. And we wanted to do this in a way that was application centric. We wanted to let you work with all the rest of the application already using C for all the services and all those dependencies you need as part of that. And with that, we're excited to talk more about docket developer environments, dev environments are new part of the Docker experience that makes it easier you to get started with your whole inner leap, working inside a container, then able to share and collaborate more than just the code. >>We want it to enable you to share your whole modern development environment, your whole setup from DACA, with your team on any operating system, we'll be launching a limited beta of dev environments in the coming month. And a GA dev environments will be ID agnostic and supporting composts. This means you'll be able to use an extend your existing composed files to create your own development environment in whatever idea, working in dev environments designed to be local. First, they work with Docker desktop and say your existing ID, and let you share that whole inner loop, that whole development context, all of your teammates in just one collect. This means if you want to get feedback on the working progress change or the PR it's as simple as opening another idea instance, and looking at what your team is working on because we're using compose. You can just extend your existing oppose file when you're already working with, to actually create this whole application and have it all working in the context of the rest of the services. >>So it's actually the whole environment you're working with module one service that doesn't really understand what it's doing alone. And with that, let's jump into a quick demo. So you can see here, two dev environments up and running. First one here is the same container dev environment. So if I want to go into that, let's see what's going on in the various code button here. If that one open, I can get straight into my application to start making changes inside that dev container. And I've got all my dependencies in here, so I can just run that straight in that second application I have here is one that's opened up in compose, and I can see that I've also got my backend, my front end and my database. So I've got all my services running here. So if I want, I can open one or more of these in a dev environment, meaning that that container has the context that dev environment has the context of the whole application. >>So I can get back into and connect to all the other services that I need to test this application properly, all of them, one unit. And then when I've made my changes and I'm ready to share, I can hit my share button type in the refund them on to share that too. And then give that image to someone to get going, pick that up and just start working with that code and all my dependencies, simple as putting an image, looking ahead, we're going to be expanding development environments, more of your dependencies for the whole developer worst space. We want to look at backing up and letting you share your volumes to make data science and database setups more repeatable and going. I'm still all of this under a single workspace for your team containing images, your dev environments, your volumes, and more we've really want to allow you to create a fully portable Linux development environment. >>So everyone you're working with on any operating system, as I said, our MVP we're coming next month. And that was for vs code using their dev container primitive and more support for other ideas. We'll follow to find out more about what's happening and what's coming up next in the future of this. And to actually get a bit of a deeper dive in the experience. Can we check out the talk I'm doing with Georgie and girl later on today? Thank you, Ben, amazing story about how Docker is helping to make developer teams more collaborative. Now I'd like to talk more about applications while the dev environment is like the workbench around what you're building. The application itself has all the different components, libraries, and frameworks, and other code that make up the application itself. And we hear developers saying all the time things like, how do they know if their images are good? >>How do they know if they're secure? How do they know if they're minimal? How do they make great images and great Docker files and how do they keep their images secure? And up-to-date on every one of those ties into how do I create more trust? How do I know that I'm building high quality applications to enable you to do this even more effectively than today? We are pleased to announce the DACA verified polisher program. This broadens trusted content by extending beyond Docker official images, to give you more and more trusted building blocks that you can incorporate into your applications. It gives you confidence that you're getting what you expect because Docker verifies every single one of these publishers to make sure they are who they say they are. This improves our secure supply chain story. And finally it simplifies your discovery of the best building blocks by making it easy for you to find things that you know, you can trust so that you can incorporate them into your applications and move on and on the right. You can see some examples of the publishers that are involved in Docker, official images and our Docker verified publisher program. Now I'm pleased to introduce you to marina. Kubicki our senior product manager who will walk you through more about what we're doing to create a better experience for you around trust. >>Thank you, Dani, >>Mario Andretti, who is a famous Italian sports car driver. One said that if everything feels under control, you're just not driving. You're not driving fast enough. Maya Andretti is not a software developer and a software developers. We know that no matter how fast we need to go in order to drive the innovation that we're working on, we can never allow our applications to spin out of control and a Docker. As we continue talking to our, to the developers, what we're realizing is that in order to reach that speed, the developers are the, the, the development community is looking for the building blocks and the tools that will, they will enable them to drive at the speed that they need to go and have the trust in those building blocks. And in those tools that they will be able to maintain control over their applications. So as we think about some of the things that we can do to, to address those concerns, uh, we're realizing that we can pursue them in a number of different venues, including creating reliable content, including creating partnerships that expands the options for the reliable content. >>Um, in order to, in a we're looking at creating integrations, no link security tools, talk about the reliable content. The first thing that comes to mind are the Docker official images, which is a program that we launched several years ago. And this is a set of curated, actively maintained, open source images that, uh, include, uh, operating systems and databases and programming languages. And it would become immensely popular for, for, for creating the base layers of, of the images of, of the different images, images, and applications. And would we realizing that, uh, many developers are, instead of creating something from scratch, basically start with one of the official images for their basis, and then build on top of that. And this program has become so popular that it now makes up a quarter of all of the, uh, Docker poles, which essentially ends up being several billion pulse every single month. >>As we look beyond what we can do for the open source. Uh, we're very ability on the open source, uh, spectrum. We are very excited to announce that we're launching the Docker verified publishers program, which is continuing providing the trust around the content, but now working with, uh, some of the industry leaders, uh, in multiple, in multiple verticals across the entire technology technical spec, it costs entire, uh, high tech in order to provide you with more options of the images that you can use for building your applications. And it still comes back to trust that when you are searching for content in Docker hub, and you see the verified publisher badge, you know, that this is, this is the content that, that is part of the, that comes from one of our partners. And you're not running the risk of pulling the malicious image from an employee master source. >>As we look beyond what we can do for, for providing the reliable content, we're also looking at some of the tools and the infrastructure that we can do, uh, to create a security around the content that you're creating. So last year at the last ad, the last year's DockerCon, we announced partnership with sneak. And later on last year, we launched our DACA, desktop and Docker hub vulnerability scans that allow you the options of writing scans in them along multiple points in your dev cycle. And in addition to providing you with information on the vulnerability on, on the vulnerabilities, in, in your code, uh, it also provides you with a guidance on how to re remediate those vulnerabilities. But as we look beyond the vulnerability scans, we're also looking at some of the other things that we can do, you know, to, to, to, uh, further ensure that the integrity and the security around your images, your images, and with that, uh, later on this year, we're looking to, uh, launch the scope, personal access tokens, and instead of talking about them, I will simply show you what they look like. >>So if you can see here, this is my page in Docker hub, where I've created a four, uh, tokens, uh, read-write delete, read, write, read only in public read in public creeper read only. So, uh, earlier today I went in and I, I logged in, uh, with my read only token. And when you see, when I'm going to pull an image, it's going to allow me to pull an image, not a problem success. And then when I do the next step, I'm going to ask to push an image into the same repo. Uh, would you see is that it's going to give me an error message saying that they access is denied, uh, because there is an additional authentication required. So these are the things that we're looking to add to our roadmap. As we continue thinking about the things that we can do to provide, um, to provide additional building blocks, content, building blocks, uh, and, and, and tools to build the trust so that our DACA developer and skinned code faster than Mario Andretti could ever imagine. Uh, thank you to >>Thank you, marina. It's amazing what you can do to improve the trusted content so that you can accelerate your development more and move more quickly, move more collaboratively and build upon the great work of others. Finally, we hear over and over as that developers are working on their applications that they're looking for, environments that are consistent, that are the same as production, and that they want their applications to really run anywhere, any environment, any architecture, any cloud one great example is the recent announcement of apple Silicon. We heard from developers on uproar that they needed Docker to be available for that architecture before they could add those to it and be successful. And we listened. And based on that, we are pleased to share with you Docker, desktop on apple Silicon. This enables you to run your apps consistently anywhere, whether that's developing on your team's latest dev hardware, deploying an ARM-based cloud environments and having a consistent architecture across your development and production or using multi-year architecture support, which enables your whole team to collaborate on its application, using private repositories on Docker hub, and thrilled to introduce you to Hughie cower, senior director for product management, who will walk you through more of what we're doing to create a great developer experience. >>Senior director of product management at Docker. And I'd like to jump straight into a demo. This is the Mac mini with the apple Silicon processor. And I want to show you how you can now do an end-to-end arm workflow from my M one Mac mini to raspberry PI. As you can see, we have vs code and Docker desktop installed on a, my, the Mac mini. I have a small example here, and I have a raspberry PI three with an led strip, and I want to turn those LEDs into a moving rainbow. This Dockerfile here, builds the application. We build the image with the Docker, build X command to make the image compatible for all raspberry pies with the arm. 64. Part of this build is built with the native power of the M one chip. I also add the push option to easily share the image with my team so they can give it a try to now Dr. >>Creates the local image with the application and uploads it to Docker hub after we've built and pushed the image. We can go to Docker hub and see the new image on Docker hub. You can also explore a variety of images that are compatible with arm processors. Now let's go to the raspberry PI. I have Docker already installed and it's running Ubuntu 64 bit with the Docker run command. I can run the application and let's see what will happen from there. You can see Docker is downloading the image automatically from Docker hub and when it's running, if it's works right, there are some nice colors. And with that, if we have an end-to-end workflow for arm, where continuing to invest into providing you a great developer experience, that's easy to install. Easy to get started with. As you saw in the demo, if you're interested in the new Mac, mini are interested in developing for our platforms in general, we've got you covered with the same experience you've come to expect from Docker with over 95,000 arm images on hub, including many Docker official images. >>We think you'll find what you're looking for. Thank you again to the community that helped us to test the tech previews. We're so delighted to hear when folks say that the new Docker desktop for apple Silicon, it just works for them, but that's not all we've been working on. As Dani mentioned, consistency of developer experience across environments is so important. We're introducing composed V2 that makes compose a first-class citizen in the Docker CLI you no longer need to install a separate composed biter in order to use composed, deploying to production is simpler than ever with the new compose integration that enables you to deploy directly to Amazon ECS or Azure ACI with the same methods you use to run your application locally. If you're interested in running slightly different services, when you're debugging versus testing or, um, just general development, you can manage that all in one place with the new composed service to hear more about what's new and Docker desktop, please join me in the three 15 breakout session this afternoon. >>And now I'd love to tell you a bit more about bill decks and convince you to try it. If you haven't already it's our next gen build command, and it's no longer experimental as shown in the demo with built X, you'll be able to do multi architecture builds, share those builds with your team and the community on Docker hub. With build X, you can speed up your build processes with remote caches or build all the targets in your composed file in parallel with build X bake. And there's so much more if you're using Docker, desktop or Docker, CE you can use build X checkout tonus is talk this afternoon at three 45 to learn more about build X. And with that, I hope everyone has a great Dr. Khan and back over to you, Donnie. >>Thank you UA. It's amazing to hear about what we're doing to create a better developer experience and make sure that Docker works everywhere you need to work. Finally, I'd like to wrap up by showing you everything that we've announced today and everything that we've done recently to make your lives better and give you more and more for the single price of your Docker subscription. We've announced the Docker verified publisher program we've announced scoped personal access tokens to make it easier for you to have a secure CCI pipeline. We've announced Docker dev environments to improve your collaboration with your team. Uh, we shared with you Docker, desktop and apple Silicon, to make sure that, you know, Docker runs everywhere. You need it to run. And we've announced Docker compose version two, finally making it a first-class citizen amongst all the other great Docker tools. And we've done so much more recently as well from audit logs to advanced image management, to compose service profiles, to improve where you can run Docker more easily. >>Finally, as we look forward, where we're headed in the upcoming year is continuing to invest in these themes of helping you build, share, and run modern apps more effectively. We're going to be doing more to help you create a secure supply chain with which only grows more and more important as time goes on. We're going to be optimizing your update experience to make sure that you can easily understand the current state of your application, all its components and keep them all current without worrying about breaking everything as you're doing. So we're going to make it easier for you to synchronize your work. Using cloud sync features. We're going to improve collaboration through dev environments and beyond, and we're going to do make it easy for you to run your microservice in your environments without worrying about things like architecture or differences between those environments. Thank you so much. I'm thrilled about what we're able to do to help make your lives better. And now you're going to be hearing from one of our customers about what they're doing to launch their business with Docker >>I'm Matt Falk, I'm the head of engineering and orbital insight. And today I want to talk to you a little bit about data from space. So who am I like many of you, I'm a software developer and a software developer about seven companies so far, and now I'm a head of engineering. So I spend most of my time doing meetings, but occasionally I'll still spend time doing design discussions, doing code reviews. And in my free time, I still like to dabble on things like project oiler. So who's Oberlin site. What do we do? Portal insight is a large data supplier and analytics provider where we take data geospatial data anywhere on the planet, any overhead sensor, and translate that into insights for the end customer. So specifically we have a suite of high performance, artificial intelligence and machine learning analytics that run on this geospatial data. >>And we build them to specifically determine natural and human service level activity anywhere on the planet. What that really means is we take any type of data associated with a latitude and longitude and we identify patterns so that we can, so we can detect anomalies. And that's everything that we do is all about identifying those patterns to detect anomalies. So more specifically, what type of problems do we solve? So supply chain intelligence, this is one of the use cases that we we'd like to talk about a lot. It's one of our main primary verticals that we go after right now. And as Scott mentioned earlier, this had a huge impact last year when COVID hit. So specifically supply chain intelligence is all about identifying movement patterns to and from operating facilities to identify changes in those supply chains. How do we do this? So for us, we can do things where we track the movement of trucks. >>So identifying trucks, moving from one location to another in aggregate, same thing we can do with foot traffic. We can do the same thing for looking at aggregate groups of people moving from one location to another and analyzing their patterns of life. We can look at two different locations to determine how people are moving from one location to another, or going back and forth. All of this is extremely valuable for detecting how a supply chain operates and then identifying the changes to that supply chain. As I said last year with COVID, everything changed in particular supply chains changed incredibly, and it was hugely important for customers to know where their goods or their products are coming from and where they were going, where there were disruptions in their supply chain and how that's affecting their overall supply and demand. So to use our platform, our suite of tools, you can start to gain a much better picture of where your suppliers or your distributors are going from coming from or going to. >>So what's our team look like? So my team is currently about 50 engineers. Um, we're spread into four different teams and the teams are structured like this. So the first team that we have is infrastructure engineering and this team largely deals with deploying our Dockers using Kubernetes. So this team is all about taking Dockers, built by other teams, sometimes building the Dockers themselves and putting them into our production system, our platform engineering team, they produce these microservices. So they produce microservice, Docker images. They develop and test with them locally. Their entire environments are dockerized. They produce these doctors, hand them over to him for infrastructure engineering to be deployed. Similarly, our product engineering team does the same thing. They develop and test with Dr. Locally. They also produce a suite of Docker images that the infrastructure team can then deploy. And lastly, we have our R and D team, and this team specifically produces machine learning algorithms using Nvidia Docker collectively, we've actually built 381 Docker repositories and 14 million. >>We've had 14 million Docker pools over the lifetime of the company, just a few stats about us. Um, but what I'm really getting to here is you can see actually doctors becoming almost a form of communication between these teams. So one of the paradigms in software engineering that you're probably familiar with encapsulation, it's really helpful for a lot of software engineering problems to break the problem down, isolate the different pieces of it and start building interfaces between the code. This allows you to scale different pieces of the platform or different pieces of your code in different ways that allows you to scale up certain pieces and keep others at a smaller level so that you can meet customer demands. And for us, one of the things that we can largely do now is use Dockers as that interface. So instead of having an entire platform where all teams are talking to each other, and everything's kind of, mishmashed in a monolithic application, we can now say this team is only able to talk to this team by passing over a particular Docker image that defines the interface of what needs to be built before it passes to the team and really allows us to scalp our development and be much more efficient. >>Also, I'd like to say we are hiring. Um, so we have a number of open roles. We have about 30 open roles in our engineering team that we're looking to fill by the end of this year. So if any of this sounds really interesting to you, please reach out after the presentation. >>So what does our platform do? Really? Our platform allows you to answer any geospatial question, and we do this at three different inputs. So first off, where do you want to look? So we did this as what we call an AOI or an area of interest larger. You can think of this as a polygon drawn on the map. So we have a curated data set of almost 4 million AOIs, which you can go and you can search and use for your analysis, but you're also free to build your own. Second question is what you want to look for. We do this with the more interesting part of our platform of our machine learning and AI capabilities. So we have a suite of algorithms that automatically allow you to identify trucks, buildings, hundreds of different types of aircraft, different types of land use, how many people are moving from one location to another different locations that people in a particular area are moving to or coming from all of these different analyses or all these different analytics are available at the click of a button, and then determine what you want to look for. >>Lastly, you determine when you want to find what you're looking for. So that's just, uh, you know, do you want to look for the next three hours? Do you want to look for the last week? Do you want to look every month for the past two, whatever the time cadence is, you decide that you hit go and out pops a time series, and that time series tells you specifically where you want it to look what you want it to look for and how many, or what percentage of the thing you're looking for appears in that area. Again, we do all of this to work towards patterns. So we use all this data to produce a time series from there. We can look at it, determine the patterns, and then specifically identify the anomalies. As I mentioned with supply chain, this is extremely valuable to identify where things change. So we can answer these questions, looking at a particular operating facility, looking at particular, what is happening with the level of activity is at that operating facility where people are coming from, where they're going to, after visiting that particular facility and identify when and where that changes here, you can just see it's a picture of our platform. It's actually showing all the devices in Manhattan, um, over a period of time. And it's more of a heat map view. So you can actually see the hotspots in the area. >>So really the, and this is the heart of the talk, but what happened in 2020? So for men, you know, like many of you, 2020 was a difficult year COVID hit. And that changed a lot of what we're doing, not from an engineering perspective, but also from an entire company perspective for us, the motivation really became to make sure that we were lowering our costs and increasing innovation simultaneously. Now those two things often compete with each other. A lot of times you want to increase innovation, that's going to increase your costs, but the challenge last year was how to do both simultaneously. So here's a few stats for you from our team. In Q1 of last year, we were spending almost $600,000 per month on compute costs prior to COVID happening. That wasn't hugely a concern for us. It was a lot of money, but it wasn't as critical as it was last year when we really needed to be much more efficient. >>Second one is flexibility for us. We were deployed on a single cloud environment while we were cloud thought ready, and that was great. We want it to be more flexible. We want it to be on more cloud environments so that we could reach more customers. And also eventually get onto class side networks, extending the base of our customers as well from a custom analytics perspective. This is where we get into our traction. So last year, over the entire year, we computed 54,000 custom analytics for different users. We wanted to make sure that this number was steadily increasing despite us trying to lower our costs. So we didn't want the lowering cost to come as the sacrifice of our user base. Lastly, of particular percentage here that I'll say definitely needs to be improved is 75% of our projects never fail. So this is where we start to get into a bit of stability of our platform. >>Now I'm not saying that 25% of our projects fail the way we measure this is if you have a particular project or computation that runs every day and any one of those runs sale account, that is a failure because from an end-user perspective, that's an issue. So this is something that we know we needed to improve on and we needed to grow and make our platform more stable. I'm going to something that we really focused on last year. So where are we now? So now coming out of the COVID valley, we are starting to soar again. Um, we had, uh, back in April of last year, we had the entire engineering team. We actually paused all development for about four weeks. You had everyone focused on reducing our compute costs in the cloud. We got it down to 200 K over the period of a few months. >>And for the next 12 months, we hit that number every month. This is huge for us. This is extremely important. Like I said, in the COVID time period where costs and operating efficiency was everything. So for us to do that, that was a huge accomplishment last year and something we'll keep going forward. One thing I would actually like to really highlight here, two is what allowed us to do that. So first off, being in the cloud, being able to migrate things like that, that was one thing. And we were able to use there's different cloud services in a more particular, in a more efficient way. We had a very detailed tracking of how we were spending things. We increased our data retention policies. We optimized our processing. However, one additional piece was switching to new technologies on, in particular, we migrated to get lab CICB. >>Um, and this is something that the costs we use Docker was extremely, extremely easy. We didn't have to go build new new code containers or repositories or change our code in order to do this. We were simply able to migrate the containers over and start using a new CIC so much. In fact, that we were able to do that migration with three engineers in just two weeks from a cloud environment and flexibility standpoint, we're now operating in two different clouds. We were able to last night, I've over the last nine months to operate in the second cloud environment. And again, this is something that Docker helped with incredibly. Um, we didn't have to go and build all new interfaces to all new, different services or all different tools in the next cloud provider. All we had to do was build a base cloud infrastructure that ups agnostic the way, all the different details of the cloud provider. >>And then our doctors just worked. We can move them to another environment up and running, and our platform was ready to go from a traction perspective. We're about a third of the way through the year. At this point, we've already exceeded the amount of customer analytics we produce last year. And this is thanks to a ton more albums, that whole suite of new analytics that we've been able to build over the past 12 months and we'll continue to build going forward. So this is really, really great outcome for us because we were able to show that our costs are staying down, but our analytics and our customer traction, honestly, from a stability perspective, we improved from 75% to 86%, not quite yet 99 or three nines or four nines, but we are getting there. Um, and this is actually thanks to really containerizing and modularizing different pieces of our platform so that we could scale up in different areas. This allowed us to increase that stability. This piece of the code works over here, toxin an interface to the rest of the system. We can scale this piece up separately from the rest of the system, and that allows us much more easily identify issues in the system, fix those and then correct the system overall. So basically this is a summary of where we were last year, where we are now and how much more successful we are now because of the issues that we went through last year and largely brought on by COVID. >>But that this is just a screenshot of the, our, our solution actually working on supply chain. So this is in particular, it is showing traceability of a distribution warehouse in salt lake city. It's right in the center of the screen here. You can see the nice kind of orange red center. That's a distribution warehouse and all the lines outside of that, all the dots outside of that are showing where people are, where trucks are moving from that location. So this is really helpful for supply chain companies because they can start to identify where their suppliers are, are coming from or where their distributors are going to. So with that, I want to say, thanks again for following along and enjoy the rest of DockerCon.

>>thank you so much that sake for inviting me to the Entity Research Summit. And I'm really excited to talk to all of them today. So I will be talking about achieving indistinguishability obfuscation from well founded assumptions. And this is really the result of a wonderful two year collaboration with But now it's standing. Graduate student I use chain will be graduating soon on my outstanding co author, Rachel Lynde from the University of Washington. So let me jump right into it. We all know that constructing indistinguishable the obfuscation. Constructing Io has been perhaps the most consequential open problem in the foundations of photography. For several years now, they've seen over 100 papers written that show how to use Iot to achieve a number of remarkable cryptographic goals. Um, that really expand the scope of cryptography in addition to doing just remarkable, really interesting new things. Unfortunately, however, until this work, I told the work I'm about to tell you about all known constructions of Iove. All required new hardness, assumptions, heart assumptions that were designed specifically to prove that Iowa secure. And unfortunately, uh, this has a torture of history. And many of the assumptions were actually broken, which led to just a lot of doubt and uncertainty about the status of Iot, whether it really exists or doesn't exist. And the work I'm about to tell you about today changes that state of affairs in the continental way in that we show how to build io from the combination of four well established topographic assumptions. Okay, let me jump right into it and tell you how we do it. So before this work that I'm about to tell you about over the last two years with Rachel and Ayush, we actually constructed a whole sequence of works that have looked at this question. And what we showed was that if we could just build a certain special object, then that would be sufficient for constructing Io, assuming well established assumptions like L W E P R g s and M C zero and the 68 assumption of a violin. Your mouths. Okay, So what is this object? The object first starts with a P. R G and >>S zero. In other words, of trg with constant locality that stretches end bits of seed to M bits of output where am is ended one plus Epsilon for any constant Epsilon zero. Yes, but in addition to this prg, we also have these l w we like samples. So as usual, we have an elder Bluey Secret s which is random vector z b two k, where K is the dimension of the secret, which is much smaller than any way also have this public about vectors ai which are also going to be okay. And now what is given out is are the elderly samples where the error is this X I that is just brilliant value. Uh, where these excise air Also the input to our prg. Okay, unfortunately, we needed to assume that these two things together, this y and Z together is actually pseudo random. But if you think about it, there is some sort of kind of strange assumption that assumes some kind of special leakage resilience, property of elderly, we where elderly samples, even with this sort of bizarre leakage on the errors from all debris, is still surround or still have some surrounding properties. And unfortunately, we had no idea how to prove that. And we still don't have any idea how to prove this. Actually, So this is just a assumption and we didn't know it's a new assumption. So far, it hasn't been broken, but that's pretty much it. That's all we knew about it. Um and that was it. If we could. If this is true, then we could actually build. I'll now to actually use this object. We needed additional property. We needed a special property that the output of this prg here can actually be computed. Every single bit of the output could be computed by a polynomial over the public. Elder Louise samples Why? And an additional secret w with the property that this additional secret w is actually quite small. It's only excise em to the one minus delta or some constant delta gradients. Barroso polynomial smaller from the output of the prg. And crucially, the degree of this polynomial is on Lee to its violin e er can this secret double that's where the bottle in your mouth will come. Okay. And in fact, this part we did not approve. So in this previous work, using various clever transformations, we were able to show that in fact we are able to construct this in a way to this Parliament has existed only degree to be short secret values. Double mhm. So now I'm gonna show you how using our new ideas were actually gonna build. That's a special object just like this from standard assumptions. We're just gonna be sufficient for building io, and we're gonna have to modify it a little bit. Okay? One of the things that makes me so excited is that actually, our ideas are extremely simple. I want to try to get that across today. Thanks. So the first idea is let's take thes elder movie samples that we have here and change them up a little bit when it changed them up. Start before I get to that in this talk, I want you to think of K the dimension of the secret here as something very small. Something like end of the excellent. That's only for the stock, not for the previous work. Okay. All right. So we have these elderly samples right from the previous work, but I'm going to change it up instead of computing them this way, as shown in the biggest slide on this line. Let's add some sparse hair. So let's replace this error x i with the air e i plus x I where e is very sparse. Almost all of these IIs or zero. But when the I is not zero is just completely random in all of Z, pizza just completely destroys all information. Okay, so first I just want to point out that the previous work that I already mentioned applies also to this case. So if we only want to compute P R g of X plus E, then that can still be computer the polynomial. That's degree to in a short W that's previous work the jail on Guess work from 2019. I'm not going to recall that you don't have time to tell you how you do it. It's very simple. Okay, so why are we doing this? Why are we adding the sparse error? The key observation is that even though I have changed the input of the PRG to the X Plus E because he is so sparse, prg of explosive is actually the same as P. R. G of X. In almost every outlet location. It's only a tiny, tiny fraction of the outputs that are actually corrupted by the sparse Arab. Okay, so for a moment Let's just pretend that in fact, we knew how to compute PRGF X with a degree to polynomial over a short seeking. We'll come back to this, I promise. But suppose for a moment we actually knew how to compute care to your ex, Not just scared of explosive in that case were essentially already done. And the reason is there's the L. P n over zp assumption that has been around for many years, which says that if you look at these sort of elderly like samples ai from the A, I s but plus a sparse air e I where you guys most zero open when it's not serious, completely random then In fact, these samples look pseudo random. They're indistinguishable from a I r r. I just completely uniform over ZP, okay? And this is a long history which I won't go because I don't have time, but it's just really nice or something. Okay, so let's see how we can use it. So again, suppose for the moment that we were able to compute, not just appeared you've explosive but appeared to you that well, the first operation that since we're adding the sparse R E I This part the the L P N part here is actually completely random by the LP an assumption so by L P and G. P, we can actually replace this entire term with just all right. And now, no, there is no more information about X present in the samples, The only place where as is being used in the input to the prg and as a result, we could just apply to sit around this of the prg and say this whole thing is pseudo random and that's it. We've now proven that this object that I wanted to construct it is actually surrounded, which is the main thing that was so bothering us and all this previous work. Now we get it like that just for the snap of our fingers just immediately from people. Okay, so the only thing that's missing that I haven't told you yet is Wait, how do we actually compute prg attacks? Right? Because we can compute p r g of X plus e. But there's still gonna be a few outputs. They're gonna be wrong. So how can we correct those few corrupted output positions to recover PRGF s? So, for the purpose of this talks because I don't have enough time. I'm gonna make sort of a crazy simplifying assumption. Let's just assume that in fact, Onley one out the position of P r g of X plus e was correct. So it's almost exactly what PR gox. There's only one position in prg of Ecstasy which needs to be corrected to get us back to PR gox. Okay, so how can we do that? The idea is again really, really simple. Okay, so the output of the PRG is an M. Becker and so Dimension and Becker. But let's actually just rearrange that into a spirit of them by spirit of them matrix. And as I mentioned, there's only one position in this matrix that actually needs to be corrected. So let's make this correction matrix, which is almost everywhere. Zero just in position. I j it contains a single correction factor. Why, right? And if you can add this matrix to prg of explosive, then we'll get PR dribbles. Okay, so now the Onley thing I need to do is to compute this extremely sparse matrix. And here the observation was almost trivia. Just I could take a spirit of em by one maker That just has why in position I and I could take a one by spirit of them matrix. I just have one in position J zero everywhere else. If I just take the tensor product was music the matrix product of these two of these two off this column vector in a row vector. Then I will get exactly this correction matrix. Right? And note that these two vectors that's called them you and be actually really, really swamped their only spirit of n dimensional way smaller than them. Right? So if I want to correct PRGF Expo see, all I have to do is add you, Tenzer V and I can add the individual vectors u and V to my short secret w it's still short. That's not gonna make W's any sufficiently bigger. And you chancery is only a degree to computation. So in this way, using a degree to computation, we can quickly, uh, correct our our computation to recover prg events. And now, of course, this was oversimplifying situation, uh, in general gonna have many more areas. We're not just gonna have one error, like as I mentioned, but it turns out that that is also easy to deal with, essentially the same way. It's again, just a very simple additional idea. Very, very briefly. The idea is that instead of just having one giant square to them by sort of a matrix, you can split up this matrix with lots of little sub matrices and with suitable concentration bound simple balls and pins arguments we can show that we could never Leslie this idea this you Tenzer v idea to correct all of the remaining yet. Okay, that's it. Just, you see, he's like, three simple >>ah ha moments. What kind of all that it took, um, that allowed >>us to achieve this result to get idol from standard assumptions. And, um, of course I'm presenting to you them to you in this very simple way. We just these three little ideas of which I told you to. Um, but of course, there were only made possible because of years of struggling with >>all the way that didn't work, that all that struggling and mapping out all the ways didn't work >>was what allowed us toe have these ideas. Um, and again, it yields the first I'll construction from well established cryptographic assumptions, namely Theo Elgon, assumption over zp learning with errors, assumption, existence of PR GS and then zero that is PR juice with constant death circuits and the SX th assumption over by linear notes, all of which have been used many years for a number of other applications, including such things as publicly inversion, something simple public inversion that's the That's the context in which the assumptions have been used so very far from the previous state of affairs where we had assumptions that were introduced on Lee Professor constructing my own. And with that I will conclude, uh and, uh, thank you for your attention. Thanks so much.

>> From theCube studios in Paloalto and Boston, connecting with thought leaders all around the world, this is a Cube conversation. >> Hi, I'm Stu Miniman, and welcome to this special Cube conversation. I'm coming to you from our Boston area studio, and theCube is really mostly about people, about network, and so we're going to have a focus in, we're going to talk about some technology, we're also going to talk a little bit about careers. I want to welcome to the program, I've got two first-time guests on the program. First, Mark Zbikowski. Probably butchered that badly, Mark, sorry, technical advisor, and Blue Gaston. Uh, Gaston. Boy, I'm doing horrible with names here. Software engineer, you're both with Polyverse. But, you know, my last name's Miniman, it has been butchered a million times. But Mark, and Blue, thank you so much for joining us. >> You're welcome. Our pleasure. >> Yes. >> All right. So one of you I've read a lot about online and the other one is Mark, go to the Wikipedia page, stuff like that. So we'll get to that too. So, Blue, maybe start with you, give us a little bit about your background. >> Yeah, so I work at Polyverse now, a cybersecurity startup. But actually I got my undergraduate degree in Philosophy, and from there, kind of just like, what am I going to do with a philosophy degree? And it just weirdly was like a natural transition. I was like, oh, computer science. And kind of the logical, like the technical version of philosophy. So got my master's in philosophy and now, or not philosophy, in computer science, and now have been working at Polyverse. I started as an intern and they hired me on, I think after a month, they were like, no, we want you full-time. So that was cool and I've loved it. So I'm starting off my story, that's kind of where my kick-off point is. >> Awesome. So, and Mark, first of all, you have to give us the connection between yourself and Blue, and a little bit surprising that she waited so long to go into the computer business. >> Uh, okay, I'm her stepfather. It's not surprising that she, you know, wanted to go into computer science. She's got lots of aptitude for it. She was just on a career path and an education path that was primarily logic, analysis, which is basically what we do in computer science. >> All right. So Mark, if you could just give our audience a little bit of a thumbnail sketch as to your background in the tech industry, and it's a storied one. >> Uh, okay. I was, I think, employee number 55 at Microsoft, when I started back in 1981. The first task that they gave me was to work on something that ended up becoming MS-DOS. I worked on MS-DOS for a long time, about five and a half years, worked on a number of other operating systems at Microsoft, ending up with being one of the initial development managers and architects for Windows. I was responsible for all file storage. And I was there for about 26 years. >> Yeah, you know, interesting, you know, when you look on the Wikipedia page, you were the third employee that reached the 25-year milestone. Some guy, Bill Gates, and Steve Balmer, were the first two to reach that milestone. So, you know, quite impressive. I think back, back when I learned computers, it was programming, and you know, today it's coding, and things are quite different there. But, Mark, you were also, you're noted as one of the early hackers there, so what does that mean to you, how have you seen that's been changing? Polyverse is in the cybersecurity realm, so would love your kind of viewpoint on just hacking in general. >> Oh, the early days, well my hacking started pretty much when I was in eighth or ninth grade back in Detroit. We had access to an academic operating system called MTS by way of Wayne State University. I grew up in, just in the suburbs of Detroit. And we had access to it, and for me Excuse me. Hacking at the time was all about trying to understand and learn stuff that was arcane and hidden and mysterious. Figuring out how, for example, password encryption algorithms worked, figuring out how operating systems worked, because at the time, there were very few organized textbooks about how to construct operating systems. Even though operating systems had been around for 20 years. So my early, earliest stuff was in basically, finding holes in security at MTS, and that's how I started, in what they would say "hacking", but it was very innocent, it was very, let's see what we can do! As opposed to, let's extract information, let's go and ransom people's data for bitcoin, which is, you know, I think, a wrong direction to go. >> Yeah. I'm curious your thoughts as the decades have progressed, you know, hacking today, what's your take on, you know, there's the white hats and the black hats, and everything in between. >> Uh, it's kind of an arms race. (laughs) Everything that the white hats will throw up, the black hats will eventually attack to some degree. Social engineering is sort of the ultimate way that people have been getting around, you know, software protections. I think it's unfortunate that there is such a financial reward to the black hat side of things, as counter to one's ethics. I think there's a lot of slippery slopes involved, in terms of, you know, boy, these companies shouldn't be making money, so I deserve my bit. I think that it's much better that, you know, people should come at this from an intellectual, you know, exploration standpoint, rather than an exploitative. But that's the nature of the world. >> Yeah, well, Blue, maybe we can help connect the dots towards what you both do at Polyverse. You mentioned you started as an intern, and I loved the article that talked about this. Well, you know, you're going to be an intern. Can you fix the internet for us? And you did some things to help, you know, help stop some of that malicious hacking. >> Yeah, I, that was crazy. I was very intimidated when I heard that, you're going to be fixing the internet. What I've been working at the company, which is different from our flagship product, but kind of in the same vein, is to stop malicious php javascript code execution. So that's what they came in, that's how they prefaced that problem to me. It was, you're going to go fix the internet. Um, and it was crazy. It was really cool and surprisingly, a lot of philosophy that goes into the way we look at our problem-solving at Polyverse, and how we tackle problems, but of course, I have my Jedi master Mark over here, and I was constantly, "What do you think about this? Isn't this crazy? "Like, look at how Polyverse is attacking this." And I think finally I broke him down, and I was like, come join. Come jump in, and you be the foresight, and you tell us what we're going to do in a year or two. And I convinced him, and now, he's, he's with us too. >> Excellent. So, Mark, tell us a little bit about, you know, more about Polyverse, your role there. In the industry there's a lot of talk about, you know, lots of money obviously gets spent on cybersecurity, but it's still a major challenge in the industry. So what's your role there and how's Polyverse helping to attack that? >> Well, my title is Technology Advisor, and I'm one of a small collection of people who have pretty wide-ranging expertise across operating systems, networks, compilers, languages, development tools, all of that. And our goal is, you know, my role, as well the other Jedi masters, is to take a look at what Polyverse is doing at present, try to figure out where we need to go, try to figure out what the next set of challenges are, use our broad experience and knowledge of the computing milieu, and try to figure out what are the tough issues we need to face? We make some progress on those tough issues, and then turn everything over for the mainline Polyverse development staff to bring it to reality. We're not like researchers, we're much more into the product planning side of things, but product planning in, I hate to use this word, but in a visionary sense. (Blue laughs) >> Yeah, no, it's-- >> We look for the vision. We're not visionaries. We look for the vision. >> You're a visionary, Mark. Admit it. >> Excellent. Well, I do love the, you know, Jedi analogy there. When you look at, I'm curious to your thoughts, both of you, you know, some of the real challenges and opportunities facing the cybersecurity industry. It's a large financial industry company, they'll spend a billion dollars and, you know, does that make them secure? Well, at least they've done what they can and they're pushing enough pieces. But, you know, fundamentally, we understand that this is such a huge issue. >> I think-- >> Blue? >> Well, (laughs) I can try to answer. I think Polyverse recognizes that as well. So we're trying to create new solutions, that instead of just being compliant and checking the boxes, we're actually trying to create systems and products that will stop attacks from actually working. Rather than being reactive and being responsive, we're trying to build these systems out where the attacks just don't work as they're currently designed. And I think we, you know, and to do so in an easy-to-deploy, time-saving kind of way is definitely our goal. Rather than the status quo and, you know, we're fighting inertia, we're trying to, to change that narrative in a really meaningful way. >> Thanks, Blue. Mark, do you have some comments you can add to that? >> Once we started taking individual computers and hooking them up to the internet, where they can communicate fairly freely with each other, and by intent communicate fairly freely with each other, by design, by intent, all of a sudden that opened us to just a wide range of malicious behavior, from being DoS'd, to leaking passwords, et cetera. There are, there's layers and layers that one can do to mitigate these problems. From IT operational manuals to buzz-testing your API, to best practices, it's a, there's a long list. And every bit, every piece of it is important. You need to secure your passwords before you can do anything else. You need to make sure that there's a firewall in your system be fore you go and start, before you even start thinking about doing things like, like what's goin on with what we're doing at Polyverse. It's a, like I said, there's a wide range of tools that people need, that people use, that people spend money on today. Polyverse has got a very unique perspective on how to go and extend this. We, it's a, it's very pragmatic, you know, the realization is that these attackers are going to keep attacking, and they're going to exploit certain features that, despite everyone's best intentions, aren't covered, and we have found a rather unique and novel way to prevent people from doing it. Is it going to solve everything? No. There's still, there's all these other early layers that need to be taken care of first, before the more sophisticated tools that, for example, that Polyverse has or that other companies have. >> Great. Well, Blue, you talked a little bit about it, but, you know, love your, what you've found, you know, working together as a family dynamic here. You know, specifically. >> Um, (laughs) I think it's really cool. What's the best, I'll say this, is when, I always like asking Mark his opinion, because why wouldn't I? The brain that guy has, and just the experience, he can add so much. Every once in a while, I'll go, and I'll say, you know, oh, this is what I'm working on, and here's what I'm kind of thinking, and he'll say, oh, yeah, well what about this? And I'll actually get to explain something to him. And I got to tell you, that feels really good. Is when I get to say, oh, well, actually it looks like this, and this was my plan, and he's like, oh yeah, definitely. And I get that validation, which is really cool. And I can, you know, drive to his house and bug him whenever I want to. I know where he lives, so if I'm really stuck, or just want to bounce ideas off of him, it's really cool. It's really cool, and I, you know, strong-armed, not strong-armed, I enticed him to come and join Polyverse just by the cool things that we're doing, and I think that's cool too. To now be able to work on something together. >> Yeah, and Mark, sounds like you're learning some things from Blue. Give us your side of that relationship. >> Well, it's a great relationship. Blue, um, Blue never hesitates to challenge. (Blue laughs) >> Blue: Okay. And that, I'm saying that in a very positive sense. Um, you know, she'll come up, every so often I'll get a text from her that says, "Help!" >> Oh my god! (laughing) >> Yes. Sorry. At least I'm not showing it. (laughs) But it's great. And we get together and we talk about stuff, and she says, you know, here's the problem I'm facing, and I'll ask her about it and she gets to go and teach me about what her problem is. I'm a big fan of teaching. I think one of the frustrations that Blue has is I almost never give her the answer when she asks a question. (laughs) >> Not even when I was in school, >> Yeah, not even when you were in school. I was always asking the questions and leading her to the answer rather than just giving it to her. >> Or saying, well why don't we sit down and I'll teach you how to implement knowledge. Just like, oh my god. What are you doing? >> Yeah. So, yeah, I'm a big fan of teaching and learning by way of teaching. One of the things I do is I'm an affiliate with the University of Washington, and I teach every year one quarter of their Operating Systems class. And I love teaching, I love seeing the light go on. But every year, when I'm teaching a class that I know pretty well, I learn something new. By a question the student asks, or by reading a paper that I'm asking the students to read, I learn something new just about every year. And so having Blue teach me is a way that I get to learn, but I think in the process Blue also gets to learn as well. You know, in the process of teaching me. >> Yeah, well, that's such a great point. All right, want to give you both the final word on what's exciting you, what draws you to working in the cybersecurity industry. >> Um, I'll start. (laughs) So when I started at Polyverse, I actually got to, as an intern, own my own product. And in, I think, less than a month now, we're actually officially releasing that product, polyscripting. Officially, like Marketing is coming up with materials for it, and that was right out of school is when I started on this project, so it's kind of like a big deal for me. You know, I've owned the project, I'd say like 90% of it, over the last year or two, and now I get to see it come into fruition. So that's really exciting to me. Um, you know, that's exciting. So I'm excited about that, I'm excited about what Polyverse is doing in general. So, yeah. >> And Mark? >> Yeah. It's great working in a startup, it's great working with a bunch of very, very bright, energetic people. For me, contributing to that environment is extremely valuable. Helping Polyverse out, they're, you know, cybersecurity is problem. Trying to come up with good, effective solutions that are really pragmatic in terms of, you know, we're not going to solve every problem, but here's a great little space that we're going to solve all the problems in. That's, there's a huge appeal to that for me. >> Well, Mark and Blue, thank you so much for joining. Appreciate you sharing some of the personal as well as the professional journeys that you've both been on. Thanks so much. >> Yeah, thank you >> Yeah, you're welcome. >> All right. Thank you for watching theCube. I'm Stu Miniman. Thanks for watching. (soothing music)

(upbeat music) >> Hey, welcome back everybody. Jeff Frick here with theCUBE. We're at our Palo Alto studios today. And obviously, what's top of the news is the coronavirus and COVID-19, and it's having a direct impact on anything where people get together. We're obviously really tied into the convention space. But we're excited to have an expert in the field coming at it from a different kind of point of view, more from the entertainment side. We'd like to welcome, calling in from Tennessee, Lauren Spahn. She is a partner for Shackelford, Bowen, McKinley, or excuse me, but yeah, McKinley & Norton. Lauren, great to see you. >> Hey there, how are ya? >> Jeff Frick: Good. So we were introduced through kind of the process of the South by Southwest cancellation. Before we get into it, tell us a little bit about kind of what you do, what type of clients do you have, who do you guys kind of represent? >> Yeah, sure, so I practice primarily in entertainment law here in Nashville. But I work with a variety of people in the music industry, whether it be artists or music festivals, record labels, publishing companies, you name it, across the US. So I do a lot of work in L.A. and New York as well. And our firm specializes in a little bit of everything, but our national hub is kind of the spearhead for the entertainment and music practice. >> So it's pretty interesting 'cause we're not so directly involved in entertainment, but we do go to a lot of conferences. And, I think, for us, the watershed moment this year was Mobile World Congress earlier this year in February, 100,000 people in Barcelona, Spain. That's a little unique because most of the main vendors are Asian in terms of all the mobile carriers and the handset tech carriers. But, you were saying before we turned the cameras on, that now the South By Southwest event cancellation is kind of sending the same shock waves if you will through the entertainment industry. >> Yeah, I mean South By Southwest obviously is a big coming together of multiple industries. You know, music, film, TV, technology, but it really was one of the first events that were canceled that impacted the music industry. And so, such a large conference to completely cancel, really just started, it was the tip of the iceberg, or I think what we are going to continue to see across the sphere in music whether its tours being canceled or music festivals that are being canceled, everything is kind of starting to ramp up, and were starting to see the effects from South By Southwest line. >> Jeff Frick: Right. So, one of the things that really is just kind of a splash of cold water, is these things are going down it just really highlights the interconnectedness of all these different parts of these events, right? whether it is the primary promoter or the primary bands in the case of South By Southwest or even the tech companies, but then there are tons and tons of secondary, third and other vendors that are involved from food and transportation and the list goes on and on. So, you're quoted quite often in the press about talking about force majeure and that this is something that kind of comes up in contract law when these types of events happen. So, I wonder if you can kind of explain the dictionary definition of force majeure and how do you see it kind of executed traditionally in a contract where maybe one person just can't uphold their part of the deal and how that contrasts with something like this, which is hitting kind of both sides of the agreement, if you will. >> Completely. So, I think it's important to step back and look at if we are going to use a music festival as an example. You have a contract, the music festival itself will have a contract with the artist, but they will also have contracts with their vendors, with the production team that comes in and sets up the staging and the sound and the light. There are a myriad of contracts and so, the language in each contract tends to govern the relationship between the festival and that third party. So, in this situation of let's use an artist, for example. There is different things in the contract that point to how you can cancel and what happens when you cancel. A force majeure is an example of that. And force majeure is something that is outside of the control of both parties. So, again, the festival and the artist. If something like the Coronavirus is coming, neither one of those parties can control that from happening. And so it typically relieves both parties of any obligation to move forward with the contract. What is important, though, is the language that's in that force majeure provision. So, you sometimes will see language like sickness or an epidemic. But then, you may not have that, and you may have language that says, a local or national state of emergency. So, depending upon the state you're in, depending upon the exact situation in the city that you are holding the event, all of those things can be looked or looked to to interpret whether or not the language that's in that force majeure contract will impact you or will give you the rights to cancel that event without having to pay additional money. >> Jeff Frick: Right. >> And so, you know, not only that but you're then seeing it carried out through the insurance policies, as well. So, even if you have force majeure language whether or not the insurance company will help cover the losses for you again depends upon the exact language that's in your insurance policy. >> Jeff Frick: Right. >> So, across the board, it really is a contractual right, that can differ for the different people that are involved. >> Right. But, there's the contractual, the language in the contract, but then there is kind of this random stuff that comes up. And, we hear kind of act of God kind of thrown up by insurance companies when it's something they haven't defined in all the fine language. And then, the other piece that we're hearing about a lot in the news here on Palo Alto, right is the specific descriptive terms used by the authorities. Is it a pandemic? Is it an outbreak? Is it a natural disaster? Is it a state of emergency called by the government? >> Or other. So, how does that figure in on something like we're experiencing? I don't know that we've seen anything quite like this before. >> You know, I was looking back through some contracts earlier this morning because I had a potential cancellation that was going to happen, and I mean some contracts go as far as to even describe the Swine Flu and similar things like that but we really are looking to the authorities to see what decision they are making on everything. And whether or not they are calling it a local state of emergency because a lot of times that exact definition or that exact cause is defined in the agreement . But, yeah, I mean really it comes down to small print wording in this situation, if you are looking at the contract itself to see what rights that you have. What I found is that people aren't going to the nitty gritty of at least the contracts, you're probably going to get into the nitty gritty of the insurance policy, if you have a chance of getting any kind of protection. But, at the end of the day, the artist doesn't want to go play a festival that could potentially cause their fans to have some outbreak of the Coronavirus. An event doesn't want to be liable for holding an event that could be connected with that, as well, because across the board, that creates a PR nightmare for whoever's making that decision. So, you're seeing people that are trying to work together to figure out exactly how we're going to handle things, and what we're going to do moving forward, because no one is going to win in this situation. >> [Jeff Frick} Right. Right. >> It's really just figuring out a way that we can all be in the best position possible across the board. >> Yeah. And I think that's what we're kind of seeing a lot too, where, you know, I think everyone is again instead of just one party that's not upholding their part of the deal and the other party getting screwed on that, this is really, you know, we're kind of in it together, this has kind of come down on both of our houses so how do we work together to minimize the pain and at least, kind of get through this window that we assume will pass at some point or at least the current heightened state will go. But, I just wonder if you have an opinion on, from a legal point of view, and it's not your space, so if you say no that's an okay answer, but, you know, if you look at kind of market forces is determining what is the appropriate action, right? Because we don't really know what's the right action. But, clearly, the market is defined based on activity and the University of Washington shutting down and Stanford shutting down >> Vanderbilt >> Almost is a self-imposed kind of semi-quarantine state, which is just, you know the latest now I think they get the local high school basketball game is they can only have 100 people in the stands in the biggest building they can find and everybody needs to spread out. So, it's just been very interesting to see you know kind of what is the appropriate response. What's the right response? Because ultimately it seems like it's driven by nobody wants to be the one that didn't take the max precautions and something bad happens. >> To be honest, I don't think that anyone really knows. You know, it really is the conversations right now are not the artist's agent calling the festival and saying we're absolutely not doing this The conversation is more so, hey what are you guys seeing? What are you guys thinking? What's the best way to handle this? You know, no one wants to put the consumers and the fans at risk. And, you know, until we have a better handle on exactly how we handle this type of situation, it's really going to be people doing their best to try to not create a situation that's going to, you know, cause some kind of massive outbreak. >> Right. Right. >> If you look at, you know, something like South By, no one wants to cancel, you know. It really impacts, not only the company and the event itself, but really everyone that's associated to it, has a financial hardship because of that decision, but the decision isn't made because someone wants to do it, it's made because collectively, you know, people are feeling like it needs to be done in order to keep people safe. >> Right. >> And if they didn't think that, they'd probably go ahead and try to hold the event and, you know, risk the liability. But, I think people truly want what's in the best interest of everyone. And that's why they are working together to try to figure this out. >> Yeah. Yeah. It really is driven home what social creatures we are when you start to kind of disconnecting crowds and groups of people from so many events and it just continues to ripple through whether it's our business, a convention business, the entertainment business, you know March Madness is coming up here in a very short order. What's going to happen there all the way down to you know, the local talent show for the local middle schoolers that they used to have before graduation, which is now canceled. So, it's interesting times. >> And I think for us, the biggest indicator in terms of just music festivals is going to be what happens with Coachella. And, you know, Billboard and Variety have reported that they're looking to potentially reschedule the event to October, if artists are able. And if not, they're going to have to completely cancel it for this year. And, you know, Coachella is such a massive festival that attracts people from all over the world. And if Coachella is canceled then I think there is a good chance that so long as this is continuing at the speed it is, that we're going to see a lot more music festivals canceled. >> When is Coachella scheduled? >> It starts in about a month. >> In about a month. >> So it's the second weekend in April, but they have to start production and really building out the grounds now. >> Wow. Wow. >> And so the decision kind of has to be made before then. And then, I wouldn't be surprised if we see a decision there in the next few days. >> Yeah. I think I would take the short if I was in Vegas, because there's just not enough data, I don't think, to go forward based on the current situation. I'm glad I'm not the one sitting in that chair. >> Yeah. It'd be a tough position. >> All right, well Lauren, well thank you for sharing your insight and, you know, it's great to get the perspective of another you know kind of industry that's all built around bring people together. And, I think we probably both would agree that this time will pass and we'll get a vaccine out, we'll get the growth curves to start to flatten out and go down which is where they need to go. And then you know I think it will be a different time, but hopefully things will get approximate a little bit more to normal in the not too distant future. >> Yeah, fingers crossed. I hope it gets figured out sooner rather than later and we can all have our summers full of conferences and festivals and the gathering of people. >> Yep. All right Lauren. Well thanks again for your time >> Thank you >> And have a great Tuesday. >> Awesome. You too. >> Alrighty. She's Lauren. I'm Jeff. Thanks for checking in on this Cube Conversation. We'll catch you next time. (upbeat music)

>>from Las Vegas. It's the Q covering. Next work. 2019 America's Do You buy Juniper Networks? Come back already. Jeffrey here with the Cube were in Las Vegas at Caesar's at the Juniper. Next work event. About 1000 people kind of going over a lot of new cool things. 400 gigs. Who knew that was coming out of new information for me? But that's not what we're here today. We're here for the fourth installment of around the Cube unpacking. I were happy to have all the winners of the three previous rounds here at the same place. We don't have to do it over the phone s so we're happy to have him. Let's jump into it. So winner of Round one was Bob Friday. He is the VP and CTO at Missed the Juniper Company. Bob, Great to see you. Good to be back. Absolutely. All the way from Seattle. Sharna Parky. She's a VP applied scientist at Tech CEO could see Sharna and, uh, from Google. We know a lot of a I happen to Google. Rajan's chef. He is the V p ay ay >>product management on Google. Welcome. Thank you, Christy. Here >>All right, so let's jump into it. So just warm everybody up and we'll start with you. Bob, What are some When you're talking to someone at a cocktail party Friday night talking to your mom And they say, What is a I What >>do you >>give him? A Zen examples of where a eyes of packing our lives today? >>Well, I think we all know the examples of the south driving car, you know? Aye, aye. Starting to help our health care industry being diagnosed cancer for me. Personally, I had kind of a weird experience last week at a retail technology event where basically had these new digital mirrors doing facial recognition. Right? And basically, you start to have little mirrors were gonna be a skeevy start guessing. Hey, you have a beard, you have some glasses, and they start calling >>me old. So this is kind >>of very personal. I have a something for >>you, Camille, but eh? I go walking >>down a mall with a bunch of mirrors, calling me old. >>That's a little Illinois. Did it bring you out like a cane or a walker? You know, you start getting some advertising's >>that were like Okay, you guys, this is a little bit over the top. >>Alright, Charlotte, what about you? What's your favorite example? Share with people? >>Yeah, E think one of my favorite examples of a I is, um, kind of accessible in on your phone where the photos you take on an iPhone. The photos you put in Google photos, they're automatically detecting the faces and their labeling them for you. They're like, Here's selfies. Here's your family. Here's your Children. And you know, that's the most successful one of the ones that I think people don't really think about a lot or things like getting loan applications right. We actually have a I deciding whether or not we get loans. And that one is is probably the most interesting one to be right now. >>Roger. So I think the father's example is probably my favorite as well. And what's interesting to me is that really a I is actually not about the Yeah, it's about the user experience that you can create as a result of a I. What's cool about Google photos is that and my entire family uses Google photos and they don't even know actually that the underlying in some of the most powerful a I in the world. But what they know is they confined every picture of our kids on the beach whenever they whenever they want to. Or, you know, we had a great example where we were with our kids. Every time they like something in the store, we take a picture of it, Um, and we can look up toy and actually find everything that they've taken picture. >>It's interesting because I think most people don't even know the power that they have. Because if you search for beach in your Google photos or you search for, uh, I was looking for an old bug picture from my high school there it came right up until you kind of explore. You know, it's pretty tricky, Raja, you know, I think a lot of conversation about A They always focus the general purpose general purpose, general purpose machines and robots and computers. But people don't really talk about the applied A that's happening all around. Why do you think that? >>So it's a good question. There's there's a lot more talk about kind of general purpose, but the reality of where this has an impact right now is, though, are those specific use cases. And so, for example, things like personalizing customer interaction or, ah, spotting trends that did that you wouldn't have spotted for turning unstructured data like documents into structure data. That's where a eyes actually having an impact right now. And I think it really boils down to getting to the right use cases where a I right? >>Sharon, I want ask you. You know, there's a lot of conversation. Always has A I replace people or is it an augmentation for people? And we had Gary Kasparov on a couple years ago, and he talked about, you know, it was the combination if he plus the computer made the best chess player, but that quickly went away. Now the computer is actually better than Garry Kasparov. Plus the computer. How should people think about a I as an augmentation tool versus a replacement tool? And is it just gonna be specific to the application? And how do you kind of think about those? >>Yeah, I would say >>that any application where you're making life and death decisions where you're making financial decisions that disadvantage people anything where you know you've got u A. V s and you're deciding whether or not to actually dropped the bomb like you need a human in the loop. If you're trying to change the words that you are using to get a different group of people to apply for jobs, you need a human in the loop because it turns out that for the example of beach, you type sheep into your phone and you might get just a field, a green field and a I doesn't know that, uh, you know, if it's always seen sheep in a field that when the sheep aren't there, that that isn't a sheep like it doesn't have that kind of recognition to it. So anything were we making decisions about parole or financial? Anything like that needs to have human in the loop because those types of decisions are changing fundamentally the way we live. >>Great. So shift gears. The team are Jeff Saunders. Okay, team, your mind may have been the liquid on my bell, so I'll be more active on the bell. Sorry about that. Everyone's even. We're starting a zero again, so I want to shift gears and talk about data sets. Um Bob, you're up on stage. Demo ing some some of your technology, the Miss Technology and really, you know, it's interesting combination of data sets A I and its current form needs a lot of data again. Kind of the classic Chihuahua on blue buried and photos. You got to run a lot of them through. How do you think about data sets? In terms of having the right data in a complete data set to drive an algorithm >>E. I think we all know data sets with one The tipping points for a I to become more real right along with cloud computing storage. But data is really one of the key points of making a I really write my example on stage was wine, right? Great wine starts a great grape street. Aye, aye. Starts a great data for us personally. L s t M is an example in our networking space where we have data for the last three months from our customers and rule using the last 30 days really trained these l s t m algorithms to really get that tsunami detection the point where we don't have false positives. >>How much of the training is done. Once you once you've gone through the data a couple times in a just versus when you first started, you're not really sure how it's gonna shake out in the algorithm. >>Yeah. So in our case right now, right, training happens every night. So every night, we're basically retraining those models, basically, to be able to predict if there's gonna be an anomaly or network, you know? And this is really an example. Where you looking all these other cat image thinks this is where these neural networks there really were one of the transformational things that really moved a I into the reality calling. And it's starting to impact all our different energy. Whether it's text imaging in the networking world is an example where even a I and deep learnings ruling starting to impact our networking customers. >>Sure, I want to go to you. What do you do if you don't have a big data set? You don't have a lot of pictures of chihuahuas and blackberries, and I want to apply some machine intelligence to the problem. >>I mean, so you need to have the right data set. You know, Big is a relative term on, and it depends on what you're using it for, right? So you can have a massive amount of data that represents solar flares, and then you're trying to detect some anomaly, right? If you train and I what normal is based upon a massive amount of data and you don't have enough examples of that anomaly you're trying to detect, then it's never going to say there's an anomaly there, so you actually need to over sample. You have to create a population of data that allows you to detect images you can't say, Um oh, >>I'm going to reflect in my data set the percentage of black women >>in Seattle, which is something below 6% and say it's fair. It's not right. You have to be able thio over sample things that you need, and in some ways you can get this through surveys. You can get it through, um, actually going to different sources. But you have to boot, strap it in some way, and then you have to refresh it, because if you leave that data set static like Bob mentioned like you, people are changing the way they do attacks and networks all the time, and so you may have been able to find the one yesterday. But today it's a completely different ball game >>project to you, which comes first, the chicken or the egg. You start with the data, and I say this is a ripe opportunity to apply some. Aye, aye. Or do you have some May I objectives that you want to achieve? And I got to go out and find the >>data. So I actually think what starts where it starts is the business problem you're trying to solve. And then from there, you need to have the right data. What's interesting about this is that you can actually have starting points. And so, for example, there's techniques around transfer, learning where you're able to take an an algorithm that's already been trained on a bunch of data and training a little bit further with with your data on DSO, we've seen that such that people that may have, for example, only 100 images of something, but they could use a model that's trained on millions of images and only use those 100 thio create something that's actually quite accurate. >>So that's a great segue. Wait, give me a ring on now. And it's a great Segway into talking about applying on one algorithm that was built around one data set and then applying it to a different data set. Is that appropriate? Is that correct? Is air you risking all kinds of interesting problems by taking that and applying it here, especially in light of when people are gonna go to outweigh the marketplace, is because I've got a date. A scientist. I couldn't go get one in the marketplace and apply to my data. How should people be careful not to make >>a bad decision based on that? So I think it really depends. And it depends on the type of machine learning that you're doing and what type of data you're talking about. So, for example, with images, they're they're they're well known techniques to be able to do this, but with other things, there aren't really and so it really depends. But then the other inter, the other really important thing is that no matter what at the end, you need to test and generate based on your based on your data sets and on based on sample data to see if it's accurate or not, and then that's gonna guide everything. Ultimately, >>Sharon has got to go to you. You brought up something in the preliminary rounds and about open A I and kind of this. We can't have this black box where stuff goes into the algorithm. That stuff comes out and we're not sure what the result was. Sounds really important. Is that Is that even plausible? Is it feasible? This is crazy statistics, Crazy math. You talked about the business objective that someone's trying to achieve. I go to the data scientist. Here's my data. You're telling this is the output. How kind of where's the line between the Lehman and the business person and the hard core data science to bring together the knowledge of Here's what's making the algorithm say this. >>Yeah, there's a lot of names for this, whether it's explainable. Aye, aye. Or interpret a belay. I are opening the black box. Things like that. Um, the algorithms that you use determine whether or not they're inspect herbal. Um, and the deeper your neural network gets, the harder it is to inspect, actually. Right. So, to your point, every time you take an aye aye and you use it in a different scenario than what it was built for. For example, um, there is a police precinct in New York that had a facial recognition software, and, uh, victim said, Oh, it looked like this actor. This person looked like Bill Cosby or something like that, and you were never supposed to take an image of an actor and put it in there to find people that look like them. But that's how people were using it. So the Russians point yes, like it. You can transfer learning to other a eyes, but it's actually the humans that are using it in ways that are unintended that we have to be more careful about, right? Um, even if you're a, I is explainable, and somebody tries to use it in a way that it was never intended to be used. The risk is much higher >>now. I think maybe I had, You know, if you look at Marvis kind of what we're building for the networking community Ah, good examples. When Marvis tries to do estimate your throughput right, your Internet throughput. That's what we usually call decision tree algorithm. And that's a very interpretive algorithm. and we predict low throughput. We know how we got to that answer, right? We know what features God, is there? No. But when we're doing something like a NAMI detection, that's a neural network. That black box it tells us yes, there's a problem. There's some anomaly, but that doesn't know what caused the anomaly. But that's a case where we actually used neural networks, actually find the anomie, and then we're using something else to find the root cause, eh? So it really depends on the use case and where the night you're going to use an interpreter of model or a neural network which is more of a black box model. T tell her you've got a cat or you've got a problem >>somewhere. So, Bob, that's really interested. So can you not unpacking? Neural network is just the nature of the way that the communication and the data flows and the inferences are made that you can't go in and unpack it, that you have to have the >>separate kind of process too. Get to the root cause. >>Yeah, assigned is always hard to say. Never. But inherently s neural networks are very complicated. Saito set of weights, right? It's basically usually a supervised training model, and we're feeding a bunch of data and trying to train it to detect a certain features, sir, an output. But that is where they're powerful, right? And that's why they basically doing such good, Because they are mimicking the brain, right? That neural network is a very complex thing. Can't like your brain, right? We really don't understand how your brain works right now when you have a problem, it's really trialling there. We try to figure out >>right going right. So I want to stay with you, bought for a minute. So what about when you change what you're optimizing? Four? So you just said you're optimizing for throughput of the network. You're looking for problems. Now, let's just say it's, uh, into the end of the quarter. Some other reason we're not. You're changing your changing what you're optimizing for, Can you? You have to write separate algorithm. Can you have dynamic movement inside that algorithm? How do you approach a problem? Because you're not always optimizing for the same things, depending on the market conditions. >>Yeah, I mean, I think a good example, you know, again, with Marvis is really with what we call reinforcement. Learning right in reinforcement. Learning is a model we use for, like, radio resource management. And there were really trying to optimize for the user experience in trying to balance the reward, the models trying to reward whether or not we have a good balance between the network and the user. Right, that reward could be changed. So that algorithm is basically reinforcement. You can finally change hell that Algren works by changing the reward you give the algorithm >>great. Um, Rajan back to you. A couple of huge things that have come into into play in the marketplace and get your take one is open source, you know, kind of. What's the impact of open source generally on the availability, desire and more applications and then to cloud and soon to be edge? You know, the current next stop. How do you guys incorporate that opportunity? How does it change what you can do? How does it open up the lens of >>a I Yeah, I think open source is really important because I think one thing that's interesting about a I is that it's a very nascent field and the more that there's open source, the more that people could build on top of each other and be able to utilize what what others others have done. And it's similar to how we've seen open source impact operating systems, the Internet, things like things like that with Cloud. I think one of the big things with cloud is now you have the processing power and the ability to access lots of data to be able to t create these thes networks. And so the capacity for data and the capacity for compute is much higher. Edge is gonna be a very important thing, especially going into next few years. You're seeing Maur things incorporated on the edge and one exciting development is around Federated learning where you can train on the edge and then combine some of those aspects into a cloud side model. And so that I think will actually make EJ even more powerful. >>But it's got to be so dynamic, right? Because the fundamental problem used to always be the move, the computer, the data or the date of the computer. Well, now you've got on these edge devices. You've got Tanya data right sensor data all kinds of machining data. You've got potentially nasty hostile conditions. You're not in a nice, pristine data center where the environmental conditions are in the connective ity issues. So when you think about that problem yet, there's still great information. There you got latent issues. Some I might have to be processed close to home. How do you incorporate that age old thing of the speed of light to still break the break up? The problem to give you a step up? Well, we see a lot >>of customers do is they do a lot of training on the cloud, but then inference on the on the edge. And so that way they're able to create the model that they want. But then they get fast response time by moving the model to the edge. The other thing is that, like you said, lots of data is coming into the edge. So one way to do it is to efficiently move that to the cloud. But the other way to do is filter. And to try to figure out what data you want to send to the clouds that you can create the next days. >>Shawna, back to you let's shift gears into ethics. This pesky, pesky issue that's not not a technological issue at all, but right. We see it often, especially in tech. Just cause you should just cause you can doesn't mean that you should. Um so and this is not a stem issue, right? There's a lot of different things that happened. So how should people be thinking about ethics? How should they incorporate ethics? Um, how should they make sure that they've got kind of a, you know, a standard kind of overlooking kind of what they're doing? The decisions are being made. >>Yeah, One of the more approachable ways that I have found to explain this is with behavioral science methodologies. So ethics is a massive field of study, and not everyone shares the same ethics. However, if you try and bring it closer to behavior change because every product that we're building is seeking to change of behavior. We need to ask questions like, What is the gap between the person's intention and the goal we have for them? Would they choose that goal for themselves or not? If they wouldn't, then you have an ethical problem, right? And this this can be true of the intention, goal gap or the intention action up. We can see when we regulated for cigarettes. What? We can't just make it look cool without telling them what the cigarettes are doing to them, right so we can apply the same principles moving forward. And they're pretty accessible without having to know. Oh, this philosopher and that philosopher in this ethicist said these things, it can be pretty human. The challenge with this is that most people building these algorithms are not. They're not trained in this way of thinking, and especially when you're working at a start up right, you don't have access to massive teams of people to guide you down this journey, so you need to build it in from the beginning, and you need to be open and based upon principles. Um, and it's going to touch every component. It should touch your data, your algorithm, the people that you're using to build the product. If you only have white men building the product, you have a problem you need to pull in other people. Otherwise, there are just blind spots that you are not going to think of in order to still that product for a wider audience, but it seems like >>they were on such a razor sharp edge. Right with Coca Cola wants you to buy Coca Cola and they show ads for Coca Cola, and they appeal to your let's all sing together on the hillside and be one right. But it feels like with a I that that is now you can cheat. Right now you can use behavioral biases that are hardwired into my brain is a biological creature against me. And so where is where is the fine line between just trying to get you to buy Coke? Which somewhat argues Probably Justus Bad is Jule cause you get diabetes and all these other issues, but that's acceptable. But cigarettes are not. And now we're seeing this stuff on Facebook with, you know, they're coming out. So >>we know that this is that and Coke isn't just selling Coke anymore. They're also selling vitamin water so they're they're play isn't to have a single product that you can purchase, but it is to have a suite of products that if you weren't that coke, you can buy it. But if you want that vitamin water you can have that >>shouldn't get vitamin water and a smile that only comes with the coat. Five. You want to jump in? >>I think we're going to see ethics really break into two different discussions, right? I mean, ethics is already, like human behavior that you're already doing right, doing bad behavior, like discriminatory hiring, training, that behavior. And today I is gonna be wrong. It's wrong in the human world is gonna be wrong in the eye world. I think the other component to this ethics discussion is really round privacy and data. It's like that mirror example, right? No. Who gave that mirror the right to basically tell me I'm old and actually do something with that data right now. Is that my data? Or is that the mirrors data that basically recognized me and basically did something with it? Right. You know, that's the Facebook. For example. When I get the email, tell me, look at that picture and someone's take me in the pictures Like, where was that? Where did that come from? Right? >>What? I'm curious about to fall upon that as social norms change. We talked about it a little bit for we turn the cameras on, right? It used to be okay. Toe have no black people drinking out of a fountain or coming in the side door of a restaurant. Not that long ago, right in the 60. So if someone had built an algorithm, then that would have incorporated probably that social norm. But social norms change. So how should we, you know, kind of try to stay ahead of that or at least go back reflectively after the fact and say kind of back to the black box, That's no longer acceptable. We need to tweak this. I >>would have said in that example, that was wrong. 50 years ago. >>Okay, it was wrong. But if you ask somebody in Alabama, you know, at the University of Alabama, Matt Department who have been born Red born, bred in that culture as well, they probably would have not necessarily agreed. But so generally, though, again, assuming things change, how should we make sure to go back and make sure that we're not again carrying four things that are no longer the right thing to do? >>Well, I think I mean, as I said, I think you know what? What we know is wrong, you know is gonna be wrong in the eye world. I think the more subtle thing is when we start relying on these Aye. Aye. To make decisions like no shit in my car, hit the pedestrian or save my life. You know, those are tough decisions to let a machine take off or your balls decision. Right when we start letting the machines Or is it okay for Marvis to give this D I ps preference over other people, right? You know, those type of decisions are kind of the ethical decision, you know, whether right or wrong, the human world, I think the same thing will apply in the eye world. I do think it will start to see more regulation. Just like we see regulation happen in our hiring. No, that regulation is going to be applied into our A I >>right solutions. We're gonna come back to regulation a minute. But, Roger, I want to follow up with you in your earlier session. You you made an interesting comment. You said, you know, 10% is clearly, you know, good. 10% is clearly bad, but it's a soft, squishy middle at 80% that aren't necessarily super clear, good or bad. So how should people, you know, kind of make judgments in this this big gray area in the middle? >>Yeah, and I think that is the toughest part. And so the approach that we've taken is to set us set out a set of AI ai principles on DDE. What we did is actually wrote down seven things that we will that we think I should do and four things that we should not do that we will not do. And we now have to actually look at everything that we're doing against those Aye aye principles. And so part of that is coming up with that governance process because ultimately it boils down to doing this over and over, seeing lots of cases and figuring out what what you should do and so that governments process is something we're doing. But I think it's something that every company is going to need to do. >>Sharon, I want to come back to you, so we'll shift gears to talk a little bit about about law. We've all seen Zuckerberg, unfortunately for him has been, you know, stuck in these congressional hearings over and over and over again. A little bit of a deer in a headlight. You made an interesting comment on your prior show that he's almost like he's asking for regulation. You know, he stumbled into some really big Harry nasty areas that were never necessarily intended when they launched Facebook out of his dorm room many, many moons ago. So what is the role of the law? Because the other thing that we've seen, unfortunately, a lot of those hearings is a lot of our elected officials are way, way, way behind there, still printing their e mails, right? So what is the role of the law? How should we think about it? What shall we What should we invite from fromthe law to help sort some of this stuff out? >>I think as an individual, right, I would like for each company not to make up their own set of principles. I would like to have a shared set of principles that were following the challenge. Right, is that with between governments, that's impossible. China is never gonna come up with same regulations that we will. They have a different privacy standards than we D'oh. Um, but we are seeing locally like the state of Washington has created a future of work task force. And they're coming into the private sector and asking companies like text you and like Google and Microsoft to actually advise them on what should we be regulating? We don't know. We're not the technologists, but they know how to regulate. And they know how to move policies through the government. What will find us if we don't advise regulators on what we should be regulating? They're going to regulate it in some way, just like they regulated the tobacco industry. Just like they regulated. Sort of, um, monopolies that tech is big enough. Now there is enough money in it now that it will be regularly. So we need to start advising them on what we should regulate because just like Mark, he said. While everyone else was doing it, my competitors were doing it. So if you >>don't want me to do it, make us all stop. What >>can I do? A negative bell and that would not for you, but for Mark's responsibly. That's crazy. So So bob old man at the mall. It's actually a little bit more codified right, There's GDP are which came through May of last year and now the newness to California Extra Gatorade, California Consumer Protection Act, which goes into effect January 1. And you know it's interesting is that the hardest part of the implementation of that I think I haven't implemented it is the right to be for gotten because, as we all know, computers, air, really good recording information and cloud. It's recorded everywhere. There's no there there. So when these types of regulations, how does that impact? Aye, aye, because if I've got an algorithm built on a data set in in person, you know, item number 472 decides they want to be forgotten How that too I deal with that. >>Well, I mean, I think with Facebook, I can see that as I think. I suspect Mark knows what's right and wrong. He's just kicking ball down tires like >>I want you guys. >>It's your problem, you know. Please tell me what to do. I see a ice kind of like any other new technology, you know, it could be abused and used in the wrong waste. I think legally we have a constitution that protects our rights. And I think we're going to see the lawyers treat a I just like any other constitutional things and people who are building products using a I just like me build medical products or other products and actually harmful people. You're gonna have to make sure that you're a I product does not harm people. You're a product does not include no promote discriminatory results. So I >>think we're going >>to see our constitutional thing is going applied A I just like we've seen other technologies work. >>And it's gonna create jobs because of that, right? Because >>it will be a whole new set of lawyers >>the holdings of lawyers and testers, even because otherwise of an individual company is saying. But we tested. It >>works. Trust us. Like, how are you gonna get the independent third party verification of that? So we're gonna start to see a whole terrorist proliferation of that type of fields that never had to exist before. >>Yeah, one of my favorite doctor room. A child. Grief from a center. If you don't follow her on Twitter Follower. She's fantastic and a great lady. So I want to stick with you for a minute, Bob, because the next topic is autonomous. And Rahman up on the keynote this morning, talked about missed and and really, this kind of shifting workload of fixing things into an autonomous set up where the system now is, is finding problems, diagnosing problems, fixing problems up to, I think, he said, even generating return authorizations for broken gear, which is amazing. But autonomy opens up all kinds of crazy, scary things. Robert Gates, we interviewed said, You know, the only guns that are that are autonomous in the entire U. S. Military are the ones on the border of North Korea. Every single other one has to run through a person when you think about autonomy and when you can actually grant this this a I the autonomy of the agency toe act. What are some of the things to think about in the word of the things to keep from just doing something bad, really, really fast and efficiently? >>Yeah. I mean, I think that what we discussed, right? I mean, I think Pakal purposes we're far, you know, there is a tipping point. I think eventually we will get to the CP 30 Terminator day where we actually build something is on par with the human. But for the purposes right now, we're really looking at tools that we're going to help businesses, doctors, self driving cars and those tools are gonna be used by our customers to basically allow them to do more productive things with their time. You know, whether it's doctor that's using a tool to actually use a I to predict help bank better predictions. They're still gonna be a human involved, you know, And what Romney talked about this morning and networking is really allowing our I T customers focus more on their business problems where they don't have to spend their time finding bad hard were bad software and making better experiences for the people. They're actually trying to serve >>right, trying to get your take on on autonomy because because it's a different level of trust that we're giving to the machine when we actually let it do things based on its own. But >>there's there's a lot that goes into this decision of whether or not to allow autonomy. There's an example I read. There's a book that just came out. Oh, what's the title? You look like a thing. And I love you. It was a book named by an A I, um if you want to learn a lot about a I, um and you don't know much about it, Get it? It's really funny. Um, so in there there is in China. Ah, factory where the Aye Aye. Is optimizing um, output of cockroaches now they just They want more cockroaches now. Why do they want that? They want to grind them up and put them in a lotion. It's one of their secret ingredients now. It depends on what parameters you allow that I to change, right? If you decide Thio let the way I flood the container, and then the cockroaches get out through the vents and then they get to the kitchen to get food, and then they reproduce the parameters in which you let them be autonomous. Over is the challenge. So when we're working with very narrow Ai ai, when use hell the Aye. Aye. You can change these three things and you can't just change anything. Then it's a lot easier to make that autonomous decision. Um and then the last part of it is that you want to know what is the results of a negative outcome, right? There was the result of a positive outcome. And are those results something that we can take actually? >>Right, Right. Roger, don't give you the last word on the time. Because kind of the next order of step is where that machines actually write their own algorithms, right? They start to write their own code, so they kind of take this next order of thought and agency, if you will. How do you guys think about that? You guys are way out ahead in the space, you have huge data set. You got great technology. Got tensorflow. When will the machines start writing their own A their own out rhythms? Well, and actually >>it's already starting there that, you know, for example, we have we have a product called Google Cloud. Ottawa. Mel Village basically takes in a data set, and then we find the best model to be able to match that data set. And so things like that that that are there already, but it's still very nascent. There's a lot more than that that can happen. And I think ultimately with with how it's used I think part of it is you have to start. Always look at the downside of automation. And what is what is the downside of a bad decision, whether it's the wrong algorithm that you create or a bad decision in that model? And so if the downside is really big, that's where you need to start to apply Human in the loop. And so, for example, in medicine. Hey, I could do amazing things to detect diseases, but you would want a doctor in the loop to be able to actually diagnose. And so you need tohave have that place in many situations to make sure that it's being applied well. >>But is that just today? Or is that tomorrow? Because, you know, with with exponential growth and and as fast as these things are growing, will there be a day where you don't necessarily need maybe need the doctor to communicate the news? Maybe there's some second order impacts in terms of how you deal with the family and, you know, kind of pros and cons of treatment options that are more emotional than necessarily mechanical, because it seems like eventually that the doctor has a role. But it isn't necessarily in accurately diagnosing a problem. >>I think >>I think for some things, absolutely over time the algorithms will get better and better, and you can rely on them and trust them more and more. But again, I think you have to look at the downside consequence that if there's a bad decision, what happens and how is that compared to what happens today? And so that's really where, where that is. So, for example, self driving cars, we will get to the point where cars are driving by themselves. There will be accidents, but the accident rate is gonna be much lower than what's there with humans today, and so that will get there. But it will take time. >>And there was a day when will be illegal for you to drive. You have manslaughter, right? >>I I believe absolutely there will be in and and I don't think it's that far off. Actually, >>wait for the day when I have my car take me up to Northern California with me. Sleepy. I've only lived that long. >>That's right. And work while you're while you're sleeping, right? Well, I want to thank everybody Aton for being on this panel. This has been super fun and these air really big issues. So I want to give you the final word will just give everyone kind of a final say and I just want to throw out their Mars law. People talk about Moore's law all the time. But tomorrow's law, which Gardner stolen made into the hype cycle, you know, is that we tend to overestimate in the short term, which is why you get the hype cycle and we turn. Tend to underestimate, in the long term the impacts of technology. So I just want it is you look forward in the future won't put a year number on it, you know, kind of. How do you see this rolling out? What do you excited about? What are you scared about? What should we be thinking about? We'll start with you, Bob. >>Yeah, you know, for me and, you know, the day of the terminus Heathrow. I don't know if it's 100 years or 1000 years. That day is coming. We will eventually build something that's in part of the human. I think the mission about the book, you know, you look like a thing and I love >>you. >>Type of thing that was written by someone who tried to train a I to basically pick up lines. Right? Cheesy pickup lines. Yeah, I'm not for sure. I'm gonna trust a I to help me in my pickup lines yet. You know I love you. Look at your thing. I love you. I don't know if they work. >>Yeah, but who would? Who would have guessed online dating is is what it is if you had asked, you know, 15 years ago. But I >>think yes, I think overall, yes, we will see the Terminator Cp through It was probably not in our lifetime, but it is in the future somewhere. A. I is definitely gonna be on par with the Internet cell phone, radio. It's gonna be a technology that's gonna be accelerating if you look where technology's been over last. Is this amazing to watch how fast things have changed in our lifetime alone, right? Yeah, we're just on this curve of technology accelerations. This in the >>exponential curves China. >>Yeah, I think the thing I'm most excited about for a I right now is the addition of creativity to a lot of our jobs. So ah, lot of we build an augmented writing product. And what we do is we look at the words that have happened in the world and their outcomes. And we tell you what words have impacted people in the past. Now, with that information, when you augment humans in that way, they get to be more creative. They get to use language that have never been used before. To communicate an idea. You can do this with any field you can do with composition of music. You can if you can have access as an individual, thio the data of a bunch of cultures the way that we evolved can change. So I'm most excited about that. I think I'm most concerned currently about the products that we're building Thio Give a I to people that don't understand how to use it or how to make sure they're making an ethical decision. So it is extremely easy right now to go on the Internet to build a model on a data set. And I'm not a specialist in data, right? And so I have no idea if I'm adding bias in or not, um and so it's It's an interesting time because we're in that middle area. Um, and >>it's getting loud, all right, Roger will throw with you before we have to cut out, or we're not gonna be able to hear anything. So I actually start every presentation out with a picture of the Mosaic browser, because what's interesting is I think that's where >>a eyes today compared to kind of weather when the Internet was around 1994 >>were just starting to see how a I can actually impact the average person. As a result, there's a lot of hype, but what I'm actually finding is that 70% of the company's I talked to the first question is, Why should I be using this? And what benefit does it give me? Why 70% ask you why? Yeah, and and what's interesting with that is that I think people are still trying to figure out what is this stuff good for? But to your point about the long >>run, and we underestimate the longer I think that every company out there and every product will be fundamentally transformed by eye over the course of the next decade, and it's actually gonna have a bigger impact on the Internet itself. And so that's really what we have to look forward to. >>All right again. Thank you everybody for participating. There was a ton of fun. Hope you had fun. And I look at the score sheet here. We've got Bob coming in and the bronze at 15 points. Rajan, it's 17 in our gold medal winner for the silver Bell. Is Sharna at 20 points. Again. Thank you. Uh, thank you so much and look forward to our next conversation. Thank Jeffrey Ake signing out from Caesar's Juniper. Next word unpacking. I Thanks for watching.

>>live from San Francisco. It's the Q covering Micron Insight 2019 >>Not to You, by Micron. >>Welcome back to San Francisco, everybody. This is a Micron Insight 2019 and you're watching the Cube, the leader in live coverage on Day Volonte with my co host, David Floyd. Di Mooney is here. She's the executive director of Micron gives. That's right. Give us the story. What's happening with Micron gives Tech for good. We love the tech for good stories. Tech companies are really taking this seriously. This is not just lip service. Give us the update. >>That's right. That's right. We're so proud of our company that they established a foundation 20 years ago to give back to our global communities. And since then we have given $115 million away and over 10,000 grands. So we have seen a lot of different opportunities in our global communities, and it's just been fabulous that our company supports >>you talk today about water dot or what's going on there. Why is that important in what your role there. >>So what we did is we started taking a look at an organization that we have. We have started recently binning beam or engaged with basic human needs and the grants that those support And when we were taking a look at, Really, what is the primary basic human need? Way discovered? It really is the need for water, and there are millions of people that cannot access this precious resource, and it's just was really surprising to us to think way, take it for granted so much. But yet it is very difficult to get. So as we took a look at this, there was a lot of information that this organization collects. And so we thought, Well, this will be a great opportunity for us to utilize information to enrich and bring in some of our advanced computing expertise along with our philanthropy, help them reach their mission even greater. >>This is huge. I was an event earlier this week, and the keynote speaker was an ultra marathoner, and he literally at one point he ran 4500 miles across the continent of Africa. He and two other ultra runners and people were asking what was The biggest challenge was that the heat was the painting. You know, the biggest challenge was see the challenges of of the community's getting part of the water. That was the number one thing that you know. He left the impression So I mean, this is a huge global problem. >>It really is. And our manufacturing operations were global, and we are located in water scarce areas of the world. And so what really became you know, it's a Micron issue to one of our biggest environmental issues that we talked about, and water dot org's has just been a >>leader in this space, and it has been just fabulous to work with on >>really, they have so much passion and dedication towards this. They've been ableto help. 22 million people already. >>All right, so they're lining up for the main stage. Just give us real quick some of the grants that you guys have. >>Last year at this event, we announced our advancing curiosity, and we announced three recipients last year, and since then we have four more. That's U C L. A. All right T, University of Texas at Austin and University of Washington. >>Awesome. That's great. Listen, congratulations. D on all your great work. We really appreciate your ticket sometime in the queue. All right, and thank you for watching her body. We're back with our next guest from Micron inside. 2019 on the Cube, right back.

>>from Miami >>Beach, Florida It's the Q covering a Cronus Global Cyber >>Summit 2019. Brought to you by a Cronus. >>Welcome to the Qi. We are in Miami, Florida, for the Cronus Global Cyber Summit. 2019 John for your host of the Cube. We're here for two days of coverage around cybersecurity and the impact to the enterprise in society in a great guest here to kick off the event. Linda Babcock, professor of economics at Carnegie Mellon University, author of the book, Ask for It, and she has a new book she's working on, and we'll get into that. Thanks for joining me. Thanks for coming on. >>Really happy to be here. >>Thanks. So Carnegie Mellon. Great. Great. Uh, University. They stole a bunch of people when I was in school, in the computer science department. Very well known for that as well. Economics, math, machine learning. I was good stuff there. What's going on in Carnegie Mellon? What's new in your world? >>Well, it's just actually just a great place to be because of the focus on interdisciplinary work. You know, problems in the world don't come as disciplines. They come with multiple perspectives needed and So it's just a place where people can flourish, attack ideas from all kinds of angles. And so it's a really great >>one of the things I hear a lot about, and we cover a lot about the the skills gap. Certainly this is Maur job openings than there are jobs and interesting. A lot of the jobs that are new haven't been skilled, important in the classic university setting. So a lot of these jobs, like cybersecurity, cloud computing, Blockchain, crypto economic token economics, all kind of have a maths economic steam to him. So you know your computer science, you got economics and policy. I seem to be the key areas around from these new skills and challenges. Way faces a society which your take on all this >>Well, actually, there's a lot going on in this area at Carnegie Mellon. Actually, the economics group at Carnegie Mellon ISS is been proposing a new major that really focuses on this interface between economics, machine learning and technology. And I think it's going to train our students just for the next generation of problems that the world of tech is gonna have. So it's very exciting. >>So let's talk about your book. Ask for it. Okay. Um, it's not a new book that's been around for a while, but you give a talk here. What's what's the talking talking track here at the event? >>Yeah, so I have a couple of themes of research, and it focuses on women's Berries to advancement in organizations. And so most of the work that I did with this book and my first book, Women Don't Ask, was looking about how men and women approached negotiation differently. And kind of the bottom line is that women are what less likely to negotiate than men over all kinds of things, like pay like opportunities for advancement like the next promotion. And it really harms them in the workplace because men are always out there asking for it and organizations reward that. And so the book is was really about shedding light on this disparity and what organizations could do about it and what women can do about it themselves, how they can learn to negotiate more effectively. >>What did you learn when you were writing the book around? Some of the use cases of best practices that women were doing in the field was it. Maura aggressive style has a more collaborative. You're seeing a lot more solidarity amongst women themselves, and men are getting involved. A lot of companies are kind of talking the game summer walking, the talk. What the big findings that you've learned >>well, I'd say that the approach is that women use are a lot different than the approaches that menus. And it's because our world lets men do a lot of different things. It lets them engage in a cooperative way, lets them be very competitive. But our world has a very narrow view about what's acceptable behavior for women. I often call it a tight rope because women are kind of balancing that they need to go out and assert themselves. But they have to do it in a way that our side, a society finds acceptable, and that that tight rope constrains women and doesn't allow them to be their authentic Selves on DSO. It makes it difficult for women to navigate that. What's your >>take on the the balancing of being aggressive and the pressure companies have to, you know, keep the women population certainly pipeline in tech. We see it all the time and the whole me to thing and the pressure goes on because norms were forming, right? So is there any new data that you can share around how, with norms and for forming and what men can do? Particularly, I get this question a lot, and I always ask myself, What am I doing? Can I do something different? Because I want to be inclusive and I want to do the right thing. But sometimes I don't know what to do. >>Yeah, of course. And it's really important that men get involved in this conversation as allies and, like you said, sometimes men but don't know what to do because they feel like maybe they don't have standing to be in the conversation when it's about women and weigh all need men, his allies. If women are gonna try to reach equality, ATT's some point. But the new data really suggests negotiation may be playing a role. The work that show Sandberg lean in, But the newest work that we have shows that actually the day to day things that happen at work that's holding women back. So let me tell you about that. So what we find is if you think about your calendar and what you do all day there a task that you can classify as being promotable, that is, they're really your core job. Responsibility there noticed, rewarded. But there's glass of other things that happen in your organization that are often below the surface that are important to dio valued but actually not rewarded. And what our research finds is that men spend much more time than women at the tasks that are these promotable task that rewarded women spend much more time than men on these tasks that we call non promotable that are not rewarded. And it's really holding women back. And how men can help is that the reason that women are doing these tasks is because everyone is asking them to do these tasks. And so what men can do is start asking men to do some of these things that are important but yet not rewarded because the portfolio's now are really out of balance and women are really shouldering the burden of these tasks disproportionately. >>So get on the wave of the promotional off the promotional oriented things that Maura and the man can come and pick up the slack on some of the things that were delegated to the women because they could order the kitchen food or whatever >>or help others with their work. Someone has to hire the summer intern. Someone has to organize events. Someone has to resolve underlying conflicts. Those are all really important things. Women get tasked with them, and that really doesn't allow them to focus on their core job responsibilities. And so men can step up to the blade, stop, do it, start doing their fair share of that work, and really then allow women to reach their full >>potential. I've been thinking a lot about this lately around how collaboration software, how collaborative teams. You started to see the big successful coming like Amazon to pizza team concept. Smaller teams, Team Orient. If you're doing it, you're in a teen. These things go. You've given you get so I think it's probably a better environment. Is that happening or no? It's >>unclear how teams kind of shake out for women in this setting, because there's actually some research that shows when a team produces an output and the supervisor trying to figure out, like who really made the output? Who was the valued player on the team. They often overvalue the contributions of men and undervalued the contributions of women. So actually, team projects can be problematic if women don't get their fair share of >>bias. Is everywhere >>biases everywhere. And you know it's not that people are trying discriminate against women. It's just that it's a subconscious, implicit bias and so affects our judgments in ways that we don't even realize. >>It's actually probably amplifies it. You know, the game are gaining a lot of things on digital indigenous communities. We see a lot where people are hiding behind their avatars. Yeah, that's also pretty bad environment. So we've been doing a lot of thinking and reporting around communities and data. I want to get your thoughts is I never really probed at this. But is there any economic incentives? And after you're an economics professor, you seeing things like crypto economics and tokens and all kinds of new things is a potential path towards creating an incentive system that's cutting edge what's progressive thinking around any kind of incentive systems for organizations or individuals. >>Well, when you think about incentives and maybe an economist, I think about those a lot, and I emerged that with my work on various to women's advancement, I think incentives is one area that you can actually play a big role. And that is that Organizational leaders should be incentive fied incentivized to see that they have equal advancement for their male and female employees in their workforce. Because if they don't it means they're losing out on this potential that women have, that they aren't able to fully be productive. And so that's, I think, the place. I think that incentives can really be important, >>a great leader and he said, and I'm quoting him. But I feel the same way says. Our incentive is business. Get a better outcome with them. We include women, give data, goes Yeah, we make software and have people that use our software with women I don't wanna have. So I'm like, Oh, that makes a lot of sense. Biases should be in there. Four Women for women by women for women >>and women spend more money as consumers than men. And so having women on teams allows them to see perspectives that men may not see, and so it can really add two new innovative thinking that hadn't been there before by including women. >>Well, I'm excited that this there's a little bit of movement in tech we're starting to see, certainly in venture capital, starting to see a lot more when you come into the board room work to do. But I think there's a nice sign that there's more jobs that are computer related that aren't just coding. That's male dominant pretty much now and still still is for a while. But there's a lot more skills, all kinds of range now in computer science. It's interesting. How is that affecting some of the new pipeline ing? >>Yeah, well, I think the good news is that there are is increasing levels of women's attainment in stem fields. And so there are more and more female workers entering the labor market today. Way just have to make sure that those workers are valued and feel included when they do doing tech companies. Otherwise they will leave because what happens unfortunately, sometimes in tech is it doesn't feel inclusive for women. And the quick rate for women in tech is over over twice the rate for men, and some of the reasons are is they're not feeling valued in their positions. They're not seeing their advancement. And so with this new wave of female workers, we have to make sure that those workplaces are ready to accept them and include them. >>That's great. Well, ask for it is a great book. I went through it and it's great handbook. I learned a lot. It really is a handbook around. Just standing up and taken what you can. You got some new, but you got a new book you're working on. What's that gonna look like? What if some of the themes in the new book >>Yeah. So the new book is on these promotable tasks, and the way I like to think about it is there's so much attention toe work, life balance, you know? How do you manage both of those with your career, your family? How does that work? But our work actually focuses on work, work, balance, and what remains is paying attention to the things that you do at work. Making sure that those things that you're doing are the things that are most valuable for your employer and are gonna be most valuable for your career. So it's a really different focus on the day to day ways that you spend your time at work and how that can propel women to the next level. >>That's awesome, Linda. Thanks for coming. I appreciate it. What do you think of the event here? Cronies? Global cyber security summit. >>Well, I got to say it's not my typical event, but I'm having a good time learning more about what's happening in the tech industry today. >>Cyber protection, Certainly a cutting edge issue. And certainly on the East Coast in Washington D certainly with national defense and all kinds of things happening, Ransomware is a big topic that kicked around here absolutely getting taken out like, Oh, my God. Yeah. Bitcoin in return for taking your systems out, >>all kinds of new stuff to add to my tool kit. >>Great to have you on. Thanks for your insight. Thanks for sharing. Appreciate it. I'm John for here at the Cube. We're here in Miami Beach for the Cronus Cyber Protection Conference. Thank you for watching

>> From Bahrain, it's theCUBE. Covering AWS Public Sector Bahrain. Brought to you by Amazon Web Services. >> Welcome back, everyone, to CUBE coverage here in Bahrain for AWS Summit. Cloud computing's changing the landscape, startups, business, government, and society. We're here with a special guest, His Excellency, Aymen Tawfiq Almoayed. Thank you very much, thanks for coming, thanks for joining us. >> Thank you for having me. >> And of course Max Peterson, Vice President of International Sales, Worldwide Public Sector for Amazon Web Services. >> Good to be here, John. >> Your Excellency, this program you're doing with Amazon, this MOU you've signed is interesting, I want to unpack it, because it speaks to the bigger picture of how the region is shaped by its generational shift of cloud computing and the people here. This is a really big part of this modernization plan. >> No question, no question. So the program that the government adopted, so Vision 2030, which was adopted a while ago, is based on one premise, one key premise. That the government is going to move from operator to regulator, and our focus would be to focus on and establish, create almost, an open, just, competitive environment. So the idea is for us to provide the platform and then allow the meritocratic system to let those that can aspire to opportunities and reach these opportunities come up through the system. So this program really sets the stage to get a new level going. >> Explain the difference with this program and why it's different than some of the things we've been hearing. We saw a cloud computing degree coming out of the University of Bahrain. We're seeing a lot of job skill training. This is different, this is a unique thing. Can you give a more detail around how it works. >> So, what we're doing is we're looking at very quick wins. And for us, six months, for somebody to spend six months, one year, in Amazon is a very quick win. This is not an extended degree. What this is is it's an opportunity to interact with the best of the best in their world sector. And to, honestly it's almost like a reset, where what Max and I were talking about earlier is somebody that spends a year with Amazon, I think that something happens to the pulse rate, right. So your pulse literally starts to beat much faster. >> Max knows all about that. >> Exactly, exactly. We hear about their traveling patterns, and that in itself is amazing. So in any case, so the reason it's different from a degree is it gives you real-life vocational experience. It gives you the networking opportunity. It gives you the lifestyle exposure. And then it gives you the shortcuts in organization. >> So you're exposing them to the excellence of what a culture looks like, Amazon in this case. They're hard-charging, they're fast. Anyone who's worked with Amazon knows that they move pretty quickly. But they're disciplined. It's a world-class organization. It's like a sports team being promoted to varsity or the pro team. Work their way up from the entry-level. >> So maybe the difference as well is, in this sort of program it's sink or swim. It's really as simple as that. I mean, you need to hit the ground running and take off. Maybe with a degree, it's much less so. With a degree, you go through your first year, your second year, your sophomore and so on. So what we do, what we want, is we want our youth to hit the ground running. We want very quick wins and I have no doubt that once the first trench, first team goes out to Amazon, comes back, I'm sure that the ripple effect that you see in industry and you see in the marketplace will be tremendous. >> Max, what's your take on this? 'Cause obviously you're on the Amazon side. You're taking them in Amazon Web Services here in Bahrain, or is it outside corporate headquarters in Seattle? Is there a definition around? >> All good questions. First, we're excited to be the first company that is partnered with the Ministry on this effort. We're sure many others are going to join, but we're excited to be first. I think what makes it different is the aspect of experiential. There's a lot of experiential learning that's going on different than the academic learning. Equally or maybe even more necessary is the sort of organizational cultural learning. Just what does it take to operate at world scale or at pace. And then to be able to bring that back to the region. We'll do that wherever we've got the right mix of skills. So it could be in Bahrain, where we've got a big office now, it could be in London, could be Washington, D.C., could be Seattle. >> Your Excellency, we always talk about on theCUBE over the years, tech athletes. Because, you know, to be an athlete, you got to have durability, intelligence, stability. Being a tech athlete, the travel schedules, we were just joking last night about it, you mentioned it. But also the intelligence and the integrity to do this at this speed. So this is kind of, I love the theme, so I want you to elaborate why this connects in with your vision and how did this idea get started, what was the origination around this effort? >> So initially the, again, if one takes a step back, we started experimenting about a year ago, a year and a half ago with the sports sector. So what we were doing with the sports sector, because it was a much smaller sector. What we're trying to experiment there is, if you were to allow our athletes to interact with the best in class, what would happen? Would they live up to that experience or not? And so one of the segments that we were looking at is, for example, triathlons. So about two years ago, this sport, triathlons in general, just simply didn't exist in the region. So two, maximum three years ago, they just, they were nonexistent. So His Highness had ordered that we go ahead and see if we can develop this and see if we can develop the athletes for it. And so what we needed to do, essentially, was pick some-- >> Find the athletes. (laughs) >> Is find the athletes, exactly. Send them out, we did a few triathlons. They did Kuna and Florida, came back, loved it, the addiction and the adrenaline kicked in, and then we started arranging duathlons and then triathletes here in Bahrain. Of course, I don't know if you know this, a year, fast forward, a year and a half later, and BE13, which is our triathlon team, is number one in the world. Simply it's number one in the world. Now we're doing this, we tried this with biking. So we sent a team to the Tour de France, and we started to do exactly the same thing. We were aspiring to look at greats like Sky team and the rest, and just learning from them, imitate, and then innovate, and-- >> One, if you have to have the talent to begin with, your theory is put 'em in, let 'em see it, and they'll either level up or they won't. It's self selection. >> Absolutely, no question. >> And you want to bring that formula to tech. >> It's pure meritocratic sink or swim. So we've got, so there's two, there's two phrases that we live by, all right. Number one, our role is open, competitive, just environment. That's it, all right. The number two is we open doors with no hand-holding. Simply no hand-holding, but we'll get you the opportunity. But if Amazon calls us and says participant number 606 or whatever isn't up to the cut, then they're not up to the cut. And what our youth have proven to us time after time is they're always up to the cut. As long as you make that clear, they-- >> The expectation defines the experience. So if you say this is what it is, you can swim or you can sink, your choice, people will tap out, they won't even jump in. >> I like the tech athletes piece. >> Yeah, I'm loving it, absolutely. >> Well, I mean, a lot of tech athletes, it takes a lot of energy, it is like you said, you don't know what it takes to build a company, it's really hard, I mean, it's not easy. >> It is, and the thing, just like this program, the thing that was interesting about the University of Bahrain idea was they're going to try and immerse everybody, because cloud and technology now is immersed in any field. I mean, anything becomes digital. And we were talkin' earlier about e-sports, so you need a whole bunch of great tech athletes to start bringing e-sports services to the world. >> Absolutely. >> Do you see e-sports emerging? >> Yeah, no doubt. So what we did on Friday is we signed the first agreement, this is the first time that a region hosts, we're hosting BLASTPro's finals in Bahrain, this is going to be on the 13th and the 14th of December, and that's running, streaming on Twitch. So we're excited, we're excited to be doing this with the guys at BLASTPro, and we're excited to be using Amazon's infrastructure to do it. So yes, absolutely, there is amazing things to be seen in e-sports and we're excited. >> This is awesome, digital disruption, you guys have been so proactive on this. I was commenting this morning on Twitter, then stats went out about entrepreneurship in Silicon Valley in the U.S., 51% of all ventures fail. And some other ones, 4% become unicorns, but it was all about optionality, et cetera, et cetera, and entrepreneurs are about getting on the right wave and falling and trying again, and this is, you guys have been very proactive on this. >> Right, so that's exactly why we think that sports plays a big role. So the idea behind the program was simply to gamify everything. The idea behind this program, the idea behind adopting the new bankruptcy law in Bahrain, and the new reform regulations that are coming in, all we're doing is we're gamifying things. What we're simply saying is when you fall, it's OK to fall. As long as you get back up and hit the ground running once again, we're OK with that. So you'll start to hear phrases that are pretty interesting. Like I said, with the entrepreneurships, what we're looking at is unlocking levels. So we're gamifying. With education we're doing exactly the same thing, we're looking at vocational training where you get to unlock levels. So as long as people know that the name of the game is just to stay in the game, and then outpace everybody else, then we're good. >> And the funding's been fantastic. You guys have been supporting it with resources. Now that the region's up and running, Max, do you feel good about the development so far with the new region? Therese was just on earlier, she mentioned first day they turned it on, a bunch of companies were launched already. >> Besides the cannons and the confetti that shot out today at the summit, the other exciting thing's I think when we launched the region, we had over 350 different companies, many small businesses, small and medium enterprises that put their offerings into the AWS Marketplace. When it was launched, anybody in the region, anybody in Bahrain, could literally turn on 1,700 different types of software solutions at the push of a button, so I think that's big. I think we heard how 35 local companies have created migration offerings and fast-start offerings. We heard from one great entrepreneur on stage today and we heard from government about how government's operating faster than business, I think Sheikh Salman threw down a bit of a challenge to the rest of the government and state enterprises and even corporations. And then of course I think we saw the digital bank of the future from Bank ABC with their first virtual banking assistant up on stage who, by the way, lives in the cloud over Bahrain. >> Yeah, digital employee, we had a great chat about that. This speaks to the generational shift, this is something that's going to be an interesting footnote in history. The sea change around expectations, you brought this up earlier, I think this is important. The younger generation, they want the world to be at a different speed, and they don't want an intolerant blockers in their way. And so whoever can be out front on setting up the environment, whether it's society, government, citizen services, but money-making potential, banks got to operate. So this is the replatforming of society is happening. >> No question, yeah, no question. I'll give you just the, when you compare ministries, when you compare government entities, you would walk in and you'd assume the ultra-bureaucratic system is still in place where you've got to go through tiers and so on and so forth. As far as the youth at the Ministry of Youth is involved, these guys are running things with chats, we've got internal chat systems, and so there is no memo-writing process where you then have to escalate it, and then it goes to the minister's office and so on. Absolutely not. These guys are on the likes of Slack, the likes of Teams from Microsoft and so on, and that's how government is run. >> Max, email's for old people like us. >> Hey, modern digital governments are redesigning the way all this stuff works, and it doesn't, the thing that's interesting to me is it doesn't just impact these things that you would think of as tech. I thought the example of going from 130 days to 5 days for permitting approvals-- >> For building permits, sure. >> That takes out a massive amount of inefficiency from the industry, right, and it enables that very industry to then move faster, instead of government as a blocker to so many of these things, becomes an enabler. And I think it's that attitude about modernized, customer-focused or citizen-focused that is the hallmark of what folks are doing now to make a difference. >> Well, thanks for coming in and sharing the insights. Your Excellency, great to see you. I have one final question, take a minute to explain to the folks what is the Ministry of Youth and Sports Affair, what's the charter, you going to add tech athletes to the mix now that we've kind of defined that term? But take a minute to explain-- >> Tech athletes. So the vast majority of the population is under the age of 35. The ministry's mandate is to make sure that anybody within that constituency, their touchpoints are being managed in the right way. So our job, very, very simply, is to be effectively the change agent for them, number one, and number two, to protect their interests. So we're the ones that are negotiating regulations that come in, but what touchpoint really is relevant? We're negotiating new laws that impact youth when it comes to their trades, new laws that impact youth when it comes to their rights, new laws-- >> Whether it's culture or art or whatever. >> Any touchpoints, so effectively we're customer-relations for youth, or client relations for youth. So that's that from one perspective. With regards to sports, we're simply regulators. So what we're doing is we're moving from an operator model to a regulator model, and what we're trying to do is we're trying to create a sports industry. So instead of us focusing on the actual tournament itself only, we're looking at sports diplomacy, we're looking at sports industry, we're looking at human performance and things like that. So any sectors that we can catalyze to grow in Bahrain that relates in any way, shape, or form to sports, whether it was medicinal development, technological development, regulations or otherwise, that falls under Ministry of Youth and Sports. >> You're charged to look at the whole individual across all spectrums touchpoints. >> Exactly >> That's awesome. >> So we're a horizontal as opposed to a vertical. >> Your Excellency, great to have you on theCUBE, great topic, could talk about it forever. We love sports, of course, on theCUBE, we love talkin' sports, Max, you're a tech athlete. >> I'm a tech athlete, I learned that today. Brilliant. >> You go from city to city, hit a home run everywhere you go. >> I'm looking for the next league to compete in. >> Guys, thanks so much for the insights. CUBE coverage here at AWS Summit in Bahrain, I'm John Furrier, thanks for watching. (bright music)