Hello everyone, thank you for coming to our session. So this session is entitled Connected Vehicle Platform, Kubernetes and Vehicle Service Mesh. So let's get started. So as end of this session, at first we will introduce our company and our team. Secondly, we will explain what we are developing and why we are using Kubernetes. Then we will explain our technical details. So let me introduce myself. So I'm Seh Kozumi, project manager of this Misaki project. So I joined Denso Corporation in 2017. So I'm developing edge and cloud integrated platform to bring cloud native ecosystem to the vehicle application. Okay, so Amasa, could you introduce yourself? Okay, so hi everyone. My name is Aman Gupta and I'm a software engineer at Denso Corporation. I joined Denso in October 2019 and this is my first full-time job. And I am also developing Misaki project in Kozumi-san's team. Kozumi-san, please continue. Okay, so I'll just explain the background of our project. So at first Denso is an automotive parts manufacturer. So we are providing the multiple type of their products and the system for global vehicle manufacturer. So we are taking the second global market share in automotive parts industry. So Denso is trying to be a service enabler by utilizing the cloud technology and creating additional values. For example, their remote maintenance, fleet management and auto mass driving and the traffic cone prediction. To be a service enabler, we are doing the three sort of activities. So first one is to hit on the new mobility subs idea. We do our design thinking. Second, to develop the prototype quickly and launch it easily. We are using the public cloud and OSS. And third option to create user values with customers, we do agile develops. So these three approaches are the same as the Silicon Valley approach. Especially our team focus on the vehicle connected platform. So Denso is providing the hardware parts like ECU, the sensors, air conditioner. But not only that, by utilizing the H computing and also cloud computing, we are providing the additional functions such as microservices and also cloud sites of the microservice module. So based on that mobility service providers can create a new service easily and quickly. So this is our team member. So we used to work in the development room, but recently we are work from home in this COVID-19 situation. So actually there are some barriers to develop the vehicle with applications. So it's not the same as a cloud application development. So let me explain what's the barriers. First barrier is a software. So this sort of the emitter software is running on the vehicle ECUs, the electric control units. So around 25 up to the 70 ECUs are running inside a vehicle.  And the middle size of the ECUs use a real-time operation system. So Redux is not our standard yet. And the computing resources of this sort of the ECUs are quite limited as there's no redundancy of the computer resources for their additional applications so far. And emulating the ECU environment on the development PC is really difficult. It requires some special hardware and the same size of the emulator. And keep updating the new software to the vehicle is not easy. So these sort of the problems are the first barrier of the software development for vehicle. And the second barrier is unstable connection. Vehicles are sort of their distributed system and they keep moving. So sometimes there is a no signal and the network is disconnected. And sometimes the network width is not good enough. So uploading or downloading speed is quite slow. So developers have to think about the sort of the network issues. For example, they're storing a data locally and send it a data again. And if it fails, it's rolled it back and send it again. The sort of the processing is quite troublesome. So this is the second barrier. So these two barriers is obstacle to develop the vehicle applications. But the motivation is developing the vehicle application is getting bigger and bigger. For example, the market size of the connected vehicle and application is getting bigger. And the number of the user is rapidly increasing. And also the vehicle itself now shifting from the feature phone style to the smartphone style much more flexibility and more new computing resources. So new vehicle will have their more flexible OS like a Linux and the platform. So some new use cases are already appeared. For example, the anomaly detection or real-time driving support. So to develop the prototype of the smartphone like vehicle. So we develop the Kubernetes-based connected vehicle platform, Misaki. So in this platform, the no MDS case is required. And quite easy to deploy and uploading the vehicle application. And developers have no need to worry about network disconnection or network failures. It enhance the productivity for their vehicle application developers. From architecture perspective, ideal architecture is like this, the left side. So centralized computing resources and centralized management. It's quite easy to manage and control but actually there is some network delay and disconnection, it's not works. So our approach is the right side. So our approach is distributed computing resources like a small crowd is located inside the vehicle but the management function is centralized to the crowd. So it's simplified our management function. So this is the architecture overview. And then some will explain the details but briefly says that we are using the some open source on AWS like this sort of the digital digital trains or the go implementation. And also we are using Kubernetes but entire Kubernetes is a little bit heavy to running inside a vehicle. So we split into the master node and the worker node. So master node work in the cloud side and also the worker nodes work in the vehicle edge side. And we are interconnected, both sides are using VPN. So only if they disconnected the JS vehicle the JS worker nodes container keep running. So why Kubernetes? So the reason why we are selected Kubernetes is flexibility. So current ECUs are not good for the Kubernetes because it have not enough computing power for that but the integrated ECU much of a bigger ECU is getting popular. And another additional computing resources like a vehicle computer will be implemented in the vehicle. So inside the vehicle there is several the small computer resources is located. So Kubernetes is a really good approach to gathering the sort of the computer resources and making one single pool and running the containers. So the Kubernetes flexibility that can give the workload off-roading. So vehicle edge only have a limited to the computer resources. So sometimes the application is consuming a lot of the computer resources inside the vehicle. So in that case, the high priority applications keep running inside the vehicle and the low priority application is off-roading and migrated to the cloud. So the application itself is a keep running but the workload inside the vehicle is stable. And the other reason are using Kubernetes is subsmash. So Nisaki provides the common network functions such as a data queuing. So if there is no this sort of the network layer subsmash so application developers should think about the network disconnection or network is slowing down the sending of data again. But by preparing this sort of a common function the application developers just try to send the data. And this connected store data to this data queue. And after they regain the connection they're sending a data again. So at that time is there this application never realized the network disconnection. So it's simplified the development process. So we are so surprised by the presentation at the Cubicon North America last year. So US North Air Force is already tried to use the Kubernetes in the F-16 fighter jet. So using Kubernetes in vehicle is more easier than that. So these sort of things are using, are we are using the Kubernetes. Okay, so let's move on to the technical details and the demonstrations. Anas, go ahead. So thank you Koizumi-san for presenting your part and hi everyone, I'm back again now I will tell you about the technical details of our Misaki project. So let's start with the most basic thing what our Misaki project consists of. So we call it a vehicle cluster. So think of it as a cluster of an edge device and a cloud instance. And they are connected by a Kubernetes. So the master node lives in the cloud side and the worker node lives on the edge side and they both are connected via VPN. So in the real world scenario, we can have one cloud instance for a car or a cloud instance can be shared among a few cars. So that's the scenario we are thinking of and we are developing for that. Now our Misaki has two different components. One is Misaki orchestrator and one is Misaki service mesh. So I will go through both of them and show you the demo scenario for each of practical real-life scenario. So let's start with the Misaki orchestrator first. This is the architecture for Misaki orchestrator and it mainly consists of four different components. You can see from the left-hand side, most right-hand side, we have a UI and on the most left-hand side, we have the vehicle cluster. So it's like an end-to-end connected vehicle platform. So I'll explain all of these four components now. So let's start with the UI first. So we call it Misaki UI. Misaki UI is implemented in Next.js. It's a Vue.js framework and think of it as a dashboard for administrator where he or she can see the list of vehicles and also can see the list of applications to deploy to this vehicles. And the applications we are talking about here are basically Hymn charts. This Hymn chart lives in a chart repository which can be hosted anywhere on GitHub, GitLab. And we are using something called chart museum which is hosted on our EKS cluster currently. So an administrator choose this Hymn chart and deploy this to a vehicle. And this request goes from this UI to the next component which is called Misaki API. So now let's move to Misaki API. Misaki API is a REST API implemented in Golang. And the main function of Misaki API is to render a Hymn chart into a useful Kubernetes manifest list. So a typical Hymn chart looks like this on the left-hand side. And the most important part of a Hymn chart is this values.yaml file. So on the right-hand side, you can see we have a manifest list which have a lot of resources like secrets, deployment, services. Now after we render this Hymn chart and convert it into a manifest, then we send it to a database. And for the database, we are using something called digital twin, also known as Dicto. And this is a open source database solution for IoT devices developed by Eclipse Foundation. The main MVP for this database is that the database clients can connect to it via a WebSocket connection. So for our case, we have two different components connected to digital twin. One is the Misaki API, which is sending the request. And the other is Misaki Kubernetes agent, which is present on the vehicle cluster. So Misaki API sends this rendered Kubernetes manifest and store it to a vehicle ID in digital twin. And once it is changed, our Kubernetes agent fetches it from the digital twin via a WebSocket. So that's the use of digital twin here. And now we go to the Misaki Kubernetes agent. So as you have seen, our Kubernetes agent fetched the Kubernetes manifest from Dicto. And the main job of Kubernetes agent is to apply this manifest to our vehicle cluster. So our vehicle cluster has two different components, right? One is the cloud instance and one is the edge device. So our application can be deployed either in edge device or cloud device or can be separated from cloud and edge device. So that's Misaki orchestrator, basically. And here is the overall overview. And you can see there is a dashboard to choose the applications. And we choose the application. It goes to the Misaki, which is basically Misaki API. And it gets the actual hand chart from the application repository. This application tells about the containers present in this scenario. And it can be deployed on both edge and cloud instance. So today I will show you a practical scenario, a real-life application which we have developed in-house. So the flow will be something like this. We will first delete an application. So the application we'll delete is called can-uploader for Prius. It has four different components. And after deleting this, I will show you the terminal in Jetson actually, Jetson JVR. And show you that pods are no longer available. Then I will install another application called via containers for Prius. So this application has eight different pods. And I will show the login screen of Jetson JVR again. And you will see eight different pods later. So let's move to the video now. So here is the Jetson JVR screen. And you can see on the top four pods are via containers or can containers. And we are going to delete them. So right now it's in the shutting down phase. And you can see it's in the terminating state right now in Jetson. And now it's no longer available. These changes are also reflect on the dashboard. You can see there are no containers available. Now we will install another services. And this is basically login to a chart repository. These are the following charts available. And we will install via containers for Prius. We can also input some additional components to this home chart. For our case, we will give the version and also the login details for that container repository because our Kubernetes needs to pull this Docker images. Right? So we have done that. And now it's in the provisioning state. Let's wait for a moment. And now it's in a working state. Let's check the Jetson JVR. So you can see there are eight different pods now on the top. And this change will also reflect on our dashboard. You can see on the edge side we have eight different pods running. So this green dot means it's in the running state. So our via containers are actually responsible for sending files to S3 bucket every 30 seconds. And I will show you that it will just send another file now. So let me refresh. And you can see there are two different files now. So our containers are working fine. So this is like end-to-end process from deploying to the deployment and actually getting the data to the S3 bucket. Okay, so let's move to the second component now. So our second component is Misaki Service Mesh. Let me give you a brief overview again. So why are we using Service Mesh? So Service Mesh take up us network concerns from the applications and application developers no longer needs to implement distributed system practices like timeouts, system discovery, et cetera. And application developers can focus on business logics and values rather than worrying about these networks. And how are we doing this? We are using Envoy as a sidecar proxy. And we are also using something called Misaki Control Pane which manages the policies for this Envoy. So the architecture looks something like this. We have a vehicle cluster here and on the top side we have a cloud mode which is running an application app C and on the bottom side we have our edge node. It is running two applications, A and FB and all these applications are running Envoy as a sidecar proxy. So all the request coming, outgoing or incoming are passing through Envoy and Envoy manages this request where to go. So to manage policies for this Envoy, this control pane is a centralized unit present in this vehicle cluster. We also have an additional component called Q. So Q basically stores the data when there is no network available. So it acts as a proxy server. It stores HTTP request streaming data from application when there's a network disconnection. It resents the HTTP request and this streaming data to server whenever the network is connected. This is the scenario where we have the network connection available and we will send an MP4 file to S3 bucket and it will be sent to the S3 bucket directly. Now, considering a case of disconnection, so our application is trying to send this file to S3 bucket but it will be redirected to the queue and once we regain the network it will be automatically sent to the S3 bucket. So that's the functioning of Q and service mesh. Now I will show you a realized scenario of an application running in Jetson JVR and also this Jetson JVR is present in a vehicle, actual vehicle, Toyota Prius. So let's start. This is a S3 bucket and it's currently empty and we will try to send a dot some file. So this is the Jetson JVR screen and on the left-hand side terminal you can see the logs of service mesh and on the right-hand side, right top side you will see my colleague will make a request to send the file to S3 bucket and on the bottom left or bottom right you see the logs of a replay component which will send the data once network connection is available. So right now connection is already available and we just see a normal response and our file should actually be sent properly to S3 bucket but soon my colleague will disconnect the LTE dongle from Jetson JVR. So how we disconnect as we put LTE dongle in a Faraday bag temporarily this will block the signal and now my colleague has made a request to send this dot some file again to the bucket and now you will see the response will be something different. Please wait a moment. You can see there is a temporary redirect message. So that means our request has been stored in the queue and now my colleague will take the dongle out and our network will be reconnected. So once our network is available our queue should do its job and you should see the changes on the bottom right terminal our replay will send the file to the S3 bucket. So here you can see the file is being sent and we got a response. So it should be there in the S3 bucket. Yeah, and we have the file. So that's it for the service mesh demo scenario and now I'll quickly summarize or quote our project. So we developed a prototype of Kubernetes-based connected vehicle platform and Kubernetes helped us a lot to develop and deploy applications on vehicle but there are still a lot of challenges that needs to be faced. The challenges we are currently facing are how to update Kubernetes worker nodes in each vehicles and how to manage many Kubernetes master nodes or how should we think about one Kubernetes master and many edge vehicle architecture. We also have to try some lightweight Kubernetes like K3S and Qwitch to minimize the required CPU requirements or memory sources on the edge device. Our journey is still just a beginning and there are a lot more things to come. And you can visit us at our GitHub page named Misaki-IEO. We are planning to release some technical documentation later in future. So please stay tuned and thank you everyone for attending our session. Yeah, thank you for joining.


