>> Announcer: From theCUBE Studios in Palo Alto and Boston, it's theCUBE, covering IBM Think, brought to you by IBM. >> Welcome back, I'm Stu Miniman and this is theCUBE's coverage of IBM Think 2020. It is the digital experience online so rather than all gathering together in San Francisco we're getting to talk to everybody where they are and we're happy to bring back one of our CUBE alums, it's actually been a little while since we've had them on the program. Willie Tejada, who is the general manager and Chief Developer Advocate with IBM. Willie, so great to see you, thanks for joining us. >> Hey Stu, thanks for having me, it's good to be back, it's been too long. >> So, first thing, obviously we're all together while we're apart, because of the global pandemic, developers, I've had so many interviews I've done over the years talking about dispersed development, around the clock development, I had a great interview with a head of remote work in the developer community at the beginning of the year before everything happened, so, how's the community doing overall and how are you seeing them react to what's happening? >> In the developer community, I think one of the interesting parts is one, developers feel oftentimes that they can actually make a difference. Two, their work oftentimes happens remotely. And so, one of the things that we've seen is a lot of the interaction that we have when we're doing our developer advocacy work has just converted to digital. And there's some interesting dynamics that come about, just even in that, where if you were doing something like a meetup in New York that was attracting something like 50 people, to maybe 100, maybe the venue was limiting the number of people that you would actually have there if you had a popular topic or speaker. We've had meetups basically be as large as 500 plus people when we went to digital. So definitely some different dynamics as we actually talk about this new normal that we're in, and everybody utilizing digital vehicles to reach the people that they want to talk to. >> All right. So I know last time we talked with you a big topic we talked about was Call for Code, and something that IBM has done different initiatives there, and you've got a very relevant one so bring our audience up to speed, this year's Call for Code, what that would involve. >> Yeah Stu, thanks very much. The Call for Code initiative inside of IBM is now in its third year. We did it in 2018, the concept was fairly simple, developers always love to solve problems and we said what if we challenge the 24 million developers to come and take a crack at society's most pressing issues? And in the first two years we focused on natural disasters, all you had to do was take a look at the coverage prior to the COVID-19 pandemic and you had wildfires in Australia and in Northern California where my home actually is based, and you had tsunamis and hurricanes and floodings. And so the ability for us to actually bring the developer community to bear on some of society's most pressing issues was really kind of the concept upfront, and IBM would help by bringing subject matter experts together, making available tools, because we're thinking let's solve the problem exactly how we solve it when we apply business. You get an expert on supply chain, you get a user of supply chain, you bring them together, developer builds these things. Well, not all the time can you get an expert in disaster, a first responder, so we actually created a lot of that fusion from there. Then, over the course of the first two years, we've had over 210,000 developers participate over across 168 nations with over 8,000 applications submitted. So, wildly successful. Now this year, Stu to your point, we had something that we could really bear down on very heavily. We announced that we were taking on climate change kind of laddering up natural disasters was let's look at the root, climate change, and then the COVID pandemic came about. We said let's tilt people towards that and it's been a tremendous outcoming for it. We've asked the developers to focus on three areas: crisis communications, you may have been one of those folks that's on a conference call or emails that haven't been responded to, on wait times forever, so those communications systems how do we fortify them get them to scale? The second area is remote learning, really look at where all the students are actually these days and what they're doing there, not just teaching but basically how do you give them entertainment, how do you actually provide them some level of social interaction. And the third area with the COVID focus is community collaboration. We really want to try to make sure people's spirits are up and that really does require everybody leaning in, and again you look at the news and tremendous examples of community collaboration and where technology can help scale or broaden that, that's really where Call for Code actually comes into play. >> Yeah, maybe it would be helpful, tell us a little bit about some of the previous winners, what have been some of the outcomes, more than just rallying the community, what resources is IBM putting into this? >> So one of the things that makes it different is rather than it just being a regular hack, this is really a processing side of IBM that we've developed over the course of this last three years. Where the challenge is one piece, the Call for Code challenge, we also developed and rolled out and committed another 25 million, with Call for Code we committed 30 million over that five years and in the following year we recognized the need to see the solutions actually get deployed. And so we committed another $25 million for the fortification, testing, scaling and deployment. So when you win a Call for Code Global Challenge, you also get IBM's support around deployment, fortification, some counseling and relation basically from development, to architecture, to even the business side of it. In our first year, we had a team called Project Owl actually come out and win, and one of the first things that happens especially in hurricanes or these natural disasters, communication grids go down. So they developed a solution that could quickly establish an ad hoc communication grid, and anybody that had a typical cell phone could connect up to that Wi-Fi grid or that grid very similar to the way they actually connect into a Starbucks Wi-Fi system. And it would allow both the first responders to understand where folks were at, and then establish communications. So that was in the first year. The second year was a team called Prometeo, and in October we selected them as the Global Challenge winner, and they were a solution that was built by a firefighter, a nurse and a developer with this concept roughly of how do they monitor essentially a firefighter's situation when they're actually in the heat of battle to best allocate the resources to the people who need them most. Understanding a little bit about their environment, understanding a little bit about the health that's actually happening with the firefighter, and again it's one of those scenarios where you couldn't just build it from the firefighter's side, you couldn't just build it from the nurse's side, and a developer would have a difficult time building it just by themselves. So bringing those people together, a nurse, a firefighter and a developer, and creating a system like this is really really what we're aspiring to do. Now, they won in October, and in February, they're in a field deployment actually doing real testing in the field in some of the fields at Catalonia, Spain. So, we've seen it first-hand exactly what happens when they win, the Project Owl team actually did some hurricane deployment testing in Puerto Rico, that of course IBM helped fortify and build connections between the Puerto Rico government so that we're really seeing essentially the challenge winner see this type of deployment. >> Willie, I love it, it's even better than a punch line I could do, what do you get when you combine a firefighter, a nurse and a developer? The answer is you can positively impact the world so phenomenal there. >> Absolutely. >> I'm curious, where does open source play into this activity? We were just covering Red Hat Summit last week, of course, lots of open source, lots of community engagement in hearing how they are helping communities engage and of course open source has been a big rallying point, everything from 3D printing to other projects in the community. So where does open source fit into this initiative? >> 100%. The amazing part about activating developers these days is just the broad availability of the technologies. And it's certainly stimulated by the community aspect of open source, this idea that they democratize access to technology, and it's really community-centric, and folks can start building very quickly on open source technologies that are material. So number one, all the things that is part of Call for Code and what we actually deployed are based on open source technologies. Now, again one of the differences is how do we actually make those winners and those technology sets become real? And becoming real requires this idea of how do you actually build durable sustainable solutions. So each five of the winners every year have the opportunity essentially to go through the Linux Foundation and have their solutions established as a project with the idea of roughly that people can download it and fork it, people can actually fortify it, but it's available to the whole globe, everybody in the world, to help build upon and fortify and continue to innovate on. So open source is right at the root of it, not just from the technology side, but from the ecosystem and community side that open source was for. And so we've seen as an example the formal establishment of Project Owl's software being open sourced by the Linux Foundation. And it's been fantastic to see both the participation actually there and see how people are basically deriving it and using it exactly what we intended to see in the vision of Call for Code, and Code and Response. >> Well, that's phenomenal. We're huge fans of the community activity, of course open source is a great driver of everything you were talking about. So I'm curious, one of the things we're all looking at is where people are spending their time, how this global pandemic is impacting what people are doing. There's plenty of memes out there on social media, it doesn't mean that you all of a sudden are going to learn a new language, or learn to play an instrument because you have lots of time at home, but I'm curious from what you've seen so far, compared to previous years, how's the engagement? What's the numbers? What can you share? Is there a significant difference or change from previous years? >> Yeah, there's so much good will, I would say, that's been brought about around the world in what we're seeing around the COVID-19 pandemic. That the way I would describe it is the rate of submissions and interest that we've seen is 3x above what we've seen in the prior years. Now keep in mind, we're not even actually at the area where we see the most. So keep in mind, right now we tried to accelerate the time to highlight some of these solutions. So April 27th will be the first deadline for COVID-19 challenge, and we'll highlight some of the solutions on May 5th. Now, when we think about it basically from that standpoint we typically actually see people waiting until that submission timeframe. And so when you think of it from that standpoint you really oftentimes see this acceleration, right? At that submission deadline. But we're already seeing 3x what we've seen in the past in terms of participation just because of the amount of good will that's actually out there, and what people are trying to do in solving these problems. And developers, they're problem solvers overall, and putting out those three areas, community crisis communications, remote learning, and community collaboration, they'll see examples of what they see on the news and think they can actually do something better, and then express that in software. >> That's excellent. So, Willie, one of the things, we've been talking to leaders across the industry and one of things we don't know is how much of what we are going through is temporary, and how much will actually be long term. I'm curious if there's any patterns you're seeing out there, discussions you're having with developers, you talk about remote work, you talk about communication. Are there anything that you've seen so far that you think that this will fundamentally just alter the way things might've been in the past going forward? >> Developers are always actually looking for this idea of how they actually sharpen their skills, their craft, new languages that they actually know, new platforms, whatever it actually might be. And I think in the past there was probably, even from our perspective, this balance of face-to-face versus digital, and a mix of both, but I think what we'll find going forward is a more robust mix of that. Because you can't deny the power of reach that actually happens when you actually move something digital. And then I would say that think about how you at theCUBE have refined your studios in dealing with an interview like mine, it gets better and better, you refine it. How you do an online workshop and how you do a workshop on a steel service mesh, you get better and better about how you engage from real time, hands-on keyboard experience in what information, what chat, what community pieces do you put on the screen to stimulate these pieces, I think in general the industry and our company and our teams have gotten better even in this short amount of time. I think those things will be long-lasting. I think we're all humans, so I think they still want the physical face-to-face and community interaction and camaraderie that comes from being in that physical energy, but I do think it'll be complemented by the things that we refined through the digital delivery that's been refined during this situation. >> All right, so Willie, final thing of course, this week, the winners are all being announced, how about people that are watching this and say this sounds phenomenal, how do I learn more, if I didn't get to participate in some of the initial pieces what should I be looking for? And how can I contribute and participate even after Think? >> Well, number one keep in mind that the challenge for the year will still actually go all the way to October, and submissions for that whole Challenger Watch will go to February first. So that's number one. But number two, going to developer.ibm.com/callforcode you'll find all the resources, we have these things called starter kits that help developers actually get up and going very quickly, finding out more information about both the competition structure, and really how you become part of the movement, go there basically and answer the call. >> Awesome. Love it, Willie, thanks so much, pleasure to catch up with you and definitely looking forward to seeing all the outcome that the community is putting forth to focus on this really important challenge. >> Hey Stu, thanks for having me, I really appreciate it. >> All right, be sure to check out thecube.net for all the coverage from IBM Think, all the backlog we had to see Willie a couple years ago when he was on the program, and check out where we will be later in the year. I'm Stu Miniman, and as always, thanks for watching. (gentle music)