>>Okay, welcome back to the Cube coverage of Dr Khan 2021. I'm John for your host. Had a great guest here. Dana Lawson. Vice president. Engineering and technology partnerships that get up dana. Welcome to the cube. You're leading the engineering team over at GIT hub. Been been around the block in the cloud enterprise area. Congratulations. Welcome to the cube. >>Well, thanks for having me. Don, I am super excited. Dr. 2021 Wow. I can't believe it's been that long. Right. >>Got the keynote coverage automation. The top trend here in the world. DevoPS DEP sec apps, developer productivity, modern errors here, a lot of action uh and dr conscious more attendance every year, containers setting up the cloud native. You know the tsunami of new ways that people are programming. New way teams are formed new way people are being super productive with the pandemic. We've seen developers really lead the charge in the virtual work environment. So a lot of action. So first tell us what's going on in the developer community right now, give us your take, >>I mean, my take on it is the developer teams are just working closer than ever before. You know, we see this across all industries, whether you're going through your own digital transformation and trying to streamline your workflow, um you know, we have this concept of devops now for about a decade and and we all were hopeful I was one of those early adopters that like, yes, this will change the world, as you can imagine, and like we're seeing it materialized and I feel like in this historic year, uh it's on steroids, we see teams working across the aisle doing things we've never experienced before with this concept of interconnected tools. And so we're seeing really the, I would say the practice of devops really going across every member of the team and not being just a practice that maybe one person on your team did. You know, this trend has been ongoing for a while. But with these new key technologies out there, it's really on fire in my opinion, >>outside of just the whole cloud native awesomeness that's happening. You see kubernetes enabling a lot of new things, the virtual work environment with the pandemic developers, just like just the way we've been working a long time. Finally, it just got standardized for the rest of the world, the world. Um they didn't really miss a beat and, and combined again with the cloud scale and we saw the earnings from all the big companies, the developers have been super productive this year. Do you see um that continuing and what, how is it going to change in your opinion as the pandemic kind of lifts a little bit and now the new normal gets back to real life. Certainly those benefits came out is what's your take on this engineering dynamic going on. >>I mean you said it they're like this is a common kind of workflow that people had pre pandemic, especially in the open source community where it's literally a bunch of random people around the world that don't obviously get to talk as as quickly and as uh you know, synchronously and so a saint communications gone up in what we've seen there is teams really tuning in their automation, right? So whereas you may have had it in your backlog to say, you know what, I should probably go automate that workflow now that we have been forced. Even even companies that haven't haven't thought about in the past to say, okay, how do I get code from A to B. Seamlessly? There's spending time on those workflows. and I think that we're seeing that naturally, you know, in the keynote where I mentioned some of the Research that we've done is we're seeing developers work more but we're seeing them work more on open source projects and the things that they want to work on not necessarily going and saying I'm going to go and spend 20 hours at work. But really it's that that continuation of like hey instead of automation being an afterthought we're gonna make it something that is at the forethought of what we're doing. And so what it's really done is just increase the time spent on writing great code and hopefully having a better up time. I am a I am a DEvops SRE sys admin, whatever you wanna call it at heart forever will be. Um and so you know, getting to have more time to spend on S. L. O. S. And really the, you know like I call it the safety guards, the rails of your system so that you can just really go in there and allow everybody to contribute. And that's what I think we're seeing and we're going to continue to see that as things just get easier as stuff happens out of the virtual box. >>I mean simple or easy. It's always a good strategy. I was just reporting for our team on the cube con and cloud native con. There's more cloud native con going on than cube con because kubernetes got kind of boring. Um, and enabled more cloud native development. And then the other trend that we've been reporting on is end user contribution to open sores. You're starting to see end users, not just the usual suspects like lift and whatnot. You're seeing like real enterprises like having teams contributing into open source in a big way. This is a kind of a new, interesting dynamic. What's your take on that? Is that a signal of simplicity? What does it mean? >>I'm going to tell you, I think that companies and big names that realized they were using open source and they have been all along, um, it's been around for a minute. Some of our most favorite libraries and frameworks have been open source from the beginning. You hear me talking about Java and Tomcat that's open source. And so it's really this understanding of the workflow. So I want to say that what we see now is there should be an investment because the world's team of open source developers are powering our technology and why shouldn't we as companies embrace and actually get back and spend that quality time because us innovating together on open source privately and publicly just makes everything better for everybody. And so I I think we're going to continue to see this trim. I'm excited about it. GIT hub has done some amazing work in this space by with get up sponsors because we want open source to continue to enable the innovation and having people participate. And now we're seeing it with businesses alike. And so I think we're going to see this practice continue on and really take a look not only of the technology they're using, but the open source practices like how do these maintainers and these open source teams shit reliable quality code that is changing the world. And how can we put those practices within our own development teams on what we're building for our customers? So you're just going to continue to see this. And I think also with that being said because the barrier of entry has has lowered some by the advancement. What we're seeing the rise of the citizen developer as well. So we're seeing you know people all within the company and some that are much more further along with their transformations participate in a way they never have before. Whether it's like you know the design part in the design thinking of it to like how do you curate and have a great experience for your customers. We're just seeing participation at all levels of development stack and that also is the stuff outside of the actual code being written because it's so interconnected and so I I don't know I'm excited. I'm excited to see what we're going to unlock by having people participate more so than ever and then having companies invest in that participation. >>I love your enthusiasm. I agree. I think it's a great time for open source because it has democratized, it is bringing in new people. The aperture of the personas coming in >>is not >>just computer science and engineering. This hybrid SRE rolls developing and then you've got creative. There's a creativity aspect coming back and I've been riffing on this for a few years but I'm kind of seeing this development, love to get your thoughts used to be like craftsmanship was involved in building software and then Agile came in ship fast and iterate. Um and now craft is coming back. You're starting to see creativity and the developer experience through collaboration tools and kind of this democratization. What's your thoughts on this? And no, I know you I know you think about this as an engineering leader. Um Craft agile bring them both together. Speed and quality is craft coming back. >>Craft is definitely coming back and I think it is because we we melt the mundane stuff, right? Like, you know, we're all hyper focused on like you want to be the bush out there, you gotta ship immediately agile, agile, agile. But what we know is like you can ship a bunch of stuff, nobody wants very fast, you can ship a bunch of stuff that hasn't been curated to really, you know, solve the problem now, you'll be fast but will be awesome. I think people demand more. And I really believe that because we've embraced some of these frameworks, workflows and tool sets, that we get a focus on the craft and that's what we're trying to do, right? Ultimately we want every person that builds to be an innovator and not just an innovator for innovation state, but because they're changing and affecting somebody's life, right? And so when we dig deep and focusing on the craft, and we still have these expertise, we're just gonna be applying that in a very intentional way versus okay, hurry up. Bill, Bill Bill, hurry up, hurry up. Bill Bill, Bill, go, go, go, because now it's connected. And so we're seeing the rise of that craft and what I think is going to in turn happen is we're all going to have a better experience, we're all going to reap the benefits of having that expertise. You know, there's a spirit sometimes when we talk about automation and devops and, you know, interconnected tool systems that maybe you're taking somebody's job that they were doing before the daily task. No way. All we're doing is saying like, cool, take the repeatable thing that you're doing over and over and over, and let's focus on that craft, lets you know if your security person and you want to get down and deep and understand where vulnerabilities are going to come from and things that people haven't even thought of. Cool, let's take away some of the other things that we know can be caught and solved without you paying attention in some aspects. I think we just need along the whole stack. So it's pretty exciting times. >>Yeah, I did it and we call that different, undifferentiated heavy lifting, you know, just get it out of the way since you brought that up. Let's take automation down that road of experience. What does it mean for the developer? Because this is really an opportunity. Right. So the phrase I've heard is if you do it more than a few times, just automated away. So when is the right time to automate where this automation play into the developer experience? When does it make it more productive? Where's the innovation angle you share your thoughts on when people look through the prism of automation productivity versus innovation? What's the what's the automation view there? >>I mean, you know it is it is a good like, you know, little metric could be done it five times and it's the same thing over and over and over. Your question is now like do you have to be doing that? I mean you should because you're doing it. So I think it's about finding and defining your own boundary for what you need, right? I mean it's hard to get out there and say every workflow like we can go and apply the stamp. We already tried that with agile frameworks for like everybody you're gonna do scrum, we're going to combine, you know what? It doesn't work. What we really need to do is have teams understand their workflows, right, understand and do some diagnosis and saying like we're in the system and I think that's powerful metrics and insights of going like where are we having a slowdown? Where are people spending their time if people are spending their time doing break fix or they're spending their time continuously trying to jam something into a certain pipeline, you have to ask yourself, is this something that we should be spending that time on? What if we had that time freed up? And so I do think you can go and put some good boundaries in there, whatever yours may be. I love I love some of those rule sets but really you know, deadlocks and automation starts with the process, right? We think about it and when I developed software always think about it through that design. Thinking lands of how will this work when I get to it. And so if we're focusing on the design aspect and the user experience, then we start looking at the pieces in between from that code to having people use it and say what do I need to do? And sometimes you know depending on your industry, you may have these other needs that not everybody has. So it's hard to say there's a one size fits all. But there is a good rule like if you've done the same repeatable thing over every every day, uh numerous days like you probably should just go spend the time to automate that. And I think it's the convincing point, right? Like if we go and and a lot of us are are nerds and engineers at heart and I love freaking math. So it's that like okay if we spend two hours building maybe a hub action for a doctor one time instead of somebody happened to repeat this process no matter what it is. Like you're giving that time back in that time is mental capacity, mental capacity that can be applied to something that's more important and hopefully the more important thing is the user experience. Um So yeah, I mean you know we all have those little systems out there. I say use them but take a step back. I think the bigger, the harder part is like yes, you will have to slow down for a minute, which is scary to go and build something repeatable so that you can speed back up. You know, >>it's awesome. Great, great inside love, love the energy a lot to ask you while you're here because this is something I've been thinking about. I'm hearing a lot of developers talking about, understand the workflow you mentioned that's a key thing. I love that. Getting in and understanding the customer experience working backwards, but that brings up the whole. How do you form the teams? How do you think about team formation? Because at cloud scale with cloud native, you can use building blocks, You have automation, you can easily compose and then build intellectual property around things. Use containers, make things easier. So as you start thinking about teams, is it better to have teams focus on, say workflows and then decoupled teams? Is there a strategy for general purpose teams or how do you look at the team formation from the developer perspective to make the experience great, high quality. Is there a state of the art in your opinion, given the compose ability and all the ease of use going on? I mean, what's the ideal way to think this through? What's your thoughts? >>Oh, you know, there's, I'm going to say there's not one team team to rule them all, there's not one team kind of foundation that's gonna be able to be applicable, it's all different, right? Like even within the same company, especially at scale, you may have these different compositions of your team and I think it comes down to like, what problems are you trying to solve within your workflow? What are you trying to accomplish? I think when we, when we step back and we think about our Ci cd pipelines and really code from idea into cloud that I believe in a unified system, because I don't want developers worrying about it and doing one offs, I'm like, you don't need to know that, and that's been an argument that's going on, you know, I'm a huge kubernetes fan and so it's been like, should, should, should the feature developers understand the entrance of kubernetes? I'm gonna say something controversial, I'm gonna say no, I'm gonna say they don't need to know, they need to know how to monitor alert and how to have smart rollbacks and have a system that does it for them. That's why we have Orchestration, that's why we have dr containers, that's why we have world class eight PM and monitoring systems in place because we've done that, we've done that hard work. So I would say no, they don't need to know that, so, but you still need these needs, right? Depending upon where you are in this transformation, right? Maybe you're still like, you know, integrating some of these cloud needed principles and toolsets and so you need some smes I do really love the SRE embedded model, not embedded, like on your, you know, like embedded, like a chip set, but embedded in the team, because that person really should be a mentor and should be a force multiplier. You don't want to fall in the trap and be like oh we have an SRE on the team. They're going to do all the devops stuff. No no no no they're going to go and help you think about your product through a customer lens right there. They're the experts going like whoa maybe we should have an S. L. A. Because this is a tier one feature lets go and make sure we build that automation so that we curate this feature with the highest level availability but then teach the team how to do that. So now you have this practice as a part right? Like you're honing your craft, you have this practice now. Does that mean they need to go learn everything about like the monitoring sweet and tools are used. No, but they should understand how to read the output of that. And so there's not one team size to rule them all. Unfortunately, I personally, I'll tell you what I'm a fan of is like I think that you should have flexibility. Like once again think about the points where you need to have the connective unified system, right? And then you have this opportunity for developers to have some agency and creative freedom because maybe you've been on a team that's been working on, I don't know, let's say your audit service. I think every every software has some component of audit uh, you know, in some ability because you want to know what he was using one well after they've done their tour of duty because most of the cool stuff, they've already fixed and made a feature set. Let them go roll into something else because then you have that connective tissue on the inner points of your system that are always the same, right? We want really repeatability. We want them just to focus on writing the code. And I think because of these advancements we are unlocking opportunity for developers to think broader, right? Like maybe you've been on the platform team and you want to go dip your toes into writing features well, 90 okay, maybe not 90 but also 80% of that, you know, every day repeatable task, like focus on that and get that shit out. But then you have the sme and you're really thinking holistically as a customer obsessed team of what you're building and why. So I love that. No one way. >>Yeah, I love the idea of the platform person just having more flex out because that brings a platform mindset to the other pieces, but also feature acceleration versus product strategy. Thinking through the arc of why you're building in the first place, Right? So and then the embedded SRE great point there, great call out there because everything's cloud scale now, you gotta have pen tests built in automation, >>who's gonna >>design that. So I think it's really interesting how you're putting that together and I think that's very relevant. Um and any um new things that you see happening now with with cloud Native, you mentioned cabernets, I think you know the story that we've been telling is kubernetes got boring and that's good. Right? So, >>meaning its meaning it's working >>and people like it, it's interoperability or frustration. It feels like a unifying connective tissue between under the hood and above at the application layer. So it's nice but the consequence of that is there's more cloud native going on, so that means more services are going to be connected and torn down. You mentioned observe ability and monitoring. That's important too. So as an engineering leader, that's not another department. Right? That's gonna be core to the developers. What's your thoughts on how to integrate observe ability now there's a zillion companies doing it now but is that you know >>there is a zillion. My thoughts are like heck yeah. Like conservative observe ability isn't at the end of the stack. Right, observe ability is apart just like qualities apart. Just like when we think about agile, let me just throw it this way right? Like when dr came right, we had it basically have this maybe this baby os encompassed on servers. So you can have multiple, multiple, multiple, multiple distributed. Right? I think of like let's let's say that like your team is that Docker container man, you want everything in their right? It is a part of the practice. You want your learning, you want your logging, you want it all wrapped up in this nice little bow and you want lots of them all working together harmoniously. The same thing can be said about our teams. We want them to be their own little micro operating system where they have all the resources available for them to go and do the thing that they are intending to do and not have to worry about that subset. But it also gives them that control. Right? So it's building in that layer of abstraction that's needed but also understanding why it's important. So it's a little bit of both. Right? We're not going to curate deep subject matter experts. You know, I'm, you know the Oh yes, I model and every aspect right? Like we're not going to turn a friend and engineer necessarily into a network engineer. But utilizing the tool sets, having a playbook where it is controlled, maintained in a part of your culture. All that's gonna do is allow you to move faster and it's allow you to see what's really running out there in the wild. And I see these trends happening. I think we're continuing to see the rise of cloud native technologies because applications now are really a set of a P. I. S. That go across the world and in and out. And so the way that we develop is slightly different. And so we need to think about, well, how is it orchestrated and deployed? Well, if you have a repeatable pattern once again, if we go back to that and think of our team and I promise nobody asked me to come up with this as like a little darker, a little docker container itself. You know, you're gonna write that image into what makes sense for you and have all the resources available and you're gonna rinse and repeat that over and over and over again. And so I mean, we're just seeing, seeing this continue this continuation of, you know, monitoring devops? S sorry, it's not a problem. It's a culture, right? It's not one person's job or a role. It's a part of how you build great software. It's just a practice. >>You mentioned abstraction layer used to be conventional wisdom that they were good. But there's trade offs whose performance tradeoffs or some overhead. Not anymore. It's good. You can basically build an abstraction layer and say, hey, I don't want to deal with networking anymore. It's gonna make it programmable. >>That's cool. No >>problem. So you start to see these new innovation patterns. Right. So what are you most excited about when you start to see these new kinds of things of being brought on that were limited years ago? Like you start an abstraction layers, you see the role of the SRE you're seeing um the democratization of new developers coming in that are bringing new perspectives. She's seeing all these new kinds of ways that's re factoring how people write code. But what are you seeing is the most exciting >>for me? Honestly, it's like the opportunity for anybody to really be a builder maker developer, right? You don't have to have a traditional CS degree if you do that's awesome, Like come and teach us awesome stuff that we probably should know. That's foundational. I don't have a CS degree. You know, we're moving on from these opportunities where it's self taught to where you actually 100% can go and learn and build and create. We're seeing the rise in these communities. I feel like these toolsets are really just lowering the barrier of entry for those people that don't have advantage to go to like a four year school and get a degree for people that are just like have a great idea what excites me is that next developer, You know, we talk about the 100 million developer sitting somewhere in the world, just going, I have a great idea and I'm gonna change the world and I don't know how to get started, but they do, they have it at their hands now. You know, if you can go onto a website, get a little bit dangerous with these tool sets, you can go and get your idea to the masses and what we're going to end up doing is like you said, democratizing tech, it's going to bring in new ways to think it's going to change how we interact with systems. We get we get our blinders on sometimes, especially, you know, I live in Portland on the West Coast, the US, we know that the world is vast, majorly huge, dynamic, awesome place. The things that work for me may not work for somebody on the other side of the world. The things that I do may not be relevant. But we're going to find that human connection. We're going to continue to say, well, wait a minute. How can we optimize for any human anywhere? How can we help take all these differences but doing them in a repeatable pattern. So like for me that's exciting is these toolsets that we've been working on for years, are now going to put put in people's hands that never thought they could. And that is exciting. And like to see to see the rise of just creativity is what really makes humans special because we build and make >>and the fact that it's more inclusive now becoming more inclusive on all aspects of inclusive whether it's individuals and coders types of code. So uh integration is the new normal right integrating in uh data control planes, all that goodness coming in because of the ease of use of developer experience. Super awesome. Um dana you're awesome. Great to have you on the cube and sharing your energy and insight. Great call outs on many topics. A lot of gems being dropped. Their thanks for coming on the cube. >>Well thanks for having me. It's been awesome and doctor comes been great. I can't wait to see the rest of the show. >>Dr khan 2021 Virtual real life coming back maybe in physical next year or hybrid for sure. Just the cube coverage of Dr khan 2021. I'm sean for your host. Thanks for watching

>> Live from Atlanta, Georgia, It's theCUBE covering Citrix Synergy Atlanta 2019. Brought to you by Citrix. >> Hey, welcome back to theCUBE's coverage day two of our coverage of Citrix Synergy 2019. Lisa Martin with my cohost Keith Townsend, and we've got another CUBE alumni joining us, Dana Gardner, President and Principle Analyst at Interarbor Solutions. >> Sorry, my language skills are declining on day two. >> It's been a long day. >> It has been a long day. We've had, speaking of, had a lot of great conversations with Citrix Execs, customers, analysts over the last day and a half. People are very excited about what Citrix is doing with intelligence, experience, and really helping businesses to transform their workforces. But you have been following Citrix for a long time. >> Yes. >> So, talk to us about some of the early days back in the 90's. I'd love to get your perspectives on what you saw back then and what your thoughts are about some of the things that they're announcing at this event. >> Sure, well back in 1995-1996, the internet was still the new kid on the block, and browsers were kind of cool but, how would they ever help a business? And then, along comes this company that says, "Oh, we're not going to deliver things through a browser, we're going to deliver the whole app experience, apps that you're familiar with, your Windows-based apps over the wire. Over the internet protocol." Wow, so I remember at Internet Expo in New York at the Javits Center, Ed Iacobucci, The co-founder of Citrix got up there and explained how, yeah, we're going to deliver apps. And basically what they were describing is cloud computing as we know it today. Wow, it was very interesting, but we all kind of look at him like he was a little crazy. (host laughing) Yes. >> And, that's been a long time, man. Citrix has made a name for itself since then. You know, the day I was talking to David Hansel, yesterday and I said, "You know what, Citrix is a verb. I'm going to Citrix in an application. They established something for themselves." And, ironically, on stage yesterday he said, "85 percent of the IT budget goes to keeping the lights on." And I would firmly, as pre-kenote yesterday I'd say, you know what Citrix is firmly in that 85 percent of, they are rock, fast, hard technology partner, but they're in that 85 percent. But this intelligent experience I think kind of pushes them into that 15 percent of innovation. What did you think about yesterday's announcement? >> Well, based on my memory from 1996, I think it's consistent. That they're looking for something that's two or three years, maybe more out that will mature then. But they're not afraid of tackling it now. They had some really strong established businesses, but they're not resting on their laurels. They're looking at, I think a problem that almost everybody can identify with. In the past, their problems were people they could identify with in IT. The end user wasn't aware that anybody was Citrixing behind the scenes. Now, they're identifying issues that people have with work. The fact they were taking apps and services from multiple clouds, multiple data centers some of them our own company, some of our partners, some across an ecosystem or a supply chain, and it's becoming rather crowded. Disenfranchised. Fragmented. And people, I think are struggling to keep up with that amount of diversity. So, we're dealing with, yet again a heterogeneity problem, a reoccurring problem in technology. And Citrix is identifying with something that's a higher elevation than they had in the past. So, they're not addressing just IT although, that's where the actions going to take place to solve some of these problems. But they're focused on just about all of us. Whether we're working in a small, two or three person mom and pop shop or a 30,000 seat enterprise. >> And they've also done this pivot in the last, what we've heard in the last 24 hours, of really being positioned to the general user. Something that I didn't know until yesterday was that the majority of enterprise software has been designed for power users, which is one percent of the users. And so, they've really made that positioning pivot yesterday to, this is for the Marketing Managers, somebody in supply chain who has a day that is bombarded with seven to ten apps. They're losing hours and hours of productivity a week. You can look at that in terms of the amount of dollars that's being spent or wasted. But really making this, bringing those tasks to the user, those actions to the user. Rather than forcing the users to go out to all the different apps, put those pieces together. Oh, and then trying to get back to our actual day-to-day function. >> Right, we wouldn't have to talk about user experience if these things had been designed properly in the first place. It's a bit myopic on behalf of the IT power designer, that they often craft the product for themselves. That, this is still the dark arts behind the curtain thinking. It's very difficult for a highly efficient, productive IT group to create something for a non-IT audience. And I don't blame them, but it has to happen. It's going to happen one way or the other. So, we've seen companies that have taken extraordinary steps on usability, Apple computer is probably the poster child for this. Look at where it got them. There were lots of mobile phones around ten years ago, before the iPhone. Why did the iPhone become so popular, so dominant? Because of the usability. So, Citrix is I think, perhaps doing IT a favor by getting out in front of this. But still, if we're going to get IT in the hands of all people for productivity, what I look to is a fit-for-purpose mentality. No more, no less. You can't design it as if it's your own baby and your own special design, I don't know, once in a lifetime opportunity to strut your stuff. It has to be fit-for-purpose and it can't just be monolithic, where we're looking at little bits and pieces. So, the software's recent acquisition that Citrix made is going to be able to start picking out productivity units, for lack of a better term, from different applications, assimilate those in an environment, the workspace, where the productivity, the work flow, the goal of accomplishing business outcomes comes first and foremost. >> So Dana, let's talk a little bit about, you know the next level. Because it's broken. Even when you look at modern applications, one of the applications they showed on stage yesterday, was a cloud application. Salesforce. I mean, we know a people who make a good deal of money simplifying Salesforce, which is a born in the cloud application. This isn't just about cloud versus legacy, this is about end-user experiences, and end-users using applications in a way that makes them productive. One of the things that caught me as soon as Citrix said that they want to be the future of work, I tweeted out, "Well, you can't be the future of work unless you start to automate processes," and boom, intelligent experience. And the first thing that came to my mind was when we attended an event a couple weeks ago for RPA, Robotic Process Automation tool, that was very user-centric, but used the term "bots". Robots, sulfer robots that did the job. Citrix only used the term, "bots" once yesterday. What's your sense, is this a competitive solution to those partners? Or is this more of a complementary solution? >> I think Citrix is correctly trying to keep the horse in front of the cart and not the other way around. We have to look at work as flows of productivity first, and not conforming to the app second. But to get out in front and say, "Oh, it's all going to be animated and the robot will tell you what to do," I think does a disservice. So, let's take first things first. But let's not also lose track of the fact that by elevating work to a process and not just being locked into one platform, one cloud, one set of microservices on one framework, that we have the opportunity to integrate in analytics along the whole path. From beginning to end. And that we can even have the context of what you're doing feed back into how the analytics come at you. And reinforce one another. So, we need to get the process stuff set first. we need to recognize that people need to rethink getting off a desktop, getting out of email, looking at the full process. Looking at working across organizational boundaries. So, extra enterprise, supply-chain interactions, contingent workforce. Then, bring in analytics. So, first things first but it's going to be a very interesting mash-up when we can elevate process, get out of sort of silos, manage that heterogeneity and inject intelligence and context along the way. That changes the game. >> So, you've seen the workforce dramatically transform throughout your career. There are five generations of people in the workforce today. Madeleine Albright, there she was on stage this morning, 82 years old. I thought that was, what an inspiration? But companies have different generations, different experiences, different experiences with technology, differing expectations. What, in your opinion, did you hear yesterday from Citrix that is going to help businesses enable five different generations to be as productive as they want to be. >> Right, it's an extension of what Citrix has been doing for decades, and it's allowing more flexibility into where you are is accommodated. What device you're using can be accommodated. The fact that you want to be outside your home office but secure can be accommodated. So, what I heard was instead of locking in an application mentality, where everybody has to learn to use the same app, we need to have flexibility. And it's not just ages and generations. It's geographics, it's language, it's culture. People do business and they do work differently around the world. And they should be very well entitled to continue to do that. So, we need to create the systems that adjust to the people and read the people's work habits. And then reinforce them rather than force them into, let's say a monolithic ERP type of affair. And we've know that a large percentage of ERP projects over the years have failed. And it's not that the technology doesn't work, it's that sometimes, you can put a round peg in a square hole. >> Wow, speaking of round peg, square hole, IT, you know, they're preaching to the choir I think on this piece. You know, we want thing to be simpler. We want to get engaged. We want to solve this problem. But, is Citrix talking to the wrong audience when it comes to process automation? To your point, you have to have the large view of it, and a lot of timeS, especially folks at this conference, may not have the large view. How does Citrix get to the CMO's the COO's, the process people versus the technology folks. >> I think that's a significant challenge. Keith and I recorded a podcast with David Henchel earlier today and it'll be out in a few weeks on Briefings Direct, and I asked him that, I said, "You're well-known in the IT department. They use a verb, they're Citrixing. The end user, not so much. But if you're going to impact work as you intend to and as you've laid out here at Synergy, you do need to become more of a household word, and you need to brand and you need to impact." And we know one of the hardest things to do is to get people to change their behavior. You don't do that behind the scenes. In some ways, Citrix has been very modest. They haven't been the Citrix inside, they haven't branded and gone to market with. They've usually let their partners like Microsoft and now even Google Cloud be on the front page, even as they're behind the scenes. But I think they need to think a little bit differently. If they're going to impact people, people need to understand the value that Citrix is bringing. But identifying themselves as they have at this show with work and productivity issues, usability and intelligence will start that process. But I do think they can go further on their go-to-market and not just bring this message to their sales accounts, but to a larger work productivity, human capital management enterprise architect type of base. >> And they are making those impacts. Keith and I today have already spoken with their three innovation award nominees. There were over a thousand nominations. And we spoke with Schroders, which is a wealth management company based out of the UK and how they have been able, a 200 year old company, to really transform their culture with Citrix's workspace was, it was done so strategically, so methodically. But how they enabled that and a seamless integration in terms of their customer experience and engagement with their wealth managers was really compelling. Not only are they able to retain their probably longstanding wealth management clients, but they have the ability now, and the technology capabilities to allow their people to work remote three days a week if they want to or from wherever, and actually work on getting new clients. So, the business impact is really clear. We also spoke with Indiana University. They have gone from just enabling the students on the seven campuses to 130,000 plus across campuses online. They're enabling sight impaired people to also, by virtualization, have access to computer technology. So, you're talking about going from tens of thousands to a ten X at a minimum multiplier, and enabling professors to have conversations and hold classes with people in Budapest. Big impact. >> So Lisa, you're bringing up the point that user experience isn't just employing experience, it's end user and-- >> Absolutely >> Consumer experience. If you're going to do this and do it right, don't consider it just for your employees. It's for reaching out to the very edge of the markets, and that includes consumers and students and mom and pop shops and everything in-between. So when you do this right, and not only will you be delivering intelligence and context to your employees, you'll be able to start to better serve your customers. And that's what digital transformation is really about. >> It is, and the cultural transformation that Citrix is undergoing and that they're enabling their businesses to achieve, like the two we just talked about, are critical catalysts for digital transformation. But to me, employee experience and customer experiences are hand in hand because every employee, whatever function you're in, in some way you're a touchpoint to the customer. If you're in retail, you're presenting a shop-able moment as often as you can. But you also are dealing with customers who have choice to turn and go to another provider of that product or service. So, having those employees not only be satisfied, but have the tools that they need and the intelligence to deliver the content. >> So, I'd be happy to go to a brick and mortor shop. I'll walk in there physically if they can help me in the shopping experience be smarter, but if I can do it online in my bedroom on my browser, then I'll do it there. So it's no so much the interface or even the place anymore, it's who's going to give me the information to make the right decision and make me feel confident that I'm spending my money the most productively. Whether I'm a consumer or a business. So B-to-B. That's what's going to be the killer app, is the smart decision making, and the experience of bringing the right information, right place, right time. That's key. And that's what Citrix has repositioned itself for. I think it's really quite a dramatic shift for the company but they've done it before. >> Well, Dana it's been great having you back on theCUBE unpacking this. It's been an exciting day and a half for us and we look forward to having you back on theCUBE sometime soon. >> My pleasure. >> For Keith Townsend, I'm Lisa Martin. You're watching theCUBE Live from Citrix Synergy 2019. Thanks for watching.

