 So hello everyone, this morning you had your first client meetings where you probably received a lot of information and before you start working on your planning this afternoon we would like to inspire you with a talk from Jón Janssus who will talk about making good things happen and as Jón said the first part will be from like presentation from your side and then it will be interactive. Okay that's totally up to you. Alright, thank you Jón. Is this loud enough or do you need to use a microphone? Is it okay? Good, maybe we can turn the lights off a bit so this is a little bit weird to see. So I came here on the train and I got an email from Greece with your schedules and you have this planning for the coming four weeks and I was like wow this looks a little bit like mission impossible. Who has that same feeling? It's not gonna work. So yeah really because we do a lot of product development and design and I work with startups and we have this golden rule that says in under 12 weeks we ain't gonna get anything done. So you have basically 12 weeks but no sleep. Eight hours, another eight hours and then another eight hours that gives you at the same amount of time in four weeks than we would have in those same 12 weeks. So who is a little bit scared here? Who thinks he's not gonna get it done? Who's 100% confident that this is a piece of cake? One week we have our dirty coat ready. We're gonna present it. Everybody's gonna be happy. It's gonna be easy. Money in the pocket. I think you get paid right? A little bit. By how much two weeks after I think Jón you're working quite hard on the beach. Who thinks like that? Maybe not. All right so I was also reading through all the different tasks that you have been given and you have different assignments from different companies as I get it and you just have meetings with them. Who had the idea that either the company didn't understand what they were asking for or the other way around that you didn't understand what the company was asking for? I see a couple going there. So that's another problem right? You're a little bit scared and then at the other end you go I don't really know what I need to do. So it's all about figuring that out. That's the first step of what you need to do in the next 24 hours basically. And I missed something in all those descriptions. All of those task descriptions that you were given, I was missing something. Any idea what? It was a lot about what you need to do. Right? You need to build something with e-badges and there's something with bikes and there's something with running in the city and stuff like that I was reading about. And it was all about what? It was one important thing missing. No idea? There was no single task description that described why are you going to do it. It all said what you have to do or what the end result should be. But it didn't say why. What is the first thing that a designer asks himself? Am I going to do this? And then coupled to that, which problem is this going to solve? And some of the task descriptions had a little bit of problem definition. What is the problem here that we are being asked to solve in four weeks? The most don't. The first thing that we always ask our clients and the people that I work with it when I start working with a startup, people always have grand ideas. It would be cool if we could take this and that and that and then we do a little bit of artificial intelligence. We build space rocket and we colonize Mars. What problem are you going to try to solve for that? So if you go back maybe tomorrow or to your teams, I think that is the question that I would ask myself. This task here, what problem does it solve? Try to figure out that core issue, that core problem, because all the decisions that you're going to make, you're going to be able to bring back to that core problem. If you don't understand the problem itself and the people giving you the assignment don't understand the problem, you're going to be pushed in all different directions. You're going to get lost and very scared in the end. But if you have a clear problem, a clear why, you're going to have a clear focus and it's going to be great to see that you'll be able to get there or at least try to get as close as possible to that. Don't be too afraid if somebody gives you a task and you only have four weeks, like I said, it's a little bit impossible you're trying to do there. So that's off to you to say this is too big of a problem. Let's make it a little bit smaller. And that's part of the agile challenge. You have agile methodologies at school, probably. You have used them. Who hasn't? Who knows about agile? Okay, what is agile? Hard questions. It's summer, you know, we have work there and everything. What is agile? It's a lot, a lot of different things to a lot of different people. There is so much about agile. There is scrum, there is canvan, there's factories that use agile, there's designers that are agile. In its core, what is agile? It's simple. Try to use the time that you have been given in the much most optimized way possible. You only have four weeks. So anything in those four weeks that takes you too much off track, that that's too much meetings that that that takes you too much of that. Why and that problem? That's overhead. Don't bother with it because it's going to take you away from reaching a specific goal or a specific focus you want to get to. That's being agile. That means asking yourself a lot of hard questions. Do we need to do this meeting? Do I need to write this email? Do I need to create this sketch? Do I need do we need to brainstorm about this new idea? You have your task set and you have a hackathon tomorrow, I think, right, Therese? Yeah, hackathon tomorrow to basically figure it out. And then from there, it's like, like a steam train forward, you know, the Japanese bullet trains, they're always come on time. It's like that, right? You set yourself on track and then you move forward. I'm going to skip some slides here. This is a little bit about my story, right? This is how I started. You know what that is? It's governor 64. This is my first computer. This thing was super powerful. It has it had a it had 16 colors of gray and white. And this was a screen, you know, it even had a mouse. We're talking 30 years ago. No more than 30 years ago. 35 years ago. 1989. I didn't have an enormous capacity, 64 kilobytes of memory. You know how much that is? Kilobytes of memory. How much? You're even older, right? The same the same era. 64 kilobytes of memory. How much is that? That's half a second of any any piece of any piece of music on your phone. Half a second. In half a second, this computer could run programs and do a lot of cool stuff. That's what I learned to work with. The internet has changed quite a bit since you talk about computer programming. And that's what you're doing. It's a very arty thing. Who actually went to school where they called your education computer science. You're in there. You went to the wrong school. You should go to a it should be called computer art. Why? Because as computer designers, computer developers and programmers, you're being tasked with problem solving that nobody has done before you nobody has as get as tried to tackle the same task that you're going to tackle in the next coming four weeks. It's a new problem. A scientist, what does a scientist do? A scientist explains the world as it is. He looks at the world and goes like, This is interesting. Why does the world work like that? An artist creates or an engineer creates the world. He builds new things that don't exist yet. To me, computer programming has nothing to do with science. It's art. Each time you're being tasked with something completely new. That's also what makes it very hard to tell the people that are going to ask you a hard question. And they're going to ask you at some point, they're going to tell you, When do you believe you're going to be done? Does anybody already know how to answer that question after those first day and a half? If I would ask you now, this is your assignment. When are you going to be done? How much time will it take? But how do you answer that question in a polite way? If the company you're working with comes to you and the boss comes to you and I met some people in the hall and they were going like, These kids in there, they're so way ahead of me. I have no idea what you're talking about. So there's already this like, right? There's already this communication problem that you have. And at some point, this person is going to go, Well, I don't understand what they're doing. I have no clue how they're doing it. But maybe I can get a little bit of grip on the situation about asking them, When are you going to be done? See, and if you were a scientist, it wouldn't be that hard if you're a builder of a house, it wouldn't be that hard because you had already built a house a hundred times. So you could know, like, well, the wall is three meters high and it's going to be that wide and need so many breaks, it's going to take three hours. But if you're a task to do something completely new, that you haven't never done before, how much time is that going to take? A little bit hard. So computer programming is expressing and transmitting a desire to machine that has no clue what it has to do, but it can do it very, very fast. And that's in a sense very arty. It's in a sense computer programming is a sort of literacy. It's about language. It's about a language to make the computer do things. And then I come back to what design is. Give me a definition of design. What could design be? Come on, guys. You're all studying something that's practical and looks good. Looks good. Practical. Yeah. Okay. Somebody else? What's design? In the back? Good. Exactly. It's a it's a way of communication. Design is communication. If you design something, it is going to communicate in some way or another. Simple example. Take this thing, right? If I do it right, see that? And it goes into a certain whoop. And there it stops. So why did it do that? This microphone? It wiggles a bit from left to right. And then it stops at this point. Why? Because the button is on top there. This is designed. Somebody thought about that somebody went like, if this microphone rolls over the table, it should always roll with the button on top because the person picking up the microphone will see that button. The button is also aligned in such a way that my time will be here. And there is this motion that I can do with it. Even if I don't know how this works, I don't eat a read a manual to understand how this works. This this communicates with me. That's design. So it's not only beautiful. It's practical because I can use it and I can speak into it. But it also communicates with me. That's part of design. So you're designing something not just to be beautiful, because that would just make you an artist, or just it would make you an artist will make your painter or sculptor. You're also designing it to communicate with the people using it to be able to do that. I go back to the thing that I said at the beginning, to be able to understand what what that you're creating needs to communicate, you need to know what problem you're going to solve. Right? Because if you don't know what problem you're going to solve, you don't know what communication that is going to happen between that device that computer program and the user of it. So this is you it's pretty cool, actually. This was not possible when I started when I started, like I had this big ass computer sitting in my desk, it was like a desktop computer, I couldn't take it out. A few years later, I went to study at at the University in Leuven. And I had a I had a laptop. Well, it was more like a desktop in a big box that I could basically drag along. You couldn't really, it was really this big. Today, you can do things like this, you could basically go over all over the world and your laptop is your office. Which is pretty cool. You can, for example, and done it before, you can, for example, take it to the valley and do a little bit of co-working there. You go to the beach, you go to the beach in the afternoon and then before noon, you work in a co-working space and you're connected on the internet and you could do your work. Most of our guys that work in my company, they're, they're not in Belgium. They're all over the place. We go from Vancouver in Canada to Manila and the Philippines and everything in between. That's all together 14 times those. Which is nice, because all these people can work forever, they want to work even if they want to go on a trip and they want to say, well, I want to only start working four hours a day. And I want to enjoy life for four hours a day. That's fine. Go wherever you want to go as long as internet, you could do that. That's a completely new way of working and living and being. Steve Jobs once said this, what a computer to me is the most remarkable tool that we have ever came up with. It's an equivalent of a bicycle for our minds. And then I'll show you this professor. You know him? Who is watching that? One. Assignment. Watch more tech. That talks. This guy as a professor, he was awarded with the tech award in 2015, I think. What you see here are the slums in India, like the poorest region in India. What he did was he took a couple of computers and put them into big boxes. So what you see here are four computers and these are all kids and children in the slums. These kids didn't understand what a computer was. They couldn't work with the computer. They had no idea how to operate it. He brought those computers, put them in the boxes and came back three months later. See what the result was. Three months later, these kids basically told them in very basic English. Listen, professor, we need faster computers. We need joysticks and games. So in those three months, they had learned to use it. And they also had learned that there was something that was even more powerful than what they had. And they wanted that, of course, to learn more. And that's what cheap jobs means, where the computer is a very remarkable tool. It's like an equivalent to a bicycle of our minds. You're going to create something, a program, a tool that is going to allow people to do things that they couldn't do before. And even worse, they're going to be able to creatively do things with it that you never imagined would happen. Because you're going to build something, you know, you have a problem, you're going to solve that problem, and then you're going to give it to somebody and say, okay, now test this. Very likely, the person is going to use it in such a way that you have never imagined. Your first user tests are going to go like, no, and then you're going to try, I'm going to help that person, right? You can say, no, no, you need to use it in this way. They're going to creatively come up with other ways of using the tools you give them. That's what computers have. They have that magical power almost. So we agree, and the person in the back completely agree with me, technology is the most powerful force in the world right now. Technology is everywhere. Digitech technology is everywhere and is disrupting every little piece of our lives. So, whoever used this, electric engineers, electronic engineers? Yeah, a few. Nice. That's old. Compile languages. Who speaks one or more multiple compiled languages? Cool. C++ people, Java people, a few. Some others, maybe some C sharp? Yeah. Small talk? No. Okay, so we started with, and then we moved through compiled languages. This is a list of the different ones that have been immersed over the years. It's actually quite cool to see that some of you still understand all of these languages. I started here. I still consider that as a very good starting point of learning computer programming because you can evolve from there into the many different languages that exist today. Then we moved on, right, from compiled languages. We started doing interpreted languages. Why? Because compiled languages were a little bit slow. You know, you have to compile the program again and again and again, and we wanted something that we could make changes to in that programming. So we came up with Ruby, some Ruby guys here, or girls, you know. Pearl? Good. Python? A bit more. It seems Python is very popular at the university today. Yeah, same song. JavaScript? See? Which is awesome, right? Because in 2005, we started Joomla in 2003-ish, and at that time JavaScript was totally knocked out. If you talked about JavaScript, everybody would go, no, no, no, no, don't do it. It's super insecure. It runs in the browser, man, and don't go there. And then in 2005, Ajax happened, and everybody talked about the washing powder, right? So Ajax happened, and then suddenly JavaScript was this super cool thing. And somebody, everybody wanted to JavaScript, you know, there was JavaScript in Ajax everywhere. And my mom always asked me, like, what, you need washing powder? No, I'm doing Ajax stuff. It's all cool. Works in the browser. It's a basic p-request. It takes a amount of all that stuff. What? So now, JavaScript is everywhere. We're doing we're doing anything and everything with JavaScript. Just nice. Some php developers here. Well, some of my friends here too. A little less, but good. So all in, those languages make up 50% of the code when Git is made. So if you look at Git up, 50% of whatever is there is made out of one of those. So probably you're going to use one of those languages to build whatever you're doing. Whoever decided to do C Sharp or C plus plus for this project? Nobody. Somebody? Because? You specifically need it? No, because of that 50%. So maybe you need to ask why is this the assignment? Why the hell do I need to do this in C plus plus? Right? Maybe there's a very good reason for that. And if it is not, you could maybe ask yourself four weeks C plus plus. Maybe I can choose something else. But if it's the assignment? Still, I would ask some questions. I'm not going to do all that in detail. But basically, when we moved from interpretative languages in 2000 somewhere to to a whole new way of working. We started from from writing desktop programs to writing web applications and interconnecting applications, which was super new. Joomla and Drupal and WordPress, tools that we built, the web application builders are the first ones. They were still installed on a server that didn't really communicate with a lot of other things. But then Gmail happened and Facebook happened and web services happened. And now we are talking about microservices and interconnecting all those different parts on the internet. But still, it's much about connecting people. Slowly, we're moving in a world where it's going to be about connecting devices. In 2018-ish, there are going to be more IoT devices out there than there are actually going to be phones or computers out there. But right now, we're still living in a world where we're trying to connect people. And that's what made Steve Jobs build the iPhone. He did the iPad first and then basically done the iPad and said, this is way cooler, this iPhone, because I can have a device that is so small fits in people's pockets. I can connect people with it. Why? What was he trying to do? He was trying to connect people using a device which looks very similar to a phone because people would accept that and know that. That's a design they're used to work with. And then we moved to web applications. Ruby on Rails, somebody going to use Ruby on Rails for his project? No. Catalyst? Just Perl? No. jQuery? One guy who's going to use jQuery. Good. Well, yeah, you know, I only have four weeks and you can. I would. Symphony? PHP guys? No. Some? Some Django? No. Some? One? So what are you going to use mostly? Node. Node? What else? Everybody, who's going to use Node? I'll add one, two, three, four, two, all JavaScript. Who's going to use something else than Node? Hmm. Yeah. What are you going to use? Ionic? Ionic framework. Also JavaScript. Yeah. Anybody going in their react direction? The Facebook react? A little bit there. Okay. So you're basically going to use what you're used to working with already from the process that you've done before or is this new for you? Our question? Is it something that you're used to use to working with? No. It's new. For who is the technology that is going to need to use new? Okay. Who is getting more scared because of that? A few. Yeah. Okay. But it's an important question to ask yourself, right? You only have four weeks. This is basically some sort of prototyping face review. Time is very short. Are you knowledgeable enough about the technology you need to work with to get this done? If not, you might be wanting to go back to the people they gave you the assignment and say, I'm not knowledgeable enough in this to get it done in those 10, 15 days. There's nothing wrong with that. It's better that you get a prototype running in something that you're that you're used to working with than that you need to use and learn a completely new technology and then not get anywhere. The time is too short for that. Go ahead. I'm not demotivating your students. I'm emerging them in real life application development. I'm trying to immerse them a little bit in real life application development. Oh, okay. You're not talking about this context. It could be this context or it could be outside. If you come if you come to work for me, right? I hire you and you go like, dude, no, I get it. React. I got it. I give you a project for two weeks and you come back and like, I'm not there yet. I'm in another two weeks. Then there's a very high likelihood that you're not going to stay long there. No, I'm not. I think a lot of these students are going to be watching live broadcasts right now and in things and just using the the base they have to start working with that language even though it is hard. I agree. And that's great. The communication is... But don't be afraid. That's the only thing I'm trying to make. Don't be afraid to go back and tell your customers that I'm not that knowledgeable in this. I'll try to learn as much as possible because then there's honest communication going on. Then we're getting on the topic of teamwork. You and the people giving you the assignment are becoming a team. What is the first requirement of creating a team? She just said it. Communication. What leads from communication? Work does, yes. Without communication work also happens. What is the result of good communication? What is the result? Teamwork? Yeah. Trust. A team are people that trust each other. You need to have trust in the people giving you the assignment, you know, that what you're doing task is fair. They also need to trust you that you're going to do your uttermost best to get the result that they're expecting. But there's nothing wrong in that process to say at some point and in this case because you only have four weeks early on that I'm not necessarily 100% comfortable here yet. And then that person might say hey great go ahead and research it which is basically what you're saying and then maybe after a couple of days you come back and said I researched it I'm still not 100% comfortable yet and then that person might say go go do it anyway or he might say well we're looking at least for some results so maybe we need to take a step back and find something else for now. That's the communication that you're going to build. If you're doing a personal project on the sidelines I completely agree then go explore as much as possible. Because that basically brings me and you're kind of like hanging in front of my point which is awesome. I'll skip a bit here. This is the point I'm trying to make. So we went from a compiled interpreted web applications programming platform. The last one is basically is basically where we're now at the cloud which is web apps, web books, HTML5 and there's so much new stuff happening. No it isn't here yet. AI is going to be a big differentiator microservices are things that we're doing. It moves forward so fast and this is it. It took us 40 years to get past compiled languages. It only took 25 years to get past interpreted languages. It took eight years to get past web applications and in three years this whole thing emerged and in the last year and a half the last six months a lot more is happening alongside it. So the technology stack that we're using is is going like this but it's going at a rate that is this. It's evolving exponentially. What does that mean? Yeah that's the problem. So everybody everybody just dumps and stuff and gets them and it goes like I open source it's cool yeah but there's no documentation there so how the freak how do I use that? There is a clear lack of documentation. There is also there is also too much right now. There is too much stuff being being thrown out there just for the fact that it's being thrown out there. There are some good stable libraries that are documented that our people are contributing on and it's fine that the experiment along the sidelines because you're basically going to prove that something can be done better. That's great but sometimes too much is too much. That's one problem. What is the other problem? What your teacher or teacher participant coach was saying exactly right the world around you cannot keep up the let alone that you can keep up. You need it's your task to keep up because you're going to build all those cool things for the people that cannot keep up. The divide between you and your user is only getting bigger and the divide between you and the people giving you the assignment is also only getting bigger and you're in the middle there and you're the one that needs to bind those two. The people defining the problem and the people that are going to try to use the solution. So that whole thing which we call digital technology is becoming vastly complex which requires one step back teamwork. It's impossible today to get something done on your own. You might be able to write a nice little library which in documentation throw it out there people are going to like it and use it but if you really want to build a product if you really want to design a product impossible to do this on your own. Ten years ago I could write 60% of Joomla on my own. I didn't have to use JavaScript I could just use PHP and it looked very ugly and I'm not proud of it but I still could do it. That's not possible anymore. I'm involved in an AI startup in London. We have designers, developers, data scientists. It only gets bigger and bigger and bigger the amount of people and the amount of knowledge that you need. Exponential growth. There's a third result of this. Whatever you use today is outdated tomorrow and the runway that you have becomes shorter and shorter and shorter. So decision-making processes also become shorter and shorter and shorter. You don't have time to spend six months to decide on what to use. You don't have that time anymore. You also know that three years later this is vastly outdated. So you're going to be outcompeted. You don't have that runway. So you need to set yourself up for change and that is agile. Write your code in such a way that it can be deleted. Create your solutions in such a way that they're modular so that they can evolve. At the time that we created this whole monolithic structures and monolithic applications they're gone. We want to have layered structures where we can play in different layers and exchange different layers. It shouldn't take too long to evolve whatever you build. The high-tech gizmos that bible the imagination we enjoy every single day. I mean devices that have more complexity and more technology condensed into them than 60 million dollar supercomputers had 40 years ago or something we get to enjoy every day. Supercomputers of yesteryear or in everybody's hand you know a young person with a cell phone in Africa has better communications technology than the U.S president had 25 years ago. So there's no doubt that these are magnificent machines that we use to extend the boundaries of our thinking of our reach. Nonetheless people have this problem with technology because they think it's somehow unnatural. Enter Kevin Kelley. Kevin Kelley's the fourth technology we want introduces the concept of the technium. He calls the technium aggregate of all of our technology. He calls it actually the seventh kingdom of life. He says the technium is self- organized. It has wants and needs and is subject to evolutionary forces. He literally says that evolution is playing out through the ocean of technology. Technology is birthed out of the human mind. If you were able to time-lapse reality you would see our thoughts spill over into the world in the form of technology. We erect matter of course with our will. We reorganize the physical materials of reality and turn them into objects of higher organization. And we give them transcendent quality. Today we have a device we have plastic and metal that sends our cloth traveling life across oceans of sky. I mean the fact that I can talk with it along with somebody and have an amber cave refers to as technologically mediated to a life of free mind to mind communication is not just astonishing but also according to Kevin Kelley's idea proof of the flowering of new possibilities. Proof that technology is a part of us. It's made of atoms. It's natural. It's just a continuum between the born and the made. Buckminster Fuller says start with the universe. The earth one is a single system an integrated system. We are of nature. Anything that's birthed out of us is birthed out of nature. So it's all good. What can we worry about? Jason Soba videos what you could they call a modern day philosopher. What he's talking about here is interesting and it ties back to that exponential growth. He goes into the fact that the technology is evolving but it's involved at an exponential rate. In one of his other videos he explains the concept of singularity. He wrote about that. No. Some did. What's singularity? So the idea here is that technology that the speed at which technology evolves and this is this is how computers are evolving. They are doubling in speed every year and a half so it's exponentially increasing. At some point that exponential increase becomes infinite. Right? So at that point the rate of technology evolution is instant and there's this guy called Kurzweil Ray Kurzweil who created a read who wrote a book about this concept which is called the singularity is mere. If you haven't heard about this concept you should. It's a little mind blowing. It's awesome for evenings with some wheat behind Netflix specifically because it takes you through spaces and places you've never been before in a sense. The thing is according to Kurzweil the singularity that point at which technology evolution will become infinite is going to happen in your lifetime and it's going to happen quite soon. He calculates that it will be in 2045 which is roughly 25 years from now. And until now all the predictions that he has made he makes predictions 10 years ahead. All the predictions that he has made are through have become through. For example he predicted that the human genome project would only take 10 years to complete. When they started everybody was saying this is impossible because we only mapped one percent of the human genome in one in one year so it's going to take us 100 years. If you extrapolate linger but if you go exponentially then it only takes your 10 years. So technology is evolving at that pace and it will continue to evolve for quite close to quantum computers and then the evolution will continue at that rate. Why is that important? Because it helps you to put whatever you're doing in a context. If you're working on a project, if you're working on a startup, if you're working on an idea understanding that your idea doesn't have a linear runway length but it has an exponential runway length and you need to evolve faster and faster and faster and faster to be able to keep up. That's the coming 25 years. What happens then is very interesting but that's for another talk maybe or maybe somewhere in a dark bar we can falsify us about all that. So quickly free software you're all going to produce something called free software right? Hopefully that's the goal. Okay so what does free software mean? Free software and the free software community and the free software philosophy and the free software movement are all about collaboration. It's all about working together. So free software it doesn't improve by use but simply using it by advocating it by mindshare or by having 10 billion users. It improves by participation, collaboration and contribution. You are going to do a lot of this already. You are going to participate and hopefully have some time for collaboration but your time is very short in just four weeks so you won't really have much time to collaborate with developers of libraries that you're going to use a little bit maybe but not much. But by using it you're already participating. You are reusing what others have built you're going to make what you built available for reuse to others. The question from this was how do you go from there to building an open source community for your little project? And then the answer we had already there was that there is so much open source code and free software code available today that that is very very hard to do. It's also not the initial goal of free software. The initial goal of free software is not to build something, put it out there and then get 10 million users. We didn't build Joomla because we want to have 30 percent of the internet. We built it because we believed in these ideals and putting it out there had a certain result. That result might be that you have people using it. It might be that you have people giving you some patches or suggesting some improvements. That's good enough specifically if you only have four weeks to work with. So don't try to be too big in your in your estimates around making it available. The fact that you're building it, making it available for others to see is great because if you later on want to get hired all the big companies today Facebook, Twitter, Google, Tesla, they're all going to look at your Github profiles. They're all going to look at the code you've written and how you have evolved as a developer. They even have automation tools for that. They just look you up and they will follow you even. Like I know a recruiter that works for Facebook. What they do is they find you, they put you in their database and then they follow your evolution. They see what code you're writing or what projects you work on, what talks you give and they add that as an internal resume. When you get invited to say okay you know here's a job you want to you want to apply for that job when you sit in front of that recruiter he has a whole history of you already. Which is much more important than what you will tell them at that point. So that is a great thing about putting your code out there but don't try to make it too big. There's a big difference between the big open source project that emerged today and what we did 10 years ago. Facebook for example would react which is a very big Node.js for example very big open source project. Facebook spends an enormous amount of money on marketing their open source project. They have a whole team that does nothing else than just that. Going to conferences giving talks about react because they want to have adoption. They're specifically marketing and spending money on that. If you get your code out there and you have people looking at it and maybe give you a bit of feedback that would be awesome already. Licenses how do you license your code when it goes out there? Any ideas? Is that a question that came up already? Not really. It's rolled by the end of the program. Yeah. So at some point you're going to need to put your code out there and you're going to need to put an open source license on it. There are different licenses that you can choose from. Do things to take into account if you're already using existing libraries you need to have a look at the licenses of those libraries that they don't conflict that's one. And two you can read a little bit into open source licenses and the philosophy behind them. There are different licenses and they have a little bit of a different philosophy. If you understand that then you can make a choice. In the end it doesn't really matter that much. It's important that you put a license on it. It is a lot of code on GitHub today that doesn't have an open source license. There's no license.txt file or license.md file in the repository. Basically means don't use the code, right? Because if you're using that code for a personal project no problem. But if you're using that code in this context for a company and the company wants to start doing something with that code later and there is no clear licensing for that library that you're reusing then at a certain point that the developer might say hey but I didn't license that code under an open source license you don't have the right to use this code in this way. So be careful with that. That's a problem on GitHub. A lot of the code more than 50% of the code on GitHub today doesn't have a licensing file. So you don't know under which terms you can use it even because it doesn't mean because it's public that you can freely use it. That's the difference. Right? So be careful with that. If you have any specific legal questions around that just ask send me an email or a combined maybe at the end we can have a very specific discussion on that. Don't make it too complex but be careful which code at this point you start using under what license. So are you a pirate? That's kind of where you're here right? This is that little guy Alex is liking me he's a little bit punker. Shall we call him Jack or Joe? Jack maybe. All right. So are you a pirate? Like are you that kind of guy or that kind of person that wants to change things and then wants to make what you're doing available to others so that you can collaborate or are you more that kind of person that will just take on the task do what is what he's being told and then just get the money and then go to the Bahamas which is more the guy in the suit. So a pirate is more driven by altruism and reputation and that's what open source people do they're not driven by ego they're not driven by they don't want to show off they're driven by reputation they put code out there they license it open source it gives them a reputation and it's an altruistic approach Linus Torvalds who built Linux didn't go and said hey I want to I want to take over the world he basically saw a problem and he said it would be cool if we could create as a free software kernel operating system that other people can collaborate on and then he went from there so there is not really boundaries or regulations that stops us as open source people we're often called hackers in a positive way we try to change things we try to hack things together we try to collaborate we try to crawl through boundaries that companies create and try to build things the internet is built in that way not because a company or a government decided we need to have the internet because hackers together decided let's build the internet and it will be hackers and pirates that continue to shape how our world evolves let alone the the Elon Musk's of this world who have actually earned a lot of money and are now doing very exciting stuff that Elon started with PayPal you know Elon Musk right he started with PayPal he basically started with nothing at all and he saw the internet happening and went like hmm this is cool there is nothing here that deals with money transactions so let's build something build PayPal made a lot of money and now you can basically go to the Bahamas and say hey you know I'm done I earn my millions I'll buy a Porsche I'll get the big villa in the yacht and I'm done but he didn't do that he took all the money that he earned and then put it into three new ventures all the 100 million that he basically earned from selling PayPal he put in three new ventures one is SpaceX the other is Tesla and he's doing new things on the side and with SpaceX he's going to go like let's think outside of the box let's try to solve a problem that is way bigger than anybody wants to tackle what wouldn't it be cool if we could actually send the rocket up and make it land again and everybody was going like impossible that's a pirate attitude it's like no I don't believe it's impossible I believe that that can be done so I'll make that happen as Steve Jobs said why join the Navy if you can be a pirate all right so there's this nice book called program or be programed from Douglas Ruskov if you haven't read it you should it talks about all the things and all the little concepts that I'm trying to put into this one hour it talks about the fact that at this point you have two choices in life you can either be the the user of the consumer and you're going to be programmed people are again deciding what your world is going to look like for you or you can be the one creating the world programming the world if you want to be on that programming side you need to keep up you need to evolve and learn very fast because otherwise you will also slowly become programmed and Douglas writes about we are creating a blueprint together a design for our collective future and that's even more important today than it was a couple of years ago because as small groups of people you know I love this idea of radical openness free exchange of information the free flow of ideas creating spaces in which ideas can have sex as Matt Ridley talks about and this is huge because it turns out that ideas are just as real as the neurons they inhabit as James Lloyd tells us you know a new kingdom rises above the biosphere the denizens of this kingdom are ideas because ideas have retained some of the properties of organisms it turns out they leap from brain to brain they compete for the limited resources of our attention they have infectivity they have strength power they are what Richard Dawkins calls the new replicators born from the primordial soup of human culture their vector of transmission is language and electronic communication and though ideas are not made of nucleic acid they have achieved more evolutionary change and at a rate it leaves the old gene panting far behind you know Ray Kurzweil says our ability to create virtual models in our heads combined with our modest looking thumbs was sufficient to usher in the secondary force of evolution called technology and it will continue until the entire universe is at our favorite tips this is unbelievable stuff it speaks to the telescopic nature of evolutionary change more change in the last 100 years than the last billion years Peretz McCann actually wrote from the moment the human beings invented language biological evolution essentially ceased and evolution became a cultural epigenetic phenomenon now we take a matter of low organization we put it through our mental filters and we extrude it in the form of space shuttles and iPhones you know the imaginary foundation tells us that what imagination does is it allows us to conceive of delightful future possibilities pick the most amazing one and pull the present over to meet it you know imagine how impoverished this world would have been if we hadn't invented the technology of the oil paints in the time for Van Gogh where the technology of the musical instruments in time for Beethoven and Mozart to uncurl through it you know with the revolutions in biotechnology nanotechnology the free exchange of information is allowing us to conceive of radical new things Freeman Dyson says in the future new generation of artists will be writing genomes with the fluency of the lake and violent road verses what is great in man said Nietzsche is that he is a bridge and not an end you know we're on a trajectory right in the middle between the born and the made wrote Kevin Kelly and so radical openness it's huge it's a universe of possibility it's grey and fused by color it's the invisible revealed it's the mundane going away by law we need to cultivate radical openness as a way of participating and accelerating evolution starting team or the team for that's you just call radical openness and this I picked this one because it matches very closely to what you're doing here with the open knowledge foundation the open knowledge foundation is all about openness and transparency and using that openness and transparency to evolve the world that we're living to accelerate that world that we're living in it's not just about taking an assignment from a company and behind closed doors making something and put it out there it's all about sharing how you do that with others and with the world so that other people can pick up on it and do something more from there it fits in that whole idea so you're in a sense what I'm trying to show you it's a little bit bigger than just the thoughts we've been given right there's a little bit more to it than just solving the problem that you have been given you have impact on the world as small groups of people you will have impact the tools that you create will have impact on probably hundreds not thousands and ideally millions of people if they start using those and that's very important to think about whoops so it's important to think about what future you wish to create because you have it in your hand with the technology tool that you have you can influence the world and that seems very far from your bet but believe me I did it before 10 years ago we started JUMLA and 10 years later 3% of the internet uses technology and 10 years later you go like shit I created a bunch of crap I should have done a difference there's a responsibility that is given to you um so the responsibility that you've been given is directly proportional to the number of people you're going to affect with it and it's not going to be five people it's going to be a lot of people it's the technology that we are reading through our lives has implications in the way that we work that we work together that we lead our lives it's not just creating a solution for our problem and making a lot of money with it it also has impact Facebook has an enormous amount of impact a.k.a. Trump elections I went Zuckerberg created Facebook 10 years ago he wouldn't have thought about that he wouldn't have thought like my technology 10 years later is going to help a president win an election that was not the problem he started with let alone thought about that that could be the end result so each mean pattern metaphor just to script API becomes part of our collective future liking is natural to us today I could just a button you press on something right first for some companies we have become liking machines we become liking robots we become liking farms in a sense people want us to click the like button is that the future we as designers want to create so Marsha McCullen said we ship our tools and thereafter our tools ship us we're going to build tools we're going to build technology that are going to shape the people using that so there's no guarantee that whatever you do will have any impact you know your project might totally fail and that's totally okay but if it does have impact the impact can be very large as in globally you can with a team of five people create a little startup today that has global impact that's not that hard anymore it's possible so you need to think about why how and what impact this is going to have so ask yourself what kind of future do I as a designer do I as a developer do I as a creative person want to create a suicide bomb a nuclear device in the heart of the nation's capital it's no wonder that we're pessimistic it's no wonder that people think that the world is getting worse but perhaps that's not the case we actually forget that we've only just begun doing what's never been done before is intellectually seductive whether or not we're going to be able to be able to be able to be able to be able to be able to be able to be able to whether or not we deem it practical what we're seeing is unfathomably new possibilities all of a sudden becoming available to us future doesn't belong to the paint right belongs to the blade you have to trust in something your gut destiny life karma whatever we truly are living in an extraordinary time and many people forget this we're not technically as wise as we are thank god can you hear me the yearning to do what we do in the service of something larger than ourselves where did we come from are we alone in the universe what is the future of the human race when you conduct those exercises the innovation follows just as day follows night we can do this I know we can because we've done it before stay hungry stay foolish a very small team you can create tools you can create technology that is going to evolve and impact the lives of a lot of people and it's not just about solving the problem that you've been given it's also why and then specifically how you're doing that and what impact it has on people using it there's a large responsibility that you have there again now I don't want to scare you as your coach was saying but it's part of the bigger picture and if you can leave that into into your work each time you're taking on new challenges you're asking yourselves why am I doing this and how is this going to impact other people then your own road to become a great developer your own road to become a great designer your own road to become a great entrepreneur and then my question is who from you actually wants to do a startup who wants to say hey I want to take on my own project do you have any ideas there is one great what do you want to build I'm not sure not yet I have no secret ideas but is there anybody that wants to go when I graduate some people might have already graduated or are still most of you are still studying I think like who goes like when I graduate I don't want to work in a company I want to do something on my own think about that all right it's a it's an interesting question for you to ask you have time to figure it out you have a couple of years to go to figure that out um but it's a it's a different life you set yourself up for it's it's the life of putting on the suit in the morning and going to the office working your day eight hours getting your paycheck and going home and making sure that your assignments are done which is fine or is the life putting on your pirate hat and your boots and taking out your ship and say hey you know let's tackle an interesting problem let's change some stuff that I I can have direct impact on it's that life which are two different things it's like the life of going to work for a bigger startup he wants to go work for Facebook Google I need big names that you want a spire of working for what are you guys gonna do actually sit each the whole day come on so other question when it became here what made you sign up for this program I'll stop making some names I wanted to learn you want to learn okay why did you sign up you're in the middle yeah I'm looking at you you're like whoa not me also to learn a lot to learn a lot learning is important somebody in the back the person all in the back the last no yeah well not not there the person at the yeah yeah you're looking at the back now yeah yes yes yeah you the blue shirt blue shirt go again experience okay what kind of experience working with people important anything else don't be scared you're about to build something okay anything else what motivates you to what motivated you to put your foot out of the out of the bed this morning to come here other people that's a good reason any other reasons you like coding all right you could do that at home too just sit back at your computer and make something that's something that's important to figure out like it's your why why do you do what you do why are you here and where do you want to go from there it's not a goal it's not I want to be there in 10 years it's more where am I focusing on because there's only so much that you can focus on you need at at some point you need to make choices in life follow a certain focused path Steve Jobs calls it connecting your dots or checking your list checking your list is easy right which is basically going to school getting the degree getting the job getting the car the girlfriend the house the children retiring and you're done right so once you have the degree and you have the job you can calculate how much money you're going to earn from there you can basically figure out where you're going to end up in life which is just checking your list and there's nothing wrong with that but that's how a lot of people live their lives is that the kind of life you want to leave you you say yes that's fine who says no that's not for me all right so what life you want to leave billionaire life and you have said that only if you have a it could be right it could be it could be but if you want to if you want to lead a billionaire life like in how many years from now 10 years from now so so then my question goes back right so you have 10 years so you're now here today why does does the the focus of becoming a billionaire bring you here today what does that have to do with that it's a very interesting big experience there's the building part that you learn to interact with different people you come out of yourself there are inspirational thoughts I'm just rambling all of it yeah but that's important to think about think about these things that you have been giving that amount of time like what I've learned is that once college is done and and you have done your initial steps then then work starts and then you don't have much time to figure that out anymore like that talks the books that I showed you tried to figure out read those read a little bit a little bit about technology philosophers read a little bit about watch a little bit of that be inspired a little bit there's so much stuff happening out there that can help you in your design work and in all the other things that you're doing so where do I want to end it so always okay there we go I'll get it right so and phrase right so what I tried to do what keeps me going is I try to pursue things that that are so important to me that even if I fail the world and that could be a very big world but it can also be a very small world is actually better of having me try it and that is that you can apply that to yourself to yourself and your friends to yourself your friends and your family to yourself your friends and your city to yourself and the rest of the world and often you fail like hopefully you will come a billionaire and then I'll hopefully still know you and then you know we can go stride around with the Maserati and stuff like that so totally okay but probably likely you will fail like one out of 10 startups nine of the 10 startups fails and it's a different life than than being in in in in university what is the graduation rate at university today 30 percent right which is three out of 10 three and a little bit out of 10 in the startup world it's one out of 10 and less so if you want to become a billionaire hopefully you do then then you need to be a lot better than that graduation 30 percent that you're not willing so why are you here exactly see now we're getting so hard that wasn't so hard was it to become better of course you're all here to become better a lot better much better because if you get better then you have more opportunity going from there like next year if you if you get through this in four weeks and you keep living your application next year is going to be a walk in the park you don't need to go classes don't go to them boring read the books where's the death box we'll go to them now I'm probably going to get in trouble again with the coach but then it's a walk in the park right and you can focus on other stuff if you are better than than than the other 50 percent in your school then school is a walk in the park and then you can start to become better than the other 10 percent in your school if you become better than the other 10 percent in your school you're doing very well for yourself and then you can either find a very nice job if you want to go there or you come come the next even musky and that's not a goal it's not I need to get there in three years from now it doesn't work like that it's a focus it's a it's a daily focus I'm getting out of bed in the morning with the idea that I want to get better I go out of out of bed this morning with the idea I'm going to try to deliver a motivational talk and get better at speaking for a group of young students and hopefully I will succeed in that and I get some feedback and I again I became a little bit better so the next time I do this I can think those experiences with me that was my focus for today right so and now we're ending up you're a builder a maker a designer a programmer you make stuff you will be making something in four weeks that's your first goal or task make it work while you're doing that think about what you're doing and what implications that work has there are going to be points in time that you make design decisions or that you need to make decisions what implications do those decisions have try to understand that and when you see it in action when you see it in front of people also try to reflect back and say we make those decisions what kind of impact did that have on the people that are now using it and you're going to code you're going to create a language you're going to create a design you're coders so that's my my wish for you in a sense right if after four weeks you are able to make good code and when you present your pros that you can really say we made good code happen we made good things happen and we understand why and how we did that then you became a lot exactly so I wish you good luck in the coming four weeks thank you you are on behalf of all students and the open sort of code team I would like to thank you with the t-shirts thank you can you sign it yeah sure begin yeah there's 39 signatures but it's okay yeah sure maybe you can maybe you can is there is there any questions and otherwise if you guys need to go then you'll be to go okay that's a question I'm happy to answer a couple of questions go ahead what's something that I started 12 years ago and Juma is an open source common management system Drupal WordPress yeah Juma and those people together make up 30 percent of the internet today so it's very similar to that so I've heard that I got involved in right after I graduated and uh helped go fun with a group of people from all over the world so it's it's how I became better no I was thinking when you say you're going in there well so that's the thing right I then decided to give it away for free and then you're later you go like why the hell did you do that so you decided to give it away for free so now we have a lot of people using it and I'm very happy with that because it doesn't make a lot of money but that's okay that's okay in a sense with all the people using the software that we build I might be a billionaire in terms of users and in terms of people you affect it doesn't make me a billionaire in times of money that I've earned but then again that was never my focus so I'm I'm not sad about that anymore any other questions one more of course right now we are building an AI on artificial intelligence I'm not building it because this is way above my understanding but we're working together with the University of Leicester in England they have a big data science team they're building an AI and we are doing the the web part basically bringing the AI to the internet making it accessible to microservices those kinds of stuff that we're doing cannot say too much about it because again under NDA and stuff but yeah that's that's what we're doing very interesting working together with data scientists that I have no clue about the web but have clues about a lot of complex uh math which is really really interesting we're making good steps we have the first prototype ready the next step is fishing that for investors one last question no all right no more 10 how was the question do I have some that talks Your hosted book was really nice. Yeah, I gave a talk myself at Tetex and Hustle. So if you look me up, you will find my TED Talk. I try to explain my why's in the talk. So that's interesting in the Jumal story, so you can find it. But our TED Talks that are very interesting are Lookup Talks from Kurzweil. They're very interesting. Some of the people that I mentioned have talks. Basically, if you go to that and you look up the top 10, 15 talks, you should see those all. The top 10 talks, you need to have seen them all. It takes you, it's like, it's like bench-watching for like three, four hours, you have seen them all. This is a really awesome story. There is one very interesting one. I think it's the top two talk from Sir Kenneth Robinson, where he talks about the problems with the education system and why the education system is failing. Yeah, a very interesting one. And then the talks from Kurzweil, where he explains singularity, a very interesting one. Look them up, there's so much stuff out there. All right, guys, after your inspirational lunch talk, I guess you're all very eager to go back to the first floor and start building the world as described by you.