Hello, I'm Jean Hartley, I'm Professor of Public Leadership in the Business School here at The Open University. Hello, my name is Engin Eisen, I'm a Professor of Citizenship in Politics and International Studies Department here at The Open University. We're here together because we're collaborating on a really interesting and exciting programme of work about citizenship and governance. And so we're exploring the changing relationships, the shifting relationships between citizens, between states but also between markets as well because all three elements are really important in a world in which different stakeholders are contesting what's important, what are priorities and who decides. In terms of citizenship and governance, of course, what brings the two together is just so significant in our time, in our age, is that there was a post-war settlement after the war where what it means to be a British citizen was practically settled on a bundle of civil, political and social rights. As part of civil rights, British citizens were promised privacy, a certain distance from the state, the ability to govern themselves, freedom of conscience and so on. In terms of political rights and democracy, elections, rule of law and in terms of social rights, there was also part of the bundle that there were certain public services such as NHS, BBC, if not a welfare state. Today, it seems all three are up in the air and being renegotiated. That makes today doing research on the relationship between how we govern ourselves citizens and the meaning of citizenship takes on an entirely different urgency. Yes, and to add to that, from the governance field, we're also noticing a shift away from the post-war settlement because the state is both too small to handle the big global challenges. We can think of climate change or we can think of migration from Africa. We can think of economic recession where actually an individual state cannot resolve the issues at hand, but it requires multiple stakeholders in the state sector, the private sector and in the community and voluntary sector. But at the same time, the state is too large for some of the smaller issues, which is about people feeling that they want to be in control of their own destiny, not be passive recipients of decisions from councils or from the NHS or whatever. So we're living in a world with a lot of debate, a lot of contest around decisions and the allocation of resources. So actually citizenship and governance is a really exciting topic to be involved in at the moment.


Hello, everybody, and welcome back here to the channel. I'm Euvo Reve, we're here on the new E-SDA course for round five of E-SDA. We're starting at the back of my E-SDA E36, next level racing, Mazda racing, E36 here. And we are going to be running full drift testing with this R5 and the R5 wheel. So we are gonna be running it with the R5, so make sure you guys follow me and also should be able to find the description box below. Let's get to it. So we're gonna go first do a quick drive through the course so we can see exactly what we are getting ourselves into with this track. So we have a really long run up, fourth, maybe fifth gear. We got a pretty quick initiation into a outer zone, tightening up into a inner clip, and then it looks like a nice big sweeper we're gonna probably try and stay out of that red. I'm not sure, to another outer zone, to a nice wall ride outer zone. Very, check this if you hit that wall, it looks like. From that outer zone, we're transitioning over to a quick outer zone to a inner clip, and then that inner clip probably stretch out to the finish. So definitely a very interesting course, and it's gonna be a very quick course, very high speed, and it's gonna have to make sure that we are on point, because your initiation will definitely tell the tale for the remainder of that course. So we're gonna try and find our way back to the start finish line, not sure where it is, but we're just going to rip it this way so you can find the start finish line because that's something we need to definitely, is bumpy over here. Oh it is all the way back this way, there's probably a cut through that section where we cut through the pits and come through so we don't have to drive all the way around the course because we would have to be driving all the way around the course in battles if we qualified in the battles because you can't respawn to pits. So first run out, we're gonna go full send, and we will take a look at the replay cameras of some of these runs to make sure, see where we're at on course. We do have a basic tune on, so we're gonna go full send. Yep, that initiation is quite quick and you can run really wide onto the grass too. And then that is a quick slow down section. Okay, so now that I kind of figured out where I need to be on course, we're gonna go and see if we can't get a full solid run in, that initiation sets you up for the whole course and going to that outer wall is definitely very, very tricky. You do not want to hit that the wrong way. Of course here, it seems to be the gear we could run though. Bring it in on the inner clip. Floated a little wide on the inner clip.  Okay, so we floated wide on that first inner clip which caused us to push out. So we need to make sure we get tight on that first inner clip. We need to maybe dial in some front grip but first two runs are just figuring out where we need to be. See, I don't want to be feathering the throttle through that section. I want to be kind of on throttle full bore. That wall is gonna come out and bite a lot of people and that threw me off for there. All right, so with that being said, we're gonna try and get this better in here. The angle initiation which pulls us tight in here. Probably not the right line we need to be on but kind of set us up for that. We definitely missed that zone, I can tell you that already. Kind of a full pull that initiation was probably where we want to be. So let's go take a look at that initiation real quick because I wanted to see if that is exactly kind of where we need to be at. Hard flick and I think, don't think we are really close to zone but we're not in it. But to kind of put us in there, we had to feather out a little bit and we did do a little dirt clip there. We need to draw a different perspective line through that. So we need to draw a different line through the inner clip. Maybe slow down a little bit more so that we're not throwing ourselves so far out back up. All right, see what we can do. That is a huge slow down zone but the rest of the course was not too bad. That was probably one of the more better, more better, more better runs, more better runs than we've had so far. But like I said, this is the first time on this track we are rocking the R5. So a little bit of adaptation for the smaller wheelbase but it does feel really good in this pro car. Full drift test is what we're doing right now. Yeah, I don't think they want us to be running on that inner zone right there. And that's just a hard angle up. But that wasn't too bad on that last section. It's definitely going to be a hard angle up in that section. So one more run and then we're gonna take a look at probably the replay if we do get a solid run here. Now what we wanted to do, too much feather of throttle, not enough commitment and that runs pretty much not gonna work. We need to be fully committed into it and we need to have full good commitment in our throttle in order to get a good score on the board for qualifying. I mean, if we throw a massive angle like that, that kind of sets us up for a really good line though. This course is just gonna be throwing some serious angle because those last two sections were actually quite good. Let's go take a look at that replay because yeah, it seems like we're just gonna be having to run some high angle stuff. Massive angle full lock deep in the zone which kind of set us up in a really good aspect for there. So yeah, we need to be throwing some high angle. We did get out into there and then this is a quick flick high angle but puts us kind of on the right line. So we need to throw way more angle than we were throwing. So we need to initiate harder, throw angle, kind of chuck it at the wind and hope it sticks. Definitely gonna need to get sure we have a lot of front grip for this. Caution to the wind on this one. Look for the grass drop but we managed to save the car. Deep in that zone, this could be another kind of caution to the wind. Oh man, that is insanely up on an angle. That is borderline unchasable with that transition going so hard and aggressive. That's almost a backwards entry. We gotta not do that. We gotta hit that threshold without rotating too much. We're all so out. We don't wanna angle up too much there. Okay, we can't angle up there. So we're getting the entry down. Now we gotta put all the pieces together for the rest of the course. I feel like we've had good sections through all but for first testing on this track and the first runs and shaking down the R5 in the pro car. Quite happy. Grass drop, saved the car though. To save the car like it was qualifying. So I think that's gonna do it here for this episode here. Out of sudden of course, first shakedown of the ESDA pro car for round five with the R5. So maybe this could be a good round. R5 for round five.  Definitely feeling very comfortable with the wheel. Just gotta get our tune dialed in and get our entry and everything squared away. And we should have plenty of time to practice before qualifying. So because like this, you guys wanna keep seeing more if you follow me on all social media. All of our sponsors, if you watch below that subscribe. And as always, I thank you guys for coming back and watching. I'm Evo Rabbit. I'll see you guys on the track.


