 Hello everybody, so I was invited, so whatever I learned is there for it. And they told me that I should speak about whatever I want to speak about, so I said that's always a good thing, which is Greek mythology. And everything I'll be talking about is a single, very metaphor on software development and computer. But at times you'll see that this course will verge a bit. The edge of heroes is something from an old concept which was developed by these, in particular these two guys. On the left is Ezjod, and we have no idea what Ezjod looked like, so this is probably not in fact the head of Ezjod. And on the right is Plato, and that one should be his real likeness. He was, as you see, a BSD developer, he was a big deal. And in the Greek nation of the cosmos, the whole course of time is a long degradation into the current present, which is the worst time ever. And three of these ages were awarded some color or metals, so the golden age was really the place where you had to be. There was no law, no work, nobody had to work or to suffer, and the first mortals would eventually die very smoothly and they could find everything, every food they needed. Then the silver age is a bit worse because then they had to work, they had to do some agriculture because there was still passing of seasons, they had to grow things, but there was no war. Then comes the present age, or age of bones, which is dominated by violence and war, and they eventually killed each other. Then the age of heroism, in the Greek age is where all the classic myth is about, including the one I will be talking about, take place, so there are no more peoples, but also heroes, which are not a positive way of talking about people. That's not the modern meaning of the name hero. I come to that. And after the Greek age comes now, which is called the I1 age, which is described by Plato as the age where there is no decency, and no more honesty, everybody has control. So Bedecois is now in its place. This definition is from the Oxford English Dictionary, so it's supposed to be a good dictionary, and there are several meanings to heroes, to the noon hero, but in that case, I'm losing the one, this one, which is a person who is a bit above the humans. In the Greek sense, it's all a question of social hierarchy with the gods on top and the slaves at the bottom, and it's all about getting a bit higher or lower on that scale, and a hero is someone who does things so extraordinary that he is a bit above the normal humans, and not quite a god, but close to it. And that's not necessarily a good person. Now when you say that somebody is a hero, it's meant as a compliment. Two thousand years ago, it was not that clear. Here is one hero, which is actually this son of a king, a great king on Pegas, but he is also a demigod, which is even better from his mother. And he's a strong warrior, he's known to be invincible, and he's rumored to be mostly invincible. He's also predicted to die young, which is kind of contradictory. And he's not extraordinarily smart, but he's very fierce. And he looks like Brad Pitt, which is always nice, and that comes with being with a demigod. And my point is that this guy is a role model for open source software developers. Not in all his aspects, because he's really a terrible person. You should not, for instance, treat women like he does, but he has in his behavior strong traits that really relate to what developers are more or less consciously trying to do, especially open source developers. So a bit of context. Context is the Trojan War. It's a long story, which is recalled in particular in the Iliad, which is a poem by Homer, and that's from the 8th century BC. And supposedly the events, which are mystical, would have taken place at the end of the Bond Age, about 13,000 years before the Quist. In fact, we did find, it was some archaeologist named Henry Gittiman, who found the ruins of the city of Troy. And apparently there has been a level of extensive destruction, with a lot of fire and looting and so on, about at the right date. So it's quite probable that there was a city in Troy, and that they had a war which was famous enough that it's made its way into the mythology. In the myth, it's a long and convoluted story, but it starts, the Proximal Code for the War starts with this here, where the three legacies on the right are basically goddesses. Aphrodite, Athena and Ivar. And they have a typical cliché of a feminine rivalry, and they were in a dispute about knowing who was the fairest of them. They first appealed to Zeus, and Zeus is not mad, so he decided that he should not choose who is the most beautiful between his bones, his daughter and his wife, because it would not be the smart move, so he decided to delegate. And he talked to Hermes, with the guy with the rings on the foot, and to find a mortal who would serve as judge, and the mortal on the left is Paris. Paris at that time was a cool shepherd, but he does not know it yet, but he's also Prince of Troy. He's been somehow exiled because it had been predicted, always with 100% reliability, that he would cause the fall of the city, which was ultimately true. So he was exiled, and while he was just keeping his head, he was summoned by Hermes to be the judge. Of course the three goddesses tried to bribe him, and Athena tells him that if he chooses her, she will give him a mastery of command. They will never do the war. Herapus proposed explicit political power to make him the biggest king of all, and to have the power of the world. And Aphrodite, since she's a goddess of love, says that if she chooses her, he will get the love of the most beautiful woman on earth. So of course Paris is a teenager, so he chooses Aphrodite, and the most beautiful woman on earth is very well known. She's Ellen, who is the queen of Sparta, and technically also the megadeth, because she is the daughter of Zeus, which is rather a big man among gods. So after a number of periods of things that happened and it's a very long story, Paris is recognized as a prince of Troy, and he sent as an embassy to Sparta just to make peace, and of course he meets Ellen, and this leads to that, that is Paris makes up with Ellen. So depending on who is recalling the story, it's called either abduction, or he dialogues with her, it's not clear whether she was totally willing or unwilling in that painting, she's rather happy to go with him, and also it makes up with the substantial part of the Spartan treasure, so it explains its second thing. So of course she is the queen of Sparta, because she's married to the king of Sparta with Menelos, and Menelos is absolutely great with that, and what he goes to think is whether again and none. This is an actual historical artifact, which has been recovered from the ruins of Mycenae by the same Enrich Chimane, who subsequently discovered the ruins of Troy. And it's called the Mask of Agar-Elenon, but inoperability was made 300 years before the birth of any king of Mycenae at the time of the War of Troy. So it's, even if Agar-Elenon existed, it's probably not Agar-Elenon, but anyway. Menelos wants his wife back, and Agar-Elenon does not really care about Menelos' wife, but he cares a lot about being the biggest king of all and having mastery of the complete Aegean Sea, and especially the commerce inside the Aegean Sea, and his next competitor on his key list is Troy. So that's a good pretext to organize an expedition, a great war against Troy. So he agrees to that. And we have this project, and this project is to conquer Troy, and with a number of business goals, one is the official protect, which is to save the honor of Menelos. But as I said, Agar-Elenon wants to break the power of Troy. Of course, in any war there will be a lot of routes, and this is what will bring all the warriors to the war because each of them wants to get home glorious and rich. So as the myth goes, he succeeded in sending out 1,000 ships full of warriors. In Agar, there is a very long 24-box, I think, and one of them is extremely long because it's a list of all the ships, and every city which sends a ship. So it's known to be interpolated, and there are two things in that, because, for instance, Athena sent apparently no ship at all because it was supposed that when that specific book was put into text, Athena was at war with all his neighbors, so that was some sort of punishment, not to incumbe them. But anyway, the project is to conquer Troy. Of course, among all the warriors, one of them is Agar-Elenon. Agar-Elenon is a carrier goal, and here the point is that Agar-Elenon's carrier goals are not aligned with the business goals. First is the throne of a king, so he's a prince, and he's already rich. He does not want really to get more rich, because he already has more than he needs, more than he can know what to do with it. What's terrified, actually, is death, but not the suffering of death. It's very gorgeous, very brave. It doesn't really mind being killed. What terrified him is the anonymity of death, to lose his logos. The things that make him unique to mind being, and he doesn't want to become a shadow who is not distinguishable from other shadows in the other world. So what he wants is to become immortal in some way, but since the really true immortality is being a complete god, not just a demigod, it's out of his reach, so he will shoot the next vaccine, which is to become extraordinarily glorious, to become immortal in name, so that nowadays, more than 3,000 years after last, he will still be remembered, and that part absolutely works. So that's why he's there, not for many years, not even for a long time, but he's not there to be present again and only. He does not like it again and only. In the real god, in the book, not in the movie, I saw a picture from the 2004 movie, which is a nice movie, but the book is much better. And the book is also absolutely reborn. I mean, in the movie, I watch it again, there are a lot of killing, but there's not even a single beheading. Whereas in the book, there are very graphic descriptions of how internal organs are extracted from people and spread in the field. At one point, one of them takes a spear just under his chin, and Omer explains how his teeth are spread out. That's atrocious. So anyway, in the book, Agamemnon is also a great hero, and he has his own moment of glory, which they call the Aristegas, in which he is proven to be a very strong warrior, almost equal to Achilles. So of course, Agamemnon really hates Achilles, and Achilles really hates Agamemnon. And since the project does not go well, because at the moment, the book starts, they are already there for almost 10 years, and it does not work. There are 50,000 Greeks, warriors, they are camping on the beach, and there are not enough of them to make a full blockade of the city, so the city has food, and the siege just takes on. So they have a very low morale, and at the start of the book, they have a plague, because they were bored, so they engage in some sort of looting in the nearby cities, and one of them hosted the temple to Apollo, and they looted it, and they win the loot, who was the cruisist, who was the daughter of the high priest of Apollo, and then they have a plague, and the god of plague is Apollo, and they had to ask to local divine to explain to them that when you await the high priest of the god of plague, you may get a plague. So... and since the cruisist was taken as a prize by Agamemnon, the divine with my name is Kalkath, I think, that he had to give it back, and of course Agamemnon was not very keen of that, but his aunt was forced by his warriors, including by Achilles, and Agamemnon had the crewed accession of his own authority to remind everybody that he was the Highest King on the place, decided to give back the cruisist, but replaced it, replaced her, so she's not an object, and treated it as an object that is not an object. And to replace her with her cousin, who was a cruisist and who was awarded to Achilles, so of course Achilles is deprived of his own price, just because Agamemnon wants to show that he is above him. And as a consequence, Achilles sees his work, and that is, he sees to fight, and when Achilles does not fight, things go really wrong for the Greeks, because then the presence becomes a funger, funger than the Greeks, and there is a whole description of how the Greeks have to fall back to their ships, and things are really not going well. So in the books there are a lot of happenings with the gods who intervene with the total lack of dignity, and so on. But anyway, at that time, in fact, this thing demonstrates that Achilles was the top performer, and the business really needs him, even he himself does not think as needed the business. And we arrived to the next episode, which is the death of Pachoclus. Pachoclus was cousin of Achilles, and he suffered to see the Greeks being pushed back by the Trojans, so he decided to go and fight, and even had Achilles' blessing, and he tried to fight in the name of Achilles, but he met Hector, who was the big hero on the Trojan side, and Hector was better than Pachoclus and Achilles. So now we see Pachoclus with a bit of penalty in his skin tone, and of course Achilles is very dismayed because that was his cousin, that was his companion, and possibly his cover, because the text is not really clear on that, but he is very hungry. So when you lose somebody who is close to you, there is a model which is called the Kugliovoz model, in which people will go for these successive stages, because they don't believe it, they deny the parents, and they are very hungry, and there is a bargaining stage where they are trying to trade things with faith, and that's where they would say they are trying to invoke gods, so they say, I'll go in his face and so on, and they become really betrayed, and at the end, over time, they begin to accept that there is a loss and to get better. Now Achilles is a reward, so it does not follow this model, but rather that one. So Achilles becomes very hungry, and when Achilles is hungry, it kills, and it kills and more and more and hundreds of people, and at some time another god has to intervene because he is sparing out so much blood that the local river has become just a river of blood, so the god of that river is irate, and begins to fight Achilles, because Achilles is a dummy god, he can take on a real god just on the field, like that. And the whole book is about, to the end of the year, there is just more and more and more murder, and that is one of the characteristics that made him a software developer. So let's see what that story means for an open source software developer, and open source is an important term here, and when you are trying to write code and you're not paid for that, you're still doing it. So there must be some sort of motivation that covers you. It's not money, but one of them is a very great notion which is the necessity for order. Most, it's not all of Greek mythology can be interpreted as a long struggle between chaos and order, and the Olympian gods, like with Zeus on their head, arrive at that position by beating the previous deities, the Titans, who were more chaotic. And the developer who just wants to run a complete project has a notion that there should be good code, and that was powerful. And he has a huge dose of hubris. Hubris is a capital sin in the Greek sense. It's when you, since they all, they envision the whole world as everybody having a specific placement in the reality, hubris is when you are trying to be higher than your true place. But you need a bit of ambition that, and for the developer, the hubris is that they can do it. Somebody in front of his computer has his text editor open, and he takes himself. I can do that. He's an open source developer, so what really, apart from that sense of order, is what he will get out of it is the same thing as he will get glory, that is, by showing his code, he's demonstrating to the world what he can do and how these things are done. So these elements might not apply to everybody, but my opinion is that that kind of motivation underlies a good proportion, possibly a majority, of the motivation of open source developers. And these are really in the same thing that he is. I mean, actually he thinks that he is the best warrior because he does not write code, he makes war, but he does it very, very well. And he can do it, and he wants to show to the world how war is to be done. Then there is a big component of hunger, and that computer opens windows, and I tried blood whenever that thing tries to apply updates. I mean, it's insufferable. And the one element of hunger comes from the idea that the existing projects are really bad. There's no, for any specific tasks, you might say, given operating systems, existing offer is two. And one very important thing, is that a lot of people appear to be content, even competent, with the majority of the existing offer. I mean, generation of users now have been tried to just reboot, and to be happy with that. And if you think about it, that's not a good thing. It should not happen. And the hunger can power the envy to feel that, and to rewrite everything. And then we see how the good developer, the efficient developer would look like Achilles. That is, once he got to the hunger stage, when he wants things to be done, he will see them through. He won't stop at the end. Be depressed and finally accept. He will go to the end of the project. If you look at the BSD operating systems, they've been on for 30 years. About. And it's still ongoing. So that means perseverance. And it's an essential quality of a developer, and especially someone with self-motivated, who just does that for his own glory, is to persevere. Otherwise, nobody will remember his name. So a good developer, in that sense, must be as thorough and complete than a Greek hero. He must go to the end of things and never compromise on things and go to the end of every idea. So in order to illustrate that, I will take a perfect example of a hero. This is my safe. And this is probably the reason why I'm here right now, because apparently it got me invited. And my own hunger was about OpenSSL. OpenSSL is a library, which is well known, is the main open source SSL-providing library. And it's used everywhere, including the BSD systems. And it's known to have had a very long development history for over 20 years. And they never delayed anything. So it's a creating successive layers of things. And it's a mess. And it's well known. It does not have really... I won't say that it does not have good engineering practice because it does not have engineering practices at all. There's a quote in which they say that the first rule of development in OpenSSL is you don't talk about development in OpenSSL. So since it's a mess and yet everybody uses it. So you see the element in which people are a bit complacent with mediocrity. And I told myself there should be good code and I can do it. And I will show to the world how these things are done. So I decided to write a new library and to make something which can be shown. Initially I wanted something such as the source code could be served as a tool for explaining how to develop the pedagogical thing. Also I wanted it to be extraordinarily light in both in RAM usage and code size. And it had to be of high quality, especially the cryptographic implementation. There is something called constant time code which means that code that is inherently resilient to side channel attacks and I wanted to have that everywhere. And the last item on the slide is an important one because what it says is that I decided to do that in early 2015 but the first time I told other people that the project existed was when I published the first public version and that was almost two years after. So I persevered. I wanted it to be done and I kept it for almost two years without external motivation. Just to show it. So as an example of how these principles of thoseness apply to technical things I will go into the technical side of things. In a specific theme which is how you decode a nested structure. There are a lot of structures more or less complicated in TLS including the unchecked messages and the X519 certificates. And by nested I meant that each structure contains sub-structures which contain sub-sub-structures and so on. And one of my goals was to save RAM so I don't buffer things. Every processing should be streamed in a fixed amount of RAM. So the usual solution to handle the decoding of a complex structure is to buffer the complete message which uses RAM and then you have some code which explored iteratively and every time it enters a sub-structure you just open another function or another block of code which uses RAM and I did not have in my goals the RAM to do that. So another solution which is applicable in some languages in which you can have one processing which is recursive with calling sub-functions and so on and that consumes input bytes and output the decoded elements. And to be able to operate in a stream fashion it has to run its own sort of thread. And there are no code routines in standard C. So you have to hack something along with long jump and so on but first it's horrible. It's fragile. It uses extra RAM and you should really not do that. So here is an example of one message that should be decoded. It's a Client Lo in TLS. What you can see here is that the message itself is a structure with a number of fields which have sub-fields and some of them the values which are indicated are length. So for instance you can have an open-ended sequence of extension up to 64 kilobytes in length. So if you want to buffer everything you have to accept the idea that your message may take up to 64 kilobytes or even more. So my first step was that I wrote as a prototype a generic decoder for that using a template. That is I had a structure in memory, in read-only memory that describes the structure of a message and then some code which was looking like an XML SACS parser. Just to read the template as a sequence of decoding instruction and to be restartable whenever it had new data bytes and to producing like a small custom code routing. It worked. It was not very satisfying but it somehow worked. But then, and this is my point here is that I wanted to be to go to the end of that idea and I recognized that that generic decoder was really a small implementation for a new programming language. And so channeling my inner hero I decided to create a new programming language and write the compiler and just be done with it. And I did. So I decided that this decoding language should really be its own programming and so I wrote a compiler which is in C sharp and using a force like syntax because force is relatively easy to do that. It's extensible. It allows metaprogramming and that compiler produces a code routine in fact it produces a small interpreter in C which is restartable and has its own stack and it's very light in RAM because the stack is bonded, it contains 17 words of 32 bits. So I'm just using 68 bytes of RAM which is relatively small. It looks like that. So it's a if you have tried to play with bootloader for free BSD you already saw force code because there is a force interpreter in it. So it looks like that and it's a bit barbaric and alien. But it's easy to pass because each basically each word becomes one instruction and in the output becomes one byte of force code. So this processes alert messages in SSL and in total it takes about 40 bytes of code 40 bytes of RAM just to do that thing. So it allows to pack a lot of behavior in a very small amount of code size. Thus to summarize a bit of what a few tips are. Since I think of myself as a hero and since I already look like Brad Pitt I decided that I could give tips. I mean it's part of the arrogance of the hero to things that he can teach others. And here are my tips which is for an heroic developer is to consider that every lines of code that he writes engages his owner and he will be judged by the quality of 40 bytes. So it's really a matter of maintaining your own standards. You have to be patient and when you decide something you have to keep to it and even if it takes time. So in the yard we see that Achilles has decided that he will not fight for a game M9 and he will effectively stops fighting for about 19 books of the 24. So for 19 books we see Achilles simply booting and a lot of things happen and he's not taking part. Because he has decided to do that and he keeps to it. And when he decides at the end to go fighting then he got he's very soft. He's not doing some small afternoon fighting or anything. The page is so slow. And you have to keep learning because you need to you want to be good at what you do. So you don't stop at some point I know everything now I can just do it and just live on it. You want to remain keen. So in the warrior metaphor you want to keep training even when you're not fighting because you're never as good as what you will be afterwards. And you have to know that you must complete your project. Otherwise, you just fall back into the anonymity that terrified Achilles. This is when you complete something, when you formally release the code that your glory becomes something else than just a dream. Now there is another side of the story which is what your manager will think of it. So this story also has tips for what are you going to do with your own hero and that's Agamemnon's problem because he has that top performer in his team but that top performer is also a diva and he must know how to do it and in the we see how Agamemnon's manages very poorly. So what you must do when you have a hero on your team is that you must understand that you can't really manage him. It's just some sort of ferocious beast that you can unleash on a problem and your job is to feed him with good challenges with good problems so that it will keep him occupied and he will do his stuff properly but you have to be to provide things that he will think fit of his own glory and your hero won't work if he feels that what you are giving him are too easy and could be done by normal people. He has to be he has to be praised and to feel that he is recognized to his own view of things and don't give fake praise because they can smell it it has to be felt and the last part time sheets are a good metaphor of administrative tax and heroes don't like that at all. So don't you have to relieve them of anything as mundane even if it's critical for good business and so on. So the notion for the manager is that if he had no hero managing would be a lot easier but then he lose the war because the top, the few top performers are in fact necessary and this raises the question of whether this will continue in the future. So let's talk a bit about the age. This is from the SEM and it's from your 2000 so they asked themselves a question which was on the time and it's still on the air which is whether software engineers should be like other engineers like for bridge building should there be a license that is can everybody just tell I can do software or should there be some sort of regulation because when you have a bridge to build you are very happy to have some sort of sanction by a state agency that says you this guy really knows how to build bridge so it will be and it won't fall down and there is a lot of regulation on that and the question was would that apply to software engineering and the SEM in 2000 basically said no they did not want it because it says that it does not work that the field is too new and there is no good definition of what would make a good software engineer it's not other if you went out building a bridge there are some parts in a bridge such as the pillar and stable and so on it's not how a bridge should be built and there is room for innovation but at least there are some there is some common knowledge and skills that can be certified and verified so you can have a notion of a big building engineer who is good at that and will give you some guarantees that the work is done properly and not so much in software at least in 2000 so the SEM took a stand and said no there should not be licensing of software engineering however that was a question which was in here ooh yes exactly association for computing ok ok so it's one of the biggest session of software engineers and another one is the IEEE who had extended and who took basically the the opposite position so SEM is against licensing and IEEE is a poor licensing so the debate is ongoing that one is from 2004 in which it's just an opinion of some guide but he writes text about how again engineering might be like big bridging because it's a good metaphor everybody talks about building a bridge in some parts of computing we are talking about cars as the general metaphor but here it's bridged and and then there are other people who are keeping on it and that one is more recent and it's from 2012 and it's from the IEEE so it's rather the poor licensing side of things at that time there were things that it's coming the age of and it's the end of the age of heroes it means that no more personally ring for your own glory people have to be professional and to be registered professionals so it's the iron age that is looming but it's not exactly happening right now and other example that one is from Wired it's also from 2012 and this is what I told that regulation is looming and they really think of it as carry and then another that one is from communication of the ACM and the guy who's called Lapland apparently is some sort of mercenary because he's also part of IEEE and he defends the viewpoint of necessary licensing within the ACM what these extracts mean is that for the last 15 to 20 years there have been ongoing discussion of finally coming to the iron age of engineering and making that a mundane regulated profession like physicians and it's not really happening in fact I mean is any of you a registered licensed software engineer not really because it's very hard to define what should be the core skills for a software developer it's a new field but it's also changing very fast all sorts of new technologies that come and go and it's very broad so you can have somebody who's very good at some specific part of software engineering but almost nobody is good at everything in software engineering this one you should have known it is part of the BSE license and it explains the current position of software developer an open source software developer is an artist he provides things without any guarantee of anything I mean it's not even guaranteed that the code actually exists and they deny any notion of responsibility if you have a bridge and it falls down you can be sure that whoever designed that bridge will get into a ball if you make some software and there's some security holes which allow the one somewhere to spread and causes losses in billions of dollars nope nobody's fault and this is even seen in the choice of the legal framework for this idea who gets the glory the laws he provides on code the same laws that for paintings it's all about an artistic production so it's not really engineering at least legally speaking we're just all artists so my conclusion is that there is an ongoing push for regulating software development and it just does not happens because it does not work you cannot really regulate software and still get the goodies that software provides you will see some regulations in some specific areas for instance when you are doing autonomous cars then necessarily there are sets of regulation of what on cars which would apply but they don't really speculate to the software layer and because as insufferable as it can be you still need him to win the war that's it any questions? It's been in news recently that one of the software engineer at Volkswagen that helped create the software that cheated on the diesel emission tests has been condemned by court so there is some regulation coming in saying that okay you can't just do anything you please and you are somehow responsible for what you're doing when you say how does this fit in your story of Harry Cage, Iron Age there's a difference to be made between incompetence and wordful malice that means it's not if you write and it just breaks you won't get much trouble but if you are doing something which is fraudulent and you know it that's how you can get some responsibility and it's not a regulation of the industry because the notion is not that he was not untitled to do some software engineering is that it deliberately cheated and the legal system makes a good difference between cheating and merely being bad at what you do so in that sense I don't think that it will really contribute to that notion of regulation because regulation would not have really prevented that I mean if you've got a cheater you can have a regulated cheater he would have his license and it would not steal it would still not prove anything it just wanted to point out that the engineering question was a manager, he was not a developer he was one of the top executives of the books like in the USA and he was sentenced for his role as a top executive not for his role as as an engineer or a software developer although this raising the question of what exactly is an amateur in software I mean if there is no definition of who is a professional then we are all amateurs all professionals but yes thank you yeah thank you for a nice talk just wanted to ask a couple related questions first of all about the over engineering which you know here is usually well not usually but sometimes too and about you know how to manage those kinds of things because like when people you know some heroes start writing code just to write code and that becomes a problem and the second thing is that you can't you can't win the war without heroes but you can't win the war with heroes only so how to bridge that gap between you know the heroes and their work and not heroes and just mediocre soldiers who need to work with the heroes as well and which who may not have that kind of expertise okay first I must say that I'm not a good manager so I don't have all the answers of that and I do that anybody really has my view is that if you've got your own hero and egos into too deep hearing he over engineer things and so on then your job would be to provide a distraction if it goes too long into one path you have to to send some way to bring it into another direction and that cannot be a necessity because that does not work but just like when you have a cat and he's doing something like trying to kill a plant that houseplant you bring out a toy just to distract his attention and that kind of developers with too much in his own ideas you can steer it by providing a fresh challenge in another direction and if you provide enough challenges he won't he won't really work well with normal workers because in his view they're all peasants he does not want to talk to them but he can be convinced to leave them alone and to just let the normal players bask in his variance as long as you don't give him time to become a really horrible person usually the top developers some of them are nice human beings but a lot of them are best kept alone they produce things and you keep them occupied so that they don't become building figures who will then express their anger on their fellow workers you want them to express their anger on problems so give them problems and hire normal people to clean up things afterwards somehow you want a good painter to make the painting then normal construction builder to build the house around the paintings okay we're running out of time so this is going to be the last question hi Thomas, thank you for your presentation I would like to know if you're ultimately a softener regarding UBER SSL is this the effort to approach an UBER SSL and bring it down eventually? I'm not sure the microphone I didn't really hear anything okay my question is is your ultimate deeds of valor regarding UBER SSL to Trojan open SSL and then burn it down during the war? I understand that question UBER SSL is not done yet I'm still working on it but at some time yes I will take over the world that's not a question thank you very much