>> Announcer: Live from San Francisco, it's theCUBE. Covering Google Cloud Next '19. Brought to you by Google Cloud and its ecosystem partners. >> Hey welcome back everyone. It's theCUBE's live coverage here in San Francisco in Moscone South. We're on the ground floor here at Google Next, Google's Cloud conference. I'm chatting with Stu Miniman; Dave Vellante's also hosting. He's out there getting stories. Our next two guests: Dana Berg, Chief Operating Officer of SADA and Chris Lehman, Head of Engineering for SADA. Guys, welcome to theCUBE. Thanks for joining us. We're here on the ground floor. >> Thank you. >> Thank you. >> This is exciting. I feel like a movie star right here. >> It's game day here. All the tech athletes are out, Dave. If you look at the show, look at the demographics, hardcore developers, lot of IT, leaders also here, cloud architects, a lot of people trying to figure it out. We heard the keynote. Google is bringing a lot to the table. So what's new with you guys? You guys recently sold your Microsoft business, going all-in on Google. Talk about that relationship. >> We are. This is a brand new day for SADA. The energy around this place, where we are in the market, and where we are with the expanded attendance here has actually reaffirmed our business strategy to go all-in with Google. I don't know if you are aware but SADA has been around for almost 20 years. Historically have always been leaders in bringing people to the cloud even before there was really much of a cloud. We were a you know a pilot partner within Microsoft and Google and had a great thriving Microsoft business but an even bigger Google business and you know, we looked at the tea leaves, we looked at where we wanted to be, and aligned with a company that shared our mission and values and it was a clear choice. We chose Google. We made a very specific and deliberate act to sell off our Microsoft business so that we could take the horsepower of all of our engineering staff and apply them to Google. >> It's interesting you know, we've been around for 10 years doing theCUBE, go to a lot of events, I mean Dave Vellante, Stu, and I have been around for 30 years covering the IT, you guys 20 years. You guys have seen many ways of innovation come and go. Now you're going all in on Google. What is it about this wave right now that made that decision? What do you guys see? You're seeing something early here. Expand on that. Give us some color commentary because there's a wave here, right? A lot of people try. It's a combination of things. I mean, we saw the client-server thing. We saw that movement. Also the internet, we saw the web, mobile, now it's cloud. What's the big wave? What are you guys riding? >> I think there's a couple of things and I think it's unique to, philosophically, how we think of our real special relationship with Google. There is a momentum, right, and not to quote like a Bernie Sanders, but, seems like there's a revolution going on here, right, and, you know, I think, you know, what we see when we look around and we hear conversations and even with our customers, the way that we're all winning together is because we're winning the hearts and minds of the people inside of our customer base that are actually the ones responsible for inventing and the ones responsible for building, so when we're in board rooms and we're selling and along with Google, we're talking with developers, we're talking with designers, we're talking about people that are actually driving the vision for these business applications. We're not always talking to the CIO down like some of our other competitors seems to have only been able to sell that way. We're talking about the people responsible for not only constructing it but maintaining it. So that revolution is there. These folks are bubbling that up and they're seeing the real value inside of Google and what is that value from our point of view, and why did we make such a bold statement just to stick with Google is, and we saw Thomas today echo this, I think there's very few cloud providers that are bold enough to actually lead with the fact that we want our customers to have full choice whether you're using GCP or not. We want to build, architect, and manufacture a product offering that allows you to keep your stuff in your data centers, move your stuff to AWS. That power of choice is really not like what we've never heard anywhere else. >> And then on top of that, too, you got an application renaissance, right? A whole new way of coding, infrastructure that's programmable and going away, I mean if you think about what that does to the existing infrastructures, they can now mix and match and rearchitect everything from scratch and accelerate the app movement. >> Well, that's absolutely true, and a lot of that has to do with the fact that there are managed services in the cloud which makes it dramatically easier to build applications of course, so there's no question about that. Some of the offerings on GCP are particularly attractive for our clients, particularly the managed Kubernetes service. That's where we're seeing perhaps most of the interest that we're seeing, like that's a very common theme. Also the ML stack is an area that our customers are very interested in. >> Chris, can you bring us in some of those customer environments, you know, one of the things you hear, you know, most customers, it's, "I've got my application portfolio." Modernizing that is pretty challenging. There are some things that are kind of easy, some things that take a lot more work, but, you know, migration is one of those things that makes most people that have been in IT a while cringe because there's always the devil in the details and something goes wrong once you've got 95 percent done. What are you seeing, what's working, what's not working, how's the role of data changing, and all of that? >> I think migrations are usually more complex than they at first appear and so even with best intentions thinking that customers can just move their workloads seamlessly to the cloud have actually in practice been more challenging. So some of the areas that we find challenges are around data migration, especially in the context of zero downtime. That's always more difficult than with applications. So that's definitely an area that were we're spending a lot of time working with our customers to deliver. >> Just to add to that, I have to keep reminding myself of the name, but obviously the Anthos announcement today sounds incredibly intriguing as a lower barrier of effort to actually migrate. Our customers have been trying to really absorb and take a hold of Kubernetes and can it containerize methods for a long time. Some are having a harder time doing it than others. I think Anthos promises to make that endeavor much, much easier, and I think about as we leave here this week and we go back and we reeducate our own engineering teams as well as our customers, I think we might see some highly accelerated project timelines go from here down to here. >> And the demo that Jennifer Lynn did was pretty impressive. I mean, running inside of containers, whether it's VMs, and then having service patches on the horizon coming to the table is going to change the implementation delivery piece too in a massive way. I mean, you've got-- >> Oh, absolutely. >> Code, build, run on the cloud side, but this this kind of changes the equation on your end. Can you guys share the insight into that equation, because Google's clearly posturing to be partner friendly. You guys are a big partner now. You're going all-in. This is an interesting dynamic because you can focus on solving customers' problems. All this heavy lifting kind of goes away. Talk about the impact to you as a partner when you look at Anthem, Anthem migrate in particular, some of these migration challenges with containers and Kubernetes seems like it's a perfect storm right now to kind of jump in and do more, faster. >> Yeah. >> Well, it's certainly very interesting. Well, we'll want to take a really hard look at it. I mean, a very, very cool announcement. Moving to containers in the source prior to the migration obviously solves a lot of challenges so for that reason, it's definitely a move forward. >> And I think... You know, we always talk about, in this industry, the acceleration for consumption, but really that's a poor way of saying... Probably what we should be saying is an acceleration of value. So we're constantly in this battle to try and deliver value to our customers faster. That's what our customers want, right, and in essence we see Anthos as being potentially a big game-changer there so that, you know, our CIOs that we're talking with can show to their various stakeholders that they are making very good proactive moves into the cloud at lower-caught barriers of entry, right? >> Yeah. So, you brought up the the ML piece of Google. Wondering if you could help share a little bit on that. When I think back two years ago, you know, data was really at the core of what a lot of what Google was talking about. I was actually surprised not to hear a lot of it on the main stage this morning, but you know, AI, ML, what are you doing, what are your customers doing, does Google have leadership in the space? >> Google certainly has leadership in the space. Our customers, I think, relatively universally, think that their ML stack is the strongest among the competitors, but I think in practice what we're finding is there's a lot more urgency as far as just literal data migrations off of their data centers into the cloud, and I foresee a lot more AI and ML work as more move in. >> John: Yeah. >> So you might, in our booth here, not to give a plug, but we've got a booth down at the end with a full-fledged racing car, just to talk about the art of the possible with AI and ML. Our engineering teams in the race teams that we sponsor, they're there, the driver's there, you should go down and talk to 'em. We've taken all the race telemetry data for the last six months and all of his races and practices, we've aggregated that data all into GCP, run AI and ML algorithms on it to provide his racing team some very predictive ways that he can get better and that team can get better, and so I'd invite just anybody that wants to go there and take a look at, even if you're in banking, or if you're in retail, or if you're in health care, take a look at some of how that was done, because it's a very, very powerful way, to answer your question, head and shoulders down why Google is actually accelerating and exceeding in AI. >> And one of the things that Thomas Kurian showed onstage was the recent Hack-a-Thon they had with the college students with the NCAA data of the game that just finished, and throughout that experience, this is a core theme of GCP, and now Anthos, which is getting data in and using it easily, and scaling at a scale level that seems unprecedented. So this team seems to be the application... The new differentiator. >> I think it is. I think that announcement, obviously the big three takeaways for us, certainly, scale, unmatched. Certainly speed and migration with Anthos. If I could highlight one other, I was incredibly pleased with, well I've been pleased since Thomas' arrival in general by bringing an enterprise class strategy within sight of Google that I think are going to respond well to our enterprise customers, and part of enterprise class is also making sure that their partner community has amazing enhancement programs that really incentivize those partners that are actually in the full managed services space from cradle to grave, lifetime customer value. So we're very excited about even further announcements this week that no doubt have been inspired by Thomas to try and really take advantage of their partner community that are in the business of cradle to grave support of customers. >> You feel comfortable with Thomas. He's taught a lot of customers, he knows the enterprise. >> We've had an opportunity to meet with him. We've had some shared customers that have had a great privilege of getting to know him and support us and collectively them. >> John: He knows the partner equation pretty well, and the enterprise. >> Without a doubt. >> It's about partnering, because there's a monetization, the shared go to markets together. Talk about the importance of that and what's it like to be a partner. >> Yeah, without a doubt, again, you know, his embrace of the open-source community that you saw today, really taking advantage of highlighting partner value is wonderful, but I think Thomas, above anything else, knows that Google needs to scale. They need to scale, and then they have to have breadth and they have to have depth, and, you know, to get to where Google needs to be over the course of the next two, three years, it's wonderful, it's refreshing, it's 100% accurate that Google knows and Thomas knows that the path to do that is via partners; partners that share in Google's vision, that are 100% aligned to the same things that Google is aligned with, and I think that's why I'm so thankful to be at SADA, large in part, because all of the things that we care about in terms of our customer success as well as Google's success, we all share that, so it's a great trifecta. >> It's a ground-floor opportunity. Congratulations. Guys, talk about your business. What's going on? You've got some new offices I heard you opened up. What's going on in the state of the business? Obviously the Google focus you're excited about obviously. >> Yeah, yeah, yeah. >> There, at the beginning, I called Google the dark horse. I think with the tech that they have and the renewed focus on the enterprise, building on what Diane Greene had put foundationally, Thomas is meeting with hundreds of customers. He's so busy he doesn't have time to come on theCUBE, but he'll come on soon, but he's focused. This is now a great opportunity. Talk about your business. What's the state of the union there? Give an update. >> I can take that one if you don't mind. >> Go ahead. >> You can add poetic color if you want. (laughing) Yeah, so as I said, we're entering a new journey for SADA in light of renewed focus, renewed conviction to Google. We are investing more than we ever have into the common belief that Google is the one to beat in terms of momentum, drive, and ultimately winning the hearts and the minds of who we've talked about. So, over the last four months, we've opened five new offices in New York, Austin, Chicago, Denver. Our headquarters is in Los Angeles, and just recently, we just opened a brand new office in Toronto, so we can really help our Canadian customers really see the the same type of white-glove treatment we provide those customers in the States and so that's why, well, I wasn't earlier, but I'm walking around with a Canadian flag. We're very excited about the presence that we're going to have in Canada >> Its "Toronno." I always blow and I call it "Toron-to," being the American that I am. It's "Toronno." >> Dana: Glad you said it right. Good. >> Now, on the engineering side, so you guys are on the front lines as also a sales, development, there's also customer relationship, engineering side, so I'm sure you guys are hiring. There's some hard problems to solve out there. Can you guys share some color commentary on the type of solutions you guys are doing? What's the heavy? What solutions are you solving, problems that you're solving for customers, what are the key things that you got going on? >> Yeah. >> Well, a lot of cloud migrations, a lot of web and application development, custom development, and data pipelines. I'd say those are really the three key focus areas that we're working on at the moment. >> One other thing, too: so... we believe that we want 100% customer retention, always, and that goes above and beyond an implementation. So the other big area of investments that we're making is in a whole revamped technical account management team, so for those of our GCP customers that have had the privilege, we've had the privilege of working with and for, we are building out a team of individuals that will, well beyond the project, stay with that customer, work with them weekly, monthly, quarterly, and try to always find ways to expand and move workloads into the cloud. We think that provides stickiness. We think that provides ultimate value to try and help our customers identify where else they can take full advantage of the cloud, and it's a fairly new program, and large in part I just want to thank Thomas and the partner team for new programs that are coming out to help us so that we can actually reinvest in things that go you know throughout the lifecycle of the customer. So, very, very good stuff. >> Dana, Chris, thanks for coming on. Appreciate it. We'll check out your booth, the car's there, with the data. Bring that data exhaust to the table, pun intended. >> Yes. >> Analyzing with Google Cloud, Anthos. Good commentary. Thanks for sharing. >> Really appreciate being on board. Thanks for having us. >> Alright, great. CUBE coverage here live on the floor in San Francisco. Google Next 2019. This is Google's cloud conference. Customers are here. A lot of developers. More action, live on the day one of three days of coverage after this short break. Stay with us. (theCUBE Theme)

>> [Announcer] Live from Los Angeles, it's The Cube, covering E3 2018. Brought to you by Silicon Angle Media. >> Hey, welcome back here, we're ready, Jeff Frick here with the Cube. We're at the Los Angeles Convention Center at E3, it's amazing. It's like 68,000 people. They're in every single hall, they're out in the streets, they're in the hotels, they're at LA Live, they're all over the place, for really the biggest gaming conference I think in the world, and we're excited to have our next guest, he's Dana Jan, he's a design director for Ready at Dawn, and you just introduced a new game, right? Great to see ya. >> Thank you very much for having me. Yes, that's true. We just announced Echo Combat last year in October, and today we're showing off on the floor. >> Private beta still or are you going to public beta you said soon? >> Yeah, we just had a closed beta actually. We're moving into open beta, and that's gonna be June 21st. >> Right, pretty amazing though, you guys have not been around that long, and this is already your third game. >> Well, the studio's been around for a while, so we've been making games for a long time. This is actually kind of a new foray for us though going into VR. We released a game called Lone Echo last year, and Echo Arena was a multi-player mode that we also launched simultaneously with Lone Echo, so yeah, this game is new and fresh, but it's, we've been developing VR now for a little over two years. >> Right, so from a design perspective in the VR space, what is some of the special considerations you have to be thinking about, either challenges and opportunities? >> Yeah, I mean some of the challenges are obviously, performance is a big deal for us. The game has to run at 90 frames per second on Oculus per eye, so that's rendering essentially like two different-- >> [Jeff] 90 frames per eye? >> Yeah, it's really fast. You have to render 90 frames per second, otherwise it gets really uncomfortable for the user, so we optimize a lot of our experiences. And it's even like, some of the ideas that we have, we have to figure out how to make them viable at that frame rate. And we have a lot of high-fidelity body movement going on in Lone Echo, Echo Arena, and now Echo Combat. We do a lot of IK work to kind of represent a full body avatar that honors essentially head, hands, and because our game takes place in zero G, we have this floating body that has to convincingly flow behind you wherever you go. >> [Jeff] Right >> Yeah, it's actually, it's a pretty big challenge for us as both designers, developers, and just on a technical standpoint to get all that to kind of harmoniously work together. >> Right, so other thing, just in terms of the game play inside VR, 'cause the other thing is right, you don't necessarily control which direction they're looking. I mean, how do you kind of direct the player to where you want them to look, and where you want them to participate? >> That's a great question. Actually, so part of the beauty of VR, is we try to do some of that like you would for a conventional game, trying to use lighting, trying to basically design environments with things, cues, details that would maybe help people along, but ultimately you're as free as you are, just like right now you and I, we can look all over the place. >> [Jeff] Right. >> We don't really want to restrict that. Part of the beauty of VR is that ultimate freedom. If you wanna of kind of go, look in that little corner underneath you for the whole game, you really can, and we try to as much as possible make that something that's beneficial too. We try to code every little bit of our world with something that's interesting to find, discover, so. >> Right, right. >> Yeah, it's freedom of movement, freedom of wherever you wanna be, whatever you wanna do. >> Right, so we're doing this as part of the Western Digital data makes possible program, and really as we get closer and closer to infinite store, infinite compute, infinite networking, you just said you've got designs, and you've got ideas that even today you can't necessarily put into place. So as you look forward for the opportunities when all these things are basically gonna be close to infinite, at close to zero cost, what are some of the things that excite you? Where do you see kind of using that power to do a better job, or different job in your storytelling? >> Yeah, I mean the horsepower that you need to run these kind of games is actually pretty staggering. We compute a lot of stuff on the GPUs, the CPUs, we have a lot of physics-oriented things in the game because VR is really big into like letting you kind of touch everything, and manipulate stuff, and it doesn't feel like you're really somewhere, you don't feel present unless you can actually interact with the environments. And for that we have to basically create tons, and tons, and tons of objects, we have physics constraints and things that are costly for the computation cycles. And then there's like memory issues. We have streaming that we have to kind of get better at. These worlds are very large, and so to store the things that you're gonna see and do, takes a lot of actual hard drive space, and the speed at which we can load and unload things, is a critical factor in terms of unlocking the freedom of your experience. >> Right, so when you get more horsepower, a new processor comes out, and you get more memory, whatever, I mean do you already have stuff keyed up where you want to use that? Is it more a realistic nature of the graphics, is it speed, I mean what are some of the priorities that you would immediately apply if you had some more horsepower tomorrow? >> Yeah, certainly I mean there are things that we absolutely know about like there's texture resolution, there's like I said, there's physics objects, there are just things that we end up going, that's too costly to do, we're gonna have to maybe stop doing that or cut back on it, or scope back. We do look at creating settings and things where our users who actually have more high-end machines, to actually turn that stuff back on, but I think every time we kind of go into another design kind of exercise and sort of looking at what do we want to do in VR, I think we're surprised at what does it take to actually accomplish it. And so I'm not sure I know right now fully what we're gonna start getting into and what kind of hardware that might require, but every day's just a different challenge, and that's part of the excitement of working in VR. >> Right, right and I was gonna say and also obviously the trade-offs. I mean you could go bananas on the texture, but at some point is it the law of diminishing returns in terms of the storytelling, in terms of the experience 'cause you can't optimize across all the potential variables. >> Yeah, no, you have to pick and choose, and you're right, like basically we look at what are our goals, what are we trying to get out of this experience, what do we want the user to really get out of it? And then we have to compromise. We have to make some of those smart choices. But I do think at some point, we'll have to make less compromises as the technology gets better, and certainly things like resolution, if the headsets have higher resolution then it makes sense to put more resolution into the textures because now you can actually see it, and so we kind of hit that synergy where both of those are unlocked, it'll never be infinite obviously, but to where they're more in sync with each other, maybe we can make that compromise now, but maybe in the future we won't. >> Yeah, the headset's a whole 'nother bucket of technology. >> It is yeah. >> That you guys have to account. >> But they're awesome I mean, yeah we're doing, I think it's really impressive to me how far we've come with the headset technology. And I think in the next few years, we're just gonna see even crazier advances. So I'm really excited about that. >> Not just slap on the phone in the cardboard box, like a couple years ago. Here's your VR box. >> I know, right? That's not that long ago if you think about it really. >> All right, Dana, well give a shout out, what's the date for the public beta so people know where to go and how to get involved. >> Yeah, our open beta's gonna be starting June 21st. They can sign up on oculus.com. And yeah, we're looking forward to people getting in there and seeing what their impressions are, and taking the feedback. >> All right, well, Dana, thanks for taking a few minutes and stopping by. >> Great, thank you very much. >> All right, he's Dana, and I'm Jeff. You're watching The Cube from E3 at the LA Convention Center. Thanks for watching. (upbeat music)

>> Announcer: Live from San Francisco, it's theCUBE, covering Red Hat Summit 2018. Brought to you by Red Hat. >> Welcome back, here, when we here live, it's theCube, here in San Francisco live for Red Hat, Summit 2018. I'm John Furrier, the host of theCUBE. Our next three guests is the Delisa Alexander, Executive Vice President, Chief People Officer at Red Hat. Welcome to theCUBE. >> Thanks. >> Zui Dighe, who's the... Did I get that right? Zz-- >> Zui, yeah, mm-hmm. >> Zui? OK, winner of the Open Source Academic Award from Duke University, Go Blue Devils (chuckles). >> Zui: Yes. >> And we have Dana Lewis, winner of Open AP with OpenAPS, which stands for? >> The Open Source Artificial Pancreas System. >> Artificial open-source Pancreas System, great stuff. So congratulations, you guys are all award winners. Before we get into some of the questions, love your applications, talk about the program. What is this about? What's the awards program here at Red Hat Summit, and why are these guys here? >> So as Red Hat, we believe, as an open-source leader, we have a responsibility to promote women in technology and particularly women in open-source. And so, one of the things we thought we could do is to create an award that really spotlights the contributions women are making in open-source to inspire future generations to consider being open-source developers or contributors. >> Congrat, Delisa, love that you're doing that. It's fantastic. We'll start with the young student gun here. What's your degree, first of all? What are you studying? >> I'm studying biomedical engineering and computer science. >> John: Tough major, huh? >> Yep, very tough. (Delisa laughing) Not easy, but I'm-- >> This is an easy-- >> First question is, how do you in a block chain impact? It's funny, Jim always asked that question on day one. No, in all serious, tell about what your application is. This is super important. >> Yeah, yeah. So I'm basically working on researching and creating a tracking system for vaccines that enter into developing countries. So through that, you're able to understand how exactly do vaccines travel through these countries as well as where does the system break. And if you can pinpoint that, you can actually solve the problem. >> And how did you get the idea? How did this all come together? >> I was in a research course at Duke, which has collaboration with the university in Uganda, and we actually got to travel to Uganda and interview various stakeholders, pharmaceutical companies, health system, and understand how does the-- We wanted to be in vaccines, but we didn't know what exactly to do. And so after interviewing, I kind of came up with the idea of why don't we actually put a tracker on these devices that gives off the GPS location and the temperature so we can actually understand the entire system. >> It's going to get that ground truth, too, and again, the local areas. >> Yeah. >> The big walk away, what, about vaccines. This is important to track it from the origination to destination and making sure it all kind of matches up. >> Making sure, first of all, you don't have any data on exactly where they're going because this box is just carried by hand. And the pharmaceutical companies, once they ship the vaccines into Uganda, after that, they don't provide any data on what's going on. So that data is also important, and it's also, you want to know when does the system break because often in last end, when the vaccines are actually administered, they've already gone out of their cold chain cycle, and so they don't work anymore. >> That's a great story. How 'about your story? This is a good one. This is a real practical one for people with diabetes. Talk about, first of all, show the product 'cause it's always good to a little live prop there. So turn, yeah, there it is. So what is that? >> So this is an open-source hardware board. It's actually got an Intel Edison on the back side. But what this does is, it talks to my insulin pump and my continuous glucose monitor, brings the data together, runs it through an algorithm, and sends commands back to the insulin pump to tell it what to do. So this is what we call a close-loop system where we have the computer doing the math instead of the human with diabetes doing the math several times throughout the day. >> And does it do auto-injections as well? So it kind of feeds the glucose levels as well? So it's data-- >> Right. So the insulin pump is automatically dosing the insulin, and we also have a continuous feed of the blood sugar every five minutes as well. >> And that's what you mean by close-loop. >> Exactly. >> For people have these monitors, they have remotes, statistics. Does it talk to a device as well? The mobile device, how does that work? >> Yeah, so I can glance down at my watch and see how I'm doing, on my phone. My loved ones, wherever they are, can see how things are going. So if they need to intervene, they're able to do that remotely. So it really provides peace of mind as well as a lot better outcomes for those of us living with Type I diabetes. >> And what was the motivation here, to get involved deeply in this project? >> It was really selfish, I wanted to sleep, and I couldn't hear my CGM alarm, my glucose alarm. And so my project actually started of, just get the data off to make a louder alarm. And then we built an algorithm that allowed us to look into the future and do proactive alarms. And then we worked with other people to actually communicate with the insulin pump, and that's how we progressed to closing the loop. And because I've been helped so much by other people in open-source, it was a no-brainer to also make our work open-source. >> And so you open-source everything. What other progress can you share? I mean, you have predictive analytics that tell you that, "OK, I'm going to go for a hike soon, "so therefore, I'm going to do this," and all kinds of cool data gathering. Does that play into it? Is it a lifestyle and-- >> Absolutely. >> So it's like a FitBit meets close-loop. (Women laugh) >> It's more like taking standard medical devices and boosting their capacities with the help of computing technologies. It's not fancy machine learning. It's the same math a person with diabetes would do, but the benefit is, it's automated to go every five minutes, and it doesn't fall asleep, it doesn't get lazy, it doesn't round up or vary down. It's going to be giving really precise increments so that when your situation changes, you skip a meal that you though you were going to eat, you're going to go hiking, for whatever reason, if you're going up or down more than expected, it can react instantaneously and much better than a human can. >> I'm so glad you're doing that, too. How does someone get involved with this project? Obviously, it's open-source software, but you have devices. Is it in market? Is there? >> So this is an open-source project because we are not a company, so we cannot distribute medical devices. That's frowned upon by the FDA. And so this is an open-source DIY project for people who want to get involved either to help with the project or build one themselves. They can go to OpenAPS.org. We've written a plain language reference design to help anybody, whether you're a person with diabetes, a loved one, a healthcare provider, a researcher or developer understand how the system works, and then that leads you to the documentation of how to build one as well as to the code where anybody can get involved and help out. >> So that's the loophole, (Dana laughs) to say it plainly, get around that whole being a company. You build your own. >> Yes. >> So that's the way, that's here. OK, great, so congratulations. So where's this all going? This is fantastic, this story. How many other people are involved in the program that you have? Share more about how people can get involved, too. >> This is our fourth year of having the program, and we're really just thrilled with the quality of the nominations. We had over 100 nominations. Our judges then narrowed the field down to 10, and then the community selected the winners. We don't really see an end to this. We just see the community adding and growing organically. So one thing we did this time is, we introduced our winners to our CO.LAB students, and so now they're creating a network. And that network density is just increasing and improving and, I think, getting stronger. >> It's really amazing. And one thing I've always loved about open-source, and you guys see the benefit of it, obviously, with winning and succeeding, is that democratization and community are coming together at a whole nother level. And I think what's interesting about the projects that you guys have is, you got good things happening with tech. So it's tech for good. But since Obama put the Jobs Act in, means fund these projects now as entrepreneurial ventures and be mission-driven OFFLEM. You don't have to do it as a non-profit. So we're seeing a huge growth in entrepreneurial activity around tech for good on projects that would never would funded before. So you're seeing a whole nother generation of great tools and technologies saying, "Hey, let's solve a problem." >> Yeah, and I think that's one of thing I love about us both being in healthcare is, it really shows that there's amazing applications. We can take this technology and apply it in healthcare and do it in different ways, and it doesn't have to be a company right away. It doesn't have to be either a for profit or non for profit. There's a lot of ways open-source is bringing people together to solve the very problems we need to be solving. >> Do you feel good that you built something great like that, and think now you got people using the software? What's the feeling like? >> Oh, it's just incredibly rewarding. I mean, myself, I just have the peace of mind to be able to go to sleep at night. That is a priceless feeling, but then when I hear other people using it, they build the project for different reasons. Some, they want to be able to remotely monitor their loved ones. Others are doing it for their children so that they have better health outcomes. But there's just these amazing stories outpouring from the community. And to me, that's the beauty of open sources. You can really apply it however you need to apply it to your lifestyle. >> Where can someone get involved in your project? Is there like a GitHub repository? >> Yep. >> Is there a site? >> Everything's on GitHub for us, but I would go to OpenAPS.org first. It links to the documentation and the code where people can connect. >> OpenAPS.org. >> That's right. >> OK, great. How 'about your project? How do people get involved with what you're doing? >> Ours is on GitHub right now, so you can get involved through there. But I guess we're kind of right now developing in the backend stages. Soon we'll be at that stage where you can contribute more. And right now, we've just been using other open-source libraries and kind of contributed in that way. But actually, we talked earlier about how do you get involved in open-source, and especially being a student, I kind of fell into coding because of open-source in a sense >> Working on your project? where, yeah, yeah, yeah. So coming into college, I wanted to apply the engineering concepts I was learning in the classroom, and I got involved in a lot of entrepreneurship on campus, and through that, I was asked to make a front-end interface, and I didn't really know how to go about doing that. So then I found an open-source library stumbling around that was doing a similar thing. And that's how I kind of taught myself, and then from there, I branched out and learned more and more. And I think for any budding student, budding entrepreneur, open-source is a great way to take your ideas further. And my interest is in healthcare, so that's where I went, but anyone could have an idea, "Oh, I want to start this business in this way." And they might not think that open-source is a way to go about doing that, but it is a great way to learn more. >> It's a good way to change a lot of things, not just career or projects. >> Yeah. >> There's a nonlinear progression of learning happening. You can come in, you're stumbling around, quote, learning. >> Yeah, yeah. >> It's not like chapter one course, online course. Go to chapter two. >> Right, that is true. >> There's a YouTube, there's stuff on GitHub, open-source. There's people involved. This points to a whole new generational shift. >> It is. >> Of learning, connecting, you're tapping into it. >> It's so exciting because she's the role model we're talking about. We want girls to see that you can become a coder later. You don't have to necessarily start-- >> She's 14, she'd coding in unity. >> Yeah! >> I tell a soliloquy, great. (Delisa laughing) Do some smart contracts and get the bobchain action. (Delisa laughing) Bobchain's the future, you're the Bitcoin in intheoreum. Some cool stuff. >> Yeah. Congratulations, thanks for doing this. >> Thank you very much. >> Very inspirational, and thanks for sharing the story on theCUBE, and keep in touch, thanks for coming, appreciate it. >> Thank you. >> Thanks for having us. >> Great women in tech, great leaders doing some great stuff. Award winners, celebrities here on theCUBE. I'm John Furrier. Be back with more live coverage after this short break. (electronic musical flourish)