Welcome to the Everton News Daily, I'll let you fact are still hopeful of completing a deal for Everton Winger Damari Gray before Friday's Saudi Arabia Pro League deadline. Gray had looked set to move to Saudi last week, Everton had looked to bring in alternative to Damari Gray but the Everton Wingers move didn't happen which surprised a lot of people. He then had his say over the weekend which he seems to be having a pop at manager Sean Diteswell. Today Everton's managed yet through a YouTube video that Everton's released has had his say back. I'm going to read it out off my phone his quote because it's quite telling. Damari made it clear he felt he was getting a move away from Everton and he told us a move which was done, which was interesting to hear from a player. He reminded him of the truth of the fact that no one moves, no one moves out of the club and that's not done without the say so, that's the truth of it. We look after these players and we look at different ways of looking after them. When it comes to a time when we let them go we will tell them and it goes on and on about all of that. He says he felt it was right to let the fans know exactly what was happening. You know how Damari gravely covers from this or how him and Sean Diteswell together moving forward from this. So maybe that's where altifax confidence in a deal being done. But the manager has kind of said he didn't want to sell a woby but he understood the logistics of the deal money wise and that's why Damari gravely has got to stay so we'll see what happens in the next few days. Everton have announced a new shining today and that is 18-year-old Oxford United goalkeeper Fraser Barnsley. He has signed a two-year deal with the football club until the summer of 2025. Amadw Omnana has denied that he was unsettled at Everton this summer. The Everton midfielder has been speaking while on international duty with Belgium. He said football was all about time and he went on and quoted the fact that he'd moved in the last two summer transfer windows, changed clubs and said he wanted to settle down and have Everton this summer and just concentrate on football. He's got a big task at Everton and he wants to concentrate on that. The reality is if someone would have come in probably with a big club he may well have wanted to move on but he has stayed and it's up to him now to take games by the scruff of the neck and prove he is a top player. Then if he really does want to be moving on to a new club there's no better way to do it than to perform at a high level every week for Everton football club then you will get the Champions League clubs coming calling. So Amadw Omnana big season ahead of him. Finally John Filippe Gabbaman who left Everton a few days ago could be about to join former Everton manager Rafa Benitez at Celtavigo. Gabbaman is a free transfer, Celtavigo are looking at him as one of the options to help Benitez strengthen his squad. That is it for the news daily. Give the video a thumbs up and subscribe if you haven't and if you want to become a toffy TV Premier member. The link is in the description and the QR code will be on the screen now. Thanks for watching. See you later.