How's everybody doing? Welcome back to my channel. My client flew in for the next two days to get his outer sleeve cover up. So with that being said, let's get this day started. Let's go! Hey, Kevin. Have a seat. Hey, man. Marcus. What do you have? Two pieces, I guess you wouldn't do that. Oh! Kind of just let him practice on me, to be honest. And it's funny, because he's actually a professional tattoo artist now, and he's actually really good at what he does, except he does traditional work. Maybe I helped him to get to where he is today. Hey, you set him up.  I checked out maybe like 20 artists, and my buddy Steven, he lives out here. He has sent me yours, and I was like, as soon as I saw your work, I saw one, I was like, that's him. That's it!  When I sent out it again, and then I got the response, I'm like, yes! I was so excited, dude, I was like, yes! That is so dope, because I feel like, I'm pretty sure you waited a while, you know? And now we're here. That was like the best email I've got. I would be sick. Which fits so nicely, and will cover up the whole thing so nicely. The features, the expression on it, it's insane. I might be able to sneak in maybe a little bit of red in it to portray the blood in it. We have three solid options that, we have the top looking amazing, the bottom, it's only gonna complement the top, so we're gonna make it work. It's gonna work out. Yes, it's gonna work out, 100%. Today is day one, and I'm gonna be covering up Jesus with another Jesus. Sounded better in my head when I said it. It's cold out there. It's chilly, huh? Right over there.  Because it's, I like wearing sweaters and not like feeling cold. Me too, man. I love the winter.  I sweat in 0.3 seconds. See you. Yo, like I step outside and it's a little hot, but my back is ripping. All right, let's go to the middle of the shop. I can have space to put this on. I don't know how your mind like, man, you know what? Can't wait to see it. I look at it, I'm like, what am I looking at? Sometimes, I think the same way. Look at this guy. Damn, Daniel. Damn, Daniel. Stasty, man. All right, so that stencil is ready to go. I really like the placement. And my starting point is gonna be on the neck area because I want that beard to stand out. That beard is gonna have a whole bunch of detail. So in order for me to make the beard stand out is by making the neck have a whole bunch of contrast and make it as dark as I can make it look before. It's too dark. Here we go. You ready? Fire. The background or the contrast on the neck went pretty fast. All I'm gonna do now is start the beard. The beard is gonna be very interesting because I'm gonna be using a seven round liner with the same voltage of a 5.0. And I'm not gonna be following my reference step by step just because my reference shows a lot of hair. And to translate that onto skin is not gonna work out because with time it's gonna fade and it's not gonna look great. So I will give him a better version of the beard to create more contrast and a long lasting tattoo. I'm just going with the flow here. I've done many type of beards throughout my career. So now I'm able to kind of pick and choose what looks great for the specific face that I'm tattooing. So here I feel like a curly beard would look a lot better. Once I see where everything is then I'll figure out where to put more black, where to put less black, where I'm gonna put my highlights and things like that. I'm starting with the darkest part of the cheekbone to create my shades and keep the dimension of the cheekbone. I'm taking it very slow, starting with a medium gray. Maybe it's like a 70% medium gray. And I'm not necessarily faded out but keep packing a lighter gray to create the face structure and the features. Shape on that is crazy. The highlights on the face? Yeah. Punch in there, bro, because that's gonna look nasty. Shoo! Alrighty then, let's eat. Today's the final day and I'm gonna be covering up the forearm, which is gonna complete the outer sleeve. Dude, that looks huge.  Easy day today. It's gonna be nice. It's gonna be nice. All right, have a seat. Oh! Right, so second day here. I'm starting off with outlining the cross. I don't wanna lose the stencil of that. I'm gonna be making that the cross red to make it stand out and make it match a little bit more with the theme. I'm really excited to do the helmet. It has a whole bunch of texture. And to finally complete the outer sleeve, it was a little tough yesterday. You were hurting a little bit? Yeah, it was hurting a little bit. We got it done, though. We got it done. But today we're gonna complete it. I probably predict we're gonna be here for like like seven hours probably. What time is your flight? Tomorrow morning. Okay. Oh, you're gonna be chilling. Yeah. Okay. To make sure that I do this cover up successfully, I want to start with my solid black first and apply my scribble technique. And do texture all over the helmet. And then after I'm done with that, I'm gonna begin to transition to my medium gray. And my last layer is gonna be my lightest gray. My lightest gray is what's gonna create the highlight on the helmet. And my solid black is what's gonna create the dimension that the helmet is curving. And I have to make sure that I keep in mind where my concepts and highlights are at because it's very easy to add too much texture to the point that the helmet is gonna get a little lost and look flat. All done? That's it. Dude. It's like on the perfect spot. That little thing. It's insane.   When I first got that email that I was accepted, I was beyond excited. Overall experience from start to finish was amazing. Everything was super easy. Kevin worked with any suggestions or came up with some of his own ideas that I loved and we went with and he made everything seamless. And it was just a great experience. He treats you well, it's very nice. His assistant Marcus, big help as well. Super nice people, good vibes, good energy. Love the whole process. The only reason I wanted to get these covered up is I mean I got these when I was young, under 18 and they were just really, really bad and I was embarrassed walking around with them on my arms.  I can do that now for sure.