>>Welcome back to the cubes coverage of Dell tech world 2022. My name is Dave Volante and I'm here in our cube studios in Massachusetts getting ready for the first in person DT w since 2019, you know, Charles Phillips, the CEO of Infor and former Oracle ex once set on the cube friends, don't let friends build data centers anymore. It's just not the best use of capital for most companies, unless you happen to be in the data center business like Sexter organizations wanna make hybrid connections to the cloud. They need a partner that knows how to build and manage world class data centers that are both efficient and resilient. And in this segment, we're gonna talk about the importance of hybrid strategies for organizations, how they're approaching hybrid and why a partner strategy is important to support the next decade of digital transformation initiatives. And with me are Randy Roland. Who's the COO of six Tara and Holland Barry, who is the field CTO for the company. Gentlemen, welcome to the cube. Thanks for coming on. >>Thank you. >>Good to meet her. Thanks for having us. >>Hey, Randy, as a relatively new player, unlike a lot of data center operators, Cera, you're not shackled by decades of technical debt. Tell us more about the company. >>Yeah. So as you, uh, already discussed Ceras a data center company, and we're one of the few that can provide colocation globally. And so that allows our customers to scale, uh, across the globe, as our business scales, we operate in 28 markets. We have over 60 data centers and we continue to add more dots to the map based on customer demand. And the primary way we differentiate is that we've built a true global data center platform. And what do I mean by that is that we have a combination of 2300 customers, uh, enterprises, technology, service providers, government agencies, we're a leader in interconnection. Uh, we have a commitment to carry neutrality and to provide low latency access to all the different cloud platforms. And we've made major investments in developing our own technology in house. And this will come out. As we talk about hybrid cloud is to make our data centers easier to consume. Uh, we live in a cloud first world, and so we've got to be able to be responsive and be able to deliver capacity on demand and to allow our customer members to dynamically connect to each other so they can start to consume these valuable services. And so that's really what we're doing at Cera. >>You know, Randy, just a follow up is because when the cloud first came out, everybody said, oh, companies like, like yours, Dana data center operations are toast. And the exact opposite happened. It was like this rising tide lifted all boats. The, the business is, is booming. It's, uh, it's actually quite room, isn't it? >>Yeah, actually it's a good point. We actually lean into, uh, cloud consumption. I think, uh, if you remember, the cloud operates in four walls. And so when a company, um, actually starts to deploy and leverage more, they need a place to land their digital infrastructure hub, where they can make connections to all the different cloud solutions they're gonna consume. And they're using their own internal resources at the same time. And so the more that we adopt cloud, um, and lean into cloud, the more likely our customer gonna choose us. And back to your opening comment about, uh, the, the quote from the Oracle executive in, in my career, I've been in the data center business for a long time and it, it's definitely a generational thing. We have newer generation of it leaders when they think about their internal data center, their actual internal data center is ours. They're thinking about their own four walls sitting on their own property like they did historically. And so, uh, they view internal data centers as the contracts they have, uh, with six companies like six. >>Excellent. All right, Holland, let's bring you into the conversation. What are you seeing with, with hybrid cloud strategies? You, why are companies choosing hybrid? Give us some color there. >>Yeah, I think, you know, we, as a company sit in an interesting confluence of some workload movements, if you will. Um, so I think there's been, in some cases, an overcorrection in the public cloud, people thought that a cloud first strategy meant that you have to throw everything up in a public cloud. Uh, especially over the last couple years when we had, you know, the surprise of a large remote workforce. And as you mentioned at the top of the call, Dave, we also have folks with the shrinking appetite to own and operate their data centers, right? So the hybrid approach is a, um, a selective methodology to really look at the applications, uh, look at the strengths of each one of those venues, where you can run your applications and workloads, and really choosing the one that uses the strengths. And there's several, uh, drivers behind that. Uh, some of them are cost. Some of them are performance. Some of them might have to do a security or data sovereignty. Um, so you can really match those requirements and those business outcomes that you're looking to achieve, uh, and align them with that platform. That's that's best suited to serve it. >>So you mentioned a few of 'em, but I wanna sort of stay on that for a minute. Is it, is it, you know, egress cost, everybody talks about that, you know, latency proximity to the cloud. I mean, I think there's a lot of times, I think the ideal situation is you put your high performance, you know, transaction low latency stuff in one of your data centers. And, you know, a lot of the data is, is in the cloud that you might need access to. But is there other innovation, you know, talk a little bit more about the drivers that you're seeing with customers? >>Absolutely. We, I think, um, as it relates to data gravity and the potential relation to egress charges, that is a huge, uh, consideration, cuz there's a cost and a performance component to that. If you decide you want to take that data and move somewhere else, if it's in the public cloud, you're gonna pay some, uh, pretty large egres fees, but there's certainly other drivers, um, performance being another big one. Uh, if I've got a, a data lake or, or a big data analytics platform or maybe an AI platform that needs to live close to the data. Um, and especially if those workloads that are associated with crunching, the data are kind of high steady state, maybe even mission critical workloads that is certainly a workload profile. That's better suited to run within our four walls. You can have those CPU or GPU comput nodes sitting right next to those large data sets, operating with each other at land speed. Um, so in terms of the drivers behind, uh, making a, a venue change, if you will, I think cost is one of the biggest ones that we see and, and maybe performance and security following close after. >>So, so how are customers approaching hybrid? Can you paint a picture of kinda what that connection looks like and how, how they, you know, land on their strategies? >>Yeah, absolutely. So they're doing, uh, what I like to call a workload appropriateness, uh, exercise. And as they think about recalibrating where those workloads live, exactly what I said before, they're looking at the strengths of the platform and, uh, lining up those application profiles to live in, in the appropriate place. We have a unique advantage, uh, because of our interconnection profile and our adjacency to public cloud platforms, where if people want to have application tiers that may be sent on both sides of the fence, if you will, uh, we have super, super low latency connections. You can connect, you know, layer two, uh, maybe out to AWS, um, and, you know, have your VPC on one side, have, uh, you know, dedicated single tenant environments on our side and have those applications interact with each other. And then in a super low latency fashion, >>Hey, lemme just ask a follow up question on that. Because I remember the Y2K days, there was a, a lot of activity, a lot of spending and then CIOs wanted to look at their portfolio and, and rationalize that portfolio. When you talk about workload appropriateness, are you seeing a similar application rationalization exercise going on or is it just a Hey can spending, >>Uh, absolutely. We're seeing rationalization and I think what's happening is folks are getting a little more savvy about forecasting, the growth of their application, uh, the growth of the data associated with it, what the cost may be associated with needing to move them around to different venues. Um, and so we're, we're definitely seeing people look at those numbers and make decisions about workload placement based on that analytics and, and kind of knowledge of what it means down the road and also where the data might need to live locally too. We're seeing people, uh, being a little more cognizant geographically around data where it lives and how that relates to where the computer associated with that data is. >>Yeah. Hey Randy, can you tell us a little bit more from a business perspective about the Dell partnership? How did that come about, you know, who does, what, what are the swim lanes overlaps? Maybe you can help us understand that. >>Yeah, so we're very excited about, uh, our Dell partnership, as you can imagine, with as many customers and many data centers, as we've got deployed, we have Dell, uh, located it in a large percentage of our customer environments. And so it's just natural that we work together to figure out how we can continue to meet, uh, our customer's needs. And so the core idea that I'm excited about around Dell is that Dell has an excellent technology platform in all fronts, they've got great compute and storage and all types of software solutions. And what we want to do is help them make their platform more on demand. And so what do I mean by that? If you think about the historical, uh, time, it takes to deploy a traditional colo environment from the time you spec the cage, do you ship the equipment, you install the network, you rack and stack the equipment, unload the cloud stack. >>It takes weeks to months to deploy. And so what we're doing is working very closely with Dell to look at our existing customers and new prospects that are interested in their platform and how can we pre-provision that capacity in, in the data center make it so it's already plugged into the data center already is powered up. It's connected to the network and a customer can purchase it on demand. And so the idea behind this is how can we give our customers all the benefits of Kolo, which is what, uh, Holland was talking about a minute ago, but deliver that platform at the speed of cloud. And that's really the essence of the partnership we have with Dell. Uh, we think it could be explosive. Uh, we think there's a lot of opportunity, not only, uh, for us, but also for Dell as they continue to retain their customers and their customers go through tech refresh cycles, if they can have on demand technology that they're already familiar with, they can get the benefits that you get from co-location at the speed of cloud. And that that's what our, the, the basis of our, our relationship. >>Yeah. Thank you. So Holland, I mean, Randy was saying one of the pillars of Dell tech world this year is the whole as a service thrust. And, you know, essentially what it is, my, my viewpoint is Dell's building out its own cloud. That's, you know, it's, it's its aspiration I think, is to connect on-prem to, through hybrid, to public clouds across clouds, out to the edge extract that all that complexity and you guys would be a key part of that from a, from a CTO's perspective, that's a different mindset. I mean, it changes the way we manage, think about procure, you know, spend, uh, um, and, and maybe that even the technical configurations of, of how we deliver and consume it, you give us some thoughts on that. >>Absolutely. Look, I think what we're doing is we're laying the foundation for a truly hybrid experience. Um, Randy mentioned, uh, us going through great lengths with our technology partners like Dell and make the data center consumable in an automated fashion. And so as we increasingly move into technologies like containers and using coordinators managers like Kubernetes, we really now have the ability to make a true hybrid experience. And if you think about the experience of deploying, you know, in a data center, whether it's your own or a co like ours, that was, you know, a 60 to 90 day conversation to, to get that infrastructure spun up. And so now if you can consume public cloud resources, just like we've been used to doing where you can swipe a card and get access to infrastructure in a matter of minutes or hours have the same experience with us, we've kind of closed that last mile of infrastructure delivery. And the other neat thing about this is, uh, if you have a cloud first mandate, if some of those workloads are running a ter data center, uh, we check all those same boxes, right? Uh, we, we have infrastructure that sits off X. We have a global platform. Uh, we have, you know, highly automated environment. So you can really now start extracting yourself a little bit from the infrastructure and start focusing on the important stuff, which the applications that sit on top. >>So from a security standpoint, you have a similar, you know, the cloud guys talk about the shared responsibility model. Is that a similar model that, that you guys have? Can you describe that? >>Yeah, it's, it's, it's very analogous to this shared responsibility model and, and public cloud. We give a little bit more control to our customers, like things like, you know, dictate maintenance windows. Um, we give a little bit more control in terms of access to the infrastructure. Uh, it's one of the reasons that organizations like running infrastructure with us is because we can hand off control to these certain things that the lower levels of the infrastructure stack versus that higher level of abstraction that happens with public cloud. >>And what, what kind of skills are you after, uh, these days? Is it people that can squeeze, you know, more power and, you know, more efficient cooling, uh, is it infrastructure management? You mentioned Kubernetes before. What, what matters to a company like yours from a skill standpoint? >>Yeah. And to terms of our staff, it is at the lower, uh, levels of the stack, if you will. So maybe going, you know, up to, uh, layer two or three, if we think about the OSI model. So certainly power engineering, cooling engineering, the stuff that physically runs our, our data center, that's our meat and potatoes. That's important to us, but as you consider our digital platform, um, certainly the networking, uh, know how knowledge of the entire stack, knowing how things are architected, understanding how cloud works, how understanding how cloud connectivity works. These are all super, super important skill sets. So we span the spectrum a bit. Um, but it's less on the upper ends of it, you know, kind of going up to layer seven, >>Although I'd imagine that data center automation is obviously a big part of your, your IP, right. Is that something that you have guys bring to the table? Yes. >>Yeah, it's actually one of our key innovations is around how we've architected our software platform, how we do our automation, uh, how we run our network. Uh, we we've, uh, built a, a super, super innovative SDN fabric that powers all of our Metro regions that enables the delivery, the infrastructure that hangs off of it. Um, so yeah, a huge percentage of our I P is around that software innovation and, uh, networking automation. >>Great. Randy, I wonder if you could close it out for us. Uh, I'd love your thoughts on where you'd like to see the Dell partnership go and any other, you know, information you'd like to leave the audience with. >>Yeah. I think you've asked a couple questions about the perspective from a CTO and the way that we want to build our solutions is if you are a CTO or if you're a cloud architect, what we are trying to build is a set of Legos to allow you to assemble your ultimate hybrid it solution to use a combination of traditional colocation, where you have equipment that you own, that you manage on demand, bare metal from great partnerships, like where we have with Dell, that can augment what you have in colo have access to a rich ecosystem of technology providers that sit in the same data center markets so that you can start to, to actually augment your it architecture with a lot of our, um, uh, solution providers that sit within our, our, our markets access to cloud OnRamp. So you get low latency access to public cloud to start to leverage some of the technologies they have, and also have the ability to switch, right? If you start with one cloud cloud provider, and at some point you find something more cost efficient, or a little bit more architecturally, uh, built that we can, uh, uh, facilitate that switch. And then also to have connectivity to all the different network carriers that we have. And so, and, and also to do it globally, right? And so our mission is to give the CTO and the cloud architect, the ultimate Legos, uh, to build their custom solution, it's highly, um, cost effective and meets all the technology requirements. >>Yeah. Hedging that risk and having exit strategies, I think is huge. Every, every customer needs to think about that, uh, before they, they dive into the cloud. Okay, guys, we gotta leave it there. Thanks so much for coming in the cube. Great discussion. >>Thank you. Thanks for having us. >>And thank you for watching our ongoing coverage of Dell technologies, world 2022, the in-person live version where we insert great deep dive interviews like this one that focus on key customer topics. Keep it right there. You're watching the cube.

>>we'll go back to the cubes. Coverage of the age of US Executive Summit at Davis. Reinvent made possible by Accenture My name is Dave Volunteer. We're gonna talk about the arm nation advantage, embraced the future of productivity, improve speed quality and customer experience through artificial intelligence. And we herewith Bhaskar goes, Who's the chief strategy Officer X censure in Rajendra RP Prasad is the senior managing director in Global Automation. The Accenture guys walk into the Cube. Get to seal. >>Thank you. >>Hey, congratulations on the new book. I know it's like giving birth, but it's a mini version. If the well, the automation advantage embraced a future of productivity, improve speed, quality and customer experience to artificial intelligence. What inspired you to write this book? Can you tell us a little bit more about it and how businesses are going to be able to take advantage of the information that's in there? Maybe you could start, >>so I think you know, if we say that what inspired as primarily the two things really style, you know, over inspired have to start this project in first of all is the technology change step change in the technology. Second is the mile maturity of the buyer maturity of the market when it's a little more, you know, when I talk about the technology change, automation is nothing new in the industry. In the starting from the Industrial Revolution, always, industry adopted the automation. But last few years would happen. That there is a significant change in the technology in terms of not of new technologies are coming together like cloud data, artificial intelligence, machine learning and they are gearing match you, and that created a huge opportunity in the industry. So that is number one second if fighting the maturity of the buyer. So buyers are always buying automation, adopting the automation. So when I talked to this different by a different industrial wire, suddenly we realise they're not asking about workings automation, how that will help. But primarily they're talking about how they can scaling. They have all have done the pilot, the prototype, how they can take the full advantage in their enterprise through scheme and talking to few client few of our clients, and he realised that it's best to write this boat and film all our clients to take advantage of this new technologies to skill up their business. If I give a little more than inside that one, exactly we are trying to do in this boat primarily, we dealt with three things. One is the individual automation which deals with the human efficiency. Second is the industrial automation who visited a group efficiency. And third is the intelligent automation. We deal city business, official efficiency while business value. So we believe that this is what will really change their business and help our client help the automation. It users to really make clear an impact in their business. >>Yeah, And so you talked about that? The maturity of the customer. And and I like the way you should describe that spectrum ending with intelligent automation. So the point is you not just paving the cow path, if you will, automating processes that maybe were invented decades ago. You're really trying to rethink the best approach. And that's where you going to get the most business value, our peace In thinking about the maturity, I think the a pre pandemic people were maybe a little reluctant s Bhaskar was saying maybe needed some education. But But how? If things change me, obviously the penned Emmick has had a huge impact. It's accelerated things, but but what's changed in the business environment? In terms of the need to implement automation? R. P >>thank you Well, that is an excellent question. As even through the pandemic, most of the enterprises accelerated what I call as the digital transformation, technology transformation and the war all time that it takes to do. The transformation is compressed in our most land prices. Now do compress transformation. The core of it is innovation and innovation, led technology and technology based solutions. To drive this transformation automation. Artificial intelligence becomes hot of what we do while we are implementing this accelerators. Innovation enablers within the enterprises, most of the enterprises prior to the pandemic we're looking automation and I as a solution for cost efficiency. Saving cost in DePina deriving capacity efficiency does if they do the transformation when we press the fast forward but draw the transformation journey liberating automation. What happens is most of the enterprises which the focus from cost efficiency to speed to market application availability and system resiliency at the core. When I speaking to most of the sea woes Corrine Wall in the tech transformation they have now embrace automation and air as a Conan able to bribe this journeys towards, you know, growth, innovation, lead application, availability and transformation and sustainability of the applications through the are A book addresses all of these aspects, including the most important element of which is compute storeys and the enablement that it can accomplish through cloud transformation, cloud computing services and how I I and Michelle learning take log technologies can in a benefit from transformation to the block. In addition, we also heard person talk about automation in the cloud zero automation taking journey towards the cloud on automation Once you're in the clouds, water the philosophy and principles he should be following to drive the motivation. We also provide holy holistic approach to dry automation by focusing process technology that includes talent and change management and also addressing automation culture for the organisations in the way they work as they go forward. >>You mentioned a couple things computing, storage and when we look at our surveys, guys is it is interesting to see em, especially since the pandemic, four items have popped up where all the spending momentum is cloud province reasons scale and in resource and, you know, be able the report to remotely containers because a lot of people have work loads on Prem that they just can automatically move in the company, want to do development in the cloud and maybe connect to some of those on from work clothes. R P A. Which is underscores automation in, of course, and R. P. You mentioned a computing storage and, of course, the other pieces. Data's We have always data, but so my question is, how has the cloud and eight of us specifically influenced changes in automation? In a >>brilliant question and brilliant point, I say no winner. I talked to my clients. One of the things that I always says, Yeah, I I is nothing but y for the data that is the of the data. So that date of place underlying a very critical part of applying intelligence, artificial intelligence and I in the organization's right as the organisation move along their automation journey. Like you said, promoting process automation to contain a realisation to establishing data, building the data cubes and managing the massive data leveraging cloud and how Yebda please can help in a significant way to help the data stratification Dana Enablement data analysis and not data clustering classification All aspects of the what we need to do within the between the data space that helps for the Lord scale automation effort, the cloud and and ablest place a significant role to help accelerate and enable the data part. Once you do that, building mission learning models on the top of it liberating containers clusters develops techniques to drive, you know the principles on the top of it is very makes it easier to drive that on foster enablement advancement through cloud technologists. Alternatively, using automation itself to come enable the cloud transformation data transformation data migration aspects to manage the complexity, speed and scale is very important. The book stresses the very importance of fuelling the motion of the entire organisation to agility, embracing new development methods like automation in the cloud develops Davis a cop's and the importance of oral cloud adoptions that bills the foundational elements of, you know, making sure you're automation and air capabilities are established in a way that it is scalable and sustainable within the organisations as they move forward, >>Right? Thank you for that r p vast crime want to come back to this notion of maturity and and just quite automation. So Andy Jossy made the phrase undifferentiated, heavy lifting popular. But that was largely last decade. Apply to it. And now we're talking about deeper business integration. And so you know, automation certainly is solves the problem of Okay, I can take Monday and cast like provisioning storage in compute and automate that great. But what is some of the business problems, that deeper business integration that we're solving through things? And I want to use the phrase they used earlier intelligent automation? What is that? Can you give an example? >>Let's a very good question as we said, that the automation is a journey, you know, if we talk to any blind, so everybody wants to use data and artificial intelligence to transform their business, so that is very simple. But the point is that you cannot reach their anti unless you follow the steps. So in our book, we have explained that the process that means you know, we defined in a five steps. We said that everybody has to follow the foundation, which is primarily tools driven optimise, which is process drivel. An official see improvement, which is primarily are driven. Then comes predictive capability, the organisation, which is data driven, and then intelligence, which is primarily artificial intelligence driven. Now, when I talked about the use of artificial intelligence and this new intelligent in the business, what the what I mean is basically improved decision making in every level in the organisation and give the example. We have given multiple example in this, both in a very simple example, if I take suppose, a financial secretary organisation, they're selling wealth management product to the client, so they have a number of management product, and they have number of their number of clients a different profile. But now what is happening? This artificial intelligence is helping their agents to target the night product for the night customers. So then, at the success rate is very high. So that is a change that is a change in the way they do business. Now some of the platform companies like Amazon on Netflix. He will see that this this killed is a very native skill for them. They used the artificial intelligence try to use everywhere, but there a lot of other companies who are trying to adopt this killed today. Their fundamental problem is they do not have the right data. They do not have the capability. They do not have all the processes so that they can inject the decision making artificial intelligence capability in every decision making to empower their workforce. And that is what we have written in this book. To provide the guidance to this in this book. How they can use the better business decision improved the create, the more business value using artificial intelligence and intelligent automation. >>Interesting. Bhaskar are gonna stay with you, you know, in their book in the middle of last decade, Erik Brynjolfsson and Andy McAfee wrote the second Machine Age, and they made a point in the book that machines have always replaced humans in instead of various tasks. But for the first time ever, we're seeing machines replacing human in cognitive task that scares a lot of people so hardy you inspire employees to embrace the change that automation can bring. What what are you seeing is the best ways to do that? >>This is a very good question. The intelligent automation implementation is not, Iet Project is primarily change management. It's primarily change in the culture, the people in the organisation into embrace this change and how they will get empowered with the machine. It is not about the replacing people by machine, which has happened historically into the earlier stages of automation, which I explained. But in this intelligent automation, it is basically empowering people to do the better. Dwelled the example. That is the thing we have written in the book about about a newspaper, 100 years old newspaper in Italy. And you know, this industry has gone through multiple automation and changes black and white printing, printing to digital. Everything happened. And now what is happening? They're using artificial intelligence, so they're writers are using those technologies to write faster. So when they are writing immediately, they're getting supported with the later they're supporting with the related article they are supporting with this script, even they're supported to the heading of this article. So the question is that it is not replacing the news, you know, the content writer, but is basically empowering them so that they can produce the better quality of product they can, better writing in a faster time. So is very different approach and that is why is, um, needs a change management and it's a cultural change. >>Garden R P What's it for me? Why should we read the automation advantage? Maybe you can talk about some of the key takeaways and, you know, maybe the best places to start on an automation journey. >>Very will cut the fastest MP, Newer automation journey and Claude Adoption Journey is to start simple and start right if you know what's have free one of the process, Guru says, If you don't know where you are on a map, a map won't help you, so to start right, a company needs to know where they are on a map today, identify the right focus areas, create a clear roadmap and then move forward with the structured approach for successful our option. The other important element is if you automate an inefficient process, we are going to make your inefficiency run more efficiently. So it is very important to baseline, and then I established the baseline and know very or on the journey map. This is one of the key teams we discuss in the Automation Advantis book, with principles and tips and real world examples on how to approach each of these stages. We also stress the importance of building the right architecture is for intelligent automation, cloud enablement, security at the core of automation and the platform centric approach. Leading enterprises can fade out adopters and Iraq, whether they are in the early stages of the automation, journey or surrender advanced stage the formation journey. They can look at the automation advantage book and build and take the best practises and and what is provided as a practical tips within the book to drive there. Automation journey. This also includes importance of having right partners in the cloud space, like a loveliest who can accelerate automation, journey and making sure accompanies cloud migration. Strategy includes automation, automation, lead, yea and data as part of their journey. Management. >>That's great. Good advice there. Bring us home. Maybe you can wrap it up with the final final world. >>So, lefty, keep it very simple. This book will help you to create difference in your business with the power of automation and artificial intelligence. >>That's a simple message and will governor what industry you're in? There is a disruptions scenario for your industry and that disruption scenarios going to involve automation, so you better get ahead of editor game. They're The book is available, of course, at amazon dot com. You can get more information. X censure dot com slash automation advantage. Gosh, thanks so much for coming in the Cube. Really appreciate your time. >>Thank you. Thank >>you. >>Eh? Thank you for watching this episode of the eight of US Executive Summit of reinvent made possible by Accenture. Keep it right there for more discussions that educating spy inspire You're watching the queue.

>>Hi, Felix. Great to be here. >>Likewise. Um, so when I started reading about data mesh, I think about a year ago, I found myself the more I read about it, the more I find myself agreeing with other principles behind data mesh, it actually took me back to almost the starting of Colibra 13 years ago, based on the research we were doing on semantic technologies, even personally my own master thesis, which was about domain driven ontologies. And we'll talk about domain-driven as it's a key principle behind data mesh, but before we get into that, let's not assume that everybody knows what data measures about. Although we've seen a lot of traction and momentum, which is fantastic to see, but maybe if you could start by talking about some of the key principles and, and a brief overview of what data mesh, uh, Isabella of >>Course, well, they're happy to, uh, so Dana mesh is an approach is a new approach. It's a decentralized, decentralized approach to managing and accessing data and particularly analytical data at scale. So we can break that down a little bit. What is analytical data? Well, analytical data is the data that fuels our reporting as a business intelligence. Most importantly, the machine learning training, right? So it's the data, that's, it's an aggregate view of historical events that happens across organizations, many domains within organizations, or even beyond one organization, right? Um, and today we manage, uh, this analytical data through very centralized solutions. So whether it's a data lake or data warehouse or combinations of the two, and, uh, to be honest, we have kind of outsource the accountability for it, to the data team, right? It doesn't happen within the domains. Uh, what we have found ourselves with is, uh, central button next. >>So as we see the growth in the scale of organizations, in terms of the origins of the data and in terms of the great expectations for the data, all of these wonderful use cases that are, that requires access to that, unless we're data, uh, we find ourselves kind of constraints and limited in agility to respond, you know, because we have a centralized bottleneck from team to technology, to architecture. So there's a mesh kind of is that looks at the past what we've done, accidental complexity that we've kind of created and tries to reimagine a different way of, uh, managing and accessing data that can truly scale as this origins of the data grows. As they become available within one organization, we didn't want a cloud or another, and it links down really the approach based on four principles. Uh, so I so far, I haven't tried to be prescriptive as exactly how you implement it. >>I leave that to Elizabeth, to the imaginations of the users. Um, of course I have my opinions, but, but without being prescriptive, I think there are full shifts that needs to happen. One is, uh, we need to start breaking down the, kind of this complex problem of accessing to data around boundaries that can allow this to scale out a solution. So boundaries that are, that naturally fits into that model or domains, right. Our business domain. So, so there's a first principle is the domain ownership of the data. So analytical data will be shared and served and accountable, uh, by the domains where they come from. And then the second dimension of that is, okay. So once we break down this, the ownership of the database on domains, how can we prevent this data siloing? So the second principle is really treating data as a product. >>So considering the success of that data based on the access and usability and the lifelong experience of data analysts, data scientists. So we talk about data as a product and that the third principle is to really make it possible feasible. We need to really rethink our data platforms, our infrastructure capabilities, and create a new set ourselves of capabilities that allows domain in fact, to own their data in fact, to manage the life cycle of their analytical data. So then self-serve daytime frustration and platform is the fourth principle. And the last principle is really around governance because we have to think about governance. In fact, when I first wrote it down, this was like a little kind of concern in, in embedded in what some of my texts and I thought about, okay, now to make this real, we need to think about securing and quality of the data accessibility of the data at scale, in a fashion that embraces this autonomous domain ownership. So we have to think about how can we make this real with competition of governance? How can we make those domains be part of the governance, federated governance, federally, the competition of governance is the fourth principle. So at insurance it's a organizational shift, it's an architectural change. And of course technology needs to change to get us to decentralize access and management of Emily's school data. >>Yeah, I think that makes a ton of sense. If you want to scale, typically you have to think much more distributed versus centralized at we've seen it in other practices as well, that domain-driven thinking as well. I think, especially around engineering, right? We've seen a lot of the same principles and best practices in order to scale engineering teams and not make the same mistakes again, but maybe we can start there with kind of the core principles around that domain driven thinking. Can you elaborate a little bit on that? Why that is so important than the kind of data organizations, data functions as well? >>Absolutely. I mean, if you look at your organizations, organizations are complex systems, right? There are eight made of parts, which are basically domains functions of the business, your automation and your customer management, yourselves marketing. And then the behavior of the organization is the result of an intuitive, you know, network of dependencies and interactions with these domains. So if we just overlay data on this complex system, it does make sense to really, to scale, to bring the ownership and, um, really access to data right at the domain where it originates, right. But to the people who know that data best and most capable of providing that data. So to optimize response, to change, to optimize creating new features, new services, new machine learning models, we've got to kind of think about your call optimization, but not that the cost of global good. Right. Uh, so the domain ownership really talks about giving autonomy to the domains and accountability to provide their data and model the data, um, in a responsible way, be accountable for its quality. >>So no collect some of the empower them and localize some of those responsibilities, but at the same time, you know, thinking about the global goods, so what are they, how that domain needs to be accountable against the other domains on the mission? That's the governance piece covers that. And that leads to some interesting kind of architectural shifts, because when you think about not submission of the data, then you think about, okay, if I have a machine learning model that needs, you know, three pieces of the data from the different domains, I ended up actually distributing the computer also back to those domains. So it actually starts shifting kind of architectural as well. We start with ownership. Yeah, >>No, I think that makes a ton of sense, but I can imagine people thinking, well, if you're organizing, according to these domains, aren't gonna be going to grades different silos, even more silos. And I think that's where it second principle that's, um, think of data as a product and it comes in, I think that's incredibly powerful in my mind. It's powerful because it helps us think about usability. It helps us think about the consumer of that data and really packaging it in the right way. And as one sentence that I've heard you use that I think is incredibly powerful, it's less collecting, more connecting. Um, and can you elaborate on that a little bit? >>Absolutely. I mean the power and the value of the data is not enhanced, which we have got and stored on this, right. It's really about connecting that data to other data sets to aluminate new insights. The higher order information is connecting that data to the users, right. Then they want to use it. So that's why I think, uh, if we shift that thinking from just collecting more in one place, like whatever, and ability to connect datasets, then, then arrive at a different solution. So, uh, I think data as a product, as you said, exactly, was a kind of a response to the challenges that domain-driven siloing could create. And the idea is that the data that now these domains own needs to be shared with some accountability and incentive structure as a product. So if you bring product thinking to data, what does that mean? >>That means delighting the experience that there are users who are they, they're the data analysts, data scientists. So, you know, how can we delight their experience of their journey starts with a hypothesis. I have a question. Do I have right data to answer this question with a particular model? Let me discover it, let me find it if it's useful. Do I trust it? So really fascinated in that journey? I think we have two choices in that we have the choice of source of that data. The people who are really shouldn't be accountable for it, shrug off the responsibility and say, you know, I dumped this data on some event streaming and somebody downstream, the governance or data team will take care of a terror again. So it usable piece of information. And that's what we have done for, you know, half century almost. And, or let's say let's bring intention of providing quality data back to the source and make the folks both empower them and make them accountable for providing that data right at the source as a product. And I think by being intentional about that, um, w we're going to remove a lot of accidental complexity that we have created with, you know, labyrinth pipelines of moving data from one place to another, and try to build quality back into it. Um, and that requires, you know, architectural shifts, organizational shifts, incentive models, and the whole package, >>The hope is absolutely. And we'll talk about that. Federated computational governance is going to be a really an important aspect, but the other part of kind of data as a product next to usability is whole trust. Right? If you, if you want to use it, why is also trusts so important if you think about data as a product? >>Well, uh, I mean, maybe we turn this question back to you. Would you buy the shiniest product if you don't trust it, if you, if you don't trust where it comes from, can I use it? Is it, does it have integrity? I wouldn't. I think, I think it's almost irresponsible to use the data that you can trust, right. And the, really the meaning of the trust is that, do I know enough about this data to, to, for it, to be useful for the purpose that I'm using it for? So, um, I think trust is absolutely fundamental to, as a fundamental characteristics of a data as a product. And again, it comes back to breaching the gap between what the data user knows needs to know to really trust them, use that data, to find it, whether it's suitable and what they know today. So we can bridge that gap with, uh, you know, adding documentation, adding SLRs, adding lineage, like all of these additional information, but not only that, but also having people that are accountable for providing that integrity and those silos and guaranteeing. So it's really those product owners. So I think, um, it's just, for me, it's a non trust is a non-negotiable characteristic of the data as a product, like any other consumer product. >>Exactly. Like you said, if you think about consumer product, consumer marketplace is almost Uber of Amazon, of Airbnb. You have the simple rating as a very simple way of showing trust and those two and those different stakeholders and that almost. And we also say, okay, how do we actually get there? And I think data measure also talks a little bit about the roles responsibilities. And I think the importance overall of a, of a data product owner probably is aligned with that, that importance and trust. Yeah, >>Absolutely. I think we can't just wish for these good things happens without putting the accountability and the right roles in place. And the data product owner is just the starting point for us to stop playing hot potato. When it comes to, you know, who owns the data will be accountable for not so much. Who's the actual owner of that data because the owner of the data is you and me where the data comes really from, but it's the data product owner who's going to be responsible for the life cycle of this. They know when the data gets changed with consumers, meaning you feel as a new information, make sure that that gets carried out and maybe one day retire that data. So that long term ownership with intimate understanding of the needs of the user for that data, as well as the data itself and the domain itself and managing the life cycle of that, uh, I think that's a, that's a necessary role. >>Um, and then we have to think about why would anybody want to be a data product owner, right? What are the incentives we have to set up in the infrastructure, you know, in the organization. Um, and it really comes down to, I think, adopting prior art that exists in the product ownership landscape and bring it really to the data and assume the data users as the, as the customers, right. To make them happy. So our incentives on KPIs for these people before they get product on it needs to be aligned with the happiness of their data users. >>Yep. I love that. The alignment again, to the consumer using things like we know from product management, product owner of these roles and reusing that for data, I think that makes it makes a ton of sense. And it's a good leeway to talk a little about governance, right? We mentioned already federated governance, computational governance at we seeing that challenge often with our customers centralizing versus decentralizing. How do we find the right balance? Can you talk a little bit about that in the context of data mesh? How do we, how do we do this? >>Yeah, absolutely. I think the, I was hoping to pack three concepts in the title of the governance, but I thought that would be quite mouthful. So, uh, as you mentioned, uh, the kind of that federated aspects, the competition aspects, and I think embedded governance, I would, if I could add another kind of phrasing there and really it's about, um, as we talked about to how to make it happen. So I think the Federation matters because the people who are really in a position listed this, their product owners in a position to provide data in a trustworthy, with integrity and secure way, they have to have a stake in doing that, right. They have to be accountable, not just for their little domain or a big domain, but also they have to have an accountability for the mesh. So some of the concerns that are applied to all of the data front, I've seen fluid, how we secure them are consistently really secure them. >>How do we model the data or the schema language or the SLO metrics, or that allows this, uh, data to be interoperable so we can join multiple data products. So we have to have, I think, a set of policies that are really minimum set of policies that we have to apply globally to all the data products and then in a federated fashion, incentivize the data product owners. So have a stake in that and make that happen because there's always going to be a challenge in prioritizing. Would I add another few attributes? So my data sets to make my customers happy, or would I adopt that this standardized modeling language, right? They have to make that kind of continuous, um, kind of prioritization. Um, and they have to be incentivized to do both. Right. Uh, and then the other piece of it is okay, if we want to apply these consistent policies, across many data products and the mesh, how would it be physically possible? >>And the only way I can see, and I have seen it done in service mesh would be possible is by embedding those policies as competition, as code into every single data product. And how do we do that again, platform has a big part of it. So be able to have this embedded policy engines and whatever those things are into the data products, uh, and to, to be able to competition. So by default, when you become a data product, as part of the scaffolding of that data product, you get all of these, um, kind of computational capabilities to configure your, your policies according to the global policies. >>No, that makes sense. That makes, that makes it on a sense. That makes sense. >>I'm just curious. Really. So you've been at this for a while. You've built this system for the 13 years came from kind of academic background. So, uh, to be honest, we run into your products, lots of our clients, and there's always like a chat conversation within ThoughtWorks that, uh, do you guys know about this product then? So and so, oh, I should have curious, well, how do you think data governance tehcnology then skip and you need to shift with data mesh, right. And, and if, if I would ask, how would your roadmap changes with database? >>Yeah, I think it's a really good question. Um, what I don't want to do is to make, make the mistake that Venice often make and think of data mesh as a product. I think it's a much more holistic mindset change, right? That that's organization. Yes. It needs to be a kind of a platform enablement component there. And we've actually, I think authentically what, how we think about governance, that's very aligned with some of the principles and data measures that federate their thinking or customers know about going to communities domains or operating model. We really support that flexibility. I think from a roadmap perspective, I think making that even easier, uh, as always kind of a, a focus focus area for us, um, specifically around data measures are a few things that come to mind. Uh, one, I think is connectivity, right? If you, if you give different teams more ownership and accountability, we're not going to live in a world where all of the data is going to be stored on one location, right? >>You want to give people themes the opportunity and the accountability to make their own technology decisions so that they are fit for purpose. So I think whatever platform being able to really provide out of the box connectivity to a very wide, um, area or a range of technologies, I think is absolutely critical, um, on the, on the product as a or data as a product, thinking that usability, I think that's top of mind, uh, that's part of our roadmap. You're going to hear us, uh, stock about that tomorrow as well. Um, that data consumer, how do we make it as easy as possible for people to discover data that they can trust that they can access? Um, and in that thinking is a big part of our roadmap. So again, making that as easy as possible, uh, is a, is a big part of it. >>And, and also on the, I think the computation aspect that you mentioned, I think we believe in as well, if, if it's just documentation is going to be really hard to keep that alive, right? And so you have to make an active, we have to get close to the actual data. So if you think about a policy enforcement, for example, some things we're talking about, it's not just definition is the enforcement data quality. That's why we are so excited about our or data quality, um, acquisition as well. Um, so these are a couple of the things that we're thinking of, again, your, your, um, your, your, uh, message around from collecting to connecting. We talk about unity. I think that that works really, really well with our mission and vision as well. So mark, thank you so much. I wish we had more time to continue the conversation, uh, but it's been great to have a conversation here. Thank you so much for being here today and, uh, let's continue to work on that on data. Hello. I'm excited >>To see it. Just come to like.

