 Live from San Francisco, it's theCUBE. Covering Google Cloud Next 2018. Brought to you by Google Cloud and it's ecosystem partners. Hey, welcome back everyone. Live here in San Francisco, it's theCUBE's coverage of Google Cloud and their big conference, Google Next. Hashtag Google Next 18. I'm John Furrier with Dave Vellott there. Next guest is Adam Siegelman, Vice President and Developer Relations at Google. Man, making it all happen. Keeping the trains on time. Keeping everyone motivated. Welcome to theCUBE. Thanks for joining us. Thanks, glad to be here. So first of all, take a step back. What is your job as Developer Relations? I mean, are you herding cats? Are you feeding them great code? Are you overseeing a big team? Google's been very big on open source. You've been part of the code program going back many, many years. Google's always been a steward of open source. And developers are just devouring open source in a big way right now. What's your job? So I run, I look after Developer Relations. There's around 20, 22 million developers in the world. And now we want to make every single one of them successful and build cool things, learn new technology, be part of community. You know, that's something that's super important. So we, I try to rally all of Google, you know, to sort of stand for developers. One of the big trends we're seeing now at open source is that it's becoming such a good norm. It used to be, I remember the days when I was getting into the business back in the late 80s, really 90s. Open source, we kind of had to steal some code here and you kind of, it was radical. It's so normal now and you start to see the clean upstream etiquette, upstream projects. Everyone's contributing, co-creating for a common good. Monetizing downstream has been really well defined. And there's some examples of probably where that could be better. But for the most part, I think people are generally seeing a positive contribution. That's a community dynamic. How do you go to the next level for developers? Because this has turned out to be quite an opportunity to, one, learn, meet new people, learn new skills, and take advantage of new technologies. How do you foster that community? What are you guys doing? Because no one wants the vendors to try to put their fingers in these upstream projects, but they're super important. They're all participating. What's the formula? How does that evolve? How do you see that? You know, Google's been in open source for maybe 20 years, you know, some big contributions early days, things like GCC, you know, like foundational compiler technology. And we have whole businesses that sort of, you know, build around open source, Chrome and the web, Android for mobile. And now we see Kubernetes and cloud and TensorFlow and AI and new things like Knative and Istio. So I think there's a course there where open source can really shape whole ecosystems and create a lot of opportunity and a lot of innovation. And I think the challenge in all that is doing a really healthy, positive community-centric way. And I think that's a real learning we've had in the last couple of years, is great leaders like Sara Novotny have really helped guide us and really interface with open-source communities and foster the right kind of community interactions. And that's a big focus. We're trying to bring that here also. Yeah. And so you had a keynote coming up. I know you got a hard stop and we're going to try to get as many questions as we can. But I want to ask you, what are you going to be talking about on your keynote? What's the topic? Because this is a, I won't say coming out party for Google Cloud in particular, but clearly setting a couple of stakes in the ground on what's going on, enterprise focus, checking the boxes, table stakes are being met, and real tech, high performance, large scale, really a good developer environment. What are you going to talk about at the keynote? Well, I think the customers like HSBC and Target and others are coming to us, not for table stakes. They're coming us for what's next. They're coming us for massive scale Kubernetes. They're coming us for AI. So I think that the introductions we've had so far, things like the cloud services platform, Istio 1.0, Knative, it really shows a bright future of service and AI driven applications. But we're going to talk in the developer keynote tomorrow in day three is really three themes, innovation, openness and open source, and then that community theme that we were just talking about. And one area of innovation that we're going to talk about is Mellie McVessel, who I think you talked to earlier, is going to talk about our approach to cloud build and integrated tool chains. We have a lot of technology we're going to open up in sort of the DevOps space. But it's really a mentality, and this is the thing that I think is really neat coming to Google, is it's not just about pushing codes sort of down the waterfall of the production. It's about building services for users and building service other developers consume and really flowing from code right out to running services. And then when you're done, the services turn on for everybody. You start routing traffic to it, right? You run Canaries. So it's a big step change in how we think about continuous delivery and DevOps. We really want to land that in the keynote tomorrow. So I got to give some props to my partner, John Furrier. In 2010, John, you said data is the new development kit. And that was a while ago, and it's turned out, in my view, anyway, to be true. But Adam, it's also changed the profile of the developer. Data hackers, statisticians, mathematicians, artists. And so it's changed the way in which we think about a developer. I wonder if you could talk about that in terms of how that's changed developer relations. Yufeng Gao is going to do a section AI in the keynote, and he does these videos on YouTube that literally millions of people have watched on how to get started in machine learning. And he's got a great line in there, which I think is a tribute to him, that says AI is programming with data. And so I think we're in a world where all this data of user interactions and event streams and Internet of Things and mobile applications, we now have a lot of data to program the world on. And I think it's an incredible opportunity for developers. But the flip side, if we just restrict it to a couple thousand data scientists, it doesn't open up the world to everyone. So I think beyond that 20 million, like what are the next 20 million we could pull in with AutoML? You know, the next 20 million that can do SQL queries and can use BigQuery and do ML and BigQuery. So that's the vision of opening it up to more people, more developers. And the democratization of software. I mean, it's interesting, that's my background in software engineering, computer science. In the 80s, you were called software engineering. Then it became software developer. Then it became a software hacker. Now we're hearing words like software artisan. So with, you know, interview a partner, she said, you don't need three PhDs to three degrees in computer science to do development anymore. The aperture is widening big time because now craft is coming back to development because a lot of these abstractions, both on the business and tech side are enabling different personas to come in. Yeah, it's not legacy development anymore. It's heritage development, right? Yeah, I love that developers have the freedom to define their own titles and define their own tools they want to work with and do a mix of the old and the new and mix it up. And so I think it's really important that we're not too narrow in how we define people. And you don't have to be this tall to ride the ride. And we really welcome everybody to be part of the community. And if your entrance to ML is auto ML, but then eventually you graduate to TPUs, that's just fantastic. And how about crypto developers? I mean, they've exploded with innovation. I mean, what are you seeing there? I could just go back to security. I think every company is really wrestling with security right now. Yeah, how do they get to factor everywhere? How do they stop phishing? How do they keep their employees safe? How do they have shielded VMs? Like at every level of security. And it's a challenge to get developers to think about security sometime. Like it's the operators that have to live with it. And so, you know, understanding your dependencies way back up with developers are like, oh, I'll just use this library and I'll just use this library. How do you ensure you're using trusted, you know, dependencies back there? You don't have vulnerabilities. You're introducing by taking dependencies and other codes. So I think there's a lot of education and best practices to share with developers to get them to care about security. My final question, I know you got to go, just want to get out there. Years ago when we used to, Dave and I used to hear on theCUBE, people come on, we want to win the developers. Well, no, they're not winnable. You don't win developers. You earn trust and you earn relationships and then they might work with you and enjoy the services that they might provide to them. So I always kind of used to poo poo that. But now with the cloud, you're seeing, again, more range of developers. So how do you keep developers happy? I might be a better question because in order to earn and have a relationship with people who are going to be contributing IP and building IP, how do you keep harmonious relations? How do you keep people happy? We hear things like technical debt bothers people and people like, oh, technical debt, shipping code times. So this, how do you think about that? Because keeping people happy is a broad answer. But in general, what's your view on keeping developers happy, harmonious, loving, working together, doing the things that they love to do? You know, it's different, it's a little different in Google's an interesting place because there's like never an us and them with developers. I mean, there's a company with tens of thousands of engineers on staff. Most of the senior leadership team have an engineering background. So it's kind of more like, we live in the community of developers. My engineers are all over the world living in developer communities. And so I think it really does matter how we show up and how we interact, but we sort of live it every day. So I don't think we have a hill to climb so much as get to developers. I think we just have to have a really clear narrative and then a really keen ear to listen to what they need. And that's what I'm trying to orient the team around. I think that's a great answer, listening. What do you want? You know, what's important to you? And then you have that perspective yourselves. Yeah, well, I mean, we're sort of a developer-centric company. And I think the important thing is we can put them at the center of everything we do. And I use the word of my team, it's empathy. We have empathy for developers. You know, they have great jobs, great opportunities, but also great challenges. And as humans, can we have empathy for them? I was hosting a panel one time. A bunch of night events, all out of fun. Bunch of nerds on there. We're talking tech and on the hood, talking about developers, all this stuff. Range of questions. And one guy introduced himself as the, I'm the CTO, I'm the chief toy officer. Because we play with technology and we turn it into product. That's kind of, you guys brought a lot of toys out here with Google, all this open source. And then if we can amplify that for all the amazing talent that's in the world, at Google I.O., we host the developer student clubs from Indonesia. And these young Indonesian women are teaching other college kids how to do Android development. So we can bring that kind of magic to all of our assets, to the cloud assets. I think there's this amazing, receptive community out there that could give us a whole bunch of new ideas that we don't just get in South of Market, San Francisco. It's inspiring to see people build things open source, pay it forward, contribute upstream, be part of a community. This is what it's all about, developer relations. Congratulations. Thanks for coming on theCUBE. Really appreciate you to be here. Thanks guys for it. Thanks Adam. Great stuff. This is theCUBE, paying it forward, the content here from Google Next, all out in the open, co-creating with Google, Google's team, Google's customers, the best engineers, the best talent here at Google Cloud. I'm with theCUBE. I'm John Furrier, Dave Vellante. Thanks for watching. Stay with us. More coverage after this short break.