Related to what is this? This is, I did find one single DOS formatted five and a quarter floppy, and this is my five and a quarter drive clunk. It's wired up to my feather, my floppy feather wing, running my grease weasel emulation mode. And what I got working was Flux Engine. So Flux Engine is another software that can read floppy disk drives with flux data and then parse it out. And I did get this working earlier and I just want to quickly show this is what was on it. This is the image that I'm opening up on my computer.  And this is Flux Engine, if you're interested in it. It's kind of a cool open source Flux reader and this is the pull request that hopefully I'll be able to get merged in soon.


A fiery horse with a speed of light, a cloud of dust, and a hearty hail silver, the Lone Ranger. With his faithful Indian companion, Tonto, the daring and resourceful masked rider of the plains led the fight for law and order in the early western United States. Nowhere in the pages of history can one find a greater champion of justice. Return with us now to those thrilling days of yesteryear, from out of the past from the thundering hoop feet to the great horse silver, the Lone Ranger rides again. The settlement had consisted of a few small cabins huddled close together in a valley near the Badlands, but the settlement was doomed to destruction. The settlers had left their buildings with fires still burning in the hearts, and meals cooking on the stoves to escape the attack of savage redskins.  Every cabin was in flames, one after another the roofs and walls fell in. The Indians rode off, disappearing into the west, leaving only the burning settlement in a tower of smoke that served as a beacon for a unit of cavalry under the command of Lieutenant Carter. The Lieutenant dismantled and stood beside old Jeff Neely, whose pale eyes were moist with tears of rage and frustration. Sergeant, search the rogers first of camp. Yes, sir. All right, men, let's go. Oh, cabins. Every last one of them. Yes, it's too bad, Neely. But it would have been a lot worse if you hadn't been warned in time to bake it. Warned, yes. Me and my friends got away with their lives, but what's a good living when everything is gone? Look over here, Lieutenant. This is where my house stood. Look at it. Nothing left but the chimney. It's too bad you didn't get to the fort a little sooner. We might have reached here in time to prevent some of this destruction. Lieutenant Carter. Yes, Sergeant? I guess Neely was right when he said everyone had gotten away from here before the Indians struck. No sign of casualties, huh? No, sir. There's a couple of horsemen coming from the west, right over there. I see them. Tell the men to spread out and hold the rifles ready until we find out who those horsemen are. Yes, sir. Hey, Lieutenant, one of those horsemen is a red scheme. So I see. Honey alert, man. There's an Indian coming. No, sir. It's nothing to fear from one red scheme. Neely, your eyes are pretty sharp. Is that man on the white horse wearing a mask? Very gully he is. And look at that white horse travel. The paint is good, but look at that white one. Horses are high.  Lieutenant Carter, that man's all right. I'll decide that, Neely. Lieutenant, are you in charge of this detachment? I am, sir. I thought I saw a band of Indians heading west. They rode hard and carried a number of small articles that looked like loot. I think they're the ones who burned the settlement. And who are you? Why do you wear a mask? Aren't you more interested in the Indians who did this damage? I am, by the center of that mass. Take my word for it, Lieutenant, this man's all right. He's the one who warned us the red schemes was coming. If it hadn't been for him, we'd all be dead. Now, I see. We've trailed the Indians and know where they went. I'll have a column formed at once and we'll go after them. I'm sorry, Lieutenant. That won't do. What? Those Indians were incited. They're no worse than any of the redskins. There's a lot behind this attack. The guilty Indians will be punished. That won't stop future attacks. Lieutenant, you've got to get at the source of the trouble. Tell me where those Indians went. That, sir, is an order. I'm sorry, Lieutenant. I'm not in uniform. Your authority doesn't cover me. Perhaps I haven't the authority to wish you an order to you. But I do have authority to place you under arrest. If you refuse to give me information, you'll return with us to the fort and talk to the colonel. Oh, now, Lieutenant. It's all right, all right, Neely. Todd and I will submit with the understanding that I am to keep my mask inside. I'll make no terms with you. Then we'll not submit to arrest without a fight. Please, Lieutenant, don't stir the fight with this man. He's proved himself a friend. He must have a reason for reckoning as he does. Very well, Neely. Mr. and view of what Neely has said will permit you to keep your mask and guns as long as you ride with us without trouble. All right, fallen men. Form a column of force. Sergeant, you're responsible for this mask man in the Indian. See that they have no opportunity to break away. Mr. You're heading for trouble. We'll take a chance, Neely. I hope it's worth it. Lieutenant Carter permitted the Lone Ranger to retain his weapons and to wear his mask. But there was a heavy guard when he was taken with Tonto to the headquarters of Colonel Richards inside the Army Garrison. What? Hold! Colonel has been advised. You'll have to wait a minute or two before you can see him. Very well. Is he busy? Yes. He's talking with that man named Burkey. Burkey? Him inside. Why, Tonto? What's that? Do you know Burkey? I don't know, Sergeant. The mask man in the Indian are to step inside and wait in the outer room. What about the guard? It ain't on duty at the door. Come on, Tonto. Wait right there until the Lieutenant comes from the Colonel's office. Very well. Tonto, Burkey is a man who watched that fire on the settlement burned down. He was with War Cloud's raiders. That's right. Indians ride west. I didn't get here to forge so quick. He must have left the Indians and come directly here. Probably took a circle route. Otherwise, he'd have met the soldiers. That's right. And what do we do? I don't know. It depends on how the Colonel acts. We're the only ones who know that Burkey is responsible for that Indian attack. We can't prove it. That's right. Did you notice where the soldiers left scouting silver? Uh-huh. Me notice. All right, be ready for a fast break. I'm going to lay the cards right on the Colonel's desk. He may not like what I have to say. In that case, we may have to make a break for it. You ready? Good. Colonel Richards will see you now. Please come in. Very well. Well, this is the mask man in the Indian you arrested on, Lieutenant. That's right, sir. You're Colonel Richards? I am. I might advise you that Lieutenant Carter went a long way when he permitted you to keep your side arms to say nothing about that mask. Who are you? I wear the mask to conceal my identity, Colonel. Lieutenant, you may wait outside. Very well, sir. First of all, I want you to know that you'd better not depend on those guns you're wearing.  I didn't come here Colonel expecting to use guns. I came because I have something to say to you and I'd like to say it in private. It seems to me he's got a plenty of nerve, Colonel. Anything you have to say, you can say in front of Berkey. Very well then. You refused to supply valuable information to Lieutenant Carter. Why? I wanted no fighting. You and the Indian learned who made that raid on the settlement. You trailed them into the Badlands. Colonel, I thought I were not fighting Indians. The army's sworn duty is to defend this territory from raids. By Indians or bad men alike. Whose raiding party was that? Chief War Cloud was... War Cloud, eh? But Chief War Cloud was not with the raiding party. If you want to know who led that war party, it was Berkey, the manager's side. Why you ornery for... Why me? I'll see you here. I don't have no gunplay. It was Berkey's idea. Now, the move like that Berkey and I'll do more than crack your wrist. I'll do all my own man. Well, you just...  Colonel, Berkey's planning to use the Indians to take control of this territory. He made a lot of promises to the young men in War Cloud's tribe. They're turning from their old leader to follow him. Ho-ho!  Have you any proof of what you say? No, sir. Not yet. I'd rather think it's my word against the word of an unknown mask, man. You, sir, refuse to tell Lieutenant Carter who's where those savages are hiding. Perhaps you'll tell me so they can be disciplined. In view of your feeling toward Berkey, I'd rather not tell where the Indians are. You'll talk, or I'll have you and your Indian friend thrown into the guardhouse. That's your final word, Colonel Richard? It is. Now, what are you going to do? Talk or face arrest? Neither. Sorry. Hey, look out! Here, Berkey, amuse the Colonel. Hey, what's up? The wind has tunneled. We've gone that way. Let me fix it. Oh, shoot him back here. Come back, I said. Hurry, tunnel out this window! This way, tunnel the stables. Man, over to the stables. Can you see him? Hey, what's the sign? You can thank the Colonel for this. Hey! Sorry about that, soldier. What's right here? Going to be a tight squeeze, Tutto. Head for the gate and lean low on the saddle. He ready. Very big fella. Moncillor's Count. The gate. Watch it, Tutto. Moncillor's Count. Found a lieutenant. Why did you let that man in the scene with his side arms? Well, it was with your permission, sir. We had guards. Guards. He literally threw Berkey at me, then went out the window. I'll find that mask man. I'll learn more about him if it's the last thing I ever do. Moncillor's Count. Very big fella. Take it easy. I think we have out well any possible pursuit, Tutto. That's right. We'll cut south from here. I want to see Chief War Cloud. Or maybe Berkey go there, too. Yes, he probably will. We've got to get there first and convince those braves that Berkey is an enemy, not a friend. Moncillor's Count. The mask man and his Indian companion rode hard toward the distant sound of war drums to confer with the old Indian leader Chief War Cloud. The low rangers talked with War Cloud was discouraging. Through it, all the other members of the tribe maintained a chant of hatred accompanied by drums. Chief War Cloud, have you lost all influence with your braves? White man, come here and speak with tongue of serpent. Him, make Indian think great reward come from fighting white people. Then call your people to the council. Let me speak to them. It's no good. You know me as a friend. That's right. But other people of tribe think Berkey's good friend. Something's happened. Let me look outside we want. Tutto's coming this way and fast. What is it, Tutto? Berkey, just come into village. Berkey. Over there. Him coming this way. So I see. War Cloud, he's bringing several of the warriors with him. That's bad. Look who's here. We've been expecting you, Berkey. Trying to make trouble for me, huh? You bad, you leave village. Save your breath, old man. From now on, I'm giving orders around here. Before I do anything else, I aim to get rid of a couple of my enemies. And I mean you.  Yeah. You and your pal are going to be staked out as an offering to the engine gods of war. The curtain falls on the first act of our lone ranger's story. Before the next exciting scenes, please permit us to pause for just a few moments. One more story, old chief War Cloud found power slipping from his fingers when the warriors of his tribe listened to promises of power and wealth made by the white man named Berkey. Berkey had the confidence of Colonel Richards and knew he could retain that confidence if he disposed of the lone ranger and Tonto. You overplayed your hand when you broke away from the fort. The game isn't over yet, Berkey. That is as far as you're concerned. These Indians are taking orders from me. Tie up this masked man and Tonto. Wait! It's no use, War Cloud. They won't listen to you anymore. My braves, he speaks with voice of evil.  Put down your weapons. We must live in peace. We must live in peace. The Indians are undecided, Tonto. I don't know whether to listen to their chief or to Berkey. Are we showing them the chief right Berkey wrong? I don't know. I don't know whether to listen to their chief or to Berkey. The old man who speaks to you. The old man who's afraid. And what's he afraid of? Where's your enemy? Where was the enemy this morning? There was no fight because the settlers fear you. And it'll be the same with painted posts. Wait! Before you make us prisoners, you'll hear what I have to say. How don't I came here in peace?  You can't make us prisoners without bringing down the anger of your gods. If you want a new leader, your council shall decide. Council has decided. And war cloud is no longer welcome. He no longer has a place in this village. It is the law of the tribe that he should be allowed to leave and take with him all those who want to follow. That's not good. You may not want to leave. You've got to do a temporary war cloud. You've got to get away from here. You must trust me. I trust you. Oh, listen to that man with a mask. He's an enemy and he must be put to death. Is this a friend who tells you to go against the law of the tribe? That was a mistake, Burkey. These people have traditions. You're going to lose their confidence if you don't follow the rule. My people, you want no leader. You want white leader. You have chosen. I abide by choice. Before the next sun rises, I, the old one, will have gone. Burkey knew better than to try to stop old war cloud when he left the village with a lone ranger and tanto. He was forced to stand by while the three rode away in the moonlit night. I don't mind. He'll probably warn the people that painted pose, but so much the better. Sure. So much the better. Braves will think even more of me when they take another town without resistance. Go on and warn the people that painted pose. See what good it does you. It was two hours after taps, but light still burned in the officers' quarters where Colonel Richards met with Lieutenant Carter and several others under his command. We can discuss the Indian situation all night, Colonel Sir. But there's one thing we can't get around. What's that, Carter? The Indians are becoming increasingly troublesome. Do you suppose there's any truth in that mask man's accusations? You mean about Burkey? Yes, Sir. Nonsense. Burkey has spent a lot of time in Indian country, Sir. He knows them. He's given me valuable information concerning them. Understand, gentlemen, I don't admire Burkey as a man, but the accusations of that mask man are too far fetched. I can't give credence to them. Something's going on outside. Open the door. I'll see what it is. Yes, Sir. Come in. Close that door. Now then, what do you want? Colonel, I have a message for a mask man. A mask man? Yes, Sir.  Yes, Sir. That's the man. I want that man. Where is he? Please, Sir, if you listen to me, you will find him tomorrow. Tomorrow? What do you mean? The Indians are going to make another attack. What's that? Where? They're going to attack painted post. War clouds Indians? Yes, Sir. The mask man says if you go where I take you, you'll be able to intercept them before they reach the town. Where's that? I'll have to serve as guide if you don't mind, Sir. This is a trick. Oh, no, Sir, it's no trick. I give you my word. You learn a lot of things. You'll also see the mask man. I see. What do you think, Carter? Well, there's nothing loose, Sir. Colonel, the mask man told me to give you this. What? He didn't know whether it would mean anything to you or not. What's that? A bullet? Yeah, a cartridge. It's made of silver. What's that? Did you say silver? Yes. Silver cartridge. Carter, I'm Colonel Richards. I've heard of a man who's known as a lone ranger. He identifies himself with silver bullets. And he wears a mask. That's right. Not only that, he has a white horse. He calls silver. Thunder, that accounts for it. That accounts for the way that mask man and his Indian friend got out of my office. His Indian friend? There's another point. The lone ranger's supposed to travel with an Indian. The man who was here was the lone ranger. Why in the name of goodness didn't he say so? He wasn't sure, Sir. Wasn't sure of what? He didn't know whether or not you'd ever heard of him. Heard of him? Of course I've heard of him. Who hasn't heard of the lone ranger? And he told you Perky was behind this Indian trouble? Order me! The man is hungry. Feed him. Then put him up for the night. We're going to ride at daybreak. Pass the word! There was action in the fort at daybreak. Horses were saddled and men mounted up in battle gear. Colonel Richards himself was in command. The gates swung wide. And a moment later, a double column of troopers headed west toward the badlands with a lone ranger, disguised as an old man, setting the route. The morning was well advanced when the troopers came out of a woods and met Chief War Cloud in Tonto. The Colonel and Lieutenant Carter recognized the lone ranger's companion and signaled a halt. Detectives! The man who had been riding an Indian pony disappeared among the trees. War Cloud, you say your people have chosen a new leader? That's what War Cloud say. That right. Him white man. Him named Berky. Now, Sir, you must believe it. You have War Cloud's word as well as a statement of the lone ranger. Look over that way. Indians come. Colonel, look to the west. Redskins! I see them. Tonto, where's your masked friend? You see him plenty soon. That old guy told us... Where'd he go? I don't know, sir. Those Redskins are coming fast. Form a skirmish line. Prepare to meet those Indians. Form a skirmish line! Are those your people, War Cloud? Those my people. Them not like war. They're coming in a way that asks for it. They're masked, man. Colonel, look there. That's the man. And the horse. That's the ranger. Post him a holer home. You, sir. Colonel Richards, those Indians are on the way to painted posts. But we're in time to intercept them. Please listen to me, sir. Those Indians don't want war. They've been misled and misguided. Don't blame them. Blame the man who's leading them. A man named Berky. I don't see Berky. No, you don't see him. But he's there with the Indians. He's dressed as one of them. Tell your men to hold their fire. The Indians won't fire on soldiers unless your men start it. How do you know? Because I know war, Cloud. And I know his people. Hold your fire until ordered. Pass the wave. Hold your fire until ordered. Watch those Indians. They've seen your men. The Indians rained up in a wide line, facing the troopers who held their carbines in readiness. For a moment, it was a strange tableau. Troopers and Indians faced to face across an open space of 50 yards. Each force waited silently for the other to make a move of aggression. Then the silence was broken. Come on, soldier. The lone ranger raced toward the Indians and rained up, facing the center of the Red Man's battle line. Hold them before I. Easy. Set him up, big fella. Easy. Where is your leader? Bring out your leader and let us see his bravery. We are War Cloud's friends. See? War Cloud is on this side. Where is your new leader? Is he afraid to step forward and meet the followers of War Cloud? The lone ranger dismounted, took off his gun belt and hung it on his saddle. Right there. And he spoke again. I am on arm. Let your new chief now step forward. Why does he not command you? Why does he hide behind your front ranks? Must I, on arm, go among you to meet him? Come on, Berky. Come out, or I'll come after you. The lone ranger waited half a minute and advanced with long strides toward the Indians. Berky, knowing that to show himself would mean instant capture by the troopers, became panic-stricken. Then he jerked his horse and bolted to the rear. Get me through there! There goes your brave new leader. The matter was to make you so great. An Indian gun barked once, and Berky fell. Close over, Colonel. The Indians have taken care of Berky. Your courage in going unarmed among them showed the Indians what a craven coward they'd chosen as their leader. What I did took no courage, sir. I know those Indians. War Cloud? They're raising their hands to you. They want you back. Go to them. They've learned their lesson. Them not learn lesson until all damage paid for. You, soldier. Yes? My people will rebuild houses for settler. It is promised. And go a long way toward future friendship. It will be done. Away! As for you, sir... I hope Colonel, the Indians will have a chance to make good their mistake. They shall have it. And as for me, I too made a mistake. I hope I shall be forgiven. I didn't know who you... We... We all make mistakes, Colonel Richards. The smartest of us admitted.  Lieutenant! Yes, sir? What's the word to form ranks? Form ranks! We all make mistakes. That's what he said. I wonder if the Lone Ranger ever made a mistake. What you have just heard is a copyrighted feature of the Lone Ranger Incorporated.