>>Welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. We're here with Amanda Silver, corporate vice president, product developer division at Microsoft. Amanda, Great to see you you were on last year, Dr khan. Great to see you again a full year later were remote. Thanks for coming on. I know you're super busy with build happening this week as well. Thanks for making the time to come on the cube for Dr khan. >>Thank you so much for having me. Yeah, I'm joining you like many developers around the globe from my personal home office, >>developers really didn't skip a beat during the pandemic and again, it was not a good situation but developers, as you talked about last year on the front lines, first responders to creating value quite frankly, looking back you were pretty accurate in your prediction, developers did have an impact this year. They did create the kind of change that really changed the game for people's lives, whether it was developing solutions from a medical standpoint or even keeping systems running from call centres to making sure people got their their their goods or services and checks and and and kept sanity together. So. >>Yeah absolutely. I mean I think I think developers you know get the M. V. P. Award for this year because you know at the end of the day they are the digital first responders to the first responders and the pivot that we've had to make over the past year in terms of supporting remote telehealth, supporting you know online retail, curbside pickup. All of these things were done through developers being the ones pushing the way forward remote learning. You know my kids are learning at home right behind me right now so you might hear them during the interview that's happening because developers made that happen. >>I don't think mom please stop hogging the band with, they've got a gigabit. Stop it. Don't be streaming. My kids are all game anyway, Hey, great to have you on and you have to get the great keynote, exciting to see you guys continue the collaboration with Docker uh with GIT hub and Microsoft, A great combination, it's a 123 power punch of value. You guys are really kind of killing it. We heard from scott and dan has been on the cube. What's your thoughts on the partnership with the developer division team at Microsoft with Doctor, What's it all about this year? What's the next level? >>Well, I mean, I think, I think what's really awesome about this partnership is that we all have, we all are basically sharing a common mission. What we want to do is make sure that we're empowering developers, that we're focused on their productivity and that we're delivering value to them so they can do their job better so that they can help others. So that's really kind of what drives us day in and day out. So what we focus on is developer productivity. And I think that's a lot of what dana was talking about in her session, the developer division. Specifically, we really try to make sure that we're improving the state of the art from modern developers. So we want to make sure that every keystroke that they take, every mouse move that they make, it sounds like a song but every every one of those matter because we want to make sure that every developers writing the code that only they can write and in terms of the partnership and how that's going. You know my team and the darker team have been collaborating a ton on things like dr desktop and the Doctor Cli tool integrations. And one of the things that we do is we think about pain points and various workflows. We want to make sure that we're shaving off the edges of all of the user experience is the developers have to go through to piece all of these applications together. So one of the big pain points that we have heard from developers is that signing into the Azure cloud and especially our sovereign clouds was challenging. So we contributed back to uh back to doctor to actually make it easier to sign into these clouds. And so dr developers can now use dr desktop and the Doctor Cli to actually change the doctor context so that its Azure. So that makes it a lot easier to connect the other. Oh, sorry, go ahead. No, I was just >>going to say, I love the reference of the police song. Every breath you take, every >>mouth moving. Great, >>great line there. Uh, but I want to ask you while you're on this modern cloud um, discussion, what is I mean we have a lot of developers here at dr khan. As you know, you guys know developers in your ecosystem in core competency. From Microsoft, Kublai khan is a very operator like focus developed. This is a developer conference. You guys have build, what is the state of the art for a modern cloud developer? Could you just share your thoughts because this comes up a lot. You know, what's through the art? What's next jan new guard guard? It's his legacy. What is the state of the art for a modern cloud developer? >>Fantastic question. And extraordinarily relevant to this particular conference. You know what I think about often times it's really what is the inner loop and the outer loop look like in terms of cycle times? Because at the end of the day, what matters is the time that it takes for you to make that code change, to be able to see it in your test environment and to be able to deploy it to production and have the confidence that it's delivering the feature set that you need it to. And it's, you know, it's secure, it's reliable, it's performance, that's what a developer cares about at the end of the day. Um, at the same time, we also need to make sure that we're growing our team to meet our demand, which means we're constantly on boarding new developers. And so what I take inspiration from our, some of the tech elite who have been able to invest significant amounts in, in tuning their engineering systems, they've been able to make it so that a new developer can join a team in just a couple of minutes or less that they can actually make a code change, see that be reflected in their application in just a few seconds and deploy with confidence within hours. And so our goal is to actually be able to take that state of the art metric and democratize that actually bring it to as many of our customers as we possibly can. >>You mentioned supply chain earlier in securing that. What are you guys doing with Docker and how to make that partnership better with registries? Is there any update there in terms of the container registry on Azure? >>Yeah, I mean, you know, we, we we have definitely seen recent events and and it almost seems like a never ending attacks that that you know, increasingly are getting more and more focused on developer watering holes is how we think about it. Kind of developers being a primary target um for these malicious hackers. And so what it's more important than ever that every developer um and Microsoft especially uh really take security extraordinarily seriously. Our engineers are working around the clock to make sure that we are responding to every security incident that we hear about and partnering with our customers to make sure that we're supporting them as well. One of the things that we announced earlier this week at Microsoft build is that we've actually taken, get have actions and we've now integrated that into the Azure Security Center. And so what this means is that, you know, we can now do things like scan for vulnerabilities. Um look at things like who is logging in, where things like that and actually have that be tracked in the Azure security center so that not just your developers get that notification but also your I. T. Operations. Um In terms of the partnership with dR you know, this is actually an ongoing partnership to make sure that we can provide more guidance to developers to make sure that they are following best practices like pulling from a private registry like Docker hub or at your container registry. So I expect that as time goes on will continue to more in partnership in this space >>and that's going to give a lot of confidence. Actually, productivity wise is going to be a big help for developers. Great stuff is always good, good progress. They're moving the needle. >>Last time we >>spoke we talked about tools and setting Azure as the doctor context duty tooling updates here at dot com this year. That's notable. >>Yeah, I mean, I think, you know, there's one major thing that we've been working on which has a big dependency on docker is get help. Code space is now one of the biggest pain points that developers have is setting up a new DEV box, which they often have to do when they are on boarding a new employee or when they're starting a new project or even if they're just kicking the tires on a new technology that they want to be able to evaluate and sometimes creating a developer environment can actually take hours um and especially when you're trying to create a developer environment that matches somebody else's developer environment that can take like a half a day and you can spend all of your time just debugging the differences in environment variables, for example, um, containers actually makes that much easier. So what you can do with this, this services, you can actually create death environment spun up in the cloud and you can access it in seconds and you get from there are working coding environment and a runtime environment and this is repeatable via containers. So it means that there's no inadvertent differences introduced by each DEV. And you might be interested to know that underneath this is actually using Docker files and dr composed to orchestrate the debits and the runtime bits for a whole bunch of different stacks. And so this is something that we're actually working on in collaboration with the with the doctor team to have a common the animal format. And in fact this week we actually introduced a couple of app templates so that everybody can see this all in action. So if you check out a ca dot m s forward slash app template, you can see this in action yourself. >>You guys have always had such a strong developer community and one thing I love about cloud as it brings more agility, as we always talk about. But when you start to see the enterprise grow into, the direction is going now, it's almost like the developer communities are emerging, it's no longer about all the Lennox folks here and the dot net folks there, you've got windows, you've got cloud, >>it's almost >>the the the solidification of everyone kind of coming together. Um and visual studio, for instance, last year, I think you were talking about that to having to be interrogated dr composed, et cetera. >>How do you see >>this melting pot emerging? Because at the end of the day, you pick the language you love and you got devops, which is infrastructure as code doesn't matter. So give us your take on where we are with that whole progress of of making that happen. >>Well, I mean I definitely think that, you know, developer environments and and kind of, you know, our approach to them don't need to be as dogmatic as they've been in the past. I really think that, you know, you can pick the right tool and language and stand developer stack for your team, for your experience and you can be productive and that's really our goal. And Microsoft is to make sure that we have tools for every developer and every team so that they can build any app that they want to want to create. Even if that means that they're actually going to end up ultimately deploying that not to our cloud, they're going to end up deploying it to AWS or another another competitive cloud. And so, you know, there's a lot of things that we've been doing to make that really much easier. We have integrated container tools in visual studio and visual studio code and better cli integrations like with the doctor context that we had talked about a little bit earlier. We continue to try to make it easier to build applications that are targeting containers and then once you create those containers it's much easier to take it to another environment. One of the examples of this kind of work is now that we have WsL and the Windows subsystem for Lennox. This makes it a lot easier for developers who prefer a Windows operating system as their environment and maybe some tools like Visual Studio that run on Windows, but they can still target Lennox with as their production environment without any impedance mismatch. They can actually be as productive as they would be if they had a Linux box as their Os >>I noticed on this session, I got to call this out. I want to get your reaction to it interesting. Selection of Microsoft talks, the container based development. Visual studio code is one that's where you're going to show some some some container action going on with note and Visual Studio code. And then you get the machine learning with Azure uh containers in the V. S. Code. Interesting how you got, you know, containers with V. S. And now you've got machine learning. What does that tell the world about where Microsoft's at? Because in a way you got the cutting edge container management on one side with the doctor integration. Now you get the machine learning which everyone's talking about shifting, left more automation. Why are these sessions so important? Why should people attend? And what's the what's the bottom line? >>Well, like I said, like containers basically empower developer productivity. Um that's what creates the reputable environments, that's what allows us to make sure that, you know, we're productive as soon as we possibly can be with any text act that we want to be able to target. Um and so that's kind of almost the ecosystem play. Um it's how every developer can contribute to the success of others and we can amor ties the kinds of work that we do to set up an environment. So that's what I would say about the container based development that we're doing with both visual studio and visual studio code. Um in terms of the machine learning development, uh you know, the number of machine learning developers in the world is relatively small, but it's growing and it's obviously a very important set of developers because to train a machine learning uh to train an ml model, it actually requires a significant amount of compute resources, and so that's a perfect opportunity to bring in the research that are in a public cloud. Um What's actually really interesting about that particular develop developer stack is that it commonly runs on things like python. And for those of you who have developed in python, you know, just how difficult it is to actually set up a python environment with the right interpreter, with the right run time, with the right libraries that can actually get going super quickly, um and you can be productive as a developer. And so it's actually one of the hardest, most challenging developer stacks to actually set up. And so this allows you to become a machine learning developer without having to spend all of your time just setting up the python runtime environment. >>Yeah, it's a nice, nice little call out on python, it's a double edged sword. It's easier to sling code around on one hand, when you start getting working then you gotta it gets complicated can get well. Um Well the great, great call out there on the island, but good, good, good project. Let me get your thoughts on this other tool that you guys are talking about project tie. Uh This is interesting because this is a trend that we're seeing a lot of conversations here on the cube about around more too many control planes. Too many services. You know, I no longer have that monolithic application. I got micro micro applications with microservices. What the hell is going on with my services? >>Yeah, I mean, I think, you know, containers brought an incredible amount of productivity in terms of having repeatable environments, both for dev environments, which we talked about a lot on this interview already, but also obviously in production and test environments. Super important. Um and with that a lot of times comes the microservices architecture that we're also moving to and the way that I view it is the microservices architecture is actually accompanied by businesses being more focused on the value that they can actually deliver to customers. And so they're trying to kind of create separations of concerns in terms of the different services that they're offering, so they can actually version and and kind of, you know, actually improve each of these services independently. But what happens when you start to have many microservices working together in a SAS or in some kind of aggregate um service environment or kind of application environment is it starts to get unwieldy, it's really hard to make it so that one micro service can actually address another micro service. They can pass information back and forth. And you know what used to be maybe easy if you were just building a client server application because, you know, within the server tear all of your code was basically contained in the same runtime environment. That's no longer the case when every microservices actually running inside of its own container. So the question is, how can we improve program ability by making it easier for one micro service that's being used in an application environment, be to be able to access another another service and kind of all of that context. Um and so, you know, you want to be able to access the service is the the api endpoint, the containers, the ingress is everything, make everything work together as though it felt just as easy as as um you know, server application development. Um And so what this means as well is that you also oftentimes need to get all of these different containers running at the same time and that can actually be a challenge in the developer and test loop as well. So what project tie does is it improves the program ability and it actually allows you to just write a command like thai run so that you can actually in stan she ate all of these containers and get them up and running and basically deploy and run your application in that environment and ultimately make the dev testing or loop much faster >>than productivity gain. Right. They're making it simple to stand up. Great, great stuff. Let me ask you a question as we kind of wrap down here for the folks here at Dakar Con, are >>there any >>special things you'd like to talk about the development you think are important for the developers here within this space? It's very dynamic. A lot of change happening in a good way. Um, but >>sometimes it's hard to keep >>track of all the cool stuff happening. Could you take a minute to, to share your thoughts on what you think are the most important develops developments in this space? That that might be interesting to ducker con attendees. >>I think the most important things are to recognize that developer environments are moving to containerized uh, environments themselves so that they can be repeated, they can be shared, the work, configuring them can be amortized across many developers. That's important thing. Number one important thing. Number two is it doesn't matter as much what operating system you're running as your chrome, you know, desktop. What matters is ultimately the production environment that you're targeting. And so I think now we're in a world where all of those things can be mixed and matched together. Um and then I think the next thing is how can we actually improve microservices, uh programming development together um so that it's easier to be able to target multiple micro services that are working in aggregate uh to create a single service experience or a single application. And how do we improve the program ability for that? >>You know, you guys have been great supporters of DACA and the community and open source and software developers as they transform and become quite frankly the superheroes for the transformation, which is re factoring businesses. So this has been a big thing. I'd love to get your thoughts on how this is all coming together inside Microsoft, you've got your division, you get the developer division, you got GIT hub, got Azure. Um, and then just historically, and he put this up last year army of an ecosystem. People who have been contributing encoding with Microsoft and the partners for many, many decades. >>Yes. The >>heart Microsoft now, how's it all working? What's the news? I get Lincoln, Lincoln, but there's no yet developer model there yet, but probably is soon. >>Um Yeah, I mean, I think that's a pretty broad question, but in some ways I think it's interesting to put it in the context of Microsoft's history. You know, I think when I think back to the beginning of my career, it was kind of a one stack shop, you know, we was all about dot net and you know, of course we want to dot net to be the best developer environment that it can possibly be. We still actually want that. We still want that need to be the most productive developer environment. It could we could possibly build. Um but at the same time, I think we have to recognize that not all developers or dot net developers and we want to make sure that Azure is the most productive cloud for developers and so to do that, we have to make sure that we're building fantastic tools and platforms to host java applications, javascript applications, no Js applications, python applications, all of those things, you know, all of these developers in the world, we want to make sure it can be productive on our tools and our platforms and so, you know, I think that's really kind of the key of you know what you're speaking of because you know, when I think about the partnership that I have with the GIT hub team or with the Azure team or with the Azure Machine learning team or the Lincoln team, um A lot of it actually comes down to helping empower developers, improving their productivity, helping them find new developers to collaborate with, um making sure that they can do that securely and confidently and they can basically respond to their customers as quickly as they possibly can. Um and when, when we think about partnering inside of Microsoft with folks like linkedin or office as an example, a lot of our partnership with them actually comes down to improving their colleagues efficiency. We build the developer tools that office and lengthen are built on top of and so every once in a while we will make an improvement that has, you know, 5% here, 3% there and it turns into an incredible amount of impact in terms of operations, costs for running these services. >>It's interesting. You mentioned earlier, I think there's a time now we're living in a time where you don't have to be dogmatic anymore, you can pick what you like and go with it. Also that you also mentioned just now this idea of distributed applications, distributed computing. You know, distributed applications and microservices go really well together. Especially with doctor. >>Can you share >>your thoughts on the framework that you guys released called Dapper? >>Yeah, yeah. We recently released Dapper. It's called D A P R. You can look it up on GIT hub and it's a programming model for common microservices pattern, two common microservices patterns that make it really easy and automatic to create those kinds of microservices. So you can choose to work with your favorite state stores or databases or pub sub components and get things like cloud events for free. You can choose either http or g R B C so that you can get mesh capabilities like service discovery and re tries and you can bring your own secret store and easily be able to call it from any environment variable. It's also like I was talking about earlier, multi lingual. Um so you don't need to embrace dot net, for example, as you're programming language to be able to benefit from Dapper, it actually supports many programming languages and Dapper itself is actually written and go. Um and so, you know, all developers can benefit from something like Dapper to make it easier to create microservices applications. >>I mean, always great to have you on great update. Take a minute to give an update on what's going on with your division. I know you had to build conference this week. V. S has got the new preview title. We just talked about what are the things you want to get to plug in for? Take a minute to get to plug in for what you're working on, your goals, your objectives hiring, give us the update. >>Yeah, sure. I mean, you know, we we built integrated container tools in visual studio uh and the Doctor extension and Visual Studio code and cli extensions. Uh and you know, even in this most recent release of our Visual Studio product, Visual Studio 16 10, we added some features to make it easier to use DR composed better. So one of the examples of this is that you can actually have uh Oftentimes you need to be able to use multiple doctor composed files together so that you can actually configure various different container environments for a single single application. But it's hard sometimes to create the right Yeah. My file so that you can actually invoke it and invoke the the container and the micro services that you need. And so what this allows you to do is to actually have just a menu of the different doctor composed files so that you can select the runtime and test environment that you need for the subset of the portion of the application that you're working on at the end of the day. This is always about developer productivity. You know, like I said, every keystroke matters. Um and we want to make sure that you as a developer can focus on the code that only you can Right. >>Amanda Silver, corporate vice president product development division of Microsoft. Always great to see you and chat with you remotely soon. We'll be back in in real life with real events soon as we come out of the pandemic and thanks for sharing your insight and congratulations on your success this year and and congratulations on your announcement here at Dakar Gone. >>Thank you so much for having me. >>Okay Cube coverage for Dunkirk on 2021. I'm John for your host of the Cube. Thanks for watching. Mhm

>>Hello and welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. Great guests here cube alumni Stephen Chin, vice president of developer relations for jay frog Stephen, great to see you again this remote this time this last time was in person. Our last physical event. We had you in the queue but great to see you. Thanks for coming in remotely. >>No, no, I'm very glad to be here. And also it was, it was awesome to be in person at our s a conference when we last talked and the last year has been super exciting with a whole bunch of crazy things like the I. P. O. And doing virtual events. So we've, we're transitioning to the new normal. We're looking forward to things getting to be hybrid. >>Great success with jay frog. We've been documenting the history of this company, very developer focused the successful I. P. O. And just the continuation that you guys have transitioned beautifully to virtual because you know, developer company, it runs virtual, but also you guys have been all about simplicity for developers and and we've been talking for many, many years with you guys on this. This is the theme that dr khan again, this is a developer conference, not so much an operator conference, but more of a deva deV developer focused. You guys have been there from the beginning, um nationally reported on it. But talk about jay Frog and the Doctor partnership and why is this event so important for you? >>Yeah. So I think um like like you said, jay Frog has and always is a developer focused company. So we we build tools and things which which focus on developer use cases, how you get your code to production and streamlining the entire devoPS pipeline. And one of the things which which we believe very strongly in and I think we're very aligned with with doctor on this is having secure clean upstream dependencies for your Docker images for other package and language dependencies and um you know, with the announcement of dr khan and dr Hubbs model changing, we wanted to make sure that we have the best integration with doctor and also the best support for our customers on with Docker hub. So one of the things we did strategically is um, we um combined our platforms so um you can get the best in class developer tools for managing images from Docker. Um everyone uses their um desktop tools for for building and managing your containers and then you can push them right to the best container registry for managing Docker Images, which is the jay frog platform. And just like Docker has free tools available for developers to use. We have a free tier which integrates nicely what their offerings and one of the things which we collaborate with them on is for anybody using our free tier in the cloud. Um there's there's no limits on the Docker images. You can pull no rate limiting, no throttling. So it just makes a clean seamless developer experience to to manage your cloud native projects and applications. >>What's the role of the container registry in cloud NATO? You brought that up? But can you just expand on that point? >>Yeah. So I think when you when you're doing deployments to production, you want to make sure both that you have the best security so that you're making sure that you're scanning and checking for vulnerabilities in your application and also that you have a complete um traceability. Basically you need a database in a log of everything you're pushing out to production. So what container registries allow you to do is um they keep all of the um releases all of the Docker images which are pushing out. You can go back and roll back to a previous version. You can see exactly what's included in those Docker images. And we jay frog, we have a product called X ray which does deep scanning of container images. So it'll go into the Docker Image, it'll go into any packages installed, it'll go into application libraries and it does kind of this onion peel apart of your entire document image to figure out exactly what you're using. Are there any vulnerabilities? And the funny thing about about Docker Images is um because of the number of libraries and packages and installed things which you haven't given Docker Image. If you just take your released Docker Image and let it sit on the shelf for a month, you have thousands of vulnerabilities, just just buy it um, by accruing from different reported zero day vulnerabilities over time. So it's extremely important that you, you know what those are, you can evaluate the risk to your organization and then mitigated as quickly as possible. If there is anything which could impact your customers, >>you bring up a great point right there and that is ultimately a developer thing that's been, that's generational, you know what generation you come from and that's always the problem getting the patches in the old days, getting a new code updated now when you have cloud native, that's more important than ever. And I also want to get your thoughts on this because you guys have been early on shift left two years ago, shift left was not it was not a new thing for you guys ever. So you got shift left building security at the point of coding, but you're bringing up a whole another thing which is okay automation. How do you make it? So the developments nothing stop what they're doing and then get back and say, okay, what's out there and my containers. So so how do you simplify that role? Because that's where the partnership, I think really people are looking to you guys and Dakar on is how do you make my life easier? Bottom line, what's it, what's it, what's it about? >>Yeah. So I I think when you when you're looking at trying to manage um large applications which are deployed to big kubernetes clusters and and how you have kind of this, this um all this infrastructure behind it. One of the one of the challenges is how do you know what you have that in production? Um So what, how do you know exactly what's released and what dependencies are out there and how easily can you trace those back? Um And one of the things which we're gonna be talking about at um swamp up next week is managing the overall devops lifecycle from code all the way through to production. Um And we we have a great platform for doing package management for doing vulnerability scanning, for doing um ci cd but you you need a bunch of other tools too. So you need um integrations like docker so you can get trusted packages into your system. You need integrations with observe ability tools like data, dog, elastic and you need it some tools for doing incident management like Patriot duty. And what we've, what we've built out um is we built out an ecosystem of partner integrations which with the J frog platform at the center lets you manage your entire and and life cycle of um devops infrastructure. And this this addresses security. It addresses the need to do quick patches and fixes and production and it kind of stitches together all the tools which all of the successful companies are using to manage their fast moving continuous release cycle, um and puts all that information together with seamless integration with even developer tools which um which folks are using on a day to day basis, like slack jeer A and M. S. Teams. >>So the bottom line then for the developer is you take the best of breed stuff and put it, make it all work together easily. That right? >>Yeah. I mean it's like it's seamless from you. You've got an incidents, you click a button, it sticks Ajira ticket in for you to resolve. Um you can tie that with the code, commits what you're doing and then directly to the security vulnerability which is reported by X ray. So it stitches all these different tools and technologies together for a for a seamless developer experience. And I think the great relationship we have with Docker um offers developers again, this this best in class container management um and trusted images combined with the world's best container registry. >>Awesome. Well let's get into that container issue products. I think that's the fascinating and super important thing that you guys solve a big problem for. So I gotta ask you, what are the security risks of using unverified and outdated Docker containers? Could you share your thoughts on what people should pay attention to because if they got unverified and outdated Docker containers, you mentioned vulnerabilities. What are those specific risks to them? >>Yeah, so I there's there's a lot of um different instances where you can see in the news or even some of the new government mandates coming out that um if you're not taking the right measures to secure your production applications and to patch critical vulnerabilities and libraries you're using, um you end up with um supply chain vulnerability risks like what happened to solar winds and what's been fueling the recent government mandates. So I think there's a there's a whole class of of different vulnerabilities which um bad actors can exploit. It can actually go quite deep with um folks um exploiting application software. Neither your your company or in other people's systems with with the move to cloud native, we also have heavily interconnected systems with a lot of different attack points from the container to the application level to the operating system level. So there's multiple different attack vectors for people to get into your software. And the best defense is an organization against security. Vulnerabilities is to know about them quickly and to mitigate them and fix them in production as quickly as possible. And this requires having a fast continuous deployment strategy for how you can update your code quickly, very quick identification of vulnerabilities with tools like X ray and other security scanning tools, um and just just good um integration with tools developers are using because at the end of the day it's the developers who both are picking the libraries and dependencies which are gonna be pushed into production and also they're the ones who have to react and and fix it when there's a uh production incident, >>you know, machine learning and automation. And it's always, I love that tech because it's always kind of cool because it's it's devops in action, but you know, it's it's not like a silver bullet, your machine, your machine learning is only as good as your your data and the code is written on staying with automation. You're not automating the right things or or wrong things. It's all it's all subjective based on what you're doing and you know Beauty's in the eye of the beholder when you do things like that. So I wanna hear your thoughts on on automation because that's really been a big part of the story here, both on simplicity and making the load lighter for developers. So when you have to go out and look at modifying code updates and looking at say um unverified containers or one that gets a little bit of a hair on it with with with more updates that are needed as we say, what do you what's the role of automation? How do you guys view that and how do you talk to the developers out there when posturing for a strategy on and a playbook for automation? >>Yeah, I think you're you're touching on one of the most critical parts of of any good devops um platform is from end to end. Everything should be automated with the right quality gates inserted at different points so that if there's a um test failure, if you have a build failure, if you have a security vulnerability, the the automatic um points in there will be triggered so that your release process will be stopped um that you have automated rollbacks in production um so that you can make sure that their issues which affect your customers, you can quickly roll back and once you get into production um having the right tools for observe ability so that you can actually sift through what is a essentially a big data problem. So with large systems you get so much data coming back from your application, from the production systems, from all these different sources that even an easy way to sift through and identify what are the messages coming back telling you that there's a problem that there's a real issue that you need to address versus what's just background noise about different different processes or different application alerts, which really don't affect the security of the functionality of your applications. So I think this this end to end automation gives you the visibility and the single pane of glass to to know how to manage and diagnose your devops infrastructure. >>You know, steve you bring up a great point. I love this conversation because it always highlights to me why I love uh Coop Con and Cloud Native con part of the C N C F and dr khan, because to me it's like a microcosm of two worlds that are living together. Right? You got I think Coop khan has proven its more operated but not like operator operator, developer operators. And you got dr khan almost pure software development, but now becoming operators. So you've got that almost those two worlds are fusing together where they are running together. You have operating concerns like well the Parachute open, will it work? And how do I roll back these roll back? These are like operating questions that now developers got to think about. So I think we're seeing this kind of confluence of true devops next level where you can't you can be just a developer and have a little bit of opposite you and not be a problem. Right? Or or get down under the under the hood and be an operator whenever you want. So they're seeing a flex. What's your thoughts on this is just more about my observation kind of real time here? >>Yeah, so um I think it's an interesting, obviously observation on the industry and I think you know, I've been doing DEVOPS for for a long time now and um I started as a developer who needed to push to production, needed to have the ability to to manage releases and packages and be able to automate everything. Um and this naturally leads you on a path of doing more operations, being able to manage your production, being able to have fewer incidents and issues. Um I think DEVOPS has evolved to become a very complicated um set of tools and problems which it solves and even kubernetes as an example. Um It's not easy to set up like setting up a kubernetes cluster and managing, it is a full time job now that said, I think what you're seeing now is more and more companies are shifting back to developers as a focus because teams and developers are the kingmakers ends with the rise of cloud computing, you don't need a full operations team, you don't need a huge infrastructure stack, you can you can easily get set up in the cloud on on amazon google or as your and start deploying today to production from from a small team straight from code to production. And I think as we evolve and as we get better tools, simpler ways of managing your deployments of managing your packages, this makes it possible for um development teams to do that entire site lifecycle from code through to production with good quality checks with um good security and also with the ability to manage simple production incidents all by themselves. So I think that's that's coming where devoPS is shifting back to development teams. >>It's great to have your leadership and your experience. All right there. That's a great call out, great observation, nice gym there. I think that's right on. I think to get your thoughts if you don't mind going next level because you're, you're nailing what I see is the successful companies having these teams that could be and and workflows and have a mix of a team. I was talking about Dana Lawson who was the VP of engineering get up and she and I were riffing on this idea that you don't have to have a monolithic team because you've got you no longer have a monolithic environment. So you have this microservices and now you can have these, I'm gonna call micro teams, but you're starting to see an SRE on the team, that's the developer. Right? So this idea of having an SRE department maybe for big companies, that could be cool if you're hyper scalar, but these development teams are having certain formations. What's your observation to your customer base in terms of how your customers are organizing? Because I think you nailed the success form of how teams are executing because it's so much more agile, you get the reliability, you need to have security baked in, you want end to end visibility because you got services starting and stopping. How are teams? How are you seeing developers? What's the state of the art in your mind for formation? >>Yeah, so I think um we we work with a lot of the biggest companies who were really at the bleeding edge of innovation and devoPS and continuous delivery. And when you look at those teams, they have, they have very, very small teams, um supporting thousands of developers teams um building and deploying applications. So um when you think of of SRE and deVOPS focus there is actually a very small number of those folks who typically support humongous organizations and I think what we're hearing from them is their increasingly getting requirements from the teams who want to be self service, right? They want to be able to take their applications, have simple platforms to deploy it themselves to manage things. Um They don't they don't want to go through heavy way processes, they wanted to be automated and lightweight and I think this is this is putting pressure on deVOPS teams to to evolve and to adopt more platforms and services which allow developers to to do things themselves. And I think over time um this doesn't this doesn't get rid of the need for for devops and for SRE roles and organizations but it it changes because now they become the enablers of success and good development teams. It's it's kind of like um like how I. T. Organizations they support you with automated rollouts with all these tools rather than in person as much as they can do with automation. Um That helps the entire organization. I think devops is becoming the same thing where they're now simplifying and automating how developers can be self service and organizations. >>And I think it's a great evolution to because that makes total sense because it is kind of like what the I. T. Used to do in the old days but its the scale is different, the services are different, the deVOPS tools are different and so they really are enabling not just the cost center there really driving value. Um and this brings up the whole next threat. I'd love to get your thoughts because you guys are, have been doing this for developers for a while. Tools versus platform because you know, this whole platform where we're a platform were control plane, there's still a need for tooling for developers. How do we thread the needle between? What's, what's good for a tool? What's good for a platform? >>Yeah, So I I think that um, you know, there's always a lot of focus and it's, it's easier if you can take an end to end platform, which solves a bunch of different use cases together. But um, I I think a lot of folks, um, when you're looking at what you need and how you want to apply, um, devops practices to your organization, you ideally you want to be able to use best in breed tools to be able to solve exactly what your use cases. And this is one of the reasons why as a company with jay frog, we we try to be as open as possible to integrations with the entire vendor ecosystem. So um, it doesn't matter what ci cd tool you're using, you could be using Jenkins circle, ci spinnaker checked on, it doesn't matter what observe ability platform you're using in production, it doesn't matter what um tools you're using for collaboration. We, we support that whole ecosystem and we make it possible for you to select the the best of breed tools and technologies that you need to be successful as an organization. And I think the risk is if, if you, if you kind of accept vendor lock in on a single platform or or a single cloud platform even um then you're, you're not getting the best in breed tools and technologies which you need to stay ahead of the curve and devops is a very, very fast moving um, um, discipline along with all the cloud native technologies which you use for application development and for production. So if you're, if you're not staying at the bleeding edge and kind of pushing things forward, then you're then you're behind and if you're behind, you're not be able to keep up with the releases, the deployments, you need to be secure. So I think what you see is the leading organizations are pushing the envelope on on security, on deployment and they're they're using the best tools in the industry to make that happen. >>Stephen great to have you on the cube. I want to just get your thoughts on jay frog and the doctor partnership to wrap this up. Could you take them in to explain what's the most important thing that developers should pay attention to when it comes to security for Docker images? >>Yeah. So I think when you're when you're developer and you're looking at your your security strategy, um you want tools that help you that come to you and that help you. So you want things which are going to give you alerts in your I. D. With things which are going to trigger your in your Ci cd and your build process. And we should make it easy for you to identify mitigate and release um things which will help you do that. So we we provide a lot of those tools with jay frog and our doctor partnership. And I think if you if you look at our push towards helping developers to become more productive, build better applications and more secure applications, this is something the entire industry needs for us to address. What's increasingly a risk to software development, which is a higher profile vulnerabilities, which are affecting the entire industry. >>Great stuff. Big fan of jay frog watching you guys be so successful, you know, making things easy for developers is uh, and simpler and reducing the steps it takes to do things as a, I say, is the classic magic formula for any company, Make it easier, reduce the steps it takes to do something and make it simple. Um, good success formula. Great stuff. Great to have you on um for a minute or two, take a minute to plug what's going on in jay frog and share what's the latest increase with the company, what you guys are doing? Obviously public company. Great place to work, getting awards for that. Give the update on jay frog, put a plug in. >>Yeah. And also dr Frog, I've been having a lot of fun working at J frog, it's very, very fast growing. We have a lot of awesome announcements at swamp up. Um like the partnerships were doing um secure release bundles for deployments and just just a range of advances. I think the number of new features and innovation we put into the product in the past six months since I. P. O. Is astounding. So we're really trying to push the edge on devops um and we're also gonna be announcing and talking about stuff that dr khan as well and continue to invest in the cloud native and the devops ecosystem with our support of the continuous delivery foundation and the C. N C F, which I'm also heavily involved in. So it's it's exciting time to be in the devoPS industry and I think you can see that we're really helping software developers to improve their art to become better, better at release. Again, managing production applications >>and the ecosystem is just flourishing. It's only the beginning and again Making bring the craft back in Agile, which is a super big theme this year. Stephen. Great, great to see you. Thanks for dropping those gems and insights here on the Cube here at Dr. 2021 virtual. Thanks for coming on. >>Yeah. Thank you john. >>Okay. Dr. 2020 coverage virtual. I'm John for your host of the Cube. Thanks for watching. Mhm. Mhm. Yeah.

