>> Live from Seattle, Washington, it's theCUBE, covering KubeCon and CloudNativeCon North America 2018, brought to you by Red Hat, the Cloud Native Computing Foundation, and its ecosystem partners. >> Hello everyone, welcome back to the live Cube coverage here, three days at Seattle's KubeCon and CloudNativeCon. It's a conference put on by the Linux Foundation. Cube's been there from the beginning, breaking down all the action. 8,000 people, doubling attendance from the last one, now global, on a global scale, seen great traction in China and other areas around the world. It's about the cloud global. I'm John Furrier with Stu Miniman, our next guest, Kelsey Hightower with Google. Former code program share, now out in the wild on his own, super dope, playing with all kinds of new technology, it's great to see you, thanks for coming on. >> Proper you said the word dope, by the way, so congratulations there. I'm an attendee, I still have a keynote on Thursday but I do get to enjoy the floor like everyone else. >> So what's new, so you're now, again, there's a lot of pressure now every year. It's more and more people here, so it's a lot of pressure to kind of get all the action packed, but the growth has been pretty phenomenal. You've been looking at serverless, we saw some tweets, again you mention it's super dope, serverless is. You've got serverless, you've got a lot of stuff going on within the CNC app, you've got Kubernetes at the core. A lot of people like calling it the Kubernetes stack or the CNCF stack. Is it really a stack, is it really more of an operating model because there's stacks involved but how do you describe it, because this is a point of clarification. I mean, Kubernetes isn't necessarily a stack. Is it, how do people use it, what's the current state? >> I think when people say stack, you think about the LAMP stack, right? Linux, Apache, MySQL, it's a way of pre-packaging these ideas. This is something that worked for me, it may work for you, you say that enough times and then you say things like the Kubernetes stack. It's a quick, shorthand for Kubernetes and building on top of it. I think from the engineering perspective, when you look at Kubernetes and all the gaps that the CNC app is trying to fill these days, it's all this stuff you're probably building yourself, someone else is building it, and now we kind of have an outlet now. If you're working on a service mesh like list was, you have an outlet to give it to the rest of the world, open governance, and get some contributors. I think what we're seeing now is that hey, CNCF is kind of the place people go to figure out is someone building the thing that I've already started building and can I stop and just download that and go off? >> It's been very successful open source community, obviously, it's been end user leverage, it's been great and it's been open source, community led. Not so much vendor led, but vendors have been participating, so it's been great, but now as Kubernetes is going mainstream, the rise of Kubernetes is undeniable. No one can really deny that. Other end users are now coming in either to participate or to consume Kubernetes. How is that going in your mind? What's going on in the landscape, because people want multicloud, they want hybrid, they want choice. How are end users coming into the ecosystem to consume Kubernetes and the variety of goodness around it and what's going on there? Can you give some color around that option? >> I think regardless of the industry buzzwords like multicloud and hybrid and all that, Kubernetes is good on its own. It solves a lot of problems that your previous tools didn't solve, so people are gravitating towards it regardless in that direction. When you start to talk about portability, yes, it's nice to have two different environments and have the same tools work in a similar way between those environments, that's working well. The people that started three years ago that were doing it themselves, they're finding value and treating that as a service. We saw this happen to DNS, e-mail, so people are saying maybe the value isn't running it myself, so now you kind of see the vendor ecosystem understand what the value is. For a lot of the cloud providers, it's running Kubernetes, patching it, updating it, upgrading it, so that you can go focus on the other parts on top. That's where I think we are as an industry, and then there's gaps to fill, so that's where you see things like native, people building CI-CD tools on top, that's just where the new opportunities are so I think we've kind of matured. People kind of know what Kubernetes is, they know where their value line is for Kubernetes, now they're looking for their partners or vendors or community to just layer the new stuff on top. >> Kelsey, you bring up a great point there because understanding that line of what I should do myself and what I have to do versus what I can buy, consume as a service, is really tough for people, you know. I always say, ask IT departments, what do you really suck at? Because there's somebody else that probably does it better. A year ago, when I talked to users at this show, they were really downloading stuff, putting their things together, and when you asked them why, it was well, the Azure stuff hasn't matured. It just released, Amazon, I'm not sure where they're going with it. It feels like a lot has changed in the last year. You did Amazon the hard way a little over a year ago. What has changed over the last year, you know. >> We saw this with Linux, right? >> Are we ready for that, yeah. >> In Linux everyone use to build their own Linux distro, you took pride in it, using Gentoo and Slackware, and then you're like, I'm tired of that so you go get Red Hat or Ubuntu and call it good, and then you go focus on the other things. Naturally, Kubernetes is early project, has lots of gaps, you can fill those gaps by gluing together open source yourself, but now most of the managed services fill in the gaps by default. You click a button in GKE and a thing comes up, it's secure, has most of the pieces you need, it's integrated, you're like alright, I'm done with that part. >> The other thing, we talked a year ago. There's lots of companies here that are involved in Kubernetes. We've got over 70 that are compliant, and then you've got the service providers. From what I hear, it's people aren't trying to differentiate with Kubernetes and that's probably a good thing. It's something that's going to be baked into the platform, it's something you're going to consume with the other services that I offer, what do you say? >> If you make it different, then it won't work. >> Right. >> It'll be a different thing, so if you make it too different then you lose most of the benefits that we're all talking about here. The ability to learn a set of abstractions once, kind of like we did on Linux, if you start changing the system calls on Linux, then it's not Linux anymore, it's a different thing. >> Just to clarify though, if I'm running in one cloud that has their Kubernetes and I want to go to another, is it similar enough? Can I make that move? Do I need a vendor-independent version? >> So I think up to this value line I've run this container, ship the log somewhere, give me a way to secure access, that's pretty standard. Give me a load balancer. What isn't standard is how do I do CI-DC on top of that, that's not standard. There's different opinions on how to do that. If I'm in Google Cloud, we have IEM one way, Azure has IEM a different way, and same thing for Amazon. There's things around networking, security, that are going to be different based on the environment you're in. Same for on-prem, and that's where you start to look for help. If I go to Google, I'm going to use GKE maybe instead of running it myself on just a bunch of VMs, so that's where you kind of see that little divide. >> Is that going to be custom work, that's a great point, security for instance, we'll just pull that out there. Is that going to automate and be seamless or is that going to be a work area that's always going to have to be differentiated or coded or? >> So for example, we have the big vulnerability recently in Kubernetes world, right? >> It's a big CVE, it affected everyone running Kubernetes. That's a thing, as a vendor, for us GKE people, we upgraded automatically for them and said hey, there's a CVE, it's going to be really scary when you read about it but hey, you're patched. We've taken care of you, so I think people will still look for that relationship. Will it always be custom? At the app level, that is a different story. When you run your container and you want to access the things in your environment, so if you're in Google Cloud you may want to talk to Spanner, you're going to need an IEM set of credentials. That's a little out of scope of Kubernetes, so that's going to be integration work that the provider will do. >> So the holy trinity of computing industry has always been storage, network, and compute, and it changes certainly with cloud and all the goodness that comes out from serverless and whatnot, so containers is interesting. We always love containers but I've heard conversations recently where it's like hey, I want to treat containers not as a first class citizen because it doesn't meet my security boundary. I'm going to put a VM around that and run that under the covers with say, Lambda. Is that feasible, is than an option? I've heard talk about it, is anyone doing that? Is that an alternative, is this going to introduce new elements? >> Let's put it right, in Kubernetes by defaults we chose to build on top of Docker. Industry momentum, great developer workflow, but you're right, it made a security trade off. We know VMs are a much tighter security boundary that people are comfortable with. In that world, at that time, they were too slow for what we needed to happen. Thanks to Intel and others who pulled the thread of let's make VMs faster. Recently you heard the announcement of Firecracker, right, it's part of a derivative from the Chrome VM and that thing is optimized for these kinds of workloads, containers and serverless workloads. Now we go from 10, 20 seconds to hundred milliseconds. Now it makes sense to probably have this become an underlying thing. Now that we have the speed, maybe people say hey, we can maybe take the security without sacrificing the performance. >> That's the trade off. >> Pulled on the thread, you mentioned Firecracker. There's still this tension between what's happening in Kubernetes and serverless. We saw Knative is a hot topic point. It's probably natural that there's some tension there because it's like oh wait, why do you need to learn any of this stuff because if serverless will just make it as a service and make it easy and you don't need to learn all that container stuff and everything, what do you say? >> If you're a Kubernetes user, if you really think about the very broad definition of serverless, meaning I'm not managing the database, I'm using a managed database, serverless database. Storage, I'm using S3 or Google Cloud storage, serverless. Your load balancer, also serverless. So most people in the Kubernetes ecosystem, networking, serverless, storage, serverless, their database, serverless. The only thing that you can say isn't serverless is this compute component, everything else is. Now people are looking at serverless as this spectrum. How serverless are you? If you're on-prem and you buy a server and you rack it and install Kubernetes, you're less serverless, you're probably not serverless at all, no matter what you do. Now, if you put a lot of work in, you can probably put a serverless interface on top. This is what native is designed to do for people. Maybe you have an organization that supports multiple businesses inside of your org. They may not know anything about Kubernetes. You just tell them hey, put your code here, it will run, oh, that feels serverless. You can provide a serverless experience. The delta then becomes what can we do between a container and a function, so the foundation of my keynote is exactly that. What does it mean to take a container and put it into Lambda? What do you have to change? In my presentation, I don't even read write the code. There's a small shim between the two worlds because you're already using managed services around it. We're not talking about throwing away Kubernetes and then starting over our entire architecture. We're swapping out the compute layer. One is a subset of the other. Lambda is about events and functions, Kubernetes is about container and run it however you want. You want to run it when an event comes in, that's native. You want to run it as a batch job, run it as a job. You want to run it as a long running service, run it as a deployment, so that's all we're really talking about here. When we break it down, you're just talking about compute. >> You talk a lot about automation in the CI-CD areas, that differentiation where the value is. In a world as automation goes faster, what does Kubernetes look like when it becomes automated away? Because I don't want to manage anything, why even have managed Kubernetes? It should just automatically, you mentioned the patching. In an automated world, is Kubernetes just running under the covers, how does Kubernetes look down the road in your mind, in terms of when automation comes in? >> I've been in this game maybe over 15 years and one thing holds true: most developers want to focus on the business logic. We hire them because that's their skillset. When they check in code, it would be really nice if you can take it from there and get it where it needs to be. That's been the holy grail. We see it in mobile, you build an app, you put it on the App Store, Apple gets it to every device on the planet, done. Now it's the server side turn to do this. Whether you're doing serverless functions, Kubernetes, VMWare, or Linux, if you have CI-CD in front of any of that, the developer can still have the same experience. I check in code and you're picking a different deploy target. If you did that five years ago, and you understood it, and you were using, let's say maybe Mesos or just VMs, you bring in Kubernetes, you don't even have to change this part of the equation. This is why I tell most people, just focus on this endgame. My keynote last year was about this is the endgame because this is your coacher, this is your change management process, this is your discipline, and this is just a target where that compute goes. >> Alright, we've got two minutes left. I want to get your thoughts and share with the audience who's not here, a big waiting list, I know there's some lobby con going on all around Seattle, people flew in. Great place too to actually have some good lobby con meetings around the lobby area. So what's happening here, in your mind's eye, now you're not in the throes of all the events, you're kind of in the wild here with us, everyone else. What's the top story, what's going on, what's the vibe, what are you extracting out of all this activity as a top story, top level stories here? >> I think everyone's finding their place. If you're a security vendor, you kind of know where your line is, right? I've got this Twistlock shirt on. They want to plan a world where they need to integrate closer to the developer workflow, not just on the infrastructure side. If you're selling load balancers, service mesh is a thing, where do you fit in? The lines are getting a lot clearer. Kubernetes is starting to say maybe we should stop here. Maybe service measures should take it from here and that's where Istio comes in. Traditional vendors can now play in this well-defined space. On the storage side, what are you integrating? Now we have the storage interface, like the container storage interface. Now, if you're a net app, you know where you fit into the puzzle. You don't need to have your own Kubernetes distro. Two years ago, everyone was trying to come out with their own Kubernetes distro so they can actually have an anchor. Now you're like, ah, now I know where to play and now we also know what's missing. After years of doing this, people look back and say there's a lot of stuff missing. It's OK now to go create something new. >> It's a clear visibility into the landscape. What about the impact to end users? What is notable in your mind in terms of highlights, impact to end user organizations really going through this quote digital transformation, which is very cloud-based of course, but they're certainly changing and impacting, what's your thoughts on the end user? >> We're using some of the same words now. Forget the technology piece, now we can all start to talk about the same things, so when we say container, we kind of now are talking about the same thing. When we start to talk about sidecars, whether that's a service mesh, Envoy sidecar, or something that adapts your existing code to the new world, now that we're using the same language, we can actually talk. Traditional enterprise can talk to the startups and have a meaningful conversation. >> That's awesome, any other observations here in terms of the size of the show? Got a lot more activity, feels a little bit like re:Invent, I'm bumping into people, swimming through the crowds, the swag's hot. >> It's 8,000 people here and it feels like there's more users that know nothing about Kubernetes so even though we're about five years in, it reminds me of when we were just getting started. >> Lot more work to do but great, congratulations on all the work you've done Kelsey. Really appreciate you taking the time every year to come on theCUBE. We love having you on, great commentary, great keynotes, very entertaining. Thanks for coming on, appreciate it. >> Awesome, thank you. >> I'm John Furrier, Cube here with Kelsey Hightower telling us about all the breakdown of KubeCon, CloudNativeCon, the beginning of the cloud tsunami is happening, certainly changing businesses, changing open source, it's changing, it's on a global scale. We're here with coverage for three days. We'll be right back with more after this short break.