Great conversation. Tell me your title again, I love your title. VP of innovation at IBS. Very nice, very nice. So how did it go on theCUBE? That was a lot of fun, we covered pretty much soup to nuts. Well let me ask you this, which time around, which one of the, was it John that was the good cop or bad cop, who was the good cop? I grew up in the Bronx, they're all good cops, don't worry about it, everything is relative. Now how do you handle some of that? Sometimes they're known for asking some pretty sharp questions, how do you handle those?  Actually there was no need, I'm actually quite serious, they were really civil, you look very surprised, which kind of worries me, what do you think of these poor guys? Maybe you know how to handle them. Maybe the answer's actually made them happy, you never know. So some tips then, we've got some folks that are going to be on later that have never been on theCUBE, never done anything like theCUBE, any suggestions, any tips for them?  No, honestly just say what you think. The worst thing in the world is you edit what you think to be politically correct even if you don't believe it, because everybody'll know anyways, you might as well just go for it. What do you think about having right here at IBM Edge 2013 this independent analysis? It's pretty unusual as far as the conferences go, what do you think about that? I think it's terrific, look, if you stand there talking to yourself, you're your own best audience but you're also your only audience. If you want to find out what people really think, put it out there and take the heckling. I mean, the bottom line is, you don't live in a vacuum anymore in this world, you get feedback whether you want it or not, you might as well take it when it's offered. Fantastic, appreciate you coming on and we'll see you the next time you're on theCUBE. My pleasure.