I welcome to my session and hope you are having a great time in Detroit. I would like to dig an angle and I'll be talking to you about container on time. First introductions, I am a developer evangelism program manager at KitLab. Mainly my role is to find new ways in creating content and also helping my team create the right content built off leadership and get results from the first leadership. Now, I'm also a Google developer expert in cloud and a CNCF ambassador. I'm currently based in The Hague Netherlands and if you want to learn more about me you can visit my website at abuango.me. Now, so let's get started. What are containers? This session is meant for people who are new to containers. I would like to learn more about how containers work in the background so I'll be starting with the assumption that the person listening to this does know a lot about containers. Now, traditional deployment of applications, once you've built your software or your team have developed that awesome projects you've been working on, they can either deploy it by just installing it. Oh, create a VM, install a party or install nginx and ship the application to the right folder and it runs. Sometimes it works, sometimes it doesn't. And we always have this saying, oh, it works on my computers. But how do you ensure that something that works on your computer also works when it goes to production. Then came virtualization. Virtualization is where there is a layer and extra layer on top of the operating system, which is the hypervisor. And the function of it is to create isolated environments, virtual machines that contain operating system binary and everything necessary for your application to run. But this is like a virtual machine. It's completely isolated from the host operating system, and it has to come with everything that application is included operating system. Also, except that if certain configurations are made, the best environment virtual machines do not have access to the host and the host also does not have access to the content in the virtual machines except if some modifications are made to it. Then we have, and this isn't always the right solution to problems in the organization. That's when containers came up. Now containers in terms of Linux have been around for some time and there's been different ways of isolating different processes on the Linux machine so that it function without interrupting other processes or having access to resources of other processes. So now, but after so many years, containers has evolved to being able to deploy an application with all the dependencies it needs in a container while still having access to the host resources or the host resources, the host system is able to access the resources on the container. So this happens instead of in virtualization where you have a hypervisor or a software that manages the creation of virtual machines. In terms of containers, because containers are mainly a group of processes that are running on the host machine but isolated from other resources. There's what we call a runtime, container runtime that talks to the kernel, uses the kernel to create this isolation for your containers and all the resources that your container needs to function. The main difference between virtualization is the virtual machines are completely isolated from the host machine for virtualization while for containers. Your containers are just a group of processes running on the host machine while isolated from other group of processes that are running. Now, if we look basically how containers are created is a client talks for most of us are used to Docker desktop, Docker CLI, where you just see Docker run, Docker EXET, Docker and so on and so forth, Docker build. And the client communicates with your Docker client application or CLI communicates with the runtime. The runtime is the one that does all the building of the images, all the building of the containers and communicating with the operating system, the kernel to do what is required for the kernel to run. Now, when your container images are built, your client also communicates with the registry where images are stored and can be pulled from anytime they are required. Basically, an image is a specification of how your container should be built when it was to run. Now, but how did all this content actually start? It has started a long time ago when Linux administrators have been looking for ways to isolate processes from one another. There should be files that a certain process has access to, should be isolated. The process should not be able to access other files. The resources to use it should be isolated to it without having access to what other processes need. And this has evolved right from the days of free BSD to C groups, control groups being created at Google to limit resources that processes can use on the system. Up to the creation of namespaces at Red Hat in 2008 to IBM creating LXC. LXC was the initial kind of the OG Linux container initiative that was created that uses C groups namespaces to isolate what a group of processes can have access to. Then came Docker in 2013 and Docker made containers cool, it made containers to be more easier to use. You just need to download the binary, set it up, you have the Docker CLI client, you have Docker demonware in your system and it creates the containers. But one thing Docker did very well, which later became a disadvantage kind of is it made it very, very easy to use that when the use of container evolves to more complex use cases like container orchestration in the server environment doing deployment at scale, it was difficult to adapt Docker to those use cases. Yeah, it's easy to use as a developer to build things, but when to automate it and add it to more complex deployments like Kubernetes, there has to be a lot of overhead in trying to make Docker work the way those platforms are supposed to want to use Docker. So which is why there has been a rise in different implementations of containers aside from Docker. Now, let's look under the hood a bit of what a container actually does in the background. This container basically is just an isolation of processes, a group of processes that are running to execute or to run your application, you have your application, you have the dependencies that your application is to run. So those dependencies running to me that have been executed to run your application runs as processes on the host Linux environment. So it has an isolation for example, what files does he has access to. If it's, if you're, if within your container CD slash is executed, where should it present as the root file system of your operating system. The home that actually is, if someone within the container says, okay, CD and tile symbol which is home, where should it go to, should it go, it won't definitely go to the home of the host operating system of the root user of the host operating system, but a folder has been designated for that group of processes for your container to be seen as its home. Now, and all these happen with the use of features of Linux, which are namespaces, C groups, and CH root will be looking more into those. Now the first one is CH root. Now, when a process is running on your system, on your Linux machine, CH root can limit where it accesses on your file system. Let's say for example, in the slide image you're seeing here, we have our main root directory slash, and we have home, we have me, then within me we create, let's say we created a folder called test. And within that test folder, we now created other system folders like being, user, and var. Then we jail a particular process into the test directory. Now, jailing the process into that directory means anytime the process tries to access a root directory, it doesn't go to the parent root, it goes to its own new root, which is basically inside tests, not the main root. So this is one way to make sure processes or groups of processes are limited to a particular directory or section of the file system. They won't be able to have access to other parts of the file system to make any modification. Now, this is not like the most security, because definitely there are ways, given the right amount of skill or given the right amount of programming, processes can definitely jump out and access the host file system. Now, here is another representation of it. So we have our root directory at the top, then we have a home, and a folder called Joe inside our home directory. But we want to jail, let's say the user Joe or the process Joe to the Joe directory, you should not be able to access any other thing. Then we create a new root inside it, its own being user and other necessary folder like we have for the root directory. Now, so anytime Joe or the process Joe tries to access root or tries to say slash being or tries to say slash versus us slash whatever they are limited to everything inside the slash home slash Joe directory. Now, another feature of Linux is namespaces. Like I mentioned earlier, namespaces was created was added was a feature added to the kernel in version 2.6.24 in 2008. Now, what this does basically is to give your process its own system view of certain resources within the Linux environment within your system. Okay, for example, like the PID process ID, like the PID namespace, when your we already know that PID one is the system D or the init process that's running on your system. Now, what becomes the init one of your container. So your container can have its own PID namespaces whereby if there's a, if you want to check on PID one, it does a specified process that is running PID one. For network resources like devices, ports, etc, there can be an isolation of, okay, this is the ETH one or it is zero off your container and not necessarily tied to the main ETH zero or ETH one of the host of system. So basically namespaces provides an isolation for your container or your group of processes to tell them that, okay, these are all the resources you have access to. And these are all the resources within your own environment, like your own namespace that you can use. Now you have other namespaces like mount point, you have IPC, you have a host and domain name namespaces that containers can take advantage from the namespace feature of Linux. Now, then the next thing is C groups, which is for resource control. Now, we've said from the beginning your container is basically a group of processes that are executing towards a common goal, maybe running your specific application. Now, your container, the process within your container can be allocated, oh, you also share one gigabyte of memory and this number of CPU. Now the C groups ensures that those processes stay within the limits that is specified for them. If any of the processes uses more memory than allowed and they get killed, or M killed out of memory killed, or if they start using too much CPU than required, they start getting slowed down. So C groups allows you to specify resource limitation for the set of processes within your container. And the image used here from Julia Evans, she creates very awesome representation of common of terms of topics in technology, you can visit on Twitter to check out some of the awesome illustrations that she's that they have done. Let's revisit this image of a container, how a container runs, basically you have the clients, you have the runtime, and you have your registry. Now, but what happens under the hood in the runtime? Now, let's take this image for example, for that of Docker. Docker, one thing Docker did at some point was to look at, oh, there's a need to have a more representation within the community and one way they can do is to give back to the community. They decoupled their Docker binary into container runcy and contributed to the community through the open container initiative. I will talk about more about that later. But basically, the Docker binary was split into, you have the clients to which is the Docker that you execute. Then you have a runtime, a high level runtime that receives all the instructions from the client to handles image creation and management and so on, then passes the instructions to the low level runtime, which does the actual execution with the Linux and how to create the container. The low level runtime actually does the creation of the container processes. Now, container D is like one of the most common high level runtime which Docker uses and runcy is like the default, most other high level runtime run times are either deprecated or not really that usable. The container runcy is like default that is being used and run it under OCI, as it's like the main OCI runtime. Now, if you look at this illustration here, it shows where when you execute Docker or Docker combos, the instructions are sent to Docker D. And Docker D is like the container engine that's receiving instruction and passing it down to container D. Between container D, you have container D machine, which abstracts some of the low level interactions that needs to be done with the main runtime, which is OCI runtime, that's runcy. And runcy at the end of the day creates all the Linux processes that is required for your container to run. Now, as time went, the community decided, okay, let's have a standard. Different tools are coming up on creating our managing containers. Let's have a standard that is agreed on. Okay, this is what a container should be called. These are the things a container should do. This is how a container should be created and so on and so forth. Then came the open container initiative. Now, what should a runtime be? It should create, it should start, it should get the state, it should kill, it should delete a container. And how should it delete it? What are the different ways it should do? So the container, open container initiative, which has a lot of people within the community, a lot of companies within the community contributing to it, specifies what a container is and what a container runtime can do. And some of the awesome things that have come out from the open container initiatives are runcy, which is like the default runtime that does all low-level creation of containers. It's very hard for you to see someone using runcy themselves on your system. It is usually used along with a container manager like container D or Docker itself. And this ensures, having this standard ensures that containers work the same anyway, without your laptop on the server or cloud. So it works on my system. If it works on your system, it should work anywhere else. Now, then if we look at the CNCF landscape, there are a couple of container run times that have graduated. We have container D, we have the CRIO. CRIO is the Kubernetes interface that was created for runtime interface that was created for Kubernetes to ensure that it's able to communicate with different run times. Now we have a couple of others. I'm going to be looking at some of them and they create and handle containers differently. Now, the first one is container D. Basically, it manages the complete container life cycle of the host operating system, which includes like image creation, storage, supervision and execution and everything around networking that ensures that a container works. And it does this by talking to the low-level runtime, container runtime, which is runcy. Now, runcy basically is the low-level CLI tool that does all the spinning and rolling of the containers according to OCI specification. That is standard OCI specification for creating containers so that if a container is created with Docker or with Buildout with any runtime at all, it should work regardless at any big level. Now, runcy was initially developed by Docker like I mentioned earlier, but it was donated to OCI as like the first runtime spec compliant as the OCI created like a specification, runtime specification. And this is like the first one that is compliant with the entire specification. Now, then we have pre-IO. Now, container runtime interface. Now, I don't remember the meaning of the O, but yeah, pre-IO. Now, it's an implementation of the Kubernetes container runtime interface, so which enables any OCI compatible runtime to be able to work with Kubernetes. You can say, oh, I want to use container D or I want to use this or I want to use that in my Kubernetes cluster. I want to use Docker. So this container runtime interface allows you to be able to use previously Kubernetes was tied to Docker, but with the container runtime interface of Kubernetes, it allows you to be able to choose which runtime to use. Oh, you want to use runcy or you want to use gvisor in the background or you want to use something else in the background to run your containers, you can do that with pre-IO. Now, we also have podman, which is a container manager. But unlike container D or Docker, it also run pods, a feature that we all know for, that we all know Kubernetes for. It run pods and another thing that it does, it allows you to be able to run rootless containers, containers that run within the context of the currently locked in user and accept if it has limitations, by the way, where there are certain activities that your containers cannot do except when you specify privileged flag to allow them to then execute those commands. But if your use case doesn't require any privileged use cases, podman is like one of the features for you that is more secure because it doesn't need any root level access. Now we have builder, builder basically is for building containers. It doesn't run, it doesn't do any execution, it basically builds your container images. You can use podman with builder. I think podman actually uses builder in the background to build images. Now we have a scope view, which is for inspecting images and also publishing your images to a container registry. Now, looking at RunSea, we've talked before about RunSea, but basically the goal of RunSea is to make a standard for how containers run anywhere completely. And the primary features of RunSea is it supports a full Linux lame spaces. All Linux lame spaces RunSea supports with a PID or network command point, it supports all of them at the low level. And also support security features like SC Linux, App Ammo, and so on. And because the specification for RunSea is governed by the Open Container Initiative, which is a Linux foundation, there's guaranteed that it will still be maintained. Unlike other ones like RKT and so on, which were popular for some time and most of them have been deprecated, this has a lot of backing with it and it's going to be around for a long time. Now, like I mentioned earlier, it was released as part of Docker container platform, but was later spinned out. I think Docker contributed a lot to the container ecosystem. Now, we have other runtimes that do things a bit differently. Like we said, containers are not necessarily isolated completely from your host operating system. They are just a group of processes that are executing your program, but in an isolated environment. But for security concerns, some folks have shared the concern that, okay, still yet processes within containers can go beyond isolation and probably wreck some havoc or escape from the isolation. So that is where sandbox container runtimes comes in, like the GVISO or CARTA, and the way it does is they use virtualization to completely isolate your containers from the host. So largely the main reason behind this is to have improved security, especially for critical workloads where you have concerns around, oh, this should be secure, it should be complete, especially in regulated environments where security is very, very important. But unlike simply just using virtualization, these runtimes are lightweight and have minimal resource footprint. Okay, it's not like it just goes create a battery box machine and run your container and it's no. The implementation is much more lightweight because you need to maximize resources and also have improved performance. Now, with this, let's see if you use cases, the main use cases for containers. The first one is build systems, of course. Okay, as a developer, you want to build your applications, you want to package your applications around them. And then to run your applications to assist the containers, but most likely push it to these containers or use Podman to run them as pods. A pod is a group of containers that are running to run a particular application. Now, and what are the main things you would require build systems for?  But when it comes to container orchestration, the images will have already been built and they've already been distributed into your registry. So the container orchestrator basically just pulls and uses, in the case of Kubernetes, cubelets, does all that, pull the image and use the image. Now, let's see an example of the flow of a build system.  When you do Docker pull, it pulls those images to your system. Now, if you, when you're using Docker, your Docker CLI with the Docker daemon. Now, the Docker daemon does takes your request from CLI and handles it with the container the runtime and container the runtime creates the containers with the help of currency, which talks to the Linux kernel. But Podman does things differently. Instead of having a daemon that does all the execution as a root, as a root user, at root level, does all the execution creating the containers, etc. Podman can work rootless without privileged access. But instead of using a daemon, it creates all the containers as child processes of Podman itself. So that means your containers can run in the context of the currently logged in user instead of root. There are limitations to that. You can explore them more depending on your use case. But this makes Podman to be more secure and more accessible to use. Now, also, Podman can be a drop in replacement for Docker. You can install your Podman and even create an alias to any time you execute Docker, it should call the Podman executable in your system. Now, Podman is part of a suite of tools, including Builder, including Scorpio and Konmon. You can use all of them together. While Docker provides everything in the daemon, the daemon checks your container for the entire live circle. Okay, it's running, it reports back the status and everything. Podman works with RunC to create the containers. But it uses Konmon to monitor the containers and handle any communication between the container to not tell you, okay, this container is dead and so on. Now, then Podman uses Builder to build and distribute images and also Scorpio too for inspecting those images. So, Podman, Konmon, Builder and Scorpio are a suite that you can use together for your containers. Now, for container registration, let's say you're using Kubernetes, for example, and with your Qubelet, you can decide, oh, I want to use Qubelet, I want to configure my Qubelet cluster to use container D, or to use Creo, or to use Kata, or to use GViso. Because Kubernetes has the container runtime interface, so any OCI compliant runtime can be blocked to the CRI for Kubernetes to use in running your containers. And it does that with RunC, just the way Docker uses Docker D to work with container D to run your OCI compliant image. Now, basically, the runtime you use depends on what exactly your use case is. If you are a developer, Docker should be fine for you, as long as you are within the limits of usage that Docker specifies. The using Docker as a company is becoming more difficult because there are restrictions. I would advise visiting Docker's website to learn if you are able to use Docker. But if you are unable to use or you want to stick to the spirit of the community, you can choose Podman. You can even use Podman to run your pods, not just containers, unlike Docker where you cannot run a pod. Now, also Podman can be a drop-in replacement for Docker, basically creating an alias for it, all that you need to Podman create, Podman, a Docker pool, Docker disk, Docker, Podman can do that. Now, but Podman is part of the streets. It uses Konmon in the background to handle the monitoring of your containers and also communication. Docker does everything, but because Podman is demo-less, doesn't use a demo, it depends on a couple of other tools to do all the activities needs for the entire lifecycle of your container. Now, Podman also uses Builder in the program to build your images and scope you for inspecting your images. So you need to use the full switch to be able to get the full benefit of the entire lifecycle. But if you work in a regulated environment, or because of this some regulation or just your need, you need a more secure runtime to run your images in a completely isolated environment.  Now, when you are using, also know that if you are using Kubernetes, you can specify what, because Kubernetes, previously Kubernetes basically was tightly coupled to Docker. After the community, the coupled Docker, which will give, which led to the uproar, one time, ah, Kubernetes is removing Docker in ETC. No, Kubernetes was not just removing Docker, but it was making it possible for different OCI compliant runtimes to be able to work with Kubernetes, including Docker. So, if you want to use a container with Cubelet, fine, you can set it in Kubernetes, you can check the Kubernetes documentation for how to configure different runtime for your Kubernetes cluster. Now, that's all from this session. Thank you very much for joining. If you have any questions or you want to engage with me, I will be waiting to answer some of your questions in the after this. But you can also reach me at on Twitter at 30247. My website is abuango.me. Also, if you would like to give feedback about this session, you can scan this QR code or follow any other instructions given after this session. Thank you very much for joining me and hope to engage with you soon.