>>Hey, everyone. I want to welcome you back. This is our intermission. And let me tell you what a morning we've had for those of you that don't know. I'm, Hayma Ganapati, I'm in product marketing at Docker. And I would just want to quote, actually someone who was in one of the chat rooms and this, I think encapsulates exactly how I feel today, because this is my first Docker con and the quote was from. And he said, I feel like a kid in an ice cream store where I don't know which flavor to choose. I want to go to all of the sessions and I got to tell you that's how I felt. And, you know, um, I want to just do some specific call-ups. Um, first of all, Dana way to keep it real in your interview. I love the cube interview. If you miss that, um, it was really great. >>She talks a lot about, uh, CI CD pipeline and you know, what to do with GoodHub. It was great. Um, I also want to say that I was, uh, slipping back and forth between the community rooms and way to go Brazil obrigado until all of the people who participate in the Brazil room, we had about 250 plus people in that room. And the, the chat window was just going crazy and in the French community room, Vive left hall. So if you've a uncle funny, uh, we had about 150 plus people in that room. So I just want to say that, you know, we've been seeing a lot of participation and I just want to thank everyone for attending and for participating on people have been so kind in the chat rooms, we just want to remind you to stay kind, you know, presenters put a lot of effort into their presentations, so just, you know, offer some positive and supportive critique to them. >>And the other thing I want to mention is all of the countries that we're seeing, all of the participation. So I'm just going to call out a few. We have people from the Netherlands, from Canada, from South Africa, Akron, Ohio, Belgium, Austria, yeah, Ecuador, New Zealand. And he cut up Westchester. Like, I mean, it just goes list goes on and on and on. And I think this really speaks to the power of Docker community. And it's a real testimony to how people from all over the world are in love with Docker technology and are excited to be here. And so I just wanted to thank everyone again and want to remind you that we want to leverage the power of community. And we have a fundraising campaign going on to help, uh, people who are affected by COVID. And you know, some of our big communities, especially in India and Brazil are, have been really affected by COVID. >>So we're asking you to contribute and we'd really like you to participate. Um, we have, uh, the, the link you can see here, Docker donates, you can tweet about it and would love to see the numbers go up for those donations, because, you know, I've personally been affected, had some family members pass away from COVID in India, and I'm sure other people may have stories that firsthand or secondhand. So please do that and let's show what the power of Docker community can do. And before I hand over to, to Peter, I'm just going to read out some of the tweets we've been getting, okay, this Brett and Peter, these are great. Uh, one of the, one of the tweets said dev environments is one of the most exciting features in the past few years. Super excited to try this out. Great, great, great tweet. Yeah. >>I agree to, um, another loving the content that was not your tweets. You can, you can slip me the 20 bucks later. Um, there's another tweet that says loving the content from hashtag Docker con so far fascinating use cases and interesting progress and future directions love that. And then there's another one I'm trying to find it here. Uh, I've been waiting for this so long Docker builds now work on Intel and M one. So keep those tweets coming. We love getting this kind of feedback and we love reading the chat room. So, um, Peter, you know, I attended your, your panel and I love that we were talking about a security and that moving, moving it left. So how did that go for you? >>Uh, it was, it was, uh, it was extremely fun. And for those that are, uh, I think my parents might be watching, so they probably watched it and were like, w this is the most boring thing I've ever seen, but, um, you know, you get a bunch of geeks and, uh, Brett has told me I should use geek instead of nerd, but I, I liked, uh, geek. So you get a bunch of geeks talking about security and coding and, um, what, what, what containers actually are, what vulnerabilities are. Yeah, it was, it was extremely fun. The panel was fantastic. They were very engaging the chat. I mean, I couldn't keep up with the chat. Right. It would just kept flying by, uh, luckily I had a helper to pull off questions, but, um, yeah, it's super exciting. You can, I know we're all remote, but you can just feel that energy, right. It was, it was great. It was great. Yeah. Yeah, for sure. It's super >>Connected. I felt that with your panel to Brett as well, sorry to talk over you there, but yeah. How did, how did it go for you? I, there was a lot of engagement in your session. >>Uh, ditto, like it was just, uh, there was so many questions. We only got to get a fraction of them. I tried to pick themes because, uh, when you talk about continuous testing and integration and all the things that take a part of that, um, you, you end up with lots of, well, what I like is the discussion around opinions, because so much of these pipelines from code on your machine, into production and everything in between, it's really, uh, it's a culture. It turns out to be the description of your culture and how you all perceive testing, how you, what you value in testing. And so that really started to come out as a theme, um, throughout that show. And we, we ran at a time. I was also watching Peters and it was fantastic, but like you think an hour is enough time to cover a topic, but it's just tipping tip of the iceberg kind of stuff. So I think it was super helpful. I learned some things, um, I really enjoyed watching Peters and, uh, yeah, can't wait for the next one. There's >>More than that. And likewise, great. I mean, I know, I know we're w maybe we pat chose it, but it, it was, it was super exciting to watch your panel. They were very Nikos, one of my favorite people in the world, uh, a fellow Austinite, but, um, yeah, I love that too. How you, uh, you were talking about opinions right. And playing off each other. It's, it's always interesting to hear smart people, uh, how they think, right. Yeah. I learned from how they think, right. Yeah. A hundred percent. >>So, all right. So we're, we're, um, what's next? Like, we, we gotta keep this thing going, so I've got to remember that. >>I want to, so I want to talk a bit about some of the panels that are, or the sessions that are coming up and just want to remind people that happened this afternoon. I'm all about use cases. You know, I was a developer for many decades, and it's great to hear how other developers are using the tools. But, uh, as a developer, I always wanted to know how are, what are the end user applications? And so we have two exciting sessions at 1:00 PM. We have sneak and red ventures, and they're going to be talking about how they used Docker containers. The title of the, uh, uh, session is great. An ounce of prevention, curing, insecure, container images. So check that out. And we also have another one at one 30 with Massimo, from AWS and Dexter Legaspi from Sirius XM. And they're going to be talking about a real world application using Docker containers. So I really want you to, to encourage you to attend those. >>Yeah. Um, can I say one really quick? Cause I'm Sue and a shout out to Eric Smalling. He's giving the red ventures talk with our partners. He's awesome. Go check out his, uh, but I'm really excited about Matt. Jarvis's sneak talk around. Uh, I think we might've talked about it earlier. My container image has 500 vulnerabilities vulnerabilities now what, right. I mean, I think as developers, as we're coming into this and dev ops and everybody right. You scan and then you see all these vulnerabilities just shoot by. And you're like, well, what do I do? So Matt, Matt will be addressing that. And he is fantastic. I can go on. There's a bunch of them. >>Yeah. There's a whole bunch of coming up and right up after this, I'm on a live stream with a bunch of panels on get ops. And then after that, Peter will be back. And so stay tuned and thanks for watching during the intermission. And we'll see you soon. >>I'm also leading the women in tech panel attend that. Don't forget to do that. >>Absolutely. Yep. All right. Ciao. Ciao >>For me like my first, oh, I get it about Docker was when I used a SQL server container on my neck book for the first time >>Being able to install Docker desktop, which was the first thing that I did and be able to build this without worrying about any of my software versions that I currently had on my machine. It was >>Awesome. One of the things, because I love the most about Docker is because I write books and I do video training courses to help a lot of people take their first steps with Docker and containers and to get a connection with those people and for them to come back to me and say, do you know what this is so cool, so easy, and it's going to change both my job. And, but also my organization, my team, all of that kind of stuff, change the experience that our customers have with our applications and what our business really puts a smile on my face. If >>You want to use containers, then Docker is the first toys, especially with tools like the mark Docker, compose, you can, uh, easily do your day-to-day job as a developer, or even if you're an ops person, then there are the books of the cloud and other things. So yeah, the idea is that we can go the simplicity one simple task, uh, to, uh, Daugherty mate and make that reuse as many times. Uh, that is one of the cool things I like about my >>Favorite part about Docker is using it as a developer tool. I using Docker desktop, really easy to install, really easy to run. >>Every time I come back to DACA, I love the simplicity of the way that it works, especially on things like security, which I find frustrating and hard. It's just done so seamlessly. And so my favorite thing about DACA is not just that it changed the world in the way that we develop in and ship and build applications and put that. It's just so easy that even the guy, like, I think >>It really is all about finding that aha moment, that hook where Docker really makes sense to you because once you have that moment, then all of a sudden, you, you know, you are on your way to being a Docker power user. >>We need for people to understand this technology better before they can, uh, actually dive deep into that. And Docker makes it easier to explain things, to explain the concept of containers, to explain how containers will work, how you can split your environments, how you can, uh, standardize all your pipelines and so on. It's important that we also take the time to help other people. And I think it's very important that we also give back and that's part of the motto of open sources. How do we give back to other people and how we help other people learn? And I think that's what I'm really passionate about. This whole thing is continuing, uh, giving back to the community. I just >>Hope and has fun at Docker con. And I know that there's a lot of great speakers coming and I will be watching the talks, even though they're happening at 3:00 AM and in my local time zone, um, I'm pretty excited to watch and, uh, hopefully watch more than later on streaming or YouTube or wherever they're going to be. So I hope everyone has fun and learn something and yeah, I don't see how you couldn't have fun.

(upbeat music) >> Okay, welcome back to theCUBES's coverage of Dockercon 2021. I'm John Furrier, your host of theCUBE. We have Justin Cormack, CTO of Docker. Was also involved in the CNCF technical oversight and variety of other technical activities. Justin, great to see you. Thanks for coming on theCUBE Virtual this year, again, twice in a row and maybe next year will be in person but certainly hybrid, great to see you. >> Yeah, great to see you too. Yeah, in person would be nice one of these days, yes. >> Yeah, when we get real life back. It's almost there, I can feel it, but there's so much activity. One of the things that we've been talking about, certainly in theCUBE and even here at DockerCon, same story. The pandemic really hasn't truly impacted developer community, because most of the people have been working remotely and virtually for many, many decades. And if you think about just in the past 10 years, all the innovation in cloud has come from virtual teams, open-source softwares, always had good kind of governance and a democratization of kind of how it becomes built. So not a bit's been skipped during the pandemic. In fact, if anything supply chain of software development has increased. So- >> Yeah, I think that it's definitely true that open-source was really the place that pioneered remote working. And a lot of the work methods the people worked out to do open-source as in communication and things like that, were things that people have adopted. It's a slightly different community. I'd say open-source projects like meetings less than some other organizations, but there was definitely that pioneering thing. And a lot of the companies that started off remote first, were in open-source software, and they started off for those reasons as well because developers were already working like that, and they could just hire them and they could continue to work like that. >> Yeah, one of the upsides of all this is that people won't tolerate even zoom or in person meetings that just go on, 15, 30 minutes good call. Why do we have a meeting? What's the purpose? (faintly speaking) the way to go. Let's get into the developer community. One of the things I love about DockerCon this year 2021 is the envelopes being pushed again almost to another level, it's almost a new level, this next level of containers is bringing more innovation to the table and productivity and simplicity. Some of the same messages last year but now more than ever, stuff's going on. What are you hearing directly from the community? You talk to a lot of the developers out of the millions of developers in the Docker ecosystem. What are they saying now in 2021? What's going on in their mind? >> Yeah, I think it's an area... More and more people are using Docker, and they're using it every day and it's a change that's been going on, obviously for a while, but it begins to sort of, as it spreads, the kind of developers using Docker, so different from... When I started at Docker, coming up for six years ago, it was a very bleeding edge type thing for early adopters. Now it's everywhere, millions and millions of ordinary developers are using Docker every day. And the kinds of things that's telling us is, well, some of this stuff that we thought, well, five years ago was an amazing breakthrough and simplicity. Now that's on its own still too hard. One of the things I mentioned in my keynote was that, we're talking to developers who just primarily have been working windows all their life but more and more applications being shipped on Linux. And they using Linux containers, but they find Docker files really hard because they have really, Linux shell scrapes and not a windows developer doesn't know how to use a Linux shell script. And it's bringing it down to that next level of use where you can adopt these things more easily, the pitched to the kind of level of developer who is just thinking about their language, their APIs and they don't want to have to learn kind of lots of new things to do Docker. They'll learn some, but they really wanted to kind of integrate better into the environments they work in and help them more. We've been working on a lot of detailed instructions about like how to use Docker better with JavaScript and Python, because people have told us, be specific about these things, tell us exactly how I do make things work well with the way I'm doing things now. >> What is the big upside for containers for the folks watching? And last year, one of the most popular sessions was the one-on-one Peter McKay did, which was fascinating, packed with people. And the adoption of containers is going everywhere and enabling a lot of growth. What's the main message to these new developers that are coming on board to ecosystem. >> I think what's happening is that people are gradually, very slowly starting to think about containers in a different way. When we started, the question everyone kept asking was about containers and VMS, what's the difference? That question didn't really, kind of really address what the big fundamental changes that containers made to how people work was. I'd like to think about it in terms of the physical shipping containers, like people are concerned about like, can you escape from the box? Can I get out of a container? These kinds of questions. This is not really the important question about containers is kind of escape from the box. The question is, what does it enable you to build? The shipping container let us build the supply chains that let people build products and factories and things that would never have been possible without the ability to actually just ship things in a routine and predictable and reliable and secure way, getting that content and the things that come in the container and you actually work more effectively. And, so I think that now we're talking about like what's the effect of containers on the industry as a whole? What are the things that we can learn about repeatability and documentation and metadata and reliability, that we kind of talked about a little bit before, but these are becoming the important use cases for containers. Containers are really about, they're not about that kind of security and escape piece, there're about the content, the supply chain and your actual process of working. >> What do you, first of all, great call out on the security piece. I want to get that in a second. I think that's a killer one. You've mentioned supply chain, can you define software supply chain, and is that where the automation value comes in? Because a lot of people are talking about automation is improving the developer experience. So can you clarify quickly, what do you mean by the software supply chain? And is that where automation comes in? Am I getting that right? >> Yeah, so the software supply chain is really that process by which you get components of software to build your applications. Around 99% of companies are using open-source software to build applications. And the vast majority of the pieces of any modern application art consists mainly of open-source software and some tries source software, and some software that people are writing themselves. But you've got to get these components in, you've got to make sure that they're updated and scanned and they're reliable. And that's the software supply chain is that process for bringing in components that you're using to build your applications. And so, the way automation comes in, is just because there's so much of the software dealing with it manually is just difficult, and it's an ongoing process of build and test and CI and all those scanning and all those processes. And I think as software developers, we fundamentally know that the most valuable things are the things that we automate. They're the things that we do all the time and they're important. And that a lot of building a software is about building repeatable processes, rather than just doing things one by one, because we know that we have to keep updating software, we have to keep fixing bags, we have to keep improving software. And so you've got to be able to keep doing these things, and automation is what helps us do that. >> I was talking to Dana Lawson the VP of Engineering at GitHub, and she and I were chatting about this one topic. I want to get your thoughts on it, because she was definitely of the camp of automation helps with productivity. No doubt, check, double check there. The question I have for you is how do you see the impact on say the developer experience and innovation specifically? Because, okay, I can see the productivity, okay, something happens a bunch of times automated. Then you start thinking about supply chain, then you thought about developer experience and ultimately with Kubernetes around the corner, with the relationship with containers, you can see the cloud-native benefits from an innovation standpoint. Can you share your thoughts on the automation impact to experience for the developer and the innovation strategies they need? >> Well, I think that one of the ways we're trying to think about everything we do at Docker is that we should be helping build processes rather than helping you do something once, because, if you do something three times, you want to automate it, but what if the first time you did it, that could also build that automated process. And if it was, why isn't it as easy to make something automated as it is to do it once? There's no real reason why it shouldn't be. And I think that kind of... I was having a conversation with someone the other day about how they would... They had kind of reversed their thinking and they found that often it was easier to start with automation and harder to do things manually. And that's a kind of real reversal of that kind of role between automation and doing stuff run, so, and it's not how we think about it, but I think it's really interesting to think about that kind of thing, and how could we make automation really, really simple. >> Well, that's a great example when you have that kind of environment, and certainly the psychology is better to have automation but if everyone's saying it's hard to do manual, that means they're at some sort of scale, right? So scale matters, right? So as you start getting the SRE vibes going, and you start getting Cloud Scale in cloud-native apps, that's going to be cool. Now, the question I want to ask you, because while the other thing that's happening is more people are coming into open-source than ever before, not just young developers, but also end users. Not like the hardcore-end users, looking like classic enterprises are coming in. So as more developers come in and increase over the year, what does that mean for the experience for developers? Now you have, does that change it? How do you view that? Because as more developers come in, you have institutional knowledge, you have scale, you have learnings, what's your thoughts on on the impact as the population of developers increase? How does Docker view that? >> Yeah, now, I think it's really interesting trend. It's been very visible in CNCF for the last few years. We've been seeing a lot more active end-user, company's doing open-source. Spotify has been one of the examples with a backstage project they brought into CNCF and other areas where they work. And I think it's part of this growing trend that's really important to Docker, Docker is a bottom up technology adoption company. Developers are using Docker because it works for them and they love it. And developers are doing open-source in their companies because open-source works for them and they love it. And it works for their business as well. And whereas historically like the the model was, you would buy kind of large enterprise products, with big procurement deals that were often not what the developers wanted, but now you're getting developers saying, what we want to do is adopt these open-source projects, because we know how they work, we already understand that we know how to integrate them better into our processes. And I think it's that developer lad demand that's really important, and it's the kind of integration that developers want to do, the kind of products that they want to work with, because they understand them and love them, and they had targeted at developers and that's incredibly important. And I think that's very much where Docker's focused and we really want to... Open-source is of the core of everything we've always done. We've built with the open-source community, and we've kind of come from that kind of environment. And we built things that we love as developers and that other developers love. >> Talk about your thoughts on security. Obviously it's always built in from the beginning, Shift-Left is the ethos, day two operations, AI apps, whatever people want to call that. Post-deployment mode, security has to be at the center of this, containers can be a great solution and give some great flexibility for developers. Can you talk about your view and Docker view on the security posture and situation? >> Yeah, I think Shift-Left is incredibly important because just doing things late, everyone knows is the wrong thing from the point of view of productivity. But I think Shift-Left can just mean, ask the developers to do everything, which is really a bit too much. I think that sometimes things need to be shifted even further left than people have actually thought. So like, why are you expecting developers to scan components to see if they're allowed to use? If they should be using them or they should be updated, why hasn't that happened before the developer even gets there? I think there's a, I sorted my keynote about this whole piece, about trusted content. And it's really important that we really shift that even further left, so it's long before it gets to the developer, those things that are happening. Security, it's a huge area, of course, but it's very much, we need to help developers because security is non-obvious. I think the more you understand about security, the more you understand that it doesn't come naturally to people and they need to be helped with it, and they need to learn a lot about things in a way to, I found myself that, learning how to think like an attacker is a really important way of thinking about how to secure softwares, like what what would they do rather than just thinking about the normal kind of, oh, this works in the (faintly speaking) What happens if things go wrong? That you have to think about as well. So there's a lot of work to do to educate and help and build tools that help developers there. And it's been really good working with Snyk, cause they're a very developer focused security company, that's why we chose to work with them. Whereas historically, security companies have been very oriented towards kind of the operator side of it, not the development side, not the developer experience. And the other piece is really around supply chain security. That's just kind of a new security area. And it's very important from the container point of view, because one of the things containers let you do is really control the components that you're using to build applications and manage them better. And so we can really build tooling that helps you manage, that helps you understand what's in a container, helps you understand where it came from, how it was built and automate those processes and sign and authenticate them as well. And we've been working with CNCF on Nature V2, which is for signing revamp of the container signing process, because people really want to know who originated this container? Where did it come from? What did they say is in it? There's a lot of work about build up materials and composition analysis and all those things that you need to know about. What's in a container, and the... >> Everyone wants to know what's in a container. If you've got a Kubernetes cluster for instance, that's all highly secure and in comes a container, how do you know what the... There's no perimeter, right? So again, as you said, thinking like an attack vector there, you got to understand that, this is where the action is, right? This is where a lot of work's being done on this idea of always on security. You don't know when the container's coming in. during the run stage, you're running a business now, it's not just build and share, your running infrastructure. >> Absolutely, you really want full control about everything that goes into it, and you want to know where everything that you're running in production came from, and you pretty tired of this, and that's your end to end supply chain. It's everything from developer inputs through the build process and grow to production. And in production, understanding whether it needs to be updated and whether there's new discover vulnerabilities and whether it's being attacked and how that relates back to what came into it in the first place. >> Lot more intelligence, lot more monitoring. You guys are enabling all that I know it's cool. Great stuff. Hey, I want to get your thoughts on just what got you here on the calendar, looking at the DockerCon '21 event, and we're having a fun time here with, we're on theCUBE track, get the keynote track. But if you look at the sessions that's going on, you got, and I'll get your comment on this, cause it's really interesting how it's cleverly laid out this is. You've got the classic run share build and then you've got a track called accelerate, interesting metadata around these labels. Take us through, because this basically shows the maturation of containers. We already talked about the relationship, somewhat with Kubernetes, everyone kind of sees that direction clearly, but you got acceleration, which is a key new track, but run, share, build, what's your reaction to that? Share your observations of what the layout of those names and what it means to an enterprise and people building. >> Yeah, (faintly speaking) has been Docker's kind of motto for a long time. It kind of encapsulates that kind of process of like, the developer building application, the collaborative piece that's really important about sharing content in containers and then obviously putting into production because that's the aim. But, accelerate is incredibly important too. Developers are just being asked to do a lot. Everything is software, there's a lot of software, and a lot of software has to be created and we've got to make it easier to do this. And that kind of getting quickly from idea to business outcomes and results is what modern software teams are really driving at. And, I think we've really been focused this last year on what the team needs to succeed, and especially, small focused teams delivering business value. It's how we're structured internally as well and is how our customers, to a large extent are structured. And there's that kind of focus on accelerating those business outcomes and the feedback loops from your ideas to what the feedback that your customers give you at helping you understand that it's really important. >> Talk about final question for you in terms of the topic here, cloud, hybrid cloud, multicloud, this is, put multicloud asides more hype. Everyone has multiple clouds, but it speaks to the general distributed computing architecture when you talk about public cloud and on-premises cloud operations. So modern developers looking at that as, okay, distributed environment, edge, whatever you're going to call it. What's your view of Docker as it goes forward for the folks watching, who have experience with Docker, loved the vibe, loved the open-source, but now I've got to start thinking about putting the containers everywhere. What's the Docker pitch, so to speak, with a tech story that they should walk away with from you? What's the story, what's the pitch? >> Yeah, so containers everywhere has been a sort of emerging trend for a while, the last year or so. The whole Kubernetes at the edge thing has really exploded with people experimenting with lots and lots of different architectures for different kinds of environments at the edge. What's totally clear is that people want to be able to update software really easily at the edge the way you can in the cloud. We can't have the sort of, there's no point in shipping a modern piece of manufacturing equipment that you can't update the software on, because the software is how it works, more and more equipment is becoming very general purpose, people making general purpose robots, general purpose factories, general purpose everything which need to be specialized into the application they're going to run that week. And also people are getting more and more feedback and data and feedback from the data. So if you're building something that runs on a farm, you're getting permanent feedback about how well it's doing and how well the crops are growing was coming back. And so everywhere you've got this, we need to update. And everywhere you need to update, you want containers because containers are the simple reliable way to update software. >> I know you talked about CNCF and your role there. Also the CTO of Docker, I have to ask cause we were just covered Coop con and cloud-native con just last month and this month. And it's clear that Kubernetes is becoming boringly good in a way that's good to be boring, right? It means it's working. And it's becoming more cloud-native con than Coop-con. That has been kind of editorial observation, which speaks to what we feel is a trend towards more cloud-native discussions, less about Kubernetes. So, it's still Kubernetes stuff going on, don't get me wrong, just saying it's not as controversial in the sense that people kind of clearly understand why that's important, and all the discussions now seem to be on cloud-native modern developer workflows. What's your reaction to that? Do you agree, if not, what's your take? >> Yeah, I think that's definitely true. Kubernetes is definitely much more boring. Everyone is using it. They're using it in production now vastly more than they were a few years ago, when it was just experiment, experiment, experiment, now it's production scale out. The ecosystem in CNCF is kind of huge. There's so many little bits that have to be filled in storage and networking and all that. So there's actually a lot of pieces that are around Kubernetes, but, there's definitely more of a focus coming on the developer experience there. Compared to DockerCon, the audience at Coop Con is incarnated kind of still much more operator focused rather than developer focused. And it's very nice coming to DockerCon, just to feel like being amongst that developer community, Coop Con still has a way to gauge to have more of a real developer audience, but the project is starting to pair with a more developer focused kind of aim or things like backstage from Spotify is a really interesting one where it's about operations, but it's a developer portal focused things. So, I think it's happening, and there's a lot more talk about that. There's a whole bunch of infrastructure, there's a lot more security projects in CNCF than they were before. And we're doing a lot of work on supply chain security and CNCF just released a white paper on that few days ago. So there's a lot of work there that touches on developer needs. I still think that audience (faintly speaking) that much different from DockerCon which is I think 80% developers and maybe 10% infrastructure rather than the other way round. >> I think if you're going to get operators it can be SRE/platformleads. The platform leads are definitely inside DockerCon now than they've ever been before from my observation. So, but that speaks to the sign of the times. Most development teams have an SRE in the team, not an SRE team. They're just starting to see much more integration amongst the kind of a threaded or threaded teams or whatnot. So... >> Yeah. (faintly speaking) Operate your apps is the model. And I think that it's going to lead to more and more crossover between these communities. It's what DevOps was supposed to be about, somehow got diverted into building DevOps teams instead of working together, but we'll get there. >> It's clear from my standpoint, at least from reporting here is that, from the DockerCon and community at large, cloud-native community, having end-to-end work-load visibility on developer test run, everything seems to be the consensus, without a doubt. And then having multiple teams, and then having some platform, have some flexing people moving between teams for the most part, but built insecurity, built in SRE, built in DevOps, DevSecOps, all the way from end-to-end. >> Absolutely, we know that that's what does work best, it's where most organizations are heading at different speeds, because it's very different from the traditional architecture. It takes time to get there, but that's the model that has come out of microservices that really containers enabled and allow that model to happen. And it's the team architecture of containers. >> Hey, monolithic applications have monolithic organizations, microservices have microservices teams. Justin, great to have you on theCUBE for this conversation. If folks watching this interview, check out Justin's keynote, came from the main stage, great stuff. Justin, thanks for coming on theCUBE, we really appreciate your time and insight. >> Thank you, good to see you again. >> Okay, this is theCUBES's coverage of DockerCon 2021 Virtual. I'm John Furrier, your host. Thanks for watching. (upbeat music)

>>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.