Cutting this ribbon is going to start a new chapter in the year 325th. The ribbon cutting ceremony that happened today was a symbolic demonstration of us opening up our new battalion headquarters. There we go! We had spent more than 18 years on CAS and now to start operations here on AUAB. It was just a great event and we wanted to make sure that we properly celebrated the opening of our new battalion headquarters.


In this study, researchers found that marmoset vascular tissues release a novel catecholamine called 6-nitrodopamine. This catecholamine is a potent and selective antagonist of dopamine D2 like receptors, suggesting that it could play a role in regulating blood pressure and cardiovascular function. This article was authored by J. Britto Jr., at Lima, J.S. Santos Xavier, and others.


You probably already know that quadratic equations look like this, but we can also have quadratic inequalities. We use inequalities to show us a range of possible values, which actually have many real-life uses. For example, I might use them to work out that I need to film a race car between 10 and 15 seconds after the start of a race. And they're used throughout finance, such as working out what loan you can afford based on your expenditure. We solve quadratic inequalities in pretty much the same way we solve quadratic equations, but also making use of the graph to help us work out which part we want. So let's have a look at an example. Solve it like you normally would. So factorise quadratic formula or complete the square. This one factorises. Notice how I've changed it to become equals. Solve each bracket, so x equals 3 and x equals negative 2. Sketch what this quadratic looks like. This u-shaped crossing the x-axis at negative 2 and 3. It's just a rough sketch to help yourself in answering the question, so don't worry about it too much. Because we want where the quadratic is less than zero, we want this part of the graph, the part that is less than zero for y, but also has the quadratic in. This means the answer is x is greater than or equal to negative 2, but less than or equal to 3. Because we've shaded one joined region, the answer is one inequality. It's this inequality sign, because that was in the question. Here's another example. Start by solving it. Roughly sketch the quadratic. Now, we want where the quadratic is more than zero. So shade where the quadratic is more than zero. This time, because we have two separate regions shaded, this means we have two separate inequality answers. Where x is less than negative 4 and where x is greater than negative 2. Because the question was greater than inequality, that's what our answers are. There's no or equals to involved. Here's two for you to do. Pause the video, solve the inequalities and click play when you're ready. How did you get on? You just need to do a quick sketch of the quadratic and then work out the values from there. If you have any questions, comment below and I'll answer them for you. Like and share our videos with your friends. If you liked the video, give it a thumbs up and don't forget to subscribe. Comment below if you have any questions. Why not check out our Fuse school app as well. Until next time.