So the question you should be asking now is where does the action potential come from? We're talking about these contractile cells which receive an action potential message directly through the gap junctions in their intercalated discs, causes them to fire. We've got this awesome mechanism for how contractile muscle cells contract with this magical action potential that appeared out of nowhere. We know that it didn't come from the nervous system as heart muscle can beat without nervous input. So it's not like the nervous system is dumping neurotransmitter on contractile cells and telling them to go. So who's doing the job? That would be your friendly auto-rhythmic cells. So auto-rhythmic cells are so cool. Here's the deal. They do not have a resting potential. Contractile cells did not have threshold. Auto-rhythmic cells have no resting potential. However, they begin the cycle at about negative 60 millivolts. And here's the thing. They have special channels. They do have threshold. Negative 40 is threshold. They have special channels. Oops, that's not what I meant to do. I meant to go like that. Auto-rhythmic cells have special channels called IF channels. And the F actually comes from the word funny. These are funny channels. The researchers thought they were super funny because they're leaky. They're leaky for sodium and potassium. Tell me, true dog pounds, who do you think they're more leaky for? Look what's happening to my membrane potential as these funny channels are doing their thing. I'm slowly depolarizing, which means that we're probably a little more leaky to sodium than to potassium. And this is totally true. Now, these funny channels create what's called the pacemaker potential. Pacemaker potential. It's not a resting potential because it doesn't stay at the same level. It's a pacemaker potential because can you imagine if... Actually, I'm not going to tell you how to imagine like making this fire faster or slower. I'll let you think about that. Eventually, the leaky channels allow enough sodium into the cell that we reach threshold. And once we reach threshold, funny channels close. And guess what kind of channels open? Calcium channels open and calcium rushes in. Calcium rushes in until we reach about 20 millivolts. Calcium comes in, we become more positive. This makes perfect sense. And then, okay, so let's make a note of that. Calcium comes in when these calcium channels open. And then, who's going to open next? Look what's going to happen. We're going to repolarize. How about opening up some potassium channels? Potassium goes out. We repolarize the cell. This is the pattern that is maintained by our friend, the auto-rhythmic cells. As soon as we reach threshold, we generate an action potential. And then, we head back down to where you start at negative 60, it isn't the resting membrane potential. It's just the starting point. And then, my funny channels are leaky. So, we can't hang out at a certain place. Eventually, we reach threshold because of those leaky channels and we fire an action potential. Now, this, my friends, this right here, we got to have a better color than that. Boy. Okay, I'll just show you how awful this color is. It's terrible. That, what was my point? We say, oh, this, we've got a positive 20 membrane potential inside our cytoplasm now. And that cytoplasm, that positive 20 passes through the gap junction and activates the voltage-gated sodium channels in the contractile cells. Only 1% of all of your heart muscle cells are auto-rhythmic cells. However, because of this phenomenon right here, they generate all the action potentials to keep your heart going. There's some anatomy here. We actually need to take a look at how auto-rhythmic cells are distributed through the heart itself so that we can see if they're firing at a certain level, how does the message get all the way through the entire heart and initiate a contraction of your heart, a beat? How do the auto-rhythmic cells coordinate heart beats? Well, we have to look at how they're anatomically arranged in the heart, and that's through the electrical conduction system.