>>Well, welcome to the special cube conversation. I'm Jennifer with the cube, your host, we're here with Jeremy and Iisha Sharma director of product management for trim. We're going to talk about data, data lakes, the future of data, and how it works with cloud and in the new applications. Iisha thanks for joining me. >>Thank you for having me, John, >>You guys are a cutting-edge startup. You've got a lot of good action going on. You're kind of on the new, the new guard as Andy Jassy at AWS always talks about this. The old guard incumbents you guys are on the, on the new breed, you guys are doing the new stuff around data lakes and also making data accessible for customers. Uh, what, what is that all about? Take us through what is Dremio. >>So Dremio is the data Lake service that essentially allows you to very simply run SQL queries on directly on your data Lake storage, without having to make any of those copies that everybody's going on about all the time. So you're really able to get that fast time to value without having to have this long process of let's put in a request to my data team, let's make all of those copies and then finally get this very reduced scope of, of your data and still have to go back to your data team every time you need it, you need a change to that. So dreamy is bringing you that fast time to value with that. No copy data strategy, and really providing you the flexibility to keep your data in your data Lake storage, as the single source of truth. >>You know, the past 10 years, we've watched with cube coverage since we've been doing this program and in the community following from the early days of Hadoop to now, we've seen the trials and tribulations of ETL data warehousing. We've seen the starts and stops, and we've seen that the most successful formula has been store everything. Um, and then, you know, then the ease of use became a challenge. I don't want to have to hire really high powered engineers to manage certain kinds of clusters. I just got cloud now comes into the mix. I got on-premise storage, but the notion of a data Lake became hugely popular because it became a phrase meant store everything, and it meant different things to different peoples. And since then, teams of people have been hired to be the data teams. So it's kind of new. So I got to ask you, what is the challenge of these data teams? What do they look like? What's the psychology going on with some of the people on these teams? What problems are they solving what's going on? Because you know, they becoming data full >>To take >>Us through what's going on with data teams, >>To your point, the volumes, the variety of data, Eastern growing exponentially every day, there's really no end to it, right? And companies are looking to get their hands on as much data as they possibly can. So that means data teams in a position to how do I provide access to as many users as easily as possible that self service experience or data, um, and data democratization as much of a great concept as it is in theory, it comes with its own challenges in terms of all of those copies that ended up being created to provide the quote unquote self service experience. And then with all of these copies comes the cost to store all of them. And you've just added a tremendous amount of complexity and delayed your time to value significantly. >>You mentioned self-service is one of those things that seems like a moving train. Everyone I talked to is like, Oh, self-service is the Holy grail we've got to get to self-service almost. And then you get to some self serves, then you gotta, you gotta re rethink it cause more stuff's changing. So I have to ask in that capacity, you've got data architects and you've got analysts, the customer of the data. How's the, what's the relationship between those two is who gives and who gets, who drives it, who leans in to the analyst, feed the requirements into the architect, set up the boundaries. How is that relationship? Can you take us through how you guys view the relationship between the data analyst and architect? I mean data architect and the data analysts. >>Sure. So you have the data architect, the data team that's actually responsible for providing data access at the end of the day, right? They're the people that have the data democratization requirement on them. And so they've created these copies, tremendous amount of copies. A lot of the times the data Lake storage is, is that source of truth. But, um, you're copying your data into a data warehouse. And then what they end up doing is your, your end user, your analyst, they want, they all want different types of data. They want different views of this data. So there's a tremendous amount of personalized copies that the architects end up creating. And then on top of it, there's performance. We need to get everything back in a timely manner. Otherwise what's the point, right? Real time analytics. So there's all these performance related copies, whether that be additive tables or, you know, VI extract cues, all of that fun stuff. >>And so the architect is the one that's responsible for creating all of those. That's what they have to do to provide access to the analyst. And then, like I'm saying, when we need an update to that data set, when I discover that I have a new data set, that I need to join with an existing one, I have the analyst go to the data architect and say, Hey, by the way, I need this new data set. Can you make this usable for me? Or can you provide me access? And so then we did protect has to process that request now. And so again, coming back to all these copies that have been created, um, the data architect goes through a tremendous amount of work and almost, um, has, has to do this over and over again to actually make the data available to the analyst. But it's a cycle that goes on between the two. >>Yeah. It's interesting dynamic. It's a power dynamic, but also trying to get to the innovation. I've got to ask you, some people are saying that data copies are the major obstacle for democratization. How do you respond to that? What's your view? >>They absolutely are. Data copies are the complete opposite of data democratization. There's no aspect of self-service there, which is exactly what you're looking to do with data democratization. Um, because of those copies, how do you manage those? How do you govern those? How, uh, like I was saying, when somebody needs a new data set or an update to one, they have to go back to that data team. And there goes that self-service actually Dana coffees create a bottleneck because it all comes back to that data team that has to continue to get through those requests that are coming in from their analysts. So, uh, data copies and data democratization is completely automated. >>You know, I remember talking to David latte in a cube event two years ago, he said infrastructure as code was the big DevOps movement. And we felt that data ops would be something similar where data as code, where you didn't have to think about it. So you're kind of getting to this idea of, you know, copies are bad because it doesn't, it holds back that self-service this modern error is looking for more of programmability with data. Kind of what you're teasing out here is that's the modern architecture. Is that how you see it? How do, how do you see, uh, a, uh, a modern data architecture? >>Yeah, so the modern data or the data architecture has evolved significantly in the last several years, right? We started with traditional data warehouses and the traditional data Lake with Duke where the storage and compute were totally tightly coupled. And then we moved on to cloud data warehouses, where there was a separation of compute and storage, and that provided a little more flexibility there. But then with the modern data architecture now with cloud data lakes, you have this aspect of separating, not only storage and compute, but also compute data. So that creates a separate tier for data altogether. What does that look like? So you have your data and your feeling storage as three ATLs, whatever it may be. And on top of that. So of course it's an open format, right? And so on top of that, thanks to technology. It's like Apache iceberg and Delta Lake. There's this ability to give your files, your data, a table structure. And so that starts to bring the capabilities that a data warehouse was providing the data. Thanks to these. You have the ability to do transactions, record level mutations, burgeoning things that were missing completely from a data Lake architecture before. And so, um, introducing that, that data to your, having that separation of compute and data really, really accelerate the ability to get that time to value because you're keeping your data in the data Lake storage at the end of the day. >>And it's interesting, you see all the hot companies tend to be, have that kind of mindset and architecture, and it's creating new opportunities as a ton of white space. So I have to kind of ask you guys, how does Dremio fit into this because you guys are playing in this kind of the new wave here with data it's growing extremely, it's moving fast. You got, again, edge is developing more. Data's coming in at the edge. You've got hybrid testing multi-cloud environments on the horizon. I mean this ultimate multicloud, but I mean, data in real time across multiple clouds is the next kind of area people are focused on. What does, what's the role of GMU and all this to take, take us through that. >>Yeah. So Dremio provides, again, like I said, this data Lake service, and we're all referring to just storage or Hadoop. When we say data Lake, we're talking about an entire solution. Um, so you keep your data, you keep your data in your data, Lake orange. And then on top of that, with the integrations that Dremio has with Apache iceberg and Delta, like we do provide that data here that I was talking about. And so you've given your data, this table structure, and now you can operate on it like you would in a data warehouse. So there's really no need to move your data from a data Lake data warehouse, again, keeping that data Lake as that source of truth. And then on top of that, um, when we talk about copies, personalized copies, performance related copies, you, you really, like I was saying, you've created so much complexity with Jeremy of you don't do that when it comes to personalized copies, we've got the semantic layer and that's a very key aspect of Dremio where you can provide as many views of, of data that you want without having to make any copies. So it really accelerates that, that data democratization story, and then when it, >>So it's the no cop, my strategy trim, you guys are on it, but you're about no copy keeps semantic layer, have that be horizontal across whatever environment and just applications have, can applications tap into this, or how do you guys integrate into apps if I'm an app developer, for instance, how does that work? >>Of course. So that's, that's one of the most important use cases in the sense that when there's an application or even when it's a, you know, a BI client or some other tool that's tapping into the data in S3 or ATLs, a lot of people see performance degradation. Typically with the Dremio, that's not the case we've got, Aeroflight integrated into Tremino, it's a key component as well. And that puts so much, uh, it, so put so much ease in terms of running dashboards off of that, running your analytics apps off of that, because that replay can deliver 20 times the performance that PIO DBC could. So coming back to the no data strategy or note copy data strategy, there's no those local copies anymore that you needed to make. >>So one of the things I got to ask you is, cause this comes up all the time. So she had less pass re-invent. I notice again, Amazon was, I was banging on this hard Azure as well on their side too. Their whole thing is we want to take the AI environment and make it so that people can normal people can use it and deploy machine learning. The same thing kind of comes down into this layer where you're talking about is this democratization is a huge trend because you don't have to be super peaked, you know, math, PhD, data scientist, or ETL, or data Wrangler. You just want to actually code the data or play party with the data in any way you want to do with it. So, so the question I have is is that that's certainly a great trend and no one debates that, but the reality is people are storing data, like almost hoarding it, just throw it in a data Lake and we'll deal with them later. How does you guys solve that problem? Because once that starts happening, do you have to hire someone super smart to dig that out or rearchitected or because that seems to be kind of the pattern, right? You know, throw everything into data Lake, uh, and we'll deal with it later >>Called the data swamp. And it's like, no one knows what's going on. >>Of course though, you don't actually want to throw everything into a data Lake. There still needs to be a certain amount of structure that all of this lands in. You want it to live in one place, but have still a little bit of structure so that, um, Dremio and other are, are much more enabled to query that with fantastic performance. So there's, there's still some amount of structure that needs to happen at a data Lake level, but from, uh, that semantic layer that we have with during the, you you're, you're creating structure for your end user, >>How would you advise, how would you advise someone who wants to hedge their future and not take on too much technical debt, but says, Hey, you know, I do have the store. Is there a best practice on kind of some guard rails around getting going, how do you, how do you advise your customers who want to get it going? >>So how we advise our customers is again, plugin put your, put your data in that data Lake. A lot of them already have three TLS in place. And getting started with Bermeo is really easy. I would say I did it for the first time and it took a matter of minutes if not less. And so what you're doing with Dremio is connecting data directly to that data source and then creating a semantic layer on top. So you bring together a bunch of data. That's sitting in your data Lake, you know, if that sales data and Sophia, and we give you a really streamlined way to say together, the, you know, last, however, we go back in time, create a view on top of all of that. If you have that structured in folders as great, we will provide you a way to create one view on top of all of that, as opposed to having a view for every day or whatnot. And so again, that semantic layer really comes in handy when you're trying to, as the architect provide access to this data Lake. And then as the user who just, just interacts with the data as, as the views are provided to them, there's really, uh, there's a whole lot of transparency there, and it's really easy to get up and running with drumming. >>I'm looking forward to it. I got to finally ask the question is how do I get started? How do people engage with you guys? Is it, is it a freemium? Is it a cloud service? What's the requirements? What are some of the ways that people can engage and work with you guys? >>Yeah, so we get started, uh, on our website at dot com. And speaking of self-service, we've got a virtual lab at dremio.com/labs that you can get started with that gives you a product tour and even gives you a getting started, walk through the tissue through your first query so that you can see how well it works. And in addition to that, we've got a free trial of Dremio available on AWS marketplace. >>Awesome. Net marketplace is a good place to download stuff. So can I ask you a personal question, Isha? Um, you're the director of product management. You get to see inside the kitchen where everyone's making the, making the product. You also got the customer relationships out there looking at product market fit, as it evolves, customer's requirements evolve. What's some of the cool things that you've seen in this space. That's just interesting to you that either you kind of expected or maybe some surprises, what's the coolest thing you've seen come out of this new data environment we're living in. >>I think just the ability to the way things have evolved, right? It used to be data Lake or data warehouse, and you pick one, you probably have both, but you're not like reaching either to their highest potential. Now you've got, this is coming together of both of them. I think it's been fantastic to see how you've got technology is like a iceberg and Delta Lake and bringing those two things together. And you know, you're in your data Lake and it's great in terms of cost and storage and all of that. But now you're able to have so much flexibility in terms of some of those data warehouse capabilities. And on top of that with technologies like Dremio, and just in general, this open format concept, you're, you're never locked in with a particular vendor with a particular format. You're not locking yourself out of a technology that you don't even know exists yet. And thinking in the past, you were always going to end up there. You always ended up putting your data in something where it was going to be difficult to change it, to get it out. But now you have so much flexibility with the open architecture that's coming. What's the DNA like of the >>Culture at Treme. And obviously you've got a cutting edge. We're in a big, hot wave data. You're enabling a lot of value. Uh, what's the, what's it like there at Jemena? What do you guys strive for? What's the purpose? What's the, what's the DNA of the culture. >>There's a lot of excitement in terms of getting customers to this flexibility, to get them out of things they're locked into really in providing them with accessibility to their data, right? This data access data democratization concept to make that actually happen so that, you know, time to value is a key thing. You want to derive insights out of your, out of your data. And everybody, I drove you in super excited and charging towards that, >>Unlocking that value. That's awesome. Aisha, thank you for coming on the cube conversation. Great to see you. Thanks for coming on. Appreciate it. He's just Sharma director of product management. Dremio here inside the cube. I'm John for your host. Thanks for watching.