Hello everybody, E here. Welcome back to another Stephen King review. If you're feeling confused and wondering, didn't he already review these books? No, I have not. You're probably thinking of my Thursday Theorist series where I go back and connect all of Stephen King's books to the Dark Tower and the Stephen King universe all in one go. I've done all of his books so far, except for the Dark Tower books and a couple collections. I will be restarting that series to get to finish up those last few books as soon as I am done with this series catching up on all the reviews that I have not done because I haven't reviewed the majority of them. But today we are talking about Misery. This one is a classic. One of the best books he has ever written. It is about an author named Paul Sheldon who gets in a car accident in the snow and is saved by his number one fan, Annie Wilkes, who is a disgraced nurse turned recluse and everything goes downhill very very quickly once Paul realizes that he is not only being taken care of and nursed back to health but he is also the hostage to this woman. There are some iconic scenes in here that differ greatly from the book in the movie version with Kathy Bates and I can never remember the actor's name but Kathy Bates and the guy who plays Paul in that movie she uses a sledgehammer with a piece of wood to hobble him. Hobbling is just you know breaking or removing the legs so that people cannot walk. So Paul once he is healed he isn't going to run away of his own steam he's gonna need his wheelchair or whatever. Hopefully he won't try at all that's Annie's hope but in the book it's actually an axe which I find the sledgehammer to be far more disturbing than him having his feet chopped off. That's just me though. I would love to hear what you guys think which one is more disturbing down there in the doobly-doo. I know it's you know it's more possible that you know he could he could walk again with just the breaking but I don't know why that one disturbed me so much more than the scene in the book. Now oddly enough my favorite parts of this book are the parts where he's writing the final misery novel or another misery novel that Annie's making him write because in the last book he killed off the main character Misery Chastain. I really liked reading those sections as Paul was writing. I loved all the tension and dread when he's trying to escape. This book is phenomenal. It is one of his shortest books but it has the biggest punch for the page count I feel. The only one that I would say is better than this one that is shorter is Dolores Claiborne. Maybe revival to and Pet Cemetery. But this one and Dolores Claiborne about the same length while as revival in you know Pet Cemetery are just a bit bigger. It's definitely his best short book I feel. Something under I think it's only like 300 pages. It's something under 400. Yeah it's only 309 pages in hardcover and I know revival is like 400 and Pet Cemetery is like 400 also. So I would say right around 300 it's his best book for that. Absolutely iconic. Annie Wilkes is one of the greatest villains ever. She is up there with Nurse Ratchet from One Fluid with a Cuckoo's Nest. Her backstory is great. Her and Kathy Bates in the movie I don't know if she won an Oscar. I don't even know if she was up for an Oscar but she damn well should have been you know. It is a fantastic performance and it's funny because there's one that there's a video. There's a viral video that goes around where this lady comes in screaming about how she wants Paul Sheldon's books because she's his number one fan and so many people don't know they think it's just another Karen outing you know another Karen spotting. But it's one of the funnier viral videos because nobody ever lets on that I think one or two people in the video are laughing in the background but nobody ever really lets on that is it's all a it's all a play you know it's all and I think the the woman who did it was actually doing a stage play of misery playing Annie Wilkes. I don't know but I've heard so many rumors about it I just love that video. But that just speaks to the iconic nature of this book and I say iconic a lot when I talk about Stephen King because he has changed the landscape for literature and pop culture numerous numerous times when people talk about number one fan usually they bring up Annie Wilkes and that number one fan connotation went from being a something that might have been a term of endearment to something stalkery and you know insidious and something reviled or it is just a person that is not in their right mind. So I you know you never see Stephen King fans say you know I'm his number one fan unless they're they're joking but I have had people tell me I'm your number one fan but don't worry I'm not gonna you know chop your legs off keep you locked in a locked in a basement you know things like that that's why I call so much of Stephen King's work iconic because it is like I said it's changed the landscape of pop culture numerous times but have you read Misery I would love to hear from you down there in the doobly-doo whether or not you loved it you hated it you felt mad about it but if you felt any of those things please tell me in detail why you felt that way so that we can have a discussion but until next time I have Annie you've been you this has been another Stephen King review I'll talk to you guys later bye bye