(upbeat music) >> Narrator: Live from Las Vegas, it's theCube covering InterConnect 2017. Brought to you by IBM. >> Okay welcome back everyone. We're here live in Las Vegas the Mandalay Bay for IBM InterConnect 2017. This is the Cube coverage I'm John Furrier my cohost Dave Vellante, our next guest is our famous Cube alumni, Tanmay Bakshi welcome back to the Cube. Now you're a cognitive developer and your new business card as part of the Darwin Ecosystem says Algorithmist. >> Dave: Algorithmist. >> Algorithmist, yes. >> John: Welcome back. >> Thank you, I'm very glad to be back on theCube. And yes, of course, as I said, I'm working on many new projects with artificial intelligence, and, of course, IBM Watson. Including ones that are provided by Darwin Ecosystem. And of course, we're working on this really interesting project called A Cognitive Story, which you will be seeing more about on my talks on Tuesday and Wednesday. The Cognitive Story is basically this collaboration between IBM, Darwin Ecosystem, Not Rocket Science, and me. Basically we're working towards really using the power of cognitive in order to change people's lives in a positive way. That's what I'm doing at the Darwin Ecosystem, generally, with IBM Watson and AI. >> Last year, we had a great chat. I remember talking about algorithms, the software, super fun. What's changed in the past year? Give us the update on you. And, two, what's changed in the code? >> Definitely. >> What are some of the things you're working on? >> Yeah, sure. So, since last year, first of all, a lot has changed. A lot of new trends have emerged in the general topic of technology, like Cybersecurity, something that people are starting to take a lot more seriously now. With things like AI and IBM Watson starting to be incorporated in with that. And, of course, though, really from my side, what I've mainly been doing is not, I've actually started to work not only with IBM Watson's cognitive capabilities, and not only the cognitive capabilities provided by these services, but also my own custom services. Crowd by neural networks, and other machine learning algorithms. Like, just for example, A Cognitive Story is powered by my own custom coded neural networks. And that's why, of course, I've been given the designation of Algorithmist. Because I love to work with algorithms, fine tune them, and, of course, design them. So that's actually what's been going on for the past year. But mainly, I guess you could say now my real focus is on how we can use artificial intelligence and cognitive computing in order to first of all, amplify and really augment human capability, and, of course, how we can use it to change people's lives in a positive way. Especially in fields like health care, where we can save people's lives with this technology, where we can make people's lives easier with this technology. Like, just for example, what IBM Watson is doing, for people with Autism, and how it's helping them with the applications that it provides. What IBM Watson's doing for the elderly in India, with the new Gentoo Robot that IBM Watson is creating, and so much that Watson is doing with healthcare. That's really what I'm focused in, with cognitive computing in general. >> What are some of the algorithms that you've been working on? What's the intent? >> Sure, well, I've actually been working on a lot of different algorithms. Mainly in the AI space, and, of course, how we can create neural networks to understand brainwave patterns. And you'll be seeing more of that on Tuesday and Wednesday, with The Cognitive Story. But, I've also been working, of course, on algorithms that I've already created, as I said, AskTanmay, you probably remember that from last year, the NLQA system. I've been working more on AskTanmay, and, in fact, in June, in Developer Connective last year, I actually open-sourced AskTanmay. So, of course, I've been working on that, improving it. I'm about to release Version 3, which is really fun. And, of course, since it's open source, I love to share my knowledge with this code so that other people can learn from it and learn how to use this type of AI technology in their own applications, as well. >> As a young, next generation, mogul, software mogul that you'll soon be, you're already one now, but you're still young, you've got a lot more ways to go, but you're living in a great time because, I wish I could be your age right now, because machine learning is really hot right now. And it's growing because of the cloud. The cloud gives you scale and compute power, and there's also a cultural vibe going on around social good. So, talk about machine learning, what you're excited about there, specifically, and some of the things that you see, from your generation of developers around this desire to provide social good. >> Yeah, definitely. Well, I guess we should start off with, really, my main focus of interest, in fact, as you said, are really cloud computing, cognitive computing, and IOT. Because in their respective fields, they are the next level of computing. And, in fact, we're already starting to adopt them. Cloud computing's already been adopted on a huge scale. Cognitive computing, we're getting there. And IOT's, again, starting to be accepted by a lot of different people. >> And you might not even get a driver's license because by the time you get your driver's license there's going to be autonomous vehicles. >> Exactly, and so, of course, IOT's being used everywhere, and so is cloud computing and cognitive. So, really, what I've been focused on in the past year is, first of all, trying to get developers really interested in cognitive. But as you said, developers are really interested in doing social good with these technologies, and, just imagine this, what we're doing with The Cognitive Story right now is, we're basically, for example, I can't, of course, go into too much detail about this right now, yet, but we are basically taking this cognitive services and we're allowing people who don't have the natural ability to be able to express themselves, or communicate, or move in any way, really, to be able to express themselves, and communicate their decisions, and communicate their emotion, or whether or not they're comfortable, and more, through this cognitive system. And, of course, that's why it's so interesting, because imagine if you can't talk, and imagine if you know that, OK, I want to do this, but you're unable to express that, you're unable to communicate that to the people around you, that means that you're quite literally trapped in your own body. And having cognitive computing able to come in and allow you to communicate, and create your own, I guess you could say, unique language using these brainwave patterns. That's something that I absolutely believe is, I guess you could say, the greatest gift, ever. To be able to give you the ability to communicate through artificial intelligence. That's really why I love working the healthcare field. >> Now, am I right, you've written a book? >> Yes, actually, and it actually started from last InterConnect. Last Interconnect, I started, and now I'm actually done writing my book, called, "Hello Swift!: IOS App Programming "for Kids and Other Beginners" and it's actually currently available for pre-order on the publisher's website, as well as lots of other book stores online. Of course, the final hard copy will be released soon. But basically, this book is really targeted towards getting the youth, and, really, kids, interested in programming, and specifically, IOS programming through Swift. And, of course, as you know, Swift is open-sourced, and I really support open source software. >> What are some of the cool things young kids want in software these days? Because, like I said, there is a tool chest of great stuff coming on, like composable software, Lego blocks, which people called like Lego blocks. What are some of the cool things that kids want these days? >> Well, there are a lot of things. But I'd actually like to highlight the main way that I like to get the youth interested in coding. And it's by showing them something that they find really interesting. For example, something that they see in movies a lot. Like, for example, artificial intelligence is the absolute perfect example of how you can have something, like artificial intelligence, that can get kids interested, and the youth interested, in these technologies like programming, in order to start to get them programming. Because of course, we need them to be prepared for their future. >> Gaming and AI are two, like, Sci-Fy is AI, kind of a cool, futuristic. And then gaming, also, is very interactive, immersion-based. >> Exactly, and, in fact, that's why a lot of companies are starting to merge AI and games. And, of course, virtual reality. Virtual reality is something else that, you know, kids, and really everybody, is really interested in nowadays. If we can, and in fact, we are, taking these AI technologies and incorporating them with these other technologies, like gaming, with the virtual reality, augmented reality, mixed reality, and we're trying to create this really interesting mix, especially for kids. And also, one more thing, here, is that not only are we doing this, AI is so diverse, it's all around us. It's on your phone, it's on your smart TV, it's in your car, and that's really why we should be showing the youth that this is all around us. We need to start adopting these technologies. >> Last year, I asked you the question, take us through a day in the life of Tanmay where you had a discovery. So let's play that back this year. Give us the time this year where you had a discovery. It could be super cool, or maybe just a breakthrough in some small way that was a notable that you'd like to share. >> Yes, and that actually happened recently. And again, I'm going to take this back to just a few weeks ago, actually. When I started working with, I mean, I had actually been working with my own custom machine learning algorithms for quite some time, since just after last InterConnect, actually, I started working with my own custom algorithms for machine learning. But a few weeks ago, I actually started working with those custom algorithms in the healthcare space. And one application that I've created that I find, actually, quite interesting because of the capability it has to help doctors, and I'll tell you this in a moment, is that it's an application that can take 69 attributes about any patient, OK, and it can actually tell you if they have a hearing disorder. And if so, what's their hearing disorder. The reason this is so great is because this can be a great help to audiologists, for example. And, in fact, I am actually in communication with an audiologist from the UK, and we're collaborating with him to try and see what this could hold in store for the future of audiology, and the future of healthcare, in general, with artificial intelligence. Apart from that, though, The Cognitive Story is another great project, where, of course, I'm trying to combine machine learning with these extremely powerful capabilities that Watson provides in order to create a great mix. In order to help people express themselves even though they don't have the natural ability to do so. >> So, Tanmay, obviously you are a big supporter of open source. You said earlier you open-sourced some of your algorithms, AskTanmay. What's been the response? Have you had contributors? >> Yes, actually, and that's the greatest part about open source, because, now, the thing is, let's just say there's some issues with AskTanmay, there's some, as you know, this is general open source stuff. But now, Ask Tanmay is really, I guess you could say, evolving much faster than I could ever have programmed it because there are many people coming to me, collaborating with me, helping out, submitting issues, pull requests, and more. And with AskTanmay, especially, now I'm about to release Version 3.0, as well, because I was able to get that help from the community. And, of course, because of that, not only does the community help me, but I am able to help the community by sharing my source code so they can learn from that and build their own QA systems on top of it. >> Awesome, so give us the report card on Bluemix and Watson. And be fair, now, I know you're IBM Champion. >> Yes, now, IBM Bluemix and Watson, I can tell, especially Watson, it has evolved a lot since last InterConnect. Of course, the new services that they're providing, like the Natural Language Understanding service, and more. And really, what I believe, is that not only are they providing these new services, but they're also improving their existing services. Like the Visual Recognition Service, how they're doing the image similarity, how they're improving their default classifier, how they are merging it with the Alchemy Vision services in order to make it even more powerful. And of course, the new, live training features that they're incorporating into visual recognition. How they're improving speech-to-text, and they're generally taking all of these Watson services that already exist and making them even more powerful so developers can really leverage them in their applications. Apart from that, though, IBM Bluemix has been going great, as well, with the new services it provides, especially from SoftLayer. Of course, Bluemix is going great, Watson has been rapidly evolving, as well. >> I notice you've got your IOT Watch on, the Apple iWatch. I bet you've been doing some stuff with IOT. What are some of the wearables you think that are needed right now? Because we had the founder of IndieGoGo on and we know the success of the crowdsourcing is there's a lot of tinkers and inventors out there who now can be up and running, so we're expecting to have a big maker culture growing exponentially around new stuff. So, what do you see that's needed from your generation? Chip implant in the brain? What's going on? >> Well, of course- >> What would you want? >> Well, in terms of, I guess you could say, wearables, there are a lot of different things that people are doing with wearables, including virtual realities. One of the main things that I believe is, I guess you could say, the most trending topic, in terms of wearables, of course watches, we've got glasses now that they're creating, like the Microsoft Hololens. And all of these different products that are focused around basically being able to, I guess you could say, run have these technologies available on your body. On yourself, quite literally. And to make it so easy to use. And really, what I believe is that one of the main things that's really going to power these wearables is AI, artificial intelligence. For example, even the Apple Watch has AI features in it. I mean, all virtual reality is powered by artificial intelligence, as well. And without that, it becomes extremely hard if not impossible for people to code in things like virtual reality. So what I believe is that we need, I guess you could say more adoption to these cognitive technologies. And we need people to adapt to it in their everyday environment, and really accept that it's all around them. And that's it's going to be extremely hard to live without it. Of course, we need to start getting the youth involved in these technologies, for them to be prepared for that future in which cognitive computing is everything, and, in fact, cognitive computing isn't just the future. It's the present, as well. That's why we need to start getting prepared for it. And that's why it's all around us. >> John was joking earlier about you getting your license. You're 14, now, is that right? >> 13, actually, about to be 14 in October. >> OK, right, so soon to be 14. So you'll probably get your license and still be able to drive. In two years we're not going to have totally autonomous vehicles, but- >> John: Maybe 25 years. >> What are your thoughts on that, though? What's the driving age in Canada, 16? >> Yes, I believe 16. >> Yeah, OK, so, you know, 16 years old, it's a symbol of freedom, you know, you get autonomy, and, you know. What's your feeling about maybe the next generation and them inheriting autonomous vehicles and not having, you know, the stick shift to drive, like when we were kids, and we all learned on the stick shift. What do you sense that? What do your colleagues and your other friends say about that? >> Sure, so, now, self-driving cars is something that is already being worked on, heavily, actually. It's a big research topic. Tesla, huge company that's really working towards self-driving cars, autonomous cars. They've already got, like, half of that done. They just have to work on the last half. Of course we've also got Google working on their self-driving cars, and so many other companies who at least aren't creating self-driving cars right now, or most are, actually, starting to work toward self-driving cars, including Uber. In fact, Uber is creating their own self-driving taxis that can take you around the city without you actually having to have a driver. But the thing is, what I believe, is that this AI technology is powerful enough to be able to work with these autonomous vehicles and more. It's just that there are a few, I guess you could say, rough edges that need to be worked out with these technologies, which I believe can be done. It's just a matter of time before we are able to get completely autonomous cars on the road. It's just that there might be a few issues with the ethics of self-driving cars, and that's an entire topic on its own. That would require an entirely separate interview. But, generally, I think autonomous cars, that's a great, great place to go with artificial intelligence, because that could completely eliminate, or at least significantly reduce, the amount of, for example, human error there is in driving. And, of course, get you around traffic faster. And, generally, maybe not even have traffic jams. There's just so many advantages to having autonomous cars. And, of course, that's why cognitive computing is all around us. >> So, AI is hot, IOT is hot. You're hot, you've got a great fan base. We know that from last year. The reaction from our audience was spectacular. >> Tanmay: Thank you. >> You almost won our Cube Madness competition because you retweeted all your followers, or all your YouTube followers. >> Tanmay: Thank you. >> Congratulations, great to see you. Come back on the Cube. >> Thank you, it's great to be on theCube. >> OK, we'll be back with more from theCube Live here in Las Vegas where IBM InterConnect, AI, cognitive computing, collective intelligence, all the data, here on theCube. We'll be right back with more after this short break. Stay with us.