Hello. This unit discusses the basic morphological processes inflection and word formation. It looks at the main inflectional categories and lists the central differences between inflection and word formation. In the virtual session, where you will find one central e-lecture, we will look at inflection and word formation in detail. This includes the central criteria that distinguish inflection from word formation as well as a discussion of the central inflectional categories. If you don't know where to start, use the question sheet with its hyperlinks as default guidance. The mastery worksheet is a drag and drop task where you have to move the component parts of words into their word formation process container. Almost again, and I'm sure you'll like it. One of the practical provides you with data, dozens of words ready for analysis and to be associated with the morphological processes involved. I'm sure that you will know a lot more about inflection and word formation after this unit.


And in a debt-based monetary system, when defaults happen, the demand for those dollars goes down at the level of the loan that's defaulted on, but supply gets really crunched more than just that level of demand. So even though demand falls, the supply of money contracts even more. And so you get this credit contraction, which means dollars are even harder to come by. So now you've got, it's like musical chairs. Not only did the music stop, but a couple of the chairs are being taken away at the same time too. So you've got, let's just use an example. You've got a hundred people walking around 30 chairs. When the music stops, it's a hundred people going for 30 chairs, but then imagine 10 chairs disappear as well. So now you've got a hundred people going towards 20 chairs. It's kind of the same dynamic. So as the price of oil comes down, it's indicative of demand falling. It's also indicative of these companies and these oil producers or the whole industry comes under pressure. It's demand destruction, it's supply destruction from a dollar perspective, and it just becomes extremely deflationary. So that actually helps my theory of the dollar getting stronger. It doesn't necessarily help my theory of US asset prices rising. That's not always gonna happen every day, but it certainly helps my theory that the supply of dollars will be constricted and it'll be harder to get ahold of them. Do you think the US is gonna amend any NAFTA agreements it had before? I think it's possible. I think it's possible.  And he's always gonna try to renegotiate things in his favor. And I can, in the last two or three months, Canada has cut rates three times, Mexico's cut a couple of times, they just cut rates again today. Their currencies have fallen since the NAFTA deal was negotiated. There's actually a clause, I don't have it right in front of me, so I don't have the language exactly, but I know that there is a clause in the recent NAFTA agreement that says if currency manipulation takes place, this agreement can be null and void or can be renegotiated. So I can see six months from now, nine months from now, Trump's taking a look at this and he's saying, well, hold on a second, your currencies are reached down 20%, you're manipulating your currency. And with Mexico and Canada gonna say, we're not manipulating our currency, our economies are in trouble. This is the markets taking our currencies lower. And Trump's gonna say, I don't care. Because he doesn't care. He just wants his pound of flesh. So I think that the dollar will be used as a weapon over the next couple of years. It's already been used as a weapon for several years, but I think it will become increasingly so. I see one upside though for Canada. So at least for the service work, knowledge base and Silicon Valley has been doing this for a while, but I think this even propagates a little bit more. The amount of developers and workforce they can get for the premium of the dollar in Canada is just, it's a win-win for the American companies. Not only that, I'll go another one for you. As companies, one of the out, when I think one of the impacts going forward of COVID, once COVID is behind us, if it ever is, right? But once it's behind us, I'm not sure that people are gonna go back to work in the way that they were before COVID. In other words, one thing that I think has been shown is that some of these service businesses, people can do their jobs from home or do them remotely. And I still think it's advantageous to have an office and I still think offices will still exist, but maybe they don't have all the square footage that they used to, right? Maybe they do offer, people have the ability to work from home in order for these employers to save some money on rental space or whatever it is. And so if they can hire Canadians who can do it just as well as an American counterpart and they can pay them in Canadian dollars at a much better telecommuting from Toronto is just as easy as telecommuting from around the block. The distance doesn't really matter. So I do agree with you on that part. Where do you see us then from a year from now? Like what I kind of want to at least lay out for people, what can like regular entrepreneurs or people who are in business, I'm not talking about billion dollar, but like what can they do in this circumstance? Are you talking about Canadians or just people in general? In general, let's say, like most people are global business anyways, like my business is online, I got customers everywhere. Yeah. Well, the first thing I would do is I would hold any savings or reserves in dollars. US, yeah, yeah, yeah. And then pay your expenses in Canadian dollars and or Australian dollars or euros or whatever it is, but I would hold my savings in dollars. Now I do anyway, it's just kind of natural for Americans to do it, but I really think that that would be one, that'd be the first step I would say, hold as little local currency as you need to. The other thing I would say is, if you have a job, keep it. This isn't, I don't think this is the time to be cavalier with putting my job and my value's really high, so I'm gonna go get another one somewhere else. Maybe that's the case for you, but I think times are gonna be tough over the next couple of years. So I think if you have a source of income, you should respect that source of income and try to keep that source of income. Now it doesn't mean that it's not an opportunity what's that saying that chaos is a ladder, right? So with this great times of disruption, if you see an opportunity, I'm not saying don't try to get it, I'm just saying be careful and don't just throw caution to the wind, make sure, but once you've made sure, if you see an opportunity, be ready to take it, but don't just, I don't think it's time to just have a hunch and buy a bunch type of thing. I think you really need to think about what your moves are. Also, Brent, I just wanna thank you so much for coming on the show and sharing all your knowledge. If people wanna get ahold of you and know more about you, what's the best resource? You know, you can email me, it's Brent at SantiagoCapital.com. My website is SantiagoCapital.com. It's just a landing page, but it has my contact information on there. I'm also pretty active on Twitter, it's SantiagoAUfund, so you can find me there. And I do a number of presentations and podcasts and funnily enough, which I laugh at this, but if you type dollar milkshake theory into Google, you will actually get a number of links that come up. So if you're interested in hearing more about that, check that out. Brent, thank you. Absolutely.