Ok guys, good morning. How was last night? Did you go to the arcade party? Who went here? To the arcade party? You only talked it? I heard that it was quite crowded and people went to bed quite late. So thank you very much for coming to this talk. I will introduce myself first. I am Manuel Garcia from Argentina. I work at Aurora Fire. We are a development shop that helps other people. We build things for other people to deliver. This talk will be about specific tools to help developers to improve two things. One is the quality of the code and most importantly the education of how to learn why you do it. The agenda will be to talk about what is an interest as an introduction and why should we care about it. Some issues that many developers run into that this tool can help. Some rules on how we can categorize them. Then we go into a specific tool that is called sulking to learn a little bit about it. How to use it and extend it and also what is next with this tool. First of all, to set up the grounds. Many of you are developers. Many of you probably develop in other languages before Solidity. You have great tooling. Then you went into Solidity and probably spent a lot of time that could have been spent adding features, building, delivering. With tooling, debugging, I heard that some guys from Biddle created stack trades recently. They announced it. And also Truffle announced a debugger, a more advanced debugger. I remember back in DevCon 3 that the tech lead from Ogre said that he was going to pay, I don't know how much, to anybody who can build a debugger. But it took a couple of years. So Linter is targeted to analyze a static code and analyze all the structure by creating the text, applying a grammar and from that grammar being able to analyze many many many things. So this what it does is start them doing a white box testing as it is considered some practices. And a tool like Solidity will allow you specifically to go through all the structure of Solidity code, being able to analyze specific semantics of the language and run it through a battle of rules and see what warnings errors you can be avoiding. And all of this of course without having to go to compile deployed smart contracts which is much more time consuming. And with no delogs, no delogs.  And as a team you can share some decisions about what you care, what you don't care and if it is not included let's build it, let's extend it. This is more, you get code that is more readable, not only for you, for the team, but also given that 95% of the code is open source and out there, when we do open source well we tend to do things right. I have seen that many many times, people becoming great developers when they started working on open source. You get to have pre-code reviews given that many things just appear there before getting the PR to be reviewed. That of course makes the life cycle of delivery much much faster. And one of the very important things is that you might be many developers in the team but the code is like coming from one team, you don't care from who. The code is the same, following the same standards. That is about coding. Also you get to know very early and be able to identify problematic patterns instead of working a few weeks and then identifying many files and you know the rest. And most importantly thing here, at least I find more importantly because I've been using Linter since Java, back in the days. We don't go to the documentation too often. With a Linter that can give you a feedback on what you're doing wrong, you can get very easy to the documentation of what you're doing wrong. You learn and you don't have to run again into this problem. So by having this feedback you learn and you learn a lot. Some of the issues that at least I think that many developers run into they are at least, well I wanted to identify top five. When you don't have conventions you get to have a code that is quite different for each other for all the files, the developers, people get very angry.  Low liability and efficiency. This goes not much for the code style but also for some patterns that are not effective as an execution complexity that can be completely avoidable from the beginning.  I don't intentionally add that to the code but well if I had somebody watching there and if it is a robot that tells me I don't have to spend time from other co-workers. And the code reviews take too long because you have reviewers, each reviewer saying, no I like things to be done this way or come on this is an issue that is very well known or you are violating a best practice that has been identified too early. What rules this tool has so far? By the way this tool has like two years now? Around two years? Yeah. So we can categorize them in three. One are style guides, second are best practices that are this first tool the first is more oriented to the solidity, the second is like any programming language and the third are security. Some examples there is like, okay I mean styles with spaces, with presentation and many other rules. Best practice is sequential value complexity and use variables, functions and security most importantly some very well known and documented rules such as re-enterancy, not being clear when you call contracts that are not written by yourself. So yep. And here, okay we have some references. There are consensus with the guy a long time ago. So that guy is quite well documented and we were able to run those rules into this lender. And the second one is a solidity style guide by the language itself, the documentation. I wanted to show you some rules. So if you go to the documentation you can see a lot of rules that are already implemented. There are quite many and some references. This is great that if you have more references that are written in text documentation we can go and program them and include it in the lender. And when I say we is we, it's completely open source. This recommended, okay I would be getting back to this. So this is about soaking, a tool that was built more than two years ago by a guy who was migrating from Java to solidity and he found like a lack of these very basic tools. He got into a parser, a grammar parser by some solidity grammar that was built by Federico Bonn. I don't know really you two guys, no? Another guy from Argentina. Well, early discovery is priceless. It increases the willingness and happiness of doing code reviews given that the reasons that I explained and shared earlier. And this is the solution. You just go to GitHub solution so it's not that much important. How to use this is extremely simple, you just install it and you have to initiate the config file for that specific project. Then you can add it to your tooling to like, I don't know, packages and you can say okay, run linter inside the cycle of the continuous integration so you don't only run it locally but you also run in the CI. And from there this configuration file is quite open. Previously it was more opinionated but we had some feedback that it was like too noisy sometimes so some teams suggested to remove everything and this thing was open sampling. By default we remove all the warnings so you can go there and start setting up. The configurations are presets of rules. You can have the rules by default are like none. Then you have recommended rules that when I show you the rules there was a column with checks on which are the rules that are recommended and the other ones that you can add manually.  The first plugin is Pretier. And allows you to extend with some other rules. Okay, there you go. So basically three properties right now. I would in bold recommend it. When you start with these devices like what I'm doing I don't have any rules. Probably in the future we will change this. Plugins and rules you can customize if you don't agree with the presets you can customize to get different type of errors or different type of rules. You can add more rules. It's quite flexible. How can you extend this and some other information? There has a plugin reference that you can follow and implement your own plugins and contribute back. You can create rules. It's just a JavaScript file. I can show you later. And one important thing that the guys from Aragon we send them a yard. And the bread said okay it's very nice but we have many, many projects. So we would like to have one definition because we have one team of many, many projects. And we created a concept of shared configs which you create, well a file and you just publish to NPM. And there you go with some presets and in the future you can start your project and I would say okay I will use Aragon down preset or noses preset. It has integrations with many ID keys some of them are kind of a pain to do but it is evolving and well the core developer of this use beam because sometimes he keeps a shit about the other ID keys and it has been integrated by default in open sapling and soon with the new version of Trafford that allows plugins and that you will have like optional in default plugins it will be one of the first plugins to be installed by default we have been working with these guys for quite some months. So let's see if I can do some demo here. These are the contracts of a project that we worked with some time ago it's a decentralized exchange based on the Dutch auctions or the book. The file was all that I was looking for a project I don't know this from this procedure a long time ago so the code is completely not the code that we have right now. You install blah blah blah then you ok I have to delete it so I will jump this and you get an output like this but such as ESLinter you can format the output so I can run like in somewhere here there format table Thanks for the full size and you can see here contract by contract sometime of the lines where this is happening of course that if you can integrate it with an IDE you can just jump into that the rules that you are writing here from this rule you can go to the documentation learn about it you don't do it again and you cycle you cycle you cycle until at least you get to know this set of rules here are some examples that we shared in the presentation because we are not going to have time again these are JavaScript files are not very hard to implement and I wanted to share this with you we applied for an Ethereum Foundation grant given that this is made with a lot of love but we have to make this address and we will be adding these features one of the things is separated from the CLI so if we have a library we can embed it in things like remix the remix team approach to us to do this and we need to do that it's coming the traffic plugin also some refactoring and very important to have an auto fix however this is dangerous because if I auto fix and I don't know what I did wrong I am losing the opportunity to learn well improve the documentation a lot that is very important and some plugins like having GradSpec that would be extremely awesome to have meaningful output when you have a resource or when you interact with the contract and more things that are requested by 7 okay this will be all of that I am going to do half of it thanks