>>from around the globe. It's the Cube presenting innovation for good, brought to you by on shape. >>Hello, everyone, and welcome to Innovation for Good Program, hosted by the Cuban. Brought to You by on Shape, which is a PTC company. My name is Dave Valentin. I'm coming to you from our studios outside of Boston. I'll be directing the conversations today. It's a very exciting, all live program. We're gonna look at how product innovation has evolved and where it's going and how engineers, entrepreneurs and educators are applying cutting edge, cutting edge product development techniques and technology to change our world. You know, the pandemic is, of course, profoundly impacted society and altered how individuals and organizations they're gonna be thinking about an approaching the coming decade. Leading technologists, engineers, product developers and educators have responded to the new challenges that we're facing from creating lifesaving products to helping students learn from home toe how to apply the latest product development techniques and solve the world's hardest problems. And in this program, you'll hear from some of the world's leading experts and practitioners on how product development and continuous innovation has evolved, how it's being applied toe positive positively affect society and importantly where it's going in the coming decades. So let's get started with our first session fueling Tech for good. And with me is John Hirschbeck, who is the president of the Suffers, a service division of PTC, which acquired on shape just over a year ago, where John was the CEO and co founder, and Dana Grayson is here. She is the co founder and general partner at Construct Capital, a new venture capital firm. Folks, welcome to the program. Thanks so much for coming on. >>Great to be here, Dave. >>All right, John. >>You're very welcome. Dana. Look, John, let's get into it for first Belated congratulations on the acquisition of Von Shape. That was an awesome seven year journey for your company. Tell our audience a little bit about the story of on shape, but take us back to Day zero. Why did you and your co founders start on shape? Well, >>actually, start before on shaping the You know, David, I've been in this business for almost 40 years. The business of building software tools for product developers and I had been part of some previous products in the industry and companies that had been in their era. Big changes in this market and about, you know, a little Before founding on shape, we started to see the problems product development teams were having with the traditional tools of that era years ago, and we saw the opportunity presented by Cloud Web and Mobile Technology. And we said, Hey, we could use Cloud Web and Mobile to solve the problems of product developers make their Their business is run better. But we have to build an entirely new system, an entirely new company, to do it. And that's what on shapes about. >>Well, so notwithstanding the challenges of co vid and difficulties this year, how is the first year been as, Ah, division of PTC for you guys? How's business? Anything you can share with us? >>Yeah, our first year of PTC has been awesome. It's been, you know, when you get acquired, Dave, you never You know, you have great optimism, but you never know what life will really be like. It's sort of like getting married or something, you know, until you're really doing it, you don't know. And so I'm happy to say that one year into our acquisition, um, PTC on shape is thriving. It's worked out better than I could have imagined a year ago. Along always, I mean sales are up. In Q four, our new sales rate grew 80% vs Excuse me, our fiscal Q four Q three. In the calendar year, it grew 80% compared to the year before. Our educational uses skyrocketing with around 400% growth, most recently year to year of students and teachers and co vid. And we've launched a major cloud platform using the core of on shape technology called Atlas. So, um, just tons of exciting things going on a TTC. >>That's awesome. But thank you for sharing some of those metrics. And of course, you're very humble individual. You know, people should know a little bit more about you mentioned, you know, we founded Solid Works, co founded Solid where I actually found it solid works. You had a great exit in the in the late nineties. But what I really appreciate is, you know, you're an entrepreneur. You've got a passion for the babies that you you helped birth. You stayed with the salt systems for a number of years. The company that quiet, solid works well over a decade. And and, of course, you and I have talked about how you participated in the the M I T. Blackjack team. You know, back in the day, a zai say you're very understated, for somebody was so accomplished. Well, >>that's kind of you, but I tend to I tend Thio always keep my eye more on what's ahead. You know what's next, then? And you know, I look back Sure to enjoy it and learn from it about what I can put to work making new memories, making new successes. >>Love it. Okay, let's bring Dana into the conversation. Hello, Dana. You look you're a fairly early investor in in on shape when you were with any A And and I think it was like it was a serious B, but it was very right close after the A raise. And and you were and still are a big believer in industrial transformation. So take us back. What did you see about on shape back then? That excited you. >>Thanks. Thanks for that. Yeah. I was lucky to be a early investment in shape. You know, the things that actually attracted me. Don shape were largely around John and, uh, the team. They're really setting out to do something, as John says humbly, something totally new, but really building off of their background was a large part of it. Um, but, you know, I was really intrigued by the design collaboration side of the product. Um, I would say that's frankly what originally attracted me to it. What kept me in the room, you know, in terms of the industrial world was seeing just if you start with collaboration around design what that does to the overall industrial product lifecycle accelerating manufacturing just, you know, modernizing all the manufacturing, just starting with design. So I'm really thankful to the on shape guys, because it was one of the first investments I've made that turned me on to the whole sector. And while just such a great pleasure to work with with John and the whole team there. Now see what they're doing inside PTC. >>And you just launched construct capital this year, right in the middle of a pandemic and which is awesome. I love it. And you're focused on early stage investing. Maybe tell us a little bit about construct capital. What your investment thesis is and you know, one of the big waves that you're hoping to ride. >>Sure, it construct it is literally lifting out of any what I was doing there. Um uh, for on shape, I went on to invest in companies such as desktop metal and Tulip, to name a couple of them form labs, another one in and around the manufacturing space. But our thesis that construct is broader than just, you know, manufacturing and industrial. It really incorporates all of what we'd call foundational industries that have let yet to be fully tech enabled or digitized. Manufacturing is a big piece of it. Supply chain, logistics, transportation of mobility or not, or other big pieces of it. And together they really drive, you know, half of the GDP in the US and have been very under invested. And frankly, they haven't attracted really great founders like they're on in droves. And I think that's going to change. We're seeing, um, entrepreneurs coming out of the tech world orthe Agnelli into these industries and then bringing them back into the tech world, which is which is something that needs to happen. So John and team were certainly early pioneers, and I think, you know, frankly, obviously, that voting with my feet that the next set, a really strong companies are going to come out of the space over the next decade. >>I think it's a huge opportunity to digitize the sort of traditionally non digital organizations. But Dana, you focused. I think it's it's accurate to say you're focused on even Mawr early stage investing now. And I want to understand why you feel it's important to be early. I mean, it's obviously riskier and reward e er, but what do you look for in companies and and founders like John >>Mhm, Um, you know, I think they're different styles of investing all the way up to public market investing. I've always been early stage investors, so I like to work with founders and teams when they're, you know, just starting out. Um, I happened to also think that we were just really early in the whole digital transformation of this world. You know, John and team have been, you know, back from solid works, etcetera around the space for a long time. But again, the downstream impact of what they're doing really changes the whole industry. And and so we're pretty early and in digitally transforming that market. Um, so that's another reason why I wanna invest early now, because I do really firmly believe that the next set of strong companies and strong returns for my own investors will be in the spaces. Um, you know, what I look for in Founders are people that really see the world in a different way. And, you know, sometimes some people think of founders or entrepreneurs is being very risk seeking. You know, if you asked John probably and another successful entrepreneurs, they would call themselves sort of risk averse, because by the time they start the company, they really have isolated all the risk out of it and think that they have given their expertise or what they're seeing their just so compelled to go change something, eh? So I look for that type of attitude experience a Z. You can also tell from John. He's fairly humble. So humility and just focus is also really important. Um, that there's a That's a lot of it. Frankly, >>Excellent. Thank you, John. You got such a rich history in the space. Uh, and one of you could sort of connect the dots over time. I mean, when you look back, what were the major forces that you saw in the market in in the early days? Particularly days of on shape on? And how is that evolved? And what are you seeing today? Well, >>I think I touched on it earlier. Actually, could I just reflect on what Dana said about risk taking for just a quick one and say, throughout my life, from blackjack to starting solid works on shape, it's about taking calculated risks. Yes, you try to eliminate the risk Sa's much as you can, but I always say, I don't mind taking a risk that I'm aware of, and I've calculated through as best I can. I don't like taking risks that I don't know I'm taking. That's right. You >>like to bet on >>sure things as much as you sure things, or at least where you feel you. You've done the research and you see them and you know they're there and you know, you, you you keep that in mind in the room, and I think that's great. And Dana did so much for us. Dana, I want to thank you again. For all that, you did it every step of the way, from where we started to to, you know, your journey with us ended formally but continues informally. Now back to you, Dave, I think, question about the opportunity and how it's shaped up. Well, I think I touched on it earlier when I said It's about helping product developers. You know, our customers of the people build the future off manufactured goods. Anything you think of that would be manufacturing factory. You know, the chair you're sitting in machine that made your coffee. You know, the computer you're using, the trucks that drive by on the street, all the covert product research, the equipment being used to make vaccines. All that stuff is designed by someone, and our job is given the tools to do it better. And I could see the problems that those product developers had that we're slowing them down with using the computing systems of the time. When we built solid works, that was almost 30 years ago. If people don't realize that it was in the early >>nineties and you know, we did the >>best we could for the early nineties, but what we did. We didn't anticipate the world of today. And so people were having problems with just installing the systems. Dave, you wouldn't believe how hard it is to install these systems. You need toe speck up a special windows computer, you know, and make sure you've got all the memory and graphics you need and getting to get that set up. You need to make sure the device drivers air, right, install a big piece of software. Ah, license key. I'm not making this up. They're still around. You may not even know what those are. You know, Dennis laughing because, you know, zero cool people do things like this anymore. Um, and it only runs some windows. You want a second user to use it? They need a copy. They need a code. Are they on the same version? It's a nightmare. The teams change, you know? You just say, Well, get everyone on the software. Well, who's everyone? You know, you got a new vendor today? A new customer tomorrow, a new employee. People come on and off the team. The other problem is the data stored in files, thousands of files. This isn't like a spreadsheet or word processor, where there's one file to pass around these air thousands of files to make one, even a simple product. People were tearing their hair out. John, what do we do? I've got copies everywhere. I don't know where the latest version is. We tried like, you know, locking people out so that only one person can change it At the time that works against speed, it works against innovation. We saw what was happening with Cloud Web and mobile. So what's happened in the years since is every one of the forces that product developers experience the need for speed, the need for innovation, the need to be more efficient with their people in their capital. Resource is every one of those trends have been amplified since we started on shape by a lot of forces in the world. And covert is amplified all those the need for agility and remote work cove it is amplified all that the same time, The acceptance of cloud. You know, a few years ago, people were like cloud, you know, how is that gonna work now They're saying to me, You know, increasingly, how would you ever even have done this without the cloud. How do you make solid works work without the cloud? How would that even happen? You know, once people understand what on shapes about >>and we're the >>Onley full SAS solution software >>as a service, >>full SAS solution in our industry. So what's happened in those years? Same problems we saw earlier, but turn up the gain, their bigger problems. And with cloud, we've seen skepticism of years ago turn into acceptance. And now even embracement in the cova driven new normal. >>Yeah. So a lot of friction in the previous environments cloud obviously a huge factor on, I guess. I guess Dana John could see it coming, you know, in the early days of solid works with, you know, had Salesforce, which is kind of the first major independent SAS player. Well, I guess that was late nineties. So his post solid works, but pre in shape and their work day was, you know, pre on shape in the mid two thousands. And and but But, you know, the bet was on the SAS model was right for Crick had and and product development, you know, which maybe the time wasn't a no brainer. Or maybe it was, I don't know, but Dana is there. Is there anything that you would invest in today? That's not Cloud based? >>Um, that's a great question. I mean, I think we still see things all the time in the manufacturing world that are not cloud based. I think you know, the closer you get to the shop floor in the production environment. Um e think John and the PTC folks would agree with this, too, but that it's, you know, there's reliability requirements, performance requirements. There's still this attitude of, you know, don't touch the printing press. So the cloud is still a little bit scary sometimes. And I think hybrid cloud is a real thing for those or on premise. Solutions, in some cases is still a real thing. What what we're more focused on. And, um, despite whether it's on premise or hybrid or or SAS and Cloud is a frictionless go to market model, um, in the companies we invest in so sass and cloud, or really make that easy to adopt for new users, you know, you sign up, started using a product, um, but whether it's hosted in the cloud, whether it's as you can still distribute buying power. And, um, I would I'm just encouraging customers in the customer world and the more industrial environment to entrust some of their lower level engineers with more budget discretionary spending so they can try more products and unlock innovation. >>Right? The unit economics are so compelling. So let's bring it, you know, toe today's you know, situation. John, you decided to exit about a year ago. You know? What did you see in PTC? Other than the obvious money? What was the strategic fit? >>Yeah, Well, David, I wanna be clear. I didn't exit anything. Really? You >>know, I love you and I don't like that term exit. I >>mean, Dana had exit is a shareholder on and so it's not It's not exit for me. It's just a step in the journey. What we saw in PTC was a partner. First of all, that shared our vision from the top down at PTC. Jim Hempleman, the CEO. He had a great vision for for the impact that SAS can make based on cloud technology and really is Dana of highlighted so much. It's not just the technology is how you go to market and the whole business being run and how you support and make the customers successful. So Jim shared a vision for the potential. And really, really, um said Hey, come join us and we can do this bigger, Better, faster. We expanded the vision really to include this Atlas platform for hosting other SAS applications. That P D. C. I mean, David Day arrived at PTC. I met the head of the academic program. He came over to me and I said, You know, and and how many people on your team? I thought he'd say 5 40 people on the PTC academic team. It was amazing to me because, you know, we were we were just near about 100 people were required are total company. We didn't even have a dedicated academic team and we had ah, lot of students signing up, you know, thousands and thousands. Well, now we have hundreds of thousands of students were approaching a million users and that shows you the power of this team that PTC had combined with our product and technology whom you get a big success for us and for the teachers and students to the world. We're giving them great tools. So so many good things were also putting some PTC technology from other parts of PTC back into on shape. One area, a little spoiler, little sneak peek. Working on taking generative design. Dana knows all about generative design. We couldn't acquire that technology were start up, you know, just to too much to do. But PTC owns one of the best in the business. This frustrated technology we're working on putting that into on shaping our customers. Um, will be happy to see it, hopefully in the coming year sometime. >>It's great to see that two way exchange. Now, you both know very well when you start a company, of course, a very exciting time. You know, a lot of baggage, you know, our customers pulling you in a lot of different directions and asking you for specials. You have this kind of clean slate, so to speak in it. I would think in many ways, John, despite you know, your install base, you have a bit of that dynamic occurring today especially, you know, driven by the forced march to digital transformation that cove it caused. So when you sit down with the team PTC and talk strategy. You now have more global resource is you got cohorts selling opportunities. What's the conversation like in terms of where you want to take the division? >>Well, Dave, you actually you sounds like we should have you coming in and talking about strategy because you've got the strategy down. I mean, we're doing everything said global expansion were able to reach across selling. We got some excellent PTC customers that we can reach reach now and they're finding uses for on shape. I think the plan is to, you know, just go, go, go and grow, grow, grow where we're looking for this year, priorities are expand the product. I mentioned the breath of the product with new things PTC did recently. Another technology that they acquired for on shape. We did an acquisition. It was it was small, wasn't widely announced. It, um, in an area related to interfacing with electrical cad systems. So So we're doing We're expanding the breath of on shape. We're going Maura, depth in the areas were already in. We have enormous opportunity to add more features and functions that's in the product. Go to market. You mentioned it global global presence. That's something we were a little light on a year ago. Now we have a team. Dana may not even know what we have. A non shape, dedicated team in Barcelona, based in Barcelona but throughout Europe were doing multiple languages. Um, the academic program just introduced a new product into that space that z even fueling more success and growth there. Um, and of course, continuing to to invest in customer success and this Atlas platform story I keep mentioning, we're going to soon have We're gonna soon have four other major PTC brands shipping products on our Atlas Saas platform. And so we're really excited about that. That's good for the other PTC products. It's also good for on shape because now there's there's. There's other interesting products that are on shape customers can use take advantage of very easily using, say, a common log in conventions about user experience there, used to invest of all they're SAS based, so they that makes it easier to begin with. So that's some of the exciting things going on. I think you'll see PTC, um, expanding our lead in SAS based applications for this sector for our our target, uh, sectors not just in, um, in cat and data management, but another area. PTC's Big and his augmented reality with of euphoria, product line leader and industrial uses of a R. That's a whole other story we should do. A whole nother show augmented reality. But these products are amazing. You can you can help factory workers people on, uh, people who are left out of the digital transformation. Sometimes we're standing from machine >>all day. >>They can't be sitting like we are doing Zoom. They can wear a R headset in our tools, let them create great content. This is an area Dana is invested in other companies. But what I wanted to note is the new releases of our authoring software. For this, our content getting released this month, used through the Atlas platform, the SAS components of on shape for things like revision management and collaboration on duh workflow activity. All that those are tools that we're able to share leverage. We get a lot of synergy. It's just really good. It's really fun to have a good time. That's >>awesome. And then we're gonna be talking to John MacLean later about that. Let's do a little deeper Dive on that. And, Dana, what is your involvement today with with on shape? But you're looking for you know, which of their customers air actually adopting. And they're gonna disrupt their industries. And you get good pipeline from that. How do you collaborate today? >>That sounds like a great idea. Um, Aziz, John will tell you I'm constantly just asking him for advice and impressions of other entrepreneurs and picking his brain on ideas. No formal relationship clearly, but continue to count John and and John and other people in on shaping in the circle of experts that I rely on for their opinions. >>All right, so we have some questions from the crowd here. Uh, one of the questions is for the dream team. You know, John and Dana. What's your next next collective venture? I don't think we're there yet, are we? No. >>I just say, as Dana said, we love talking to her about. You know, Dana, you just returned the compliment. We would try and give you advice and the deals you're looking at, and I'm sort of casually mentoring at least one of your portfolio entrepreneurs, and that's been a lot of fun for May on, hopefully a value to them. But also Dana. We uran important pipeline to us in the world of some new things that are happening that we wouldn't see if you know you've shown us some things that you've said. What do you think of this business? And for us, it's like, Wow, it's cool to see that's going on And that's what's supposed to work in an ecosystem like this. So we we deeply value the ongoing relationship. And no, we're not starting something new. I got a lot of work left to do with what I'm doing and really happy. But we can We can collaborate in this way on other ventures. >>I like this question to somebody asking With the cloud options like on shape, Wilmore students have stem opportunities s Oh, that's a great question. Are you because of sass and cloud? Are you able to reach? You know, more students? Much more cost effectively. >>Yeah, Dave, I'm so glad that that that I was asked about this because Yes, and it's extremely gratified us. Yes, we are because of cloud, because on shape is the only full cloud full SAS system or industry were able to reach. Stem education brings able to be part of bringing step education to students who couldn't get it otherwise. And one of most gratifying gratifying things to me is the emails were getting from teachers, um, that that really, um, on the phone calls that were they really pour their heart out and say We're able to get to students in areas that have very limited compute resource is that don't have an I T staff where they don't know what computer that the students can have at home, and they probably don't even have a computer. We're talking about being able to teach them on a phone to have an android phone a low end android phone. You can do three D modeling on there with on shape. Now you can't do it any other system, but with on shape, you could do it. And so the teacher can say to the students, They have to have Internet access, and I know there's a huge community that doesn't even have Internet access, and we're not able, unfortunately to help that. But if you have Internet and you have even an android phone, we can enable the educator to teach them. And so we have case after case of saving a stem program or expanding it into the students that need it most is the ones we're helping here. So really excited about that. And we're also able to let in addition to the run on run on whatever computing devices they have, we also offer them the tools they need for remote teaching with a much richer experience. Could you teach solid works remotely? Well, maybe if the student ran it had a windows workstation. You know, big, big, high end workstation. Maybe it could, but it would be like the difference between collaborating with on shape and collaborate with solid works. Like the difference between a zoom video call and talking on the landline phone. You know, it's a much richer experience, and that's what you need. And stem teaching stem is hard, So yeah, we're super super. Um, I'm excited about bringing stem to more students because of cloud yond >>we're talking about innovation for good, and then the discussion, John, you just had it. Really? There could be a whole another vector here. We could discuss on diversity, and I wanna end with just pointing out. So, Dana, your new firm, it's a woman led firm, too. Two women leaders, you know, going forward. So that's awesome to see, so really? Yeah, thumbs up on that. Congratulations on getting that off the ground. >>Thank you. Thank you. >>Okay, so thank you guys. Really appreciate It was a great discussion. I learned a lot and I'm sure the audience did a swell in a moment. We're gonna talk with on shaped customers to see how they're applying tech for good and some of the products that they're building. So keep it right there. I'm Dave Volonte. You're watching innovation for good on the Cube, the global leader in digital tech event coverage. Stay right there. >>Oh, yeah, it's >>yeah, yeah, around >>the globe. It's the Cube presenting innovation for good. Brought to you by on shape. >>Okay, we're back. This is Dave Volonte and you're watching innovation for good. A program on Cuba 3 65 made possible by on shape of PTC company. We're live today really live tv, which is the heritage of the Cube. And now we're gonna go to the sources and talkto on shape customers to find out how they're applying technology to create real world innovations that are changing the world. So let me introduce our panel members. Rafael Gomez Furberg is with the Chan Zuckerberg bio hub. A very big idea. And collaborative nonprofit was initiative that was funded by Mark Zuckerberg and his wife, Priscilla Chan, and really around diagnosing and curing and better managing infectious diseases. So really timely topic. Philip Tabor is also joining us. He's with silver side detectors, which develops neutron detective detection systems. Yet you want to know if early, if neutrons and radiation or in places where you don't want them, So this should be really interesting. And last but not least, Matthew Shields is with the Charlottesville schools and is gonna educate us on how he and his team are educating students in the use of modern engineering tools and techniques. Gentlemen, welcome to the Cuban to the program. This should be really interesting. Thanks for coming on. >>Hi. Or pleasure >>for having us. >>You're very welcome. Okay, let me ask each of you because you're all doing such interesting and compelling work. Let's start with Rafael. Tell us more about the bio hub and your role there, please. >>Okay. Yeah. So you said that I hope is a nonprofit research institution, um, funded by Mark Zuckerberg and his wife, Priscilla Chan. Um, and our main mission is to develop new technologies to help advance medicine and help, hopefully cure and manage diseases. Um, we also have very close collaborations with Universe California, San Francisco, Stanford University and the University California Berkeley on. We tried to bring those universities together, so they collaborate more of biomedical topics. And I manage a team of engineers. They by joining platform. Um, and we're tasked with creating instruments for the laboratory to help the scientist boats inside the organization and also in the partner universities Do their experiments in better ways in ways that they couldn't do before >>in this edition was launched Well, five years ago, >>it was announced at the end of 2016, and we actually started operation with at the beginning of 2017, which is when I joined, um, So this is our third year. >>And how's how's it going? How does it work? I mean, these things take time. >>It's been a fantastic experience. Uh, the organization works beautifully. Um, it was amazing to see it grow From the beginning, I was employee number 12, I think eso When I came in, it was just a nem P office building and empty labs. And very quickly we had something running about. It's amazing eso I'm very proud of the work that we have done to make that possible. Um And then, of course, that's you mentioned now with co vid, um, we've been able to do a lot of very cool work attire being of the pandemic in March, when there was a deficit of testing, uh, capacity in California, we spun up a testing laboratory in record time in about a week. It was crazy. It was a crazy project, Um, but but incredibly satisfying. And we ended up running all the way until the beginning of November, when the lab was finally shut down. We could process about 3000 samples a day. I think at the end of it all, we were able to test about 100 on the order of 100 and 50,000 samples from all over the state. We were providing free testing toe all of the Department of Public Health Department of Public Health in California, which at the media pandemic, had no way to do testing affordably and fast. So I think that was a great service to the state. Now the state has created that testing system that would serve those departments. So then we decided that it was unnecessary to keep going with testing in the other biopsy that would shut down. >>All right. Thank you for that. Now, Now, Philip, you What you do is mind melting. You basically helped keep the world safe. Maybe describe a little bit more about silver sod detectors and what your role is there and how it all works. >>Tour. So we make a nuclear bomb detectors and we also make water detectors. So we try and do our part thio keep the world from blowing up and make it a better place at the same time. Both of these applications use neutron radiation detectors. That's what we make. Put them out by import border crossing places like that. They can help make sure that people aren't smuggling. Shall we say very bad things. Um, there's also a burgeoning field of research and application where you can use neutrons with some pretty cool physics to find water so you could do things. Like what? A detector up in the mountains and measure snowpack. Put it out in the middle of the field and measure soil moisture content. And as you might imagine, there's some really cool applications in, uh, research and agronomy and public policy for this. >>All right, so it's OK, so it's a It's much more than, you know, whatever fighting terrorism, it's there's a riel edge or I kind of i o t application for what you guys >>do. We do both its's to plowshares. You might >>say a mat. I I look at your role is kind of scaling the brain power for for the future. Maybe tell us more about Charlottesville schools and in the mission that you're pursuing and what you do. >>Thank you. Um, I've been in Charlottesville City schools for about 11 or 12 years. I started their teaching, um, a handful of classes, math and science and things like that. But Thescore board and my administration had the crazy idea of starting an engineering program about seven years ago. My background is an engineering is an engineering. My masters is in mechanical and aerospace engineering and um, I basically spent a summer kind of coming up with what might be a fun engineering curriculum for our students. And it started with just me and 30 students about seven years ago, Um, kind of a home spun from scratch curriculum. One of my goals from the outset was to be a completely project based curriculum, and it's now grown. We probably have about six or 700 students, five or six full time teachers. We now have pre engineering going on at the 5th and 6th grade level. I now have students graduating. Uh, you know, graduating after senior year with, like, seven years of engineering under their belt and heading off to doing some pretty cool stuff. So it's It's been a lot of fun building a program and, um, and learning a lot in the process. >>That's awesome. I mean, you know, Cuba's. We've been passionate about things like women in tech, uh, diversity stem. You know, not only do we need more, more students and stem, we need mawr underrepresented women, minorities, etcetera. We were just talking to John Herstek and integrate gration about this is Do you do you feel is though you're I mean, first of all, the work that you do is awesome, but but I'll go one step further. Do you feel as though it's reaching, um, or diverse base? And how is that going? >>That's a great question. I think research shows that a lot of people get funneled into one kind of track or career path or set of interests really early on in their educational career, and sometimes that that funnel is kind of artificial. And so that's one of the reasons we keep pushing back. Um, so our school systems introducing kindergartners to programming on DSO We're trying to push back how we expose students to engineering and to stem fields as early as possible. And we've definitely seen the first of that in my program. In fact, my engineering program, uh, sprung out of an after school in Extracurricular Science Club that actually three girls started at our school. So I think that actually has helped that three girls started the club that eventually is what led to our engineering programs that sort of baked into the DNA and also our eyes a big public school. And we have about 50% of the students are under the poverty line and we e in Charlottesville, which is a big refugee town. And so I've been adamant from Day one that there are no barriers to entry into the program. There's no test you have to take. You don't have to have be taking a certain level of math or anything like that. That's been a lot of fun. To have a really diverse set of kids enter the program and be successful, >>that's final. That's great to hear. So, Philip, I wanna come back to you. You know, I think about maybe some day we'll be able to go back to a sporting events, and I know when I when I'm in there, there's somebody up on the roof looking out for me, you know, watching the crowd, and they have my back. And I think in many ways, the products that you build, you know, our similar. I may not know they're there, but they're keeping us safe or they're measuring things that that that I don't necessarily see. But I wonder if you could talk about a little bit more detail about the products you build and how they're impacting society. >>Sure, so There are certainly a lot of people who are who are watching, trying to make sure things were going well in keeping you safe that you may or may not be aware of. And we try and support ah lot of them. So we have detectors that are that are deployed in a variety of variety of uses, with a number of agencies and governments that dio like I was saying, ports and border crossing some other interesting applications that are looking for looking for signals that should not be there and working closely to fit into the operations these folks do. Onda. We also have a lot of outreach to researchers and scientists trying to help them support the work they're doing. Um, using neutron detection for soil moisture monitoring is a some really cool opportunities for doing it at large scale and with much less, um, expense or complication than would have been done. Previous technologies. Um, you know, they were talking about collaboration in the previous segment. We've been able to join a number of conferences for that, virtually including one that was supposed to be held in Boston, but another one that was held out of the University of Heidelberg in Germany. And, uh, this is sort of things that in some ways, the pandemic is pushing people towards greater collaboration than they would have been able to do. Had it all but in person. >>Yeah, we did. Uh, the cube did live works a couple years ago in Boston. It was awesome show. And I think, you know, with this whole trend toward digit, I call it the Force march to digital. Thanks to cove it I think that's just gonna continue. Thio grow. Rafael. What if you could describe the process that you use to better understand diseases? And what's your organization's involvement? Been in more detail, addressing the cove in pandemic. >>Um, so so we have the bio be structured in, Um um in a way that foster so the combination of technology and science. So we have to scientific tracks, one about infectious diseases and the other one about understanding just basic human biology, how the human body functions, and especially how the cells in the human body function on how they're organized to create tissues in the body. On Ben, it has this set of platforms. Um, mind is one of them by engineering that are all technology rated. So we have data science platform, all about data analysis, machine learning, things like that. Um, we have a mass spectrometry platform is all about mass spectrometry technologies to, um, exploit those ones in service for the scientist on. We have a genomics platform that it's all about sequencing DNA and are gonna, um and then an advanced microscopy. It's all about developing technologies, uh, to look at things with advanced microscopes and developed technologies to marry computation on microscopy. So, um, the scientists set the agenda and the platforms, we just serve their needs, support their needs, and hopefully develop technologies that help them do their experiments better, faster, or allow them to the experiment that they couldn't do in any other way before. Um And so with cove, it because we have that very strong group of scientists that work on have been working on infectious disease before, and especially in viruses, we've been able to very quickly pivot to working on that s O. For example, my team was able to build pretty quickly a machine to automatically purified proteins on is being used to purify all these different important proteins in the cove. It virus the SARS cov to virus Onda. We're sending some of those purified proteins all over the world. Two scientists that are researching the virus and trying to figure out how to develop vaccines, understand how the virus affects the body and all that. Um, so some of the machines we built are having a very direct impact on this. Um, Also for the copy testing lab, we were able to very quickly develop some very simple machines that allowed the lab to function sort of faster and more efficiently. Sort of had a little bit of automation in places where we couldn't find commercial machines that would do it. >>Um, eso Matt. I mean, you gotta be listening to this and thinking about Okay, So someday your students are gonna be working at organizations like like, like Bio Hub and Silver Side. And you know, a lot of young people they're just don't know about you guys, but like my kids, they're really passionate about changing the world. You know, there's way more important than you know, the financial angles and it z e. I gotta believe you're seeing that you're right in the front lines there. >>Really? Um, in fact, when I started the curriculum six or seven years ago, one of the first bits of feedback I got from my students is they said Okay, this is a lot of fun. So I had my students designing projects and programming microcontrollers raspberry, PiS and order we nose and things like that. The first bit of feedback I got from students was they said Okay, when do we get to impact the world? I've heard engineering >>is about >>making the world a better place, and robots are fun and all, but, you know, where is the real impact? And so um, dude, yeah, thanks to the guidance of my students, I'm baking that Maurin. Now I'm like day one of engineering one. We talk about how the things that the tools they're learning and the skills they're gaining, uh, eventually, you know, very soon could be could be used to make the world a better place. >>You know, we all probably heard that famous line by Jeff Hammer Barker. The greatest minds of my generation are trying to figure out how to get people to click on ads. I think we're really generally generationally, finally, at the point where young students and engineering a really, you know, a passionate about affecting society. I wanna get into the product, you know, side and understand how each of you are using on shape and and the value that that it brings. Maybe Raphael, you could start how long you've been using it. You know, what's your experience with it? Let's let's start there. >>I begin for about two years, and I switched to it with some trepidation. You know, I was used to always using the traditional product that you have to install on your computer, that everybody uses that. So I was kind of locked into that. But I started being very frustrated with the way it worked, um, and decided to give on ship chance. Which reputation? Because any change always, you know, causes anxiety. Um, but very quickly my engineers started loving it, Uh, just because it's it's first of all, the learning curve wasn't very difficult at all. You can transfer from one from the traditional product to entree very quickly and easily. You can learn all the concepts very, very fast. It has all the functionality that we needed and and what's best is that it allows to do things that we couldn't do before or we couldn't do easily. Now we can access the our cat documents from anywhere in the world. Um, so when we're in the lab fabricating something or testing a machine, any computer we have next to us or a tablet or on iPhone, we can pull it up and look at the cad and check things or make changes. That's something that couldn't do before because before you had to pay for every installation off the software for the computer, and I couldn't afford to have 20 installations to have some computers with the cat ready to use them like once every six months would have been very inefficient. So we love that part. And the collaboration features are fantastic, especially now with Kobe, that we have to have all the remote meetings eyes fantastic, that you can have another person drive the cad while the whole team is watching that person change the model and do things and point to things that is absolutely revolutionary. We love it. The fact that you have very, very sophisticated version control before it was always a challenge asking people, please, if you create anniversary and apart, how do we name it so that people find it? And then you end up with all these collection of files with names that nobody ever remembers, what they are, the person left. And now nobody knows which version is the right one. A mess with on shape on the version ING system it has, and the fact that you can go back in history off the document and go back to previous version so easily and then go back to the press and version and explore the history of the part that is truly, um, just world changing for us, that we can do that so easily on for me as a manager to manage this collection of information that is critical for our operations. It makes it so much easier because everything is in one place. I don't have to worry about file servers that go down that I have to administer that have to have I t taken care off that have to figure how to keep access to people to those servers when they're at home, and they need a virtual private network and all of that mess disappears. I just simply give give a person in accounting on shape and then magically, they have access to everything in the way I want. And we can manage the lower documents and everything in a way that is absolutely fantastic. >>Feel what was your what? What were some of the concerns you had mentioned? You had some trepidation. Was it a performance? Was it security? You know some of the traditional cloud stuff, and I'm curious as to how, How, whether any of those act manifested really that you had to manage. What were your concerns? >>Look, the main concern is how long is it going to take for everybody in the team to learn to use the system like it and buy into it? Because I don't want to have my engineers using tools against their will write. I want everybody to be happy because that's how they're productive. They're happy, and they enjoyed the tools they have. That was my main concern. I was a little bit worried about the whole concept of not having the files in a place where I couldn't quote unquote seat in some server and on site, but that That's kind of an outdated concept, right? So that took a little bit of a mind shift, but very quickly. Then I started thinking, Look, I have a lot of documents on Google Drive. Like, I don't worry about that. Why would I worry about my cat on on shape, right? Is the same thing. So I just needed to sort of put things in perspective that way. Um, the other, um, you know, the concern was the learning curve, right? Is like, how is he Will be for everybody to and for me to learn it on whether it had all of the features that we needed. And there were a few features that I actually discussed with, um uh, Cody at on shape on, they were actually awesome about using their scripting language in on shape to sort of mimic some of the features of the old cat, uh, in on, shaped in a way that actually works even better than the old system. So it was It was amazing. Yeah, >>Great. Thank you for that, Philip. What's your experience been? Maybe you could take us through your journey within shape. >>Sure. So we've been we've been using on shaped silver side for coming up on about four years now, and we love it. We're very happy with it. We have a very modular product line, so we make anything from detectors that would go into backpacks. Two vehicles, two very large things that a shipping container would go through and saw. Excuse me. Shape helps us to track and collaborate faster on the design. Have multiple people working a same time on a project. And it also helps us to figure out if somebody else comes to us and say, Hey, I want something new how we congrats modules from things that we already have put them together and then keep track of the design development and the different branches and ideas that we have, how they all fit together. A za design comes together, and it's just been fantastic from a mechanical engineering background. I will also say that having used a number of different systems and solid works was the greatest thing since sliced bread. Before I got using on shape, I went, Wow, this is amazing and I really don't want to design in any other platform. After after getting on Lee, a little bit familiar with it. >>You know, it's funny, right? I'll have the speed of technology progression. I was explaining to some young guns the other day how I used to have a daytime er and that was my life. And if I lost that daytime, er I was dead. And I don't know how we weigh existed without, you know, Google maps eso we get anywhere, I don't know, but, uh but so So, Matt, you know, it's interesting to think about, you know, some of the concerns that Raphael brought up, you hear? For instance, you know, all the time. Wow. You know, I get my Amazon bill at the end of the month that zip through the roof in, But the reality is that Yeah, well, maybe you are doing more, but you're doing things that you couldn't have done before. And I think about your experience in teaching and educating. I mean, you so much more limited in terms of the resource is that you would have had to be able to educate people. So what's your experience been with With on shape and what is it enabled? >>Um, yeah, it was actually talking before we went with on shape. We had a previous CAD program, and I was talking to my vendor about it, and he let me know that we were actually one of the biggest CAD shops in the state. Because if you think about it a really big program, you know, really big company might employ. 5, 10, 15, 20 cad guys, right? I mean, when I worked for a large defense contractor, I think there were probably 20 of us as the cad guys. I now have about 300 students doing cat. So there's probably more students with more hours of cat under their belt in my building than there were when I worked for the big defense contractor. Um, but like you mentioned, uh, probably our biggest hurdle is just re sources. And so we want We want one of things I've always prided myself and trying to do in this. Programs provide students with access two tools and skills that they're going to see either in college or in the real world. So it's one of the reason we went with a big professional cad program. There are, you know, sort of K 12 oriented software and programs and things. But, you know, I want my kids coding and python and using slack and using professional type of tools on DSO when it comes to cat. That's just that That was a really hurt. I mean, you know, you could spend $30,000 on one seat of, you know, professional level cad program, and then you need a $30,000 computer to run it on if you're doing a heavy assemblies, Um and so one of my dreams And it was always just a crazy dream. And I was the way I would always pitcher in my school system and say, someday I'm gonna have a kid on a school issued chromebook in subsidized housing, on public WiFi doing professional level bad and that that was a crazy statement until a couple of years ago. So we're really excited that I literally and you know, March and you said the forced march, the forced march into, you know, modernity, March 13th kids sitting in my engineering lab that we spent a lot of money on doing cad March 14th. Those kids were at home on their school issued chromebooks on public WiFi, uh, keeping their designs going and collaborating. And then, yeah, I could go on and on about some of the things you know, the features that we've learned since then they're even better. So it's not like this is some inferior, diminished version of Academy. There's so much about it. Well, I >>wanna I wanna ask you that I may be over my skis on this, but we're seeing we're starting to see the early days of the democratization of CAD and product design. It is the the citizen engineer, I mean, maybe insulting to the engineers in the room, But but is that we're beginning to see that >>I have to believe that everything moves into the cloud. Part of that is democratization that I don't need. I can whether you know, I think artists, you know, I could have a music studio in my basement with a nice enough software package. And Aiken, I could be a professional for now. My wife's a photographer. I'm not allowed to say that I could be a professional photographer with, you know, some cloud based software, and so, yeah, I do think that's part of what we're seeing is more and more technology is moving to the cloud. >>Philip. Rafael Anything you Dad, >>I think I mean, yeah, that that that combination of cloud based cat and then three d printing that is becoming more and more affordable on ubiquitous It's truly transformative, and I think for education is fantastic. I wish when I was a kid I had the opportunity to play with those kinds of things because I was always the late things. But, you know, the in a very primitive way. So, um, I think this is a dream for kids. Teoh be able to do this. And, um, yeah, there's so many other technologies coming on, like Arduino on all of these electronic things that live kids play at home very cheaply with things that back in my day would have been unthinkable. >>So we know there's a go ahead. Philip, please. >>We had a pandemic and silver site moved to a new manufacturing facility this year. I was just on the shop floor, talking with contractors, standing 6 ft apart, pointing at things. But through it all, our CAD system was completely unruffled. Nothing stopped in our development work. Nothing stopped in our support for existing systems in the field. We didn't have to think about it. We had other server issues, but none with our, you know, engineering cad, platform and product development in support world right ahead, which was cool, but also a in that's point. I think it's just really cool what you're doing with the kids. The most interesting secondary and college level engineering work that I did was project based, taken important problem to the world. Go solve it and that is what we do here. That is what my entire career has been. And I'm super excited to see. See what your students are going to be doing, uh, in there home classrooms on their chromebooks now and what they do building on that. >>Yeah, I'm super excited to see your kids coming out of college with engineering degrees because, yeah, I think that Project based experience is so much better than just sitting in a classroom, taking notes and doing math problems on day. I think it will give the kids a much better flavor. What engineering is really about Think a lot of kids get turned off by engineering because they think it's kind of dry because it's just about the math for some very abstract abstract concept on they are there. But I think the most important thing is just that hands on a building and the creativity off, making things that you can touch that you can see that you can see functioning. >>Great. So, you know, we all know the relentless pace of technology progression. So when you think about when you're sitting down with the folks that on shape and there the customer advisor for one of the things that that you want on shape to do that it doesn't do today >>I could start by saying, I just love some of the things that does do because it's such a modern platform. And I think some of these, uh, some some platforms that have a lot of legacy and a lot of history behind them. I think we're dragging some of that behind them. So it's cool to see a platform that seemed to be developed in the modern era, and so that Z it is the Google docks. And so the fact that collaboration and version ing and link sharing is and like platform agnostic abilities, the fact that that seems to be just built into the nature of the thing so far, That's super exciting. As far as things that, uh, to go from there, Um, I don't know, >>Other than price. >>You can't say >>I >>can't say lower price. >>Yeah, so far on P. D. C. S that work with us. Really? Well, so I'm not complaining. There you there, >>right? Yeah. Yeah. No gaps, guys. Whitespace, Come on. >>We've been really enjoying the three week update. Cadence. You know, there's a new version every three weeks and we don't have to install it. We just get all the latest and greatest goodies. One of the trends that we've been following and enjoying is the the help with a revision management and release work flows. Um, and I know that there's more than on shape is working on that we're very excited for, because that's a big important part about making real hardware and supporting it in the field. Something that was cool. They just integrated Cem markup capability. In the last release that took, we were doing that anyway, but we were doing it outside of on shapes. And now we get to streamline our workflow and put it in the CAD system where We're making those changes anyway when we're reviewing drawings and doing this kind of collaboration. And so I think from our perspective, we continue to look forward. Toa further progress on that. There's a lot of capability in the cloud that I think they're just kind of scratching the surface on you, >>right? I would. I mean, you're you're asking to knit. Pick. I would say one of the things that I would like to see is is faster regeneration speed. There are a few times with convicts, necessities that regenerating the document takes a little longer than I would like. It's not a serious issue, but anyway, I I'm being spoiled, >>you know? That's good. I've been doing this a long time, and I like toe ask that question of practitioners and to me, it It's a signal like when you're nit picking and that's what you're struggling to knit. Pick that to me is a sign of a successful product, and and I wonder, I don't know, uh, have the deep dive into the architecture. But are things like alternative processors. You're seeing them hit the market in a big way. Uh, you know, maybe helping address the challenge, But I'm gonna ask you the big, chewy question now. Then we maybe go to some audience questions when you think about the world's biggest problems. I mean, we're global pandemics, obviously top of mind. You think about nutrition, you know, feeding the global community. We've actually done a pretty good job of that. But it's not necessarily with the greatest nutrition, climate change, alternative energy, the economic divides. You've got geopolitical threats and social unrest. Health care is a continuing problem. What's your vision for changing the world and how product innovation for good and be applied to some of the the problems that that you all are passionate about? Big question. Who wants toe start? >>Not biased. But for years I've been saying that if you want to solve the economy, the environment, uh, global unrest, pandemics, education is the case. If you wanna. If you want to, um, make progress in those in those realms, I think funding funding education is probably gonna pay off pretty well. >>Absolutely. And I think Stam is key to that. I mean, all of the ah lot of the well being that we have today and then industrialized countries. Thanks to science and technology, right improvements in health care, improvements in communication, transportation, air conditioning. Um, every aspect of life is touched by science and technology. So I think having more kids studying and understanding that is absolutely key. Yeah, I agree, >>Philip, you got anything to add? >>I think there's some big technical problems in the world today, Raphael and ourselves there certainly working on a couple of them. Think they're also collaboration problems and getting everybody to be able to pull together instead of pulling separately and to be able to spur the ideas on words. So that's where I think the education side is really exciting. What Matt is doing and it just kind of collaboration in general when we could do provide tools to help people do good work. Uh, that is, I think, valuable. >>Yeah, I think that's a very good point. And along those lines, we have some projects that are about creating very low cost instruments for low research settings, places in Africa, Southeast Asia, South America, so that they can do, um, um, biomedical research that it's difficult to do in those place because they don't have the money to buy the fancy lab machines that cost $30,000 an hour. Um, so we're trying to sort of democratize some of those instruments. And I think thanks to tools like Kahn shape then is easier, for example, to have a conversation with somebody in Africa and show them the design that we have and discuss the details of it with them on. But it's amazing, right to have somebody, you know, 10 time zones away, Um, looking really life in real time with you about your design and discussing the details or teaching them how to build a machine, right? Because, um, you know, they have a three D printer. You can you can just give them the design and say like, you build it yourself, uh, even cheaper than and, you know, also billing and shipping it there. Um, so all that that that aspect of it is also super important. I think for any of these efforts to improve some of the hardest part was in the world for climate change. Do you say, as you say, poverty, nutrition issues? Um, you know, availability of water. You have that project at about finding water. Um, if we can also help deploy technologies that teach people remotely how to create their own technologies or how to build their own systems that will help them solve those forms locally. I think that's very powerful. >>Yeah, the point about education is right on. I think some people in the audience may be familiar with the work of Erik Brynjolfsson and Andrew McAfee, the second machine age where they sort of put forth the premise that, uh, is it laid it out. Look, for the first time in history, machines air replacing humans from a cognitive perspective. Machines have always replaced humans, but that's gonna have an impact on jobs. But the answer is not toe protect the past from the future. The answer is education and public policy that really supports that. So I couldn't agree more. I think it's a really great point. Um, we have We do have some questions from the audience. If if we could If I can ask you guys, um, you know, this one kind of stands out. How do you see artificial intelligence? I was just talking about machine intelligence. Um, how do you see that? Impacting the design space guys trying to infuse a I into your product development. Can you tell me? >>Um, absolutely, like, we're using AI for some things, including some of these very low cost instruments that will hopefully help us diagnose certain diseases, especially this is that are very prevalent in the Third World. Um, and some of those diagnostics are these days done by thes armies of technicians that are trained to look under the microscope. But, um, that's a very slow process. Is very error prone and having machine learning systems that can to the same diagnosis faster, cheaper and also little machines that can be taken to very remote places to these villages that have no access to a fancy microscope. To look at a sample from a patient that's very powerful. And I we don't do this, but I have read quite a bit about how certain places air using a Tribune attorneys to actually help them optimize designs for parts. So you get these very interesting looking parts that you would have never thought off a person would have never thought off, but that are incredibly light ink. Earlier, strong and I have all sort of properties that are interesting thanks to artificial intelligence machine learning in particular >>yet another. The advantage you get when when your work is in the cloud I've seen. I mean, there's just so many applications that so if the radiology scan is in the cloud and the radiologist is goes to bed at night, Radiologist could come in in the morning and and say, Oh, the machine while you were sleeping was using artificial intelligence to scan these 40,000 images. And here's the five that we picked out that we think you should take a closer look at. Or like Raphael said, I can design my part. My, my, my, my, my you know, mount or bracket or whatever and go to sleep. And then I wake up in the morning. The machine has improved. It for me has made it strider strider stronger and lighter. Um And so just when your when your work is in the cloud, that's just that's a really cool advantage that you get that you can have machines doing some of your design work for you. >>Yeah, we've been watching, uh, you know, this week is this month, I guess is AWS re invent and it's just amazing to see how much effort is coming around machine learning machine intelligence. You know Amazon has sage maker Google's got, you know, embedded you no ML and big query. Uh, certainly Microsoft with Azure is doing tons of stuff and machine learning. I think the point there is that that these things will be infused in tow R and D and in tow software product by the vendor community. And you all will apply that to your business and and build value through the unique data that your collecting, you know, in your ecosystems. And and that's how you add value. You don't have to be necessarily, you know, developers of artificial intelligence, but you have to be practitioners to apply that. Does that make sense to you, Philip? >>Yeah, absolutely. And I think your point about value is really well chosen. We see AI involved from the physics simulations all the way up to interpreting radiation data, and that's where the value question, I think, is really important because it's is the output of the AI giving helpful information that the people that need to be looking at it. So if it's curating a serious of radiation alert, saying, Hey, like these air the anomalies. You need to look at eyes it, doing that in a way that's going to help a good response on. In some cases, the II is only as good as the people. That sort of gave it a direction and turn it loose. And you want to make sure that you don't have biases or things like that underlying your AI that they're going to result in less than helpful outcomes coming from it. So we spend quite a lot of time thinking about how do we provide the right outcomes to people who are who are relying on our systems? >>That's a great point, right? Humans air biased and humans build models, so models are inherently biased. But then the software is hitting the market. That's gonna help us identify those biases and help us, you know? Of course. Correct. So we're entering Cem some very exciting times, guys. Great conversation. I can't thank you enough for spending the time with us and sharing with our audience the innovations that you're bringing to help the world. So thanks again. >>Thank you so much. >>Thank you. >>Okay. Welcome. Okay. When we come back, John McElheny is gonna join me. He's on shape. Co founder. And he's currently the VP of strategy at PTC. He's gonna join the program. We're gonna take a look at what's next and product innovation. I'm Dave Volonte and you're watching innovation for good on the Cube, the global leader. Digital technology event coverage. We'll be right back. >>Okay? Okay. Yeah. Okay. >>From around >>the globe, it's the Cube. Presenting innovation for good. Brought to you by on shape. >>Okay, welcome back to innovation. For good. With me is John McElheny, who is one of the co founders of On Shape and is now the VP of strategy at PTC. John, it's good to see you. Thanks for making the time to come on the program. Thanks, Dave. So we heard earlier some of the accomplishments that you've made since the acquisition. How has the acquisition affected your strategy? Maybe you could talk about what resource is PTC brought to the table that allowed you toe sort of rethink or evolve your strategy? What can you share with us? >>Sure. You know, a year ago, when when John and myself met with Jim Pepperman early on is we're we're pondering. Started joining PTC one of things became very clear is that we had a very clear shared vision about how we could take the on shape platform and really extended for, for all of the PTC products, particular sort of their augmented reality as well as their their thing works or the i o. T business and their product. And so from the very beginning there was a clear strategy about taking on shape, extending the platform and really investing, um, pretty significantly in the product development as well as go to market side of things, uh, toe to bring on shape out to not only the PTC based but sort of the broader community at large. So So So PTC has been a terrific, terrific, um, sort of partner as we've we've gonna go on after this market together. Eso We've added a lot of resource and product development side of things. Ah, lot of resource and they go to market and customer success and support. So, really, on many fronts, that's been both. Resource is as well a sort of support at the corporate level from from a strategic standpoint and then in the field, we've had wonderful interactions with many large enterprise customers as well as the PTC channels. So it's been really a great a great year. >>Well, and you think about the challenges of in your business going to SAS, which you guys, you know, took on that journey. You know, 78 years ago. Uh, it's not trivial for a lot of companies to make that transition, especially a company that's been around as long as PTC. So So I'm wondering how much you know, I was just asking you How about what PCP TC brought to the table? E gotta believe you're bringing a lot to the table to in terms of the mindset, uh, even things is, is mundane is not the right word, but things like how you compensate salespeople, how you interact with customers, the notion of a service versus a product. I wonder if you could address >>that. Yeah, it's a it's a really great point. In fact, after we had met Jim last year, John and I one of the things we walked out in the seaport area in Boston, one of things we sort of said is, you know, Jim really gets what we're trying to do here and and part of let me bring you into the thinking early on. Part of what Jim talked about is there's lots of, you know, installed base sort of software that's inside of PTC base. That's helped literally thousands of customers around the world. But the idea of moving to sass and all that it entails both from a technology standpoint but also a cultural standpoint. Like How do you not not just compensate the sales people as an example? But how do you think about customer success? In the past, it might have been that you had professional services that you bring out to a customer, help them deploy your solutions. Well, when you're thinking about a SAS based offering, it's really critical that you get customers successful with it. Otherwise, you may have turned, and you know it will be very expensive in terms of your business long term. So you've got to get customers success with software in the very beginning. So you know, Jim really looked at on shape and he said that John and I, from a cultural standpoint, you know, a lot of times companies get acquired and they've acquired technology in the past that they integrate directly into into PTC and then sort of roll it out through their products, are there just reached channel, he said. In some respects, John John, think about it as we're gonna take PTC and we want to integrate it into on shape because we want you to share with us both on the sales side and customer success on marketing on operations. You know all the things because long term, we believe the world is a SAS world, that the whole industry is gonna move too. So really, it was sort of an inverse in terms of the thought process related to normal transactions >>on That makes a lot of sense to me. You mentioned Sharon turns the silent killer of a SAS company, and you know, there's a lot of discussion, you know, in the entrepreneurial community because you live this, you know what's the best path? I mean today, You see, you know, if you watch Silicon Valley double, double, triple triple, but but there's a lot of people who believe, and I wonder, if you come in there is the best path to, you know, in the X Y axis. If if it's if it's uh, growth on one and retention on the other axis. What's the best way to get to the upper right on? Really? The the best path is probably make sure you've nailed obviously the product market fit, But make sure that you can retain customers and then throw gas on the fire. You see a lot of companies they burn out trying to grow too fast, but they haven't figured out, you know that. But there's too much churn. They haven't figured out those metrics. I mean, obviously on shape. You know, you were sort of a pioneer in here. I gotta believe you've figured out that customer retention before you really, You know, put the pedal to the >>metal. Yeah, and you know, growth growth can mask a lot of things, but getting getting customers, especially the engineering space. Nobody goes and sits there and says, Tomorrow we're gonna go and and, you know, put 100 users on this and and immediately swap out all of our existing tools. These tools are very rich and deep in terms of capability, and they become part of the operational process of how a company designs and builds products. So any time anybody is actually going through the purchasing process. Typically, they will run a try along or they'll run a project where they look at. Kind of What? What is this new solution gonna help them dio. How are we gonna orient ourselves for success? Longer term. So for us, you know, getting new customers and customer acquisition is really critical. But getting those customers to actually deploy the solution to be successful with it. You know, we like to sort of, say, the marketing or the lead generation and even some of the initial sales. That's sort of like the Kindle ing. But the fire really starts when customers deploy it and get successful. The solution because they bring other customers into the fold. And then, of course, if they're successful with it, you know, then in fact, you have negative turn which, ironically, means growth in terms of your inside of your install. Bates. >>Right? And you've seen that with some of the emerging, you know, SAS companies, where you're you're actually you know, when you calculate whatever its net retention or renew ALS, it's actually from a dollar standpoint. It's up in the high nineties or even over 100%. >>So >>and that's a trend we're gonna continue. See, I >>wonder >>if we could sort of go back. Uh, and when you guys were starting on shape, some of the things that you saw that you were trying to strategically leverage and what's changed, you know, today we were talking. I was talking to John earlier about in a way, you kinda you kinda got a blank slate is like doing another startup. >>You're >>not. Obviously you've got installed base and customers to service, but But it's a new beginning for you guys. So one of the things that you saw then you know, cloud and and sas and okay, but that's we've been there, done that. What are you seeing? You know today? >>Well, you know, So So this is a journey, of course, that that on shape on its own has gone through it had I'll sort of say, you know, several iterations, both in terms of of of, you know, how do you How do you get customers? How do you How do you get them successful? How do you grow those customers? And now that we've been part of PTC, the question becomes okay. One, There is certainly a higher level of credibility that helps us in terms of our our megaphone is much bigger than it was when we're standalone company. But on top of that now, figuring out how to work with their channel with their direct sales force, you know, they have, um, for example, you know, very large enterprises. Well, many of those customers are not gonna go in forklift out their existing solution to replace it with with on shape. However, many of them do have challenges in their supply chain and communications with contractors and vendors across the globe. And so, you know, finding our fit inside of those large enterprises as they extend out with their their customers is a very interesting area that we've really been sort of incremental to to PTC. And then, you know, they they have access to lots of other technology, like the i o. T business. And now, of course, the augmented reality business that that we can bring things to bear. For example, in the augmented reality world, they've they've got something called expert capture. And this is essentially imagine, you know, in a are ah, headset that allows you to be ableto to speak to it, but also capture images still images in video. And you could take somebody who's doing their task and capture literally the steps that they're taking its geo location and from their builds steps for new employees to be, we'll learn and understand how todo use that technology to help them do their job better. Well, when they do that, if there is replacement products or variation of of some of the tools that that they built the original design instruction set for they now have another version. Well, they have to manage multiple versions. Well, that's what on shape is really great at doing and so taking our technology and helping their solutions as well. So it's not only expanding our customer footprint, it's expanding the application footprint in terms of how we can help them and help customers. >>So that leads me to the tam discussion and again, as part of your strategist role. How do you think about that? Was just talking to some of your customers earlier about the democratization of cat and engineering? You know, I kind of joked, sort of like citizen engineering, but but so that you know, the demographics are changing the number of users potentially that can access the products because the it's so much more of a facile experience. How are you thinking about the total available market? >>It really is a great question, You know, it used to be when you when you sold boxes of software, it was how many engineers were out there. And that's the size of the market. The fact that matter is now when, When you think about access to that information, that data is simply a pane of glass. Whether it's a computer, whether it's a laptop, UH, a a cell phone or whether it's a tablet, the ability to to use different vehicles, access information and data expands the capabilities and power of a system to allow feedback and iteration. I mean, one of the one of the very interesting things is in technology is when you can take something and really unleash it to a larger audience and builds, you know, purpose built applications. You can start to iterate, get better feedback. You know there's a classic case in the clothing industry where Zara, you know, is a fast sort of turnaround. Agile manufacturer. And there was a great New York Times article written a couple years ago. My wife's a fan of Zara, and I think she justifies any purchases by saying, You know, Zara, you gotta purchase it now. Otherwise it may not be there the next time. Yet you go back to the store. They had some people in a store in New York that had this woman's throw kind of covering Shaw. And they said, Well, it would be great if we could have this little clip here so we can hook it through or something. And they sent a note back toe to the factory in Spain, and literally two weeks later they had, you know, 4000 of these things in store, and they sold out because they had a closed loop and iterative process. And so if we could take information and allow people access in multiple ways through different devices and different screens, that could be very specific information that, you know, we remove a lot of the engineering data book, bring the end user products conceptually to somebody that would have had to wait months to get the actual physical prototype, and we could get feedback well, Weaken have a better chance of making sure whatever product we're building is the right product when it ultimately gets delivered to a customer. So it's really it's a much larger market that has to be thought of rather than just the kind of selling A boxes software to an engineer. >>That's a great story. And again, it's gonna be exciting for you guys to see that with. The added resource is that you have a PTC, Um, so let's talk. I promise people we wanna talk about Atlas. Let's talk about the platform. A little bit of Atlas was announced last year. Atlas. For those who don't know it's a SAS space platform, it purports to go beyond product lifecycle management and you You're talking cloud like agility and scale to CAD and product design. But John, you could do a better job than I. What do >>we need to know about Atlas? Well, I think Atlas is a great description because it really is metaphorically sort of holding up all of the PTC applications themselves. But from the very beginning, when John and I met with Jim, part of what we were intrigued about was that he shared a vision that on shape was more than just going to be a cad authoring tool that, in fact, you know, in the past these engineering tools were very powerful, but they were very narrow in their purpose and focus. And we had specialty applications to manage the versions, etcetera. What we did in on shape is we kind of inverted that thinking. We built this collaboration and sharing engine at the core and then kind of wrap the CAD system around it. But that collaboration sharing and version ING engine is really powerful. And it was that vision that Jim had that he shared that we had from the beginning, which was, how do we take this thing to make a platform that could be used for many other applications inside of inside of any company? And so not only do we have a partner application area that is is much like the APP store or Google play store. Uh, that was sort of our first Stan Shih ation of this. This this platform. But now we're extending out to broader applications and much meatier applications. And internally, that's the thing works in the in the augmented reality. But there'll be other applications that ultimately find its way on top of this platform. And so they'll get all the benefits of of the collaboration, sharing the version ing the multi platform, multi device. And that's an extremely extremely, um, strategic leverage point for the company. >>You know, it's interesting, John, you mentioned the seaport before. So PTC, for those who don't know, built a beautiful facility down at the Seaport in Boston. And, of course, when PTC started, you know, back in the mid 19 eighties, there was nothing at the seaport s. >>So it's >>kind of kind of ironic, you know, we were way seeing the transformation of the seaport. We're seeing the transformation of industry and of course, PTC. And I'm sure someday you'll get back into that beautiful office, you know? Wait. Yeah, I'll bet. And, uh and but I wanna bring this up because I want I want you to talk about the future. How you how you see that our industry and you've observed this has moved from very product centric, uh, plat platform centric with sass and cloud. And now we're seeing ecosystems form around those products and platforms and data flowing through the ecosystem powering, you know, new innovation. I wonder if you could paint a picture for us of what the future looks like to you from your vantage point. >>Yeah, I think one of the key words you said there is data because up until now, data for companies really was sort of trapped in different applications. And it wasn't because people were nefarious and they want to keep it limited. It was just the way in which things were built. And, you know, when people use an application like on shape, what ends up happening is there their day to day interaction and everything that they do is actually captured by the platform. And, you know, we don't have access to that data. Of course it's it's the customer's data. But as as an artifact of them using the system than doing their day to day job, what's happening is they're creating huge amounts of information that can then be accessed and analyzed to help them both improve their design process, improve their efficiencies, improve their actual schedules in terms of making sure they can hit delivery times and be able to understand where there might be roadblocks in the future. So the way I see it is companies now are deploying SAS based tools like on shape and an artifact of them. Using that platform is that they have now analytics and tools to better understand and an instrument and manage their business. And then from there, I think you're going to see, because these systems are all you know extremely well. Architected allow through, you know, very structured AP. I calls to connect other SAS based applications. You're gonna start seeing closed loop sort of system. So, for example, people design using on shape, they end up going and deploying their system or installing it, or people use the end using products. People then may call back into the customers support line and report issues, problems, challenges. They'll be able to do traceability back to the underlying design. They'll be able to do trend analysis and defect analysis from the support lines and tie it back and closed loop the product design, manufacture, deployment in the field sort of cycles. In addition, you can imagine there's many things that air sort of as designed. But then when people go on site and they have to install it. There's some alterations modifications. Think about think about like a large air conditioning units for buildings. You go and you go to train and you get a large air conditioning unit that put up on top of building with a crane. They have to build all kinds of adaptors to make sure that that will fit inside of the particulars of that building. You know, with on shape and tools like this, you'll be able to not only take the design of what the air conditioning system might be, but also the all the adapter plates, but also how they installed it. So it sort of as designed as manufactured as stalled. And all these things can be traced, just like if you think about the transformation of customer service or customer contacts. In the early days, you used to have tools that were PC based tools called contact management solution, you know, kind of act or gold mine. And these were basically glorified Elektronik role in Texas. It had a customer names and they had phone numbers and whatever else. And Salesforce and Siebel, you know, these types of systems really broadened out the perspective of what a customer relationship? Waas. So it wasn't just the contact information it was, you know, How did they come to find out about you as a company? So all of the pre sort of marketing and then kind of what happens after they become a customer and it really was a 3 60 view. I think that 3 60 view gets extended to not just to the customers, but also tools and the products they use. And then, of course, the performance information that could come back to the manufacturer. So, you know, as an engineer, one of the things you learn about with systems is the following. And if you remember, when the CD first came out CDs that used to talk about four times over sampling or eight times over sampling and it was really kind of, you know, the fidelity the system. And we know from systems theory that the best way to improve the performance of a system is to actually have more feedback. The more feedback you have, the better system could be. And so that's why you get 16 60 for example, etcetera. Same thing here. The more feedback we have of different parts of a company that a better performance, The company will be better customer relationships. Better, uh, overall financial performance as well. So that's that's the view I have of how these systems all tied together. >>It's a great vision in your point about the data is I think right on. It used to be so fragmented in silos, and in order to take a system view, you've gotta have a system view of the data. Now, for years, we've optimized maybe on one little component of the system and that sometimes we lose sight of the overall outcome. And so what you just described, I think is, I think sets up. You know very well as we exit. Hopefully soon we exit this this covert era on John. I hope that you and I can sit down face to face at a PTC on shape event in the near term >>in the seaport in the >>seaport would tell you that great facility toe have have an event for sure. It >>z wonderful >>there. So So John McElhinney. Thanks so much for for participating in the program. It was really great to have you on, >>right? Thanks, Dave. >>Okay. And I want to thank everyone for participating. Today we have some great guest speakers. And remember, this is a live program. So give us a little bit of time. We're gonna flip this site over toe on demand mode so you can share it with your colleagues and you, or you can come back and and watch the sessions that you heard today. Uh, this is Dave Volonte for the Cube and on shape PTC. Thank you so much for watching innovation for good. Be well, Have a great holiday. And we'll see you next time. Yeah.