Thanks, Jen. It's a pleasure to be here. Let me first of all start off by expressing my appreciation to our two Agency colleagues NSF USDA for joining us to put this This workshop together. We had a very selfish reason why we wanted this workshop, which is what I'm going to talk about We're related to a round of strategic planning We're in the midst of but it was really great to be able to reach out to two other federal agencies who have overlapping interests in this area and having such a productive collaboration to put this on certainly appreciate people who organize this and Appreciate all of you for coming and now staying until through through Friday afternoon before departing I Unfortunately my schedule a little crazy this week and so I wasn't able to get here yesterday I watched a little bit on our video feed and I I've been hearing from various people including some of the staff that sounds like Extremely robust discussion and great presentation. So I appreciate all of you who have participated what I wanted to do is to Looking out at the audience and looking at the roster people are here There are a number of you who have not been involved in any of the activities so far to my knowledge Related to NHGRI's current round of strategic planning And so I was asked to come give a brief overview about this But also we wanted then I'll turn this over to Carolyn Hutter who will help along with I think Jen and others to help sort of Stimulate a discussion to get your feedback while we have a captive audience because this is an area We are interested in and knowing what your thoughts are as it integrates with a very important part of NHGRI's future Now one thing to appreciate about NHGRI maybe the whole field of genomics But certainly NHGRI is that we very much embrace the notion of strategic planning We'd probably do it in a be honest with you in a more robust fashion than any of the other 26 other institutes and centers at NIH. I think the history of that relates to our origins Where we were created as a part of NIH to lead The NIH's effort in the human genome project and we sort of just grew up As part of an international collaboration of the human genome project Which was guided by a series of strategic plans three of those are shown here whereby there was this very Comfortable feeling of engaging the community getting their input on how do you actually do what you're trying to achieve? But recognizing that within a year or two you're willing to rip that up and come up with a new approach as Technologies advance and new opportunities arise and we have just stuck to that kind of a style playbook to help frame Our scientific agenda when the genome project ended literally the day the genome project ended We published this strategic plan in 2003 which really guided us for the rest of that decade and then in 2011 We published our most recent strategic plan One that went beyond some of the fundamentals we had described at the end of the human genome project And up and through 2010 but in particular Expanded our research portfolio that included reaching out into clinical research and thinking about how to implement genomic medicine And so this 2011 strategic plan sort of is organized around five major Progressive research domains that start from the far left Understanding fundamentals of structure and function of genomes in the middle more translational work to use genomics to understand human disease Of course an important priority at the National Institutes of Health and then in the far and the right word domains Thinking about how you can use genomics to advance medicine eventually improve the effectiveness of health care And this is sort of the centerpiece figure from our 2011 strategic plan I can tell you we have almost every aspect of the Institute Organized around this strategic plan and it has served us well actually serves us extremely well even up to the present time But in thinking about it, it was you know Basically came out a strategic plan and that took place mostly in 2009 2010 was really Drafted into and mostly written in 2010 and then was published in 2011 And we just felt as we thought about the next decade that it was probably important Not to stay too fixed to a strategic plan that at that point would be 10 years old And we just thought it was important for us to start the new decade with a new strategic plan And so as a result of that and having done this multiple times We know we need a two-plus years to accomplish this if we're going to do it Well and engage and and recognize and we were going to have to engage even more stakeholders than ever Because our community has just grown and grown and grown especially as we've moved from very basic genomics into more Translational and clinical applications of genomics. So we really plan for this going back to 2017 And then in February 2018 we formally kicked off this new Rhonda strategic planning knowing it would take us two years Sometime in 2020 we would publish it. We looked across 2020 Send one won't be a nice time to publish a new strategic plan and we like odometer moments And so we happen to pick October of 2020 because conveniently that'll be the 30th anniversary of the launch of the human genome project Just seemed like a good time to publish it. We're gonna publish this in October It means we really have to submit the manuscript sometime over the summer We need to have a good draft for feedback to get lots of feedback from people by the spring And so basically we've had this interval of time to try to think about all those different ways to get the input We want to write a strategic plan and thinking about what we're gonna be the elements we would use We just reached into the toolkit. We've used in previous Rhonda strategic planning But also grab some newer approaches and those are just listed here We've now had I think this engagement this afternoon probably is getting near number 40 If you're gonna add up all the ways We've been gone to meetings or had workshops or had town halls or had special sessions or had webinars Etc. Etc. I think our number is approaching 40 and this is just emblematic of the kind of things We've been doing both here in Bethesda Actually across the country and actually we've even gone abroad and done at least one or a couple of these kinds of things as well And so all these things are going on we are past the halfway mark We're probably about there in the process you can see we are certainly getting Past the point where we're just hearing open-ended feedback and we're be we have certainly are now Very much into synthesize and what we're hearing. I think some of the things you're gonna hear We're gonna put up in front of you relate to some of the early synthesis as you can see We hope as we hone in on the spring of 2020 when we want to have a draft Paper available for comment But before I turn this over to Caroline, there are two other nuances. I think I've really I in many ways shaped Many aspects I guarantee you these nuances will shape the crafting of the actual strategic plan because The world is a different place now from our perspective with respect in genomics Then it was previously in a ways that I'll describe and so there's just two nuances I want to introduce you to that I think are important for you to know the first nuance which if you're not Geeky familiar with NIH You may not quite appreciate but it is important for me to remind you about this is That the NIH has 27 institutes and centers and they are very different in size is the thing to know So here's NHGRI and if proportional to the diameter of that circle That is the size of our budget relative to the other 26 And you could quickly appreciate that while we all believe that genomics is incredibly important and while genomics has this massive Intellectual footprint the National Human Genome Research Institute is a small Institute at NIH Relative to the other most others in fact we account for about 1.5 percent of the NIH budget So keep that in mind now once upon a time that was probably perfectly fine when genomics was young And we were synonymous with genomics, but that's the other nuance. I want to introduce you to is There has been a remarkable I think successful dissemination of genomics across all of NIH obviously across all of biology and all the life sciences But if we're just honing in on the National Institute to Health Genomics has been widely widely widely disseminated across the NIH We think this is successful. We think this is what we should be doing is getting others to be doing genomics We should be enabling it, but it really does put us in a very different place now than we've been in the past And let me give you real data so you can appreciate the scale at which the world has changed around us at NIH So if you actually just search NIH databases for all the money We've given out of the money we spend on campus on our intramural program And you look at keywords like human genome and you simply ask the question What is the percent of NIH awarded funds that carry a keyword like human genomic that comes from our Institute? And look at that over different periods of time I can tell you that during the human genome project was a very easy number to keep track of because it was nearly 100% was over 95% and even when the genome project ended and we published our 2003 strategic plan it was still an easy number to keep track of NHGRI was largely synonymous with genomics research at NIH But starting 16 years ago the world began to change around us because we were successful at getting other Institutes to do genomics in very productive ways so that by 2011 when our strategic plan came out We'd actually dipped below 50% although still we were with our one and a half percent of the NIH budget We were still accounting for about 50% of genomics research But that's just not the case anymore. In fact by the time our 2020 strategic plan comes out It is RS right now. We're at about 15 percent Accounting for 15 percent of genomics research We think by the time our plan comes out that number is going to be about 10% So NHGRI once upon a time synonymous with genomics at NIH Almost a hundred percent of county for genomics research is now down to only about a tenth of genomics research at NIH that trend has been remarkably Important we think it's the right trend But at the same time it changes our place in the universe as the way we think of it And in fact before we actually even embarked on our new round of strategic planning Recognizing that things were changing around us that we felt it was really important to sort of re-identify ourselves What is our role in NIH and biomedicine and so forth and we actually came up with the new mantra and probably you've seen some of This on slides and so forth, but our strategic plan in 2020 is very much going to be a reflection of our view of what it is like to be at the forefront of genomics We are not all of genomics We're not even 20% of at NIH only about 10% of genomics But we are the forefront of genomics and what we need to hear and what we're constantly asking is when you're at the Forefront of genomics, what does that mean because that's what we should be doing with the 10% of NIH money going to genomics research So in summary this strategic plan that you can look for in October of 2020 is going to be we think the driving force for much of Genomics at NIH and around the world. We hope it'll provide clear Yes, 2020 vision for using genomics to advance human health It's going to obviously guide our scientific priorities that will shape our research portfolio It will also foster partnerships that are much wider and further than we've ever had before because our Communities have gotten bigger especially as we've begun to touch health care and Make genomic medicine a reality such that now patients are part of our stakeholder group not to mention policy groups and other general public communities And of course what's going to be most important about the strategic plan is it's going to really help us define What does it mean to be at the forefront of genomics? So lots of ways to engage with us obviously websites and through email and through social media and so forth But that's the overview. I wanted to provide you and with that in mind I'm going to turn this over to Carolyn Hutter who I think is going to now drill down from this very high level that I Describe to what we would like to hear from you in the next I don't know 40 minutes or 30 minutes