Welcome to Zandam the Netherlands. And this place has to have one of the quirkiest implementations of transit-oriented development that I have ever seen. Just look at this place. It is like a post-modern Disneyland. But believe it or not, below all of this is a giant train station and plenty of bike paths. So what we're going to do today is I'm going to show you around the town of Zandam the Netherlands. And then we're going to give it a human mobility score for each mode of transport including walking, cycling, bike share and public transit. This train station has just been finished in the year 2020 and it's almost brand new. From this train station you can get trains to Amsterdam every 10 minutes with a ride time of only 12 minutes and to the airport every 10 minutes with a ride time of just under 20 minutes. So there's lots of options from here to get to the big city. Taking a walk out from the station which was right back there you see that there is plenty of things to do behind us. That is a hotel up there with all the stacked houses and you'll see a movie theater place to get all the things to eat. And there's even a downstairs level which feels a lot like one of those American malls. And if you proceed further this canal takes you all the way to the Zand River which is the center point of the city. Wow what a great environment around the train station you might be thinking.  You can see now that we're down here um it's just really a giant parking lot but you got all the nice houses still going on up there. And come around to the back of the station you can see that this is not nearly as nice as the front of the station. But you see that the architectural style continues all the way in the background and this is cool they built this new bicycle bridge that spans across this road for you to get to the other side. Of course the Dutch train station would not be complete without an amazing bike parking facility. And here is the free one which is unsecured, unmonitored. Though even this one is very very nice on the inside and I imagine these ramps to be very fun to ride down. What we're going to do now is go rent a bike from this Ove Fietze parking which is the Dutch version of the bike rental and this is an automated system so we'll go through the process here. So now that I've got my public transport bike the Ove Fietze let's go for a ride around Zandam. I'll show you some windmills, some cool bridges and even the ferry on the way to Amsterdam. Let's go. What's cool about these blue dots is that it marks the way of the bicycle highway and you can follow these blue dots all the way to Amsterdam. Well look it's a pickup truck. What do you normally do with the highway underpass? Normally you would put a parking garage or something like that but look at what they've done here. They put a grocery store under the highway underpass. Now I'm not precisely sure how wide this bike path is but I do know that I am 1 meter 76 which is about 5'10 from my American audiences and I guess that makes a bike path like 4 meters. Now I'm riding my bike a bit north of the Zandam area up to the windmills. Oh look the drawbridge is up. This is always fun to watch and I love seeing this. Some beautiful windmills here and as you can see most of them are actually functional. We're only about a 20 minute bike ride from Zandam and there is a train station right across the water over there which places you about a 10 minute walk from this wonderful location. It's a working town. The houses are real. People do live in them and I'm so amused by how they put this whole village together. Apparently they've had to bring in houses from elsewhere, the materials and such and really made this a place of historical preservation and along with refurbishing these really interesting homes here they've also made a good use of the public space so that's a boat dock with a nice seating at the end of it and check out that view. I hope you enjoyed that tour of this quirky little town called Zandam in the Netherlands and now we're going to end off by giving it a human mobility score. So on the front of transit access we're going to give it a five out of five for its ease of accessibility to the train station and how easily it takes you into the major city of Amsterdam and beyond including the airport. On the front of cycling well it's a Dutch city so I'm going to have to give it a five out of five plus we are in the middle of a bike path right here so that's more than bonus points. Walking a four out of five because while this pedestrian mall that they've done is very nice we are basically on top of two major highways and a bridge spanning a canal so you can walk one way but the other way isn't so pleasant and for that a four out of five and finally a two out of five for bike share because if you're a local resident you can get one of these nice yellow bikes but if you're from abroad or anywhere else then you are really out of luck. I hope you enjoyed this tour of Zandam the Netherlands and hopefully this video has given you some ideas about how to implement human scale transportation in your city. See you next time. Guess what they make here chocolate chocolate so this whole place just smells like chocolate everywhere but also cool houses right?