 Good morning. How are you all doing? Yeah? Here we are. This is what? When we started this, where is James here? Is James even here this morning? Back there? When we started, yeah, I know, right? When we started this, we all knew that we were on a mission, creating a religion, creating a movement. It is simply amazing. But deep down inside, when you look inside yourselves, what do you see? You're computer scientists, right? Some of you think you're superheroes? Maybe. I certainly wake up thinking I'm a superhero. But what you want to be is a computer scientist, superhero artist. We are walking around as technologists, as developers, with an incredible amount of swag. It feels great to be alive, doesn't it? We have such power, but with power comes what? Great responsibility. So what I'm going to try to do, Sam, in the next 14 minutes or so, is give us 10 steps, 10 things to think about that will help us be computer scientists, superhero artists, because we need a canvas, and that canvas needs to be stretchable. We need brushes, many different brushes. We need colors, lots of different colors, and we're going to build paintings. But the difference is that those paintings are fixed, need an extra sketch. You got to be able to change that painting, and that's what Cloud Foundry gives us. The canvas is your infrastructure. The brushes is the middleware, the databases, the colors are the APIs, and the painting, well, the painting's the unicorn, and that unicorn's moving, okay? So that's what we're going to do here in 10 easy steps. The first step, you guys got it, you're here. Thank you so much. You're at the Cloud Foundry Summit. You're participating in this community, because last time I was on stage talking to all, I said, look, we're building a platform for the people. Get it? Platform? I'm on a platform for the people, and we're preaching, because it is a polyglot world. It's about mixing and matching runtimes. It's about getting APIs. It's about doing what you need to get the job done. So thank you for being here, and the immense amount of uptake that has just occurred in such a short amount of time is unbelievable. At IBM, we created a platform, Bluemix, built on Cloud Foundry. We've got 8,000 developers signing up a week. That is a testament to what we all have done together. It is simply amazing, and at that last conference, I challenged everyone, hey, I said, hey, please sign up for IBM Bluemix. It's good to try. And you all did with, say, mixed results. Sign up now. Give it a try. It is awesome. Learn how to use Cloud Foundry. Step number two, your brain. Now, I tend to be on the more analytical side. That building on the left makes me on the right. Looks great, but doesn't make me feel so good. There was a study done back in the 70s, on architects. Real architects, I mean, we're not real architects, but physical architects, right, who build buildings, and they found that the best architects combine the left and the right-hand sides of their brain to build something special. So if we want to be artists, we have to learn how to bring these two worlds together. It is about building function with form and design, taking a design thinking approach. Because we'll never build that cathedral if we don't think about the end user. Whether it's an API you're building, whether it's a piece of marketing material, whether it's a piece of documentation you're contributing, take that approach when you think about this. Now, number three, code, community, and culture. Okay? Code is great. Code without community is useless. And without good culture is just toxic. Okay? So we, as a community, already have great code. We've got strong community and a wonderful culture. But we need to continue as we focus on that. Because no application, no community is an island, right? I was walking by and I crashed a meeting with a finance firm. And so, you know, they certainly know this. They've been using Swift to connect, you know, banking applications. This is great, yeah? Everything's connected. But everything's hyper-connected now, right? Everything is kind of coming in and out of your value chain. You need to be able to manage that. So number four, you need to think about four things when you build on cloud. First of all, you need capability. You need capacity, compute, storage, network. You need a platform, right? You need to be able to deliver that. On-premise, off-premise. Sam, you mentioned hybrid, right? A connected cloud. But there is not a single cloud, right? There isn't one. There's many. And there's many places that you connect. So what you want to be able to do when we build out the Cloud Foundry platform, right? And we continue to innovate and drive code into the code base is to build a cloud that makes all of them behave as one, your cloud. So it is very important that as we build skills and we think about how this stuff is being used, we understand the reality of where this stuff is going to be deployed, all right? Behind your four walls, outside your four walls, everywhere in between. Because no application is an island. And, you know, we've been doing our darkness that tried to experiment with that. Let's talk about a couple of colors. Diversity, lots of colors. I love colors, right? We've got a client that's here. And they built an application. It's a gaming company. And they built an application to determine when they should offer discounts on downloadable content. I don't play video games at all. So I don't know much about this. I'm out of my comfort zone. But they used the Twitter, right? To look at what things are going on and when they should do this. But then, all of a sudden, they had access within Cloud Foundry and Bluemix to look at the weather channel. Because guess what? When it snows in the east coast or you've got bad weather, people are home bored. Their kids are, you know, sitting there. And the parents give them the credit cards. Huge! Yes, I know. You do that, don't you? That's not good parenting. Can someone call the Parenting Association? Because that's when they should be given the discounts. When it's bad weather. So this is just an example of a painting that had to change, right? If you build a monolithic painting, Mona Lisa is beautiful, right? But what if you've got to change it? You've got a new color to add, right? So that's what we're trying to do. So there's a couple of really cool brushes that we kind of tried to time to give some more excitement to the event. You talked about our friend Bill, right? We have a .NET build pack, which we'll be bringing to the community. We also have several other kind of brushes that we're bringing. Some things focused on getting access to open data, which is kind of a government format for data, some stuff around KPIs and some other interesting brushes. But a really cool brush that I think is really neat is one about getting access to proximity-aware mobile applications. Now, we all, certainly in the Bay Area, are very familiar with the idea that we're being monitored, centered, and with everything we do. You can't walk from here to here without 10,000 devices knowing what you're doing. The problem is, there's no apps. We're connected. We're not doing anything. As users, imagine the power of you can use Cloud Foundry to bring together all of this information, right? So I challenge you to do that, to start to bring in those brushes. And of course, my favorite one, which is a dating service for APIs, a dating service for colors, right? Imagine if, as a developer, you don't have to really worry about the semantics, about the data matching, about the security context. You can get at the interfaces you want and build your applications quicker, right? Those are the kinds of innovation that helps us build that cathedral, Sam. So, five. Community, I'm sorry, code. Now, look, everybody know what Knuth Volume One is, two is, because if you don't, you should just leave. Knuth, we're computer scientists, guys. I used to teach graduate level computer science, and I am appalled at the garbage open source that's out there, okay? It's freaking garbage code, right? Look, think when you code. Reuse stuff that works. Don't rebuild. Look, we solved the sorting algorithms years ago. It's done. You don't need to do it again, right? Reuse code. Make sure that your code is well-formed, documented, reusable. Because code that you put out there in open source is kind of, and that no one uses, is like putting out garbage, you know, and the garbage man doesn't come or person doesn't come, right? It just piles up, right? That's not good. Hashtag no bueno, right? You don't want that. So, let's work on this. Six. Now, let's talk a little bit about community. Spaces. We need to create spaces. This concept of a dojo, okay? This concept of, within your own companies, creating a center of excellence, where you give permission to yourselves. You don't need permission from your bosses. You've got that. Permission from yourselves to build with confidence, know that there's no boundary, allocate time to think before you code. Use all of that time. The very first squad was not Spotify, who does squad and kind of start talking about how they do agile DevOps, continuous integration, delivery, blah, blah, blah, with squads, right? It was Monty Python. And if you look at how they built up their squads, it was simply amazing. They reached out to experts when they needed help. No idea was bad. And their best creativity was done at the bar. Now, I'm not endorsing libations, okay? And coding. That kind of maybe goes in the wrong direction. But I am endorsing fun, okay? Having fun within your teams. And that's what we need to do here. And we do do. And we've been doing an IBM as well. When we build our software, whether it's Cloud Foundry or all application, we are having a freaking blast. These are photos from my lab here. I got to show family pictures, right? Everybody has family pictures. Family pictures of my teams here in Silicon Valley. I mean, the energy is amazing. And we're always, and we're always looking for more teams who want to come join us. If anyone wants to come, you're welcome. Give me a call. We're always hiring. But this is the kind of fun that we all have as a community. And we have at enterprise scale. And by the way, hats off to you all. Hats off to Pivotal for bringing this to an open foundation. Let's give them a round of applause. Okay? Hats off to all of the sponsors. All of you all here. And let's not forget the press and the analysts. I mean, there's maybe four or five of them in there. Because you've got to spread the word, right? Yeah, I know you think your blog is great. You know, my cat reads it and my mom reads it. That's it, right? So we need the press. We need the press to spread the word. So let's give them applause as well. Thank you all for coming. All right? Because an open community and open governance and a meritocracy and a clear vision of how you can go from an individual contributor to a project leader is how these things are successful. And we can do that now with Sam's help and what we did starting December 9th. Nine. Culture. Two examples on culture. Perfect timing. I'm doing great. Two examples on culture. I have this big clock in front of me. It's just sticking away. Culture. 3M. The sticky note. Does anybody know what a sticky note is? I was informed that cool kids no longer use sticky notes. They actually do it on like computer programs now. They're virtual sticky notes. I'm like, I'm sorry, dude. I got sticky notes at home. Put them all over my walls. You know, the sticky note, the way it was created, some engineers came up with this thing that was sticky, kind of sticky, not sticky, not sticky enough. You can unstick it, stick it. What are we going to do with this thing? Right? 3M didn't kick them out. They said, keep on experimenting. Figure it out. I would say they created something pretty cool, right? That has been very, very usable. That is an example of good culture, right? An example of perhaps not so good culture. There's this beer company in Germany, and they do distribution of their libations. At the time, they were doing it kind of early in the week, and then didn't do much later on. They always did that way. They couldn't be competitive. They basically falling behind in the marketplace. They go through World War I, World War II, modern days, what's going on. They kind of said, why do we always distribute beer on the beginning of the week? Why can't we just, you know, with the whole FedEx thing or whatever? I don't know. Can we distribute beer more times? Well, we always did it that way. And they did it, right? Because they were fuel rationing back in the war days, and horses would get tired, right? That's why they did it that way. So question things. Question, Sam. Question the community. But question with purpose, right? That was the difference here. They're trying to do something to change their market. A good thing to question. Just don't be a kind of a person that's negative, but question with purpose, okay? And in fact, one thing, Sam, that we're very proud to announce, probably the most proud thing that I'm trying to announce today, is that we're going to try to help bring all these things together. We're opening up the first of several Cloud Foundry community dojos. We're going to sponsor this one. I suspect others will be sponsoring other dojos as well, as the time goes on, in Raleigh, North Carolina. I mean, the vibrant community there is unbelievable, okay? It is like Silicon Island. Is that an applause? Thank you. Thank you. Can we get more an applause for that? Come on. Thank you. So you're going to be able to go pair up with folks who are already in the community, do pair programming, go through the dojo process in Raleigh, North Carolina. We're going to build out center of competence there. We're doing it here in San Francisco. We do it in the Bay Area. We're going to do it all over the world. That is how we spread the word. We spread the word by communicating. We spread the word by showing how you build that cathedral. You spread the word by hands-on keyboard, right? So number 10. What is number 10? 10 is all about you. 10 is you. It is the painting that you create. In order to do that, you need to make sure you build a cloud that is open by design and that you use a cloud that is open by design. And then you're going to wake up in the morning and you're going to look in the mirror and say, you know, my painting looks good, but man, it was a rough holidays at Sam's house and I put on a little bit of weight. I got to go hit the gym and work out a little bit and change my painting, right? Get it? Painting is your code, okay? You could also work out too. That's what 10 is about. Do not be rigid. Constantly change. Constantly innovate. If we do these 10 things, if we do these 10 things, I have no doubt next time we're here together, we're going to triple the size of this audience and there will be even more Cloud Foundry here. So thank you so much for attending and thank you for listening. Take care, everybody.