When I'm attacking up around their hip area, double leg, it's a little bit tougher for them to move their hips. Right? So the money just trying to low single here, I can take my feet back pretty quick. Right? But when she's attacking higher up on my body, it's tougher. Plus, when I take stuff away, see what my chest starts doing, it starts dropping. Right? So low level attacks, in my opinion, I gotta be a little bit more quick and a little bit more tricky with my timing. To really mess up her timing, not just from a circle in, maybe in her step motion, but a level change. Cause that's gonna get, if she's thinking about this, she's not thinking about that. So I'm gonna give you a couple, that's what you're gonna make your own recipe. So we got a couple skills that we already do as a club, right? Head pale. Outside hand to the ear, inside hand to the neck. Okay? And I'm just pushing away. She's focused on, my head's getting pushed away. I'm having to circle out of this. She's not thinking about where I'm going with the legs. Right? Or I might head's hair. Now we're starting to mix in some of that. Mid-level to low level. Mid-level fakes to where I want that foot. Take touch, level changes about J.O. And watch it. Jordan Oliver, teach this stuff. Man, he's one of the best. He said, obviously, John spent very long on good at teaching this. But at J.O., man, this is his wheelhouse. Level changes. So just stand. So I got level changes in fakes. I got head hair. I got fake touches. And then snap them back. Start scrambling their brain. And they're simple. You can be on the neck. Or just circle forever. Just looking for a release. Yeah.