>>from around the globe. It's the Cube presenting innovation for good, brought to you by on shape. >>Hello, everyone, and welcome to Innovation for Good Program, hosted by the Cuban. Brought to You by on Shape, which is a PTC company. My name is Dave Valentin. I'm coming to you from our studios outside of Boston. I'll be directing the conversations today. It's a very exciting, all live program. We're gonna look at how product innovation has evolved, where it's going and how engineers, entrepreneurs and educators are applying cutting edge, cutting edge product development techniques and technology to change our world. You know, the pandemic is, of course, profoundly impacted society and altered how individuals and organizations they're gonna be thinking about and approaching the coming decade. Leading technologists, engineers, product developers and educators have responded to the new challenges that we're facing from creating lifesaving products to helping students learn from home toe how to apply the latest product development techniques and solve the world's hardest problems. And in this program, you'll hear from some of the world's leading experts and practitioners on how product development and continuous innovation has evolved, how it's being applied toe positive, positively affect society and importantly where it's going in the coming decades. So let's get started with our first session fueling Tech for good. And with me is John Herstek, who is the president of the Suffers, a service division of PTC, which required on shape just over a year ago, where John was the CEO and co founder. And Dana Grayson is here. She is the co founder and general partner at Construct Capital, a new venture capital firm. Folks, welcome to the program. Thanks so much for coming on. Great >>to be here, Dave. >>All right, John. You're very welcome. Dana. Look, John, let's get into it for first. A belated congratulations on the acquisition of Von Shape. That was an awesome seven year journey for your company. Tell our audience a little bit about the story of on shape, but take us back to Day zero. Why did you and your co founders start on shape? Well, >>actually, start before on shaping the You know, David, I've been in this business for almost 40 years. The business of building software tools for product developers and I had been part of some previous products in the industry and companies that had been in their era. Big changes in this market and about, you know, a little Before founding on shape, we started to see the problems product development teams were having with the traditional tools of that era years ago, and we saw the opportunity presented by Cloud Web and Mobile Technology. And we said, Hey, we could use Cloud Web and Mobile to solve the problems of product developers make their Their business is run better. But we have to build an entirely new system, an entirely new company, to do it. And that's what on shapes about. >>Well, so notwithstanding the challenges of co vid and difficulties this year, how is the first year been as, Ah, division of PTC for you guys? How's business? Anything you can share with us? >>Yeah, our first year of PTC has been awesome. It's been, you know, when you get acquired, Dave, you never You know, you have great optimism, but you never know what life will really be like. It's sort of like getting married or something, you know, until you're really doing it, you don't know. And so I'm happy to say that one year into our acquisition, a TPI TC on shape is thriving. It's worked out better than I could have imagined a year ago. Along always, I mean sales are up. In Q four, our new sales rate grew 80% vs Excuse me, our fiscal Q four Q three. In the calendar year, it grew 80% compared to the year before. Our educational uses skyrocketing with around 400% growth, most recently year to year of students and teachers and co vid. And we've launched a major cloud platform using the core of on shape technology called Atlas. So, um, just tons of exciting things going on a TTC. >>That's awesome. But thank you for sharing some of those metrics. And of course, you're very humble individual. You know, people should know a little bit more about you mentioned, you know, we founded solid works, go founded solid, where I actually found it solid works. You had a great exit in the late nineties. But what I really appreciate is, you know, you're an entrepreneur. You've got a passion for the babies that you helped birth. You stayed with the salt systems for a number of years. The company that quiet, solid works well over a decade. And and, of course, you and I have talked about how you participated in the M I t blackjack team. You know, back in the day a Z I say you're very understated, for somebody was so accomplished. So well, >>that's kind of you. But I tend to I tend Thio always keep my eye more on what's ahead. You know what's next then? And you know, I look back Sure to enjoy it and learn from it about what I can put toe work, making new memories, making new successes. >>I love it. Okay, let's bring Dana into the conversation. Hello, Dana. And you Look, you were fairly early investor in on shape when you were with any A. And I think it was like it was a Siri's B. But it was very right close after the A raise. And and you were and still are a big believer in industrial transformation. So take us back. What did you see about on shape back then? That that excited you? >>Thanks. Thanks for that. Yeah. I was lucky to be a early investment in shape. You know, the things that actually attracted me. Don shape were largely around John and, uh, the team. They're really setting out to do something, as John says humbly, something totally new, but really building off of their background was a large part of it. Um, but, you know, I was really intrigued by the design collaboration side of the product. Um, I would say that's frankly what originally attracted me to it. What kept me in the room, you know, in terms of the industrial world was seeing just if you start with collaboration around design what that does to the overall industrial product lifecycle accelerating manufacturing just, you know, modernizing, manufacturing, just starting with design. So I'm really thankful to the on shape guys, because it was one of the first investments I've made that turned me on to the whole sector. And, wow, just such a great pleasure to work with with John and the whole team there. Now see what they're doing inside PTC, >>and you just launched construct capital this year, right in the middle of a pandemic and which is awesome. I love it. And you're focused on early stage investing. Maybe tell us a little bit about construct capital. What? Your investment thesis is and you know, one of the big waves that you're hoping to ride. >>Sure, it construct it is literally lifting out of any what I was doing there, um uh, you're on shape. I went on to invest in companies such as desktop metal and Tulip, to name a couple of them form labs, another one in and around the manufacturing space. But our thesis it construct is broader than just, you know, manufacturing and industrial. It really incorporates all of what we'd call foundational industries that have let yet to be fully tech enabled or digitized. Manufacturing is a big piece of it. Supply chain, logistics, transportation and mobility or not, or other big pieces of it. And together they really drive, you know, half of the GDP in the US and have been very under invested. And frankly, they haven't attracted really great founders like Iran in droves. And I think that's going to change. We're seeing, um, entrepreneurs coming out of the tech world or staggolee into these industries and then bringing them back into the tech world, which is which is something that needs to happen. So John and team were certainly early pioneers and I think, you know, frankly, obviously, that voting with my feet that the next set, a really strong companies are going to come out of this space over the next decade. >>I think there's a huge opportunity to digitize the sort of traditionally non digital organizations. But Dana, you focused. I think it's it's accurate to say you're focused on even Mawr early stage investing now. And I want to understand why you feel it's important to be early. I mean, it's obviously riskier and reward e er, but what do you look for in companies and and founders like John >>Mhm, Um, you know, I think they're different styles of investing all the way up to public market investing. I've always been early stage investors, so I like to work with founders and teams when they're, you know, just starting out. Um, I happened to also think that we were just really early in the whole digital transformation of this world. You know, John and team have been, you know, back from solid works, etcetera around the space for a long time. But again, the downstream impact of what they're doing really changes the whole industry and and so we're pretty early and in digitally transforming that market. Um, so that's another reason why I wanna invest early now, because I do really firmly believe that the next set of strong companies and strong returns for my own investors will be in the spaces. Um, you know, what I look for in Founders are people that really see the world in a different way. And, you know, sometimes some people think of founders or entrepreneurs is being very risk seeking. You know, if you asked John probably and another successful entrepreneurs, they would call themselves sort of risk averse, because by the time they start the company, they really have isolated all the risk out of it and think that they have given their expertise or what they're seeing their just so compelled to go change something, eh? So I look for that type of attitude experience a Z. You can also tell from John. He's fairly humble. So humility and just focus is also really important. Um, that there's a that's a lot of it. Frankly, >>excellent. Thank you. And John, you got such a rich history in the space in one of you could sort of connect the dots over time. I mean, when you look back, what were the major forces that you saw in the market in in the early days? Uh, particularly days of on shape on how is that evolved? And what are you seeing today? Well, I >>think I touched on it earlier. Actually, could I just reflect on what Dana said about risk taking for just a quick one and say, throughout my life, from blackjack to starting solid works on shape, it's about taking calculated risks. Yes, you try to eliminate the risk sa's much as you can, but I always say, I don't mind taking a risk that I'm aware of, and I've calculated through as best I can. I don't like taking risks that I don't know I'm taking. >>That's right. You like to bet on >>sure things as much sure things, or at least where you feel you. You've done the research and you see them and you know they're there and you know, you, you you keep that in mind in the room, and I think that's great. And Dana did so much for us. Dana, I want to thank you again for all that you did it every step of the way from where we started. Thio, Thio You know your journey with us ended formally but continues informally. Now back to you. Um, Dave, I think question about the opportunity and how it's shaped up. Well, I think I touched on it earlier when I said It's about helping product developers. You know, our customers of the people build the future of manufactured goods. Anything you think of that would be manufacturing factory. You know, the chair you're sitting in machine that made your coffee. You know, the computer you're using that trucks that drive by on the street, all the covert product research, the equipment being used to make vaccines. All that stuff is designed by someone, and our job is given the tools to do it better. And I could see the problems that those product developers had that we're slowing them down with using the computing systems of the time. When we built solid works, that was almost 30 years ago. People don't realize that it was in the early >>nineties, and, you know, we did the >>best we could for the early nineties, but what we did, we didn't anticipate the world of today. And so people were having problems with just installing the systems. Dave, you wouldn't believe how hard it is to install these systems. You need a spec up a special windows computer, you know, and make sure you've got all the memory and graphics you need and getting to get that set up. You need to make sure the device drivers air, right, install a big piece of software. Ah, license key. I'm not making this up. They're still around. You may not even know what those are. You know, Dennis laughing because, you know, zero cool people do things like this anymore on but only runs some windows. You want a second user to use it? They need a copy. They need a code. Are they on the same version? It's a nightmare. The teams change. You know? You just say, Well, get everyone on the software. Well, who's everyone? You know? You got a new vendor today? A new customer tomorrow, a new employee. People come on and off the team. The other problem is the data stored in files, thousands of files. This isn't like a spreadsheet or word processor where there's one file to pass around these air thousands of files to make one, even a simple product. People were tearing their hair out. John, what do we do? I've got copies everywhere. I don't know where the latest version is. We tried like, you know, locking people out so that only one person can change it at the time that works against speed. It works against innovation. We saw what was happening with Cloud Web and mobile. So what's happened in the years since is every one of the forces that product developers experience the need for speed, the need for innovation, the need to be more efficient with their people in their capital. Resource is every one of those trends have been amplified since we started on shape by a lot of forces in the world. And covert is amplified all those the need for agility and remote work cove it is amplified all that the same time, The acceptance of cloud. You know, a few years ago, people were like cloud, you know, how is that gonna work now They're saying to me, you know, increasingly, how would you ever even have done this without the cloud? How do you make solid works Work without the cloud? How would that even happen? You know, And once people understand what on shapes about >>and we're the >>Onley full SAS solution software as a service, full SAS solution in our industry. So what's happened in those years? Same problems we saw earlier, but turn up the gain, their bigger problems. And with cloud, we've seen skepticism of years ago turn into acceptance. And now even embracement in the cova driven new normal. >>Yeah. So a lot of friction in the previous environments cloud obviously a huge factor on, I guess. I guess Dana John could see it coming, you know, in the early days of solid works with Salesforce, which is kind of the first major independent SAS player. Well, I guess that was late nineties. So it was post solid works, but pre in shape and their work day was, you know, pre on shape in the mid two thousands. And and but But, you know, the bet was on the SAS model was right for Crick had and and product development, you know, which Maybe the time wasn't a no brainer. Or maybe it was I don't know, but Dana is there. Is there anything that you would invest in today that's not Cloud based? >>Um, that's a great question. I mean, I think we still see things all the time in the manufacturing world that are not cloud based. I think you know, the closer you get to the shop floor in the production environment. Um, e think John and the PTC folks would agree with this, too, but that it's, you know, there's reliability requirements. There's performance requirements. There's still this attitude of, you know, don't touch the printing press. So the cloud is still a little bit scary sometimes. And I think hybrid cloud is a real thing for those or on premise. Solutions, in some cases is still a real thing. What, what were more focused on. And, um, despite whether it's on premise or hybrid or or SAS and Cloud is a frictionless go to market model, um, in the companies we invest in so sass and cloud, or really make that easy to adopt for new users, you know, you sign up, start using a product, um, but whether it's hosted in the cloud, whether it's as you can still distribute buying power. And, um, I would I'm just encouraging customers in the customer world and the more industrial environment to entrust some of their lower level engineers with more budget discretionary spending so they can try more products and unlock innovation. >>Right? The unit economics are so compelling. So let's bring it, you know, toe today's you know, situation. John, you decided to exit about a year ago. You know? What did you see in PTC? Other than the obvious money? What was the strategic fit? >>Yeah, Well, David, I wanna be clear. I didn't exit anything. Really? You >>know, I love you and I don't like that term exit. I >>mean, Dana had exit is a shareholder on and so it's not It's not exit for me. It's just a step in the journey. Um, what we saw in PTC was a partner. First of all, that shared our vision from the top down at PTC. Jim Hempleman, the CEO. He had a great vision for for the impact that SAS can make based on cloud technology. And really is Dana of highlighted so much. It's not just the technology is how you go to market and the whole business being run and how you support and make the customers successful. So Jim shared a vision for the potential. And really, really, um said Hey, come join us and we can do this bigger, Better, faster. We expanded the vision really to include this Atlas platform for hosting other SAS applications. That P D. C. I mean, David Day arrived at PTC. I met the head of the academic program. He came over to me and I said, You know, and and how many people on your team? I thought he'd say 5 40 people on the PTC academic team. It was amazing to me because, you know, we were we were just near about 100 people were required are total company. We didn't even have a dedicated academic team and we had ah, lot of students signing up, you know, thousands and thousands. Well, now we have hundreds of thousands of students were approaching a million users, and that shows you the power of this team that PTC had combined with our product and technology whom you get a big success for us and for the teachers and students to the world. We're giving them great tools. So so many good things were also putting some PTC technology from other parts of PTC back into on shape. One area, a little spoiler, little sneak peek. Working on taking generative design. Dana knows all about generative design. We couldn't acquire that technology were start up, you know, just to too much to do. But PTC owns one of the best in the business. This frustrated technology we're working on putting that into on shaping our customers. Um, will be happy to see it, hopefully in the coming year sometime. >>It's great to see that two way exchange. Now, you both know very well when you start a company, of course, a very exciting time. You know, a lot of baggage, you know, our customers pulling you in a lot of different directions and asking you for specials. You have this kind of clean slate, so to speak in it. I would think in many ways, John, despite you know, your install base, you have a bit of that dynamic occurring today especially, you know, driven by the forced march to digital transformation that cove it caused. So when you sit down with the team PTC and talk strategy, you now have more global resource is you got cohorts selling opportunities. What's the conversation like in terms of where you want to take the division? >>Well, Dave, you actually you sounds like we should have you coming in and talking about strategy because you've got the strategy down. I mean, we're doing everything said global expansion were able to reach across selling. We've got some excellent PTC customers that we can reach reach now and they're finding uses for on shape. I think the plan is to, you know, just go, go, go and grow, grow, grow where we're looking for this year, priorities are expand the product. I mentioned the breath of the product with new things PTC did recently. Another technology that they acquired for on shape. We did an acquisition. It was it was small, wasn't widely announced. It, um, in an area related to interfacing with electrical cad systems. So? So we're doing We're expanding the breath of on shape. We're going Maura. Depth in the areas were already in. We have enormous opportunity. Add more features and functions that's in the product. Go to market. You mentioned it global global presence. That's something we were a little light on a year ago. Now we have a team. Dana may not even know what we have a non shape, dedicated team in Barcelona, based in Barcelona but throughout Europe were doing multiple languages. Um, the academic program just introduced a new product into that space. That's that's even fueling more success and growth there, Um, and of course, continuing to to invest in customer success. And this Atlas platform story I keep mentioning, we're going to soon have We're gonna soon have four other major PTC brands shipping products on our Atlas Saas platform. And so we're really excited about that. That's good for the other PTC products. It's also good for on shape because now there's there's. There's other interesting products that are on shape customers can use take advantage of very easily using, say, a common log in conventions about user experience there used to invest of all their SAS based, so they that makes it easier to begin with. So that's some of the exciting things going on. I think you'll see P. D. C. Um expanding our lead in saas based applications for this sector for our target sectors, not just in in cat and data management. But another area, PTC's Big and his augmented reality with of euphoria, product line leader and industrial uses of a R. That's a whole other story we should do. A whole nother show augmented reality. But these products are amazing. You can You can help factory workers people on, uh, people who are left out of the digital transformation. Sometimes we're standing from machine >>all day. >>They can't be sitting like we are doing Zoom. They could wear a R headset in our tools. Let them create great content. This is an area Dana is invested in in other companies, but what I wanted to note is the new releases of our authoring software. For this, our content getting released this month, used through the Atlas platform, the SAS components of on shape for things like revision management and collaboration on duh workflow activity. All that those are tools that we're able to share leverage. We get a lot of synergy. It's just really good. It's really fun to We'll have a good time, >>that's awesome. And then we're gonna be talking to John MacLean later about Atlas and do a little deeper dive on that. And, Dana, what is your involvement today with with on shape? But you're looking for you know, which of their customers air actually adopting, and they're gonna disrupt their industries. You get good pipeline from that. How do you collaborate today? >>That sounds like a great idea. Um, a Z John will tell you I'm constantly just ask him for advice and impressions of other entrepreneurs and picking his brain on ideas. No formal relationship clearly, but continue to count John and and John and other people in on shaping in the circle of experts that I rely on for their opinions. >>All right, so we have some questions from the crowd here. Uh, one of the questions is for the dream team. You know, John and Dana. What's your next next collective venture? I don't think we're there yet, are we? No. I >>just say, as Dana said, we love talking to her about. You know, Dana, you just returned the compliment. We would try and give you advice and the deals you're looking at, and I'm sort of casually mentoring at least one of your portfolio entrepreneurs, and that's been a lot of fun for May on hopefully a value to them. But also Dana, We uran important pipeline to us in the world of some new things that are happening that we wouldn't see if you know you've shown us some things that you've said. What do you think of this business? And for us, it's like, Wow, it's cool to see that's going on And that's what's supposed to work in an ecosystem like this. So we we deeply value the ongoing relationship. And no, we're not starting something new. I got a lot of work left to do with what I'm doing and really happy. But we can We can collaborate in this way on other ventures. >>I like this question to somebody asking with the cloud options like on shape, Wilmore students have stem opportunities s Oh, that's a great question. Are you because of sass and cloud? Are you able to reach? You know, more students? Much more cost effectively. >>Yeah, Dave, I'm so glad that that that I was asked about this because Yes, and it's extremely gratifying us. Yes, we are because of cloud, because on shape is the only full cloud full SAS system. Our industry were able to reach stem education brings able to be part of bringing step education to students who couldn't get it otherwise. And one of most gratifying gratifying things to me is the emails were getting from teachers, um, that that really, um, on the phone calls that were they really pour their heart out and say We're able to get to students in areas that have very limited compute resource is that don't have an I T staff where they don't know what computer that the students can have at home, and they probably don't even have a computer. We're talking about being able to teach them on a phone to have an android phone a low end android phone. You could do three D modeling on there with on shape. Now you can't do it any other system, but with on shape, you could do it. And so the teacher can say to the students, They have to have Internet access, and I know there's a huge community that doesn't even have Internet access, and we're not able, unfortunately to help that. But if you have Internet and you have even an android phone, we can enable the educator to teach them. And so we have case after case of saving a stem program or expanding it into the students that need it most is the ones we're helping here. So really excited about that. And we're also able to let in addition to the run on run on whatever computing devices they have, we also offer them the tools they need for remote teaching with a much richer experience. You know, could you teach solid works remotely? Well, maybe if the student ran it had a windows workstation, you know, big, big, high and workstation. Maybe it could, but it would be like the difference between collaborating with on shape and collaborate with solid works. Like the difference between a zoom video call and talking on the landline phone. You know, it's a much richer experience, and that's what you need in stem teaching. Stem is hard. So, yeah, we're super super excited about bringing stem to more students because of clouds. >>Yeah, we're talking about innovation for good, and then the discussion, John, you just had it. Really? There could be a whole another vector here. We could discuss on diversity, and I wanna end with just pointing out So, Dana, your new firm. It's a woman led firm, too. Two women leaders, you know, going forward. So that's awesome to see, so really? Yeah, thumbs up on that. Congratulations on getting that off the ground. Yeah. Thank you. Okay. So thank you guys. Really appreciate It was a great discussion. I learned a lot, and I'm sure the audience did a swell in a moment. We're gonna talk with on shape customers to see how they're applying tech for good and some of the products that they're building. So keep it right there. I'm Dave Volonte. You're watching innovation for good on the Cube, the global leader in digital tech event coverage. Stay right there. Yeah.