Good morning, John. It's Friday. I'm sitting here in my usual spot, but with an unusual camera this is a VidCon 2010 flip camera. There were like 10 or 20 of these made. I actually did the design on the front of the camera. Thank you very much to Barry Carr who got this flip cam at VidCon 2010 and gave it to me as a present in celebration of 10 years of VidCon. It's like taking pictures of the Polaroid camera. It really feels like of another era for example. I love that. John, among the many things that of course happened at VidCon, the most important, the thing everybody wants to see is yes, I crushed the gush. A while back I uploaded a video on Vlogbrothers that was meant for Hank's channel. It was like four minutes and two seconds long. So I had to get punished and the punishment I settled on because of a weird thing that I have with gushers is that I would drink the gush juice. Turns out there's not a lot of juice per gusher. So I needed help and I got it in the form of these nice people who squeezed gushers into cups for most of the live episode of Dear Hank and John that we did on the stage at VidCon. And then So right there, right that moment, something interesting happened inside of my mouth. I knew that it was gonna be very sweet, but I didn't know that it was gonna be extremely sour. Like it's both, but it it's very sour. The first sensation is kind of a weight because it's it's kind of heavy and it doesn't like move around like water does. So it's sort of like slapped into my tongue. The second sensation was my salivary glands responding to the sourness of it and immediately releasing the maximum amount of saliva that they could. You gotta swallow it. It does not count if you don't swallow it. Just get it down. It was like jacuzzi jets of saliva. It was helpful though because it would have been very difficult to swallow the gush because it's so thick without all that added liquid. What I was actually swallowing was like spit gush. And then I went back, I don't know because I was on stage and my people had worked really hard to squeeze all this gush out of gushers for a second of helping. Questionable. Oh God! Oh God! Yeah, and then like a piece fell off the top of the gush cup into my glasses, which made me panic a little bit. So I knew that drinking the gush was gonna be bad. But I did not realize that having drunk the gush was going to be worse. Partially because my stomach was just very upset. Extremely acidic. I would love to know the pH of gush juice. The crash came quickly and lasted for the rest of the day. And of course to my crew of lovely gush milkers, you're the best. Thank you for your support. Additional things that are happening. One, John and I are going on a very short tour in Madison, Wisconsin in Minneapolis, Minnesota. We're gonna do live podcasts. Me and Catherine are gonna do one. John and is gonna do Anthropocene reviewed and we're gonna do a live Dear Hank and John. We're calling it a minute tour because it's a mini tour and also because Steve the Minotaur will be giving a short lecture. There's more expensive tickets for people who want to meet us afterward and all the money we make is gonna go to support our community's work improving maternal health in Sierra Leone. Also SciShow just released its first documentary film. It's discussing whether Apollo was actually a good idea in celebration of Apollo's 50th anniversary. And to celebrate that we've got a mission patch and we're also doing a new pin every month celebrating a different space mission. We're starting off celebrating Apollo. There's two different colors. There's standard and go in the dark. They're the same price. That's all the things. Can't wait to see people next month in Minneapolis and Madison. John, I'll see you on Tuesday. There's gusher on my glasses.  I guess. These are the milk gushers. Oh, that's so horrifying.


You guys can probably hear the thunder going on outside. There is a severe Thunderstorm going on outside right now, and I don't have any network here at the office. I drove over here I kind of expected not to have internet because of the severe storm It's been going on for a few hours now torrential downpours local flooding So I'm just gonna do one of these quick phone vlogs today and since I can't get on the internet I'm not even gonna check like show notes or anything anything I had planned What I'm gonna do speak off the cuff a little bit about life tips every now and then I do one of these videos where I try to give you guys Life tips life advice and you guys seem to enjoy when I do these kinds of off-topic videos every now and then so today I wanted to talk to you about a method of living and that method is be do have and Not have do be what I'm talking about is be do have be what do you want to be? Right, what is your goal? Who do you want to become in life? That is the be and then the do part is what you have to do To become what you want to be right and then the have part is ultimately the goal What is it you want to achieve? What do you want to acquire? Right many people do this and completely the reverse direction many people do things in a have do be fashion Where they try to have the things that for example Let's say you want to be a successful business man I see this all the time with these people that say they want to become successful at business and they Go and buy an expensive car. They go buy that Lamborghini or whatever And you know because that's what a successful business man has they have to look the part right? They have to dress nice. They have to have the expensive car They have to have the good-looking girl Right because that's the things that a successful business man would have and they figure if they have these things Then they will be a successful business man, but you can't do things in reverse order Just having that stuff doesn't mean all of a sudden you can then do what a successful business man does And it doesn't mean that you can be a successful business man because you've got it all twisted But you see this all the time these people that try to do things in reverse order They'll go into debt. They'll go buy expensive clothes expensive car And they don't get anywhere because they think they can just skip ahead In line as far as the progression of things you see this all the time with musicians as a former musician I said well, I am a musician, but somebody who went to school For music and I've seen a lot of professional musicians I've seen people imagine that they were rock stars Like they were famous rock stars and everybody knew them everybody loved them You see this all the time even in traffic You'll look at the car next to you and you'll see somebody singing along with the radio as loud as they can With this rock tune on this radio and in their head You know they imagine they're on stage in front of thousands of people and everybody loves them people are are throwing You know hotel keys and babies at them because they're they're so great Right and again because they're trying to play the part of a rock star rather than actually doing the work to actually be A rock star and then doing the things a rock star does which is making records going on to or things like that Right and then ultimately you will have what a rock star has which of course is the thing and fortune And this is how you have to do in life be do have not have do be so figure out what you want to be first If you want to be a successful businessman or successful musician or you know, do you want to be a good husband? A good father a good christian a good muslim and whatever it is that ultimately is your goal Then focus on being that thing and then ultimately when you start being that thing fundamentally I am that thing naturally you will do the things that that kind of person does And then ultimately you will have the things that that person should have so just don't get things twisted in life always start By be not have right go in the right order be do have not have do be all right guys Peace