Hi, welcome to my talk navigating the shift to remote developer environments like a year of insights and challenges My name is Andre Marcello Tanner. I'm a staff DevOps engineer at Ada support a Toronto Canada AI company You can find me on the hang-up slack or the CNCF slack and I also previously gave a talk at KubeCon Amsterdam about how we do ARCO CD and get ups and disaster recovery. So please check that out Now this talk is a continuation from a talk also done at KubeCon Amsterdam by my teammate Raj Using death space to usher in an era of peace for our developers. So you want to see Where we were back then and how we got started on this journey. Please go check out that talk after this So I want to start with a statement Local development is outdated remote development rules to present and then after this talk, let me know How where we are in Latin? What do you think? Let's start with some definitions and the two most important ones I want to find is local and remote development Just to make sure we're on the same page So local development is when you read your service on your local machine like your laptop and You don't really need an internet connection to get feedback during your development's life cycle Remote development on the other hand is where you're running your application probably in a remote server in the cloud or on-prem And you need to have that internet connection running to be able to get feedback in your development So that's the two definitions. I want to highlight here So what was the problem at ADA a year ago and why did we look for a remote development? Environment solution. Well, we were company about seven years old We've had lots of changes over the years lots of developers lots of services people coming and going come changing teams and You know every time you make a new service or things change in that service the complexity grows the development becomes harder and so testing and working in those services Really became a bottleneck So you want to find a solution to make it easier for everybody to develop all those services and be able to move faster and some of the problems we we saw was like People were developing locally and then when they would deploy to the dev environment to test it out with our other depend services things would break because other people would be using those services or They're test what they develop locally wouldn't work in the Remote environment because it's not the same as their local machine Even if they're using Docker So there would be various changes and think things would break and see if we even had a second development cluster just to Make testing easier, but that didn't really solve the problem and so really had a scheduling problem here where people wanted to test and make sure their their thing works in Their their feature works before getting it out to production But they want to make sure nothing else is broken So they ended up with schedules that they were using and we were using like a Google Calendar to schedule testing on our dev environments and it really slowed down development, you know, it was more like a Not a great solution And so we look through many solutions to solve this and we we land on dev space Dev space is an open-source project by started by loft labs and it's now a CNCF Sandbox project We started using it before it became a sandbox project and it's really awesome in that it allows you to deploy to any remote environment Kubernetes environment Whether local or remote using a single command dev space deploy similar how you might do get push or Docker run Dev space makes it really simple to do that and We could use our existing Kubernetes Manifests we were using helm. We can also use customize or plain Kubernetes manifests and so It worked really well. We didn't have to learn like a new paradigm for developing new templating language and Another thing we really liked about is the way it deployed in the pet dependent services because we had Modeleth and dependent microservices and Making all those work together was quite a challenge. We actually had our own homegrown shell script solution before this made of, you know Bash line bash scripts that in our CI service that would try to piece all these remote deployments together and make them work It's really hard to maintain and once we got dev space working an open source project That did the same thing where it was it basically delete all our custom Scripts that we used to use for remote deployments and just use dev space Another two things that are great is it takes care. Oh, it does it You don't need, you know Server-side daemon to run. You can you just need access to a Kubernetes cluster even a local cluster or remote cluster And it's totally client-side. It even has a client-side dashboard And It can take user input like ask the user questions you need to customize the deployment with some user Something from the user. You don't have to like have them memorize a long command of Parameters and I'll show you what that looks like in a second So this is how we implement dev space. We put a dev space.yaml file in all of our core repositories and We specify the helm chart and the values we wanted to override there and also like Other things you can customize about it. I mean that there's they have great documentation available and so What we did was when someone dev space can build images using canico or Docker build kit, but we chose to have our images built by the same process we do for production our CI process. So What people do now to what our developers do is they just clone the repo Or their branch and then they they run dev space create namespace and then their their name of their unique Namespace that they want to develop in and then they just run dev space deploy and out it goes and So what that looks like here is you can see here we just ran dev space deploy We asked the user some questions. What branches do they want to deploy of some dependent services? what what URL do they want to make this deployment available at and then Takes those in saves them so you don't have to enter it the next time and then just run the helm chart deployment and Give some helpful links after that that we added in that makes it easier for the developer to know where to find its logs and dashboard and everything So that that's dev space in a nutshell. And so this was our remote environment solution that we were able to deploy Using dev space we took it one step further where Since it's a single command dev space deploy We ran that from our CI which is in GitHub Actions now and we use just standard GitHub Actions for doing PR comments and When when everybody adds a PR comment to a PR a pull request Slash dev space deploy it runs the same command in our CI and deploys to our cluster and Then gives you some nice comments with a feedback is what what we made here but this really lowered the barrier to entry and Made and this actually became our most popular Method of using dev space at our company You know because you didn't even have to have access to the cluster or set that up or even download the CLI even clone the repo. You just had to go into a pull request and Add a comment and we use pull requests every day as part of a developed lifecycle of our company. So Yeah, this became really popular And so what are the wins what would be win after a year using dev space? Well There were thousands of deployments using dev space. It's used every single day by a lot of our developers Anybody can just join when they join a company join a team or start and on a service that they haven't worked on before They can get it up and running in less than five minutes And that that's huge like before these like set up your local environment with that service get all the dependencies installed To fix the issues that are that are there that took like one to two weeks You know and when you have that local the environment working You didn't want to touch it because if it broke that all you have to fix it and you know that it works with my machine problem didn't really exist anymore, you know and Also because we lowered the barrier to entry and you saw there via the PR comments Actually anybody who even wasn't an engineer or company like maybe a designer or product manager Or even our C-suite could come in and like add a PR comment slash that space deploy and get the service deployed or test out the changes and so this made it really good for feedback where Someone would open up a change or even non-technical people could make could look go into the code and deploy that change Without having to understand all the complexities of actually getting that service running because it was all basically abstracted into that devspace.yaml file and Lowering that barrier entry lowering the complexity to make these remote deployments and making easier to test Made complex big changes much simpler. So things like upgrading we use Python at our company and Upgrading Python versions is a big deal and it made this much simpler even for our largest services So we used to do like big changes very slowly and do a lot of testing locally and slowly roll that out to production But because of how we implemented devspace Our developers were able to make big changes to our services That had you know big blast radius, but they were able to test and work out all the issues in the remote environments And get things out faster And like I mentioned because they weren't relying only on their local machine to test changes They would catch issues in these remote devspace environments that would previously only be caught in production because Our development environment or remote clusters are a lot closer to our production environments. They're Kubernetes, they're running on the same, you know cloud using all the same services. So There were there was huge value there and we had a lot less incidents And so another big win was the data that developers were able to access since it we these remote environments had you know production like data or data that was very secure and Well managed If you if you depending on how your company works It may have to adhere to certain regulations around customer data or around user data. And so Doing that in local environments is really complicated, but then With remote environment, it's a lot lot easier. So that's one of the I think our developers love about a remote environment is that the data is easy to access and easy to use Also because it's not just one one local machine like the laptop you and when you change branches, yeah, you lose the old changes You can basically have multiple deployments going at the same time So you can take one branch deploy that using devspace change go deploy another branch or change to another namespace or environment and you don't have ten of them for all it matters and people and Basically context switch or have people test this one move on to the next one Have people test that there, you know, they can have multiple parallel streams work going on at the same time Which is a lot harder to do with a single local machine Another big advantage, but this is probably a given but like using remote Environments give you access to everything else that is out there in the cloud or your other dependent services that are in your environment things like GPUs are very easy to use With with the cloud and so that's all available via remote environments where doing these things locally like running our databases locally is It's possible and there are solutions out there things like AWS local, but it's a lot harder and Most companies nowadays or at least our company is a cloud native sass service So it really doesn't make sense to try and do a replicate all cloud native develop services locally, right? And so it's a lot easier to do that remotely and It comes in it has a better result And so after we deployed dev space other developers started Wanting to implement based on their services that didn't have death space yet. And so we were able to expand a search of death space By having other engineers Come and learn how we how we did it and implemented in their service and we helped work with them so we saw this also as a win of spreading the knowledge and the usage of Death space and remote environments and became like an expected standard at a company for all services. So When you're working in a service or feature People know they could they can always use depth space deploy to Work on it and develop Rather than trying to figure out how to deploy it locally, you know, it's now a standard but What are the learnings like what was the hard things that we learned and We had to fix and I think this is where the meat of the talk is is So the first thing was like remote your remote environments have to be 10 times better they can't just be two or three times better than What your developers were using before it can't be just like a long list of commands or Something that breaks off and you know, it can't has to be because it's because they imagine they've been doing this Probably local development for like 10 plus years in their career before you implemented remote remote environments and now you're asking them to just use this new way of developing and so We're able to solve this by making a lot simpler to deploy. I show you the PR comments Remove as much points of friction as possible and so that made a lot easier for people to use it where Even if they still like local development because it was familiar to them They knew the simplicity of using the remote environments and the value was was there so That that was our first, you know big learning Second one is like the quality has to be always kept high Distribute systems are hard things fail Versus a laptop. It's easy to fix. It's it's it's a controlled environment. So When you when you run this run this like a service like as a Any other service you run at your company, you know, you have to have monitoring alerting when there are errors you have to fix it And even though death space is a client side thing we have a support channel where when people run into errors that aren't working or they can't get to work we help them fix it because It's it they may not always know how death space works or how how to fix problems. And so We want to be proactive and see if it fails to deploy Find out why and fix that, right? and if you don't, you know people will complain and the loudest one and and Your remote environment solution will have like a negative Stigma attached to it. So you really have to keep Marketing and selling the value of your product your remote development environments to your teams to your company As you know probably For everyone complaint there are like 10 Successes that the users don't say anything about right? It's only the so when people complain That is feedback that you should you should take into account and and you know But also don't forget to keep marketing and telling people the value of what's going on and How it's being used successfully and how many successful deployments it it is and how much value, you know How much time it's saving so have those metrics to your observability observability platform We use Kubernetes metrics for tracking how many deployments are made How long they're up How long a PR takes to go through to production and all that and we regularly Talk about that with our teams and our leadership to make sure we know where it's successful And over time we've seen the number of errors decrease and the number and the success The successful deployments increase. So that's where you want to get to Another thing is I mentioned before about the data so Always keep in mind the data of That your developers need when they make these deployments like Because if they just do the deployment to the remote environment and there's no data there's an empty slate It's not really that useful for most of the time And so for us we have we came up with custom solutions that bring to our company of how we deploy and get access to the data that our users need for the development so I Think about how to do this and this problem is solved outside of dev space outside of how you deploy your remote environments So you really have to think hard about where to get the data from and how to make it easy to access for your teams Another one your early adopters like how users are critical to the success of your Remote environments, so we had early users early on who helped us test and figure out all the bugs and give us feedback and then We we they we help them you know like advocate for this to their teams so At our company we call them in for champions and they help go to teams and find out Problems and take them back to us and we help them. So, you know There are these people within various teams that want to help you that want to learn how to develop this way and you know Take the chance on it. So find those people and work with them really closely so that you can your remote development environments will be successful also Don't make your team the single point of failure. So Also teach people how to get around things and teach your your advocates how to fix things when things break, you know and Having using an open source product that has documentation out there and many use cases and and Is a really miss one way to do that also But we also have documentation things within our company that help people use depth space in our remote environments Here's the one is that the job is never done. Yeah, so I've been doing this for a year improving it It wasn't roses at first, but it's a lot better now and a lot more a lot of people use it at our company every day There will always be people who don't want to use it. So When you do get that negative feedback, that's good signal because they're willing to say something versus the people who just Stop using it and don't say anything. So work with those people To get feedback find out why don't I like using it where doesn't fit the use case and and also do road shows with teams because the same like with them with the Selling use case you just got to keep selling this right and so we also have regular feedback cycles with teams to get there to find out when things aren't working and We're also looking for more ways to improve the use the use of our remote environments. We also implemented and With our quality team implemented end-to-end tests to make it easier to test to run end-to-end tests On any branch and using depth space. So that was another way. So we're using and we also implemented part of our ML testing processes too, so We'll keep finding ways to add more value to it and you'll you'll get more and more Usage of it over time if you keep finding keep talking to your users Another one is here you're not going to solve everything with it you won't totally get away from local but Try to solve the the hardest problem and where there's most value We could have implemented death space at our company on a simple, you know cookie cutter template service that Maybe one team uses that's really simple to to implement But that wouldn't have much value overall for us if we did that So we implemented on the biggest all this hardest services at our company And it took a while to get working But when it did get working and after fixing bugs of how it works, you know It provided the most value and so instead of people having to go through a really hard time deploying it their local machine Now most developers could Could do this every day using depth space and that's where we found the most value And so really look for where is where is it most where you're gonna make the biggest impact With your remote environments and start there Yeah, it's and There will always be use cases that won't be covered by your mode environments so That's okay, but try to find, you know, the biggest ones, you know, the parental principle 8020 To go back to local development, it still will be there There will be people who love using it and we'll still want to use it and we'll still want to sell their local We found that the the death space dev It has a development mode that syncs to a remote container Had a lot of issues because of the remote connections and that failing out and Wasn't as snappy as just, you know developing locally on your IDE and getting immediate feedback using something like hot reloading So we're still looking into ways to solve this there are solutions out there like dev pod By loft lab that do solve this so That quick feedback loop in your IDE is still something That is hard to solve, but I think We're gonna find a way to do that so local development will still be there, but that's fine, but So what's next like I mentioned We've been looking to dev pod, which is another open source project by loft labs And it's sort of like get pod and get hub code spaces, but totally open source Where you could deploy and run any branch on an eye in your IDE When it's sort of like the same way you do development locally, we could standardize that and Make it also Use the same way to do development remotely. So we're sort of blurring that line And so if developer wants to do deployment locally That's fine. We'll have a standard way to do that And if they want to take it to remote and get all the value that's already there Then they can do that in the same way So they could deploy locally using Docker and then they could deploy remotely to Kubernetes and We've already done a POC with dev pod for this and it turns out to be pretty good So we're looking to get that implemented next Also, we want to standardize dev space and how it's used and customized There is that YAML file, but we don't think it has to be so unique for every single service So we have an internal IDP or internal developer platform at our company and we want to standard make it standard so that Every service can be developed and use and use dev space and Take advantage of remote environments Another two things here is dev space is a really versatile tool. You don't have to use it for just Kubernetes deployments For production, we do have like Argo CD and GitOps But we've been thinking of well, what do you do when Argo CD and the GitOps process fails and you still need to get Something out to production Well, dev space can be a really great tool to simplify that for developers If they in case they need to break the glass and deploy the production and skip the whole Process in case though that those things are down, you know, so That's one thing that we're looking into and then also for standardizing workflows Dev space is sort of like a workflow tool If you look at the docs has really great docs and that so We're thinking about replacing things like our custom make files and and other Short-gut scripts and just putting that into dev space Basically using dev space as the one command to rule them all Could be that way where we're looking into that so Like I said in the start local development is outdated Remote development rules the present. Well, local development still exists but in the past 12 months we've gained so much value from our remote develop environments and We are so much better off than before so I Think this is where everybody should be and should get to and If you have questions find me on the CNCF slack or scan the QR code here and leave feedback on my talk Thank you very much


Oh, he did do it. All right, get me out of here then. Downward angle coming up forward angle coming me up Three-person coming up How's it going everybody? Dato do it here back with another round of Dragon Ball fighters online ranked matches And today we are once again playing the fusion team trying to get some more stuff down And I believe this might be the end of gojira week not like that means much to me I'm definitely going to be playing some more gojira after this the three days for me It's filled up a full week for you guys, but it's been a little while from oh god My super dad okay super dashing was a bad idea I'm a super-dash famous last words Those for me. I'm a down-tech Down-tech did not go off there. All right. Well, we're gonna have to spark if he doesn't snap actually I was gonna say let's just get out of here. I wish I went with my first instinct to spark That definitely would have been a lot safer probably better in the long run as well We could have turned things around Not get done in like that to a Vegeta assist dude that proved poor judgment Oh get them up get them all for me. Let's go All right, and then we just switch them out not trying to play that game. All right nice 1 2 DP Okay, I think I want go tanks back. Oh, I almost had to bait. I Almost had the bait boom one Dude dude, I messed it up again.  Oh, that was my bad my bad.  I assume we're gonna go ahead and bring go tanks back and try to get a kill Don't want to press the offensive too bad though There we go a beam takes a month I didn't want to press the offense because I was worried he'd level three and that would really set us back a spark there Okay, I'm fine with that as well. Don't want to go out into Vegeta. So I'll just take sliding He probably wants to stay on the ground. I didn't want to come to that I wanted to see if you block it first wanted to see if you would block it He didn't so I'm fine with saving the three bars moving on to Vegeta next. What are you gonna do go Jita? What's the strap? Wow, he did that wrong. Wow. That was risky. I can respect it though taking big risk gambling like that Oh Are we doing here? What is this all about? I forgot to hold that was the dumbest mistake of all time. I forgot to hold the sparking. Oh We're out though genuinely. We're out. Oh, we were out now. We're kind of dead Jesus. Hold on. Oh, hold on Vegeta Poor choices for me. All right, let's try to rush him down. We'll be still sparking not with super-dash. That's too obvious Okay, I'm fine with that I don't know what I want to do here. I think I want a little three. Hopefully it connects good I don't play a lot of good things didn't know if it was fast enough one two Set him up three It's a mix. What's the mix? What's the mix? You don't know the mix. Oh, come on. Get out of there. Oh We actually hit him with that. You gotta respect it. He has to respect it, dude Okay Hopefully that connects Yeah, that's all right. We take game one it was kind of close But our vegeto play was super sloppy, so I'm glad we got the win I could get out of game one with the w man I did not want to start off with a loss and we for didn't do the sparking thing do there's so much more I want to do with this team. It's just very clear that I kind of sucked the other characters kind of hard as well Dude, this has been a start That was a bad down heavy for me. I was panicking. I was like, what is the what button is there left to click?  Did he think I was gonna drag her it was that supposed to be a tech? I don't know why he would dr there, but I Gotta respect it. It's gotta respect the Vegeta says you are not getting past that man, especially with this slow L Nice read nice read nice read now we go again in the corner still no level three being spent.  I thought it would be all got Okay, I think I just kind of want to get out of here most of all, but that's not an option. Boom Shall show their check? Okay, this might kill. I don't want to promise anything Okay, I Figured two bars would kill so why not just switch right there? Yes. All right. Good stuff good starter from go Jita. We are on to the last character I'm a let go G to heal a little bit. We're just gonna get kind of get I was gonna say risky But yeah, we were gonna get risky there and kind of just got stuff. Do you to come back out already confirmed? It's confirmed boys Nice to him. I got I'll give it. I'll give it up. I reeled back to my chair. I didn't expect to run up My dude said neutral G blast. Nah, I don't believe in any of that Snag them. Oh, we're not getting bars. We need Three I don't know if this is gonna kill power through Vigito Fusion team gets plus 30 bonus to damage. Oh, it didn't work. Oh, I couldn't get it Okay, understandable understandable 6m 6m another one. Is it gonna kill? No, there's no way. There's literally no way this kills We're living this boys We'll take a hard knockdown We'll take a hard knockdown. He's gonna try to DP my sparking Wow 6m to the forehead make it a five-head baby. I kind of dented it in game did a little more vertical mass All right, one more game one more game. Come on. You're G to put the work in on that one, but I need I need more I want go G to sparking mixes. I'm getting excited me too.  I was really pushing. Oh No Vigito just says and no All right, I didn't dash. I didn't dash. I deserved it try to make it a safe jump Woefully underprepared Wow, I didn't even think he saw me through the clash Okay, we need to get out of here with Vigito. Oh, is he gonna take me out? Nope. I got to do it myself I ain't sticking around. I ain't sticking around to see how that story ends. All right.  I choked on this by good.  Keep you wild and keep going though. Wow. I did place myself pretty pretty poorly there in the neutral I'll take it though Going down take a slide. He's gonna swap us out.  He didn't expect the cross-up for corner. No, we're probably dead He didn't expect to change sides there. So that kind of threw him off. We didn't make the most of it though Two bars Vigito is gone for good. But we're not out. I mean go tanks is My go tanks is definitely worse than my Vigito and that's saying something Wow super dash from that close bounce was Bounce was good, but not not where I thought it would place it still got to get used to the old assist as well What I thought it was how did I not get the first fire? You learn the darnest things when you try to test somebody on fighters. I try to throw some wow damage damage Yeah, I deserved it.  That was good defense Also, I ran out of sparking a little bit before I thought I was going to What get time to DP and Down heavy with this is probably gonna be the L for us. Gojita goes down here. It is not looking pretty go things coming up interesting Wow, that's it. I don't play a lot of go tanks. I thought that down heavy was a shoe in I got to start looking at these characters more. Okay. Gojita. If you can make this come back You can do it. Gojita. Nothing to panic about He'll come to us. Don't worry about that.  He was he wanted to win. I'm tired of you running He said he just ran in with it. Okay, we played a bit too passive that game I think also a bit that Now passives not the word for we were definitely super dashing from full screen like it wasn't gonna get us killed Game for technically not even technically it's game for Block I haven't done much block. How about we how about we just flex the block? No, not six M Run up medium. Oh god jumping M sausage fingers coming in hella nice today How long have you been cooking those sausage fingers at me? Let's go Looking a little overcooked Got him snap out. Let's just do it again He's looking for the he's looking for it, dude. He wants that down heavy He'll be with a lot of the last game. I ain't gonna let it be that easy though Got him. Let's go tanks down play some normal fighters We don't gotta let's not act like these are all random characters that we barely play. Let's bring it home Who faked it? I like that. I like that choice actually I Was more so faking it as like a neutral fake out, but it actually like delayed me from getting hit by the beam So I looked like a genius But really in reality, I was mad dumb.  What did he? Well, I'm a guard cancel to them. I'll take it getting hit by that is not the worst thing in the world Okay, there we go. No, I always Consider it a mix Please consider in a mix. It's embarrassing if you don't Level three Let's do this Gojira's out and about what's the spark? Do we actually try it? No, let's go for the snap, dude Oh, he did do it. All right.  Oh my god. This is this. This is why gojira is so sick. Oh My goodness, that was great. That was a great gojira like a minute and a half there. Okay, we win We win dude and with that we can finally wrap up the official gojira week Three days for me seven days for you guys We've been playing so much fighters and I feel like my gojira is still rusty, dude Hopefully you guys enjoyed this week of gojira I know yesterday's video or I think it was yesterday's video where we didn't get that run back ended kind of Anticlimatic, but I feel like that ended just like how you'd like gojira week that let me know your thoughts on gojira after the week You've spent with him down below if you've been playing him Of course, let me know that in the comments while you're down there though If you like the channel and the videos make sure to the like button and subscribe for more videos just like this With other fighting games and of course dragon ball fighters as well There's also some more videos on your screen right now if you want to check those out Make sure to give them a watch if any of them catch your eye. I have been not to do it Thank you guys so much for watching these videos and I will see you in the next one


The black preaching tradition is deeply connected to gospel music. Our singers preach and our preachers sing. God, we ask that you read and rigorate somebody. You feel it deep down in your soul. It makes you want to shout. It makes you want to sing.


Alrighty, I haven't watched this yet. Let's check it out. Oh my That is really loud from here. It's all fun. I gotta put this down Actually, what would really help me is after critiques if you tell me Which parts are helpful or not? It's like my first instinct is okay. Let me check the feet Is there something where you have offset in the in the orientation which you do we can see this But then is that too picky like do you need? To know that seems like you have a bit of squash in there or something. I thought that's cool. Is that something that is important or Not like my main things I would mention are things like this when you got double-arm poses kind of twins There's a bit of a frame offset there, but overall Like this could be a bit more of a potentially go like, you know, maybe Open arms open fingers like the excitement and then and then you're here And that's the the tighter excitement where you got the arms together, but then I would try to not overlap He's too much to get a clean a silhouette for as long as you can like something like that And maybe on a turn like that not go so far that you lose that arm so maybe only this far so you can retain A silhouette there Also, it was like the head and the body turn as one piece. I would try to I always say chest Pelvis chest and head, but she can't really put that egg So it would just be mainly something in the head Maybe with people till towards us where the head leads towards us That's cute I like that he goes down That excitement but watch out it it's definitely offset obviously in the pose bend and straight us well I'll be careful generally do not have a bend towards straight towards camera or away, but then we don't see that the Structure this gives us a bit of idea. There's a bends. This just feels like a short arm and silhouette But I would just kind of try to avoid double arm mirror stuff It could also be like if he's playful Instead of can you believe it because you have the fists here, which you have before Here just variety, but also could make something cuter. It could be can you believe it? What if the arms are? down Hands are flat and it's almost kind of not flapping but kind of you know like swinging his arms and Kind of tapping the sides of the egg shell and excitement. Can you believe it like that? Maybe and if that's too Playful or too? I don't know. I am so proud of you. You have worked so hard and learn so Like that to me seems more like worked so hard Where the fists are okay versus the other one but again watch out. So what why is that arm? It's not as clear structure-wise as this one This I'm not sure it is almost was like are you insane much and then that is all like flipping someone off in some different language Put that in there If you do though watch out it feels like we're hitting bit of a sharp wall oops, hold on in the spacing of This how that hand just kind of stops there Same thing with this one here here Well, I like this like that gesture there going up there a slight hold nice offset in the fingers and They're going up into haha. I would just not go over once I just gonna go keep like that section of the face clear I hope you're it's really nice. I really like this part where he has that gesture then simultaneously walks backwards Yeah, that's cool like they're a lot also clean silhouette and also keeping the arm front of it and not hiding it's cool That's great too because you have to go back there, but you keep keeping it clean here There's more reading lessons in the storylands area books to read it. I like that too You go there, but then don't do much so that the eye goes and then we we can hold and look at it read it And there's nothing distracting in terms of movement area books to read Watch out almost off-balancer with no recovery of like that foot going further back or something Which I wouldn't go further than this books to read in my program and words to spell in the skills bank Yeah, that's great. I like that. It's all very cool That's Really cute. See now it makes sense because now it's a steering wheel and it's kids will get that That's really cute, I like that a lot Watch out. It's a little bit of a hiccup. There's a little spacing Yeah, how that body goes over this is a really horrendous color for me to critique you with Where that body goes over here? Right there this in real-time It was harsh stop there That's cute too, right away we lean forward so that that has to go up in the air when you're ready for something you try fast phonics or reading egg express This is cool, too. I wonder though if on that point you actually lean Towards it So it's everything's leaning and whoo-ho everything is leaning and pointing towards that versus back I personally would bring closer to the purse the point of interest Then that way you have somewhere to go when he talks here Then you can load you can lean back to bring the attention back to him Right, so you have this you have all of that But he's leaning forward and then well, how do I get the audience's eye back to him? This arm down might not be enough I mean, I'm sure it is but you know, it wouldn't lean back where the head was here body here to body here head here So the eye really jumps back to him so many new things to learn This is generally something I wouldn't do it. It's kind of the classic I mean not that it's that they're up that high, but it gets into that W pose Where I would potentially get something else Or reading express there are so many new things to learn in both of these The thing is you have just a lot of gestures generally So I mean this could also be told be fine do this Then he goes over there that arm just goes down and then he just swings his arms as he walks They're just there for balance And then they go back up because here's a new important point That way it makes the contrast to be a bigger because that's important now I'm talking and that's important but then when you talk and you do all this It's kind of dilutes the importance of the gestures Super cute. Yeah, that's great. All right, that's it All right, there's an email you can sign up you can start whenever you want You can submit whatever you want you get 16 submissions either way like and subscribe would be awesome. All right. Thank you


I welcome you in the course of leadership, emotional intelligence and decision making. This is module number 11 and we're going to talk about evidence-based management. When we talk about evidence-based management, Albert Einstein came up with a very interesting idea. His famous quote is that no problem can be solved from the same level of thinking that created it. In this particular quotation given by Albert Einstein, there are three important things to be highlighted. One, that we need to talk about the problem and remember that every problem is a unique problem. Koi bhi problem, kisi bhi incident se related jab akar kar rahi hai, toh wo with the passage of time usme uniqueness create ho jaati hai. With the passage of time, harik problem hum ek unique context pe lenge because usme humari expectation, usme humari performance might be different, ya at least time frame would be different. One important thing to be highlighted in this particular quotation is that when we talk about the solution of the problem, there are different solutions which can give us the same result and we need to be very much conscious that what solutions are going to be operated or usse hum optimized outcome wo kais se hasal kar pahenge. The third important thing is that we have to move in a higher level context. In a higher level hum apne aapko us problem se alehda karke, ek holistic view me cheezon ko dekhenge. Holistically je cheezon ko hum dekhenge toh humare saamne ek bigger picture aayegi jissse ke hum ek better solution wo devise kar sakte hain. Sorry, remember my dear students, teen important cheezne hum ne zihin me rakni hain. One, what is the context of the problem? Two, humare pas uske expected solutions kya hain? And three, that we have to have the bigger picture, the holistic view, jaaha se hum apne evidence ko create aur shape wo karenge. So let's talk about ke evidence-based management me important aspects hume kya zihin me rakne hain. The most important thing that we have to bear in mind, that when we talk about evidence-based management jab hum decision making based on evidence, jab hum innovation based on evidence ki baat karte hain, to the first thing we should bear in our mind is that we have to be conscious. Me apne conscientiousness ko higher levels peh lekar jaana hain, ta ke hum zyada optimise decision kar sakhe hum logic-based baat wo kar sakhe hum. Jab hum logic-based baat karenge, evidence-based baat karenge, hum us baat ko mukammal toh par rely krwainge on the precedents available to humare liye decision making zyada baasani hogi. The second thing we need to talk about, that the evidence we are going to talk about is going to be explicit. It should not be hidden, it should be documented, it should be recorded aur hum us cheez ko iss tarike se baasya karenge, that everybody, every stakeholder involved in the decision making should be able to capture the whole scenario and the whole picture. So explicitly cheezon ko humne baasya karna hain, rather than ke hum implicit applications ki baat wo karenge. The third thing we need to talk about, jab hum decision making based upon evidence ki baat krte hain. So that is going to be that the decision is judicious. Judicious ka matlab hiye hoga, it should be based on ethics, usme distributive justice, usme aapka justice based upon the scenario wo mujood ho aur us justice ko base panaakar, us fairness ko base panaakar, hum apna faisla wo kar paaye. So three important ingredients, yad rakh yega that the decision should be taken when you are conscious, when you are expressing the things explicitly, and when your decision is based upon some judicious evidence. Abin teen baaton ko zehen mein rakh kar, the first thing you need to see, ke jo practitioner decision making kar raha hain uske paas expertise ka hain, uski judgments ka hain aur based upon those expertise and judgments, based upon his or her proficiencies and competencies hum decision making ko bahta toh par apply kar sakenge. The second thing is that the evidence should be from the local context, ek asa context aapke same ho, ek asa organizational evidence aapke paas ho, jis evidence ko aap locally prove bhi kar sako, ke based upon the facts aapis evidence kyu par baat wo kar rahe ho. The third important thing we need to talk about is that jo aapke paas research evidence hai jab aapne usfaisla ko karne ke liye us problems related to research conduct ki, so us research ka aapne critical review wo bhi kar hoge. So that you could know ke uske pros and cons kya hain, so that you could know ke us problem ko humne ki strike se hal karna hain. The fourth important thing as you are looking in the slide is talking about the importance of the stakeholders, ke kone kone se stakeholders hain, jin stakeholders ne us decision making mein apna contribution wo dena hain aur us decision se kone log So, three important things, consciousness, explicit and judicious, yateenu cheeze hain hume chahiye when we talk about evidence based upon the importance of the stakeholder, the critical review and the practitioner's knowledge and judgment. Aap hain is baat ko ek step aage aur chalaate hain, jaha paar hain elements of decision making ki baat kare hain, evidence based decision making ki baat kare hain. Ish mein jab hum practitioner knowledge ki baat karte hain to uska background, uska experience that is something that is very important to be counted, uske expertise ka andaza hume wahan se hoga, uska exposure kaisa hain usse hume pata chaleega ki wo decision making mein kin cheezon ko participate wo karwara hain. The second thing is ke kis level ke upa decision making ho rahi hain, organization ki kone se haraar ki involve hain, kin logon ke liye hume decision making kare hain aur management team jo us decision making ka main component hain wo logon hain. The third thing we need to look at ke jab hum evidence collect kare hain to it can be based upon the case studies jo ke already ek industri ke andar different context mein available ho. And we have to see ke jo data collect hum kare hain wo data authentic ho aur us data ki criticality, us data ki importance should be evident. And the third thing as we have talked about ke data ki authentication ke saad saad, ab jo fourth context hume dekhna hoega that would be the stakeholder preferences. Unki innovative problems kya hain, unko kin decisions par apna amaldaramat wo karwana hain. Ab is baat ko ek step aaka chalaan ke liye jab hum evidence based decision making ki baat krte hain to ek evidence ko collect kare hain ke liye sbse pehle hum stakeholder se puchhenge ke unke pas problems kya hain aur usse related evidence kya hain. So we talk about the asking aspect. The second thing is ke unse data collect hoega. So that is the acquiring aspect. The third thing is ke ab jo data hume pehle pas collect hoa uska hume critical review kare, so that would be the appraising aspect. The fourth thing is ke wo sara data collected usko hum aggregate kare hain usko hum collective formation mein lekar hain. So that would be the aggregating aspect, the fourth step in evidence based decision making. The fifth aspect is ke ab jo hume faisla based upon evidence kya hain usko hum apply kare hain aur apply krne ke baat the sixth step would be ke hum assess kare hain ke aaya humare jo solutions thay wo karamat thay ya nahi thay. Ab kis kisam ke hum faisla karte hain based upon evidence? For example, it can be selection technique, it can be performance management and it can be job satisfaction. Dear students, agar hain ussari baat ko conclude kare hain, to yad rakhyeega ke problem ki importance wo bohot zoroori hain jaanna Dursari baat ke hum jo faisla kar rahe hain usse related humare pahs data collect accurate ho aur uske shawahid uske evidences humare pahs mojood ho, koi precedent record hosakta hain koi case study hosakti hain, jisko base banakar hum faisla ko kar na chata hain. Thank you.


Hi everyone, Joe for jaspyscasebreaks.com coming at you with 2021 tops definitive collection baseball one box random team break number one With an opening-day mixer spot being given away here So you can get the monster hits out of definitive and then we'll re-randomize everybody's names in a different dice ball at the end You've got a chance at a $1,500 mixer spot. So pretty nice big. Thanks to this group of people right here for getting it on the Action appreciated. There are the teams right here. Let's do it. Let's roll it Let's randomize names and teams full 12 times six and a six the giveaway will be in a different dice roll one two two There's two three four five six seven Eight and 12th and final time after 12. We got Josh down to E 10 12 times for the teams one two and 12th and final time after 12 we got the Giants down to the Washington Nashian Alls All right, Josh with the Giants Derek with the Rangers Wade with the Blue Jays Josh with the Mariners Derek with the Mets Sean with the twins Rex with the tribe Tyler with the Phillies Levi with my Dodgers Daniel with the Cubs last Bob Mojo Matt with the Royals and the A's Josh with the Marlins Matt Medlin with the Diamondbacks Brian with the Pirates David with the Rockies Monty with the Yankees Levi with the Red Sox Andy with the Braves Jared with the Astros Clint with the O's John with the Rays Josh with the Angels David with The Tigers Stephen K with the Reds Clint with the Cardinals Logan with the Friars Edd with the Brew Crew Clint with the White Sox and E with the Nationals Get all this on one page. Let's sort by column B All right while you're considering well, it's even though this is a filler break since it's a definitive we will allow trades It's a pretty serious break right here. Here's the fresh case right here. Let's pop this open Here's my knife. Let's see which three boxes. We're gonna do. All right, so we'll select a die. Let's select that Vegas Dodger blue die right here one two three four five six on the dice roll six one two three four five six Right there. These will save for next time I don't know when the next time will be but there you go. We'll put X's on there And we're gonna pause the video and allow for a little bit of a trade window when we come back We're gonna see if there's any trades and then we'll have the one box break stick around All right, welcome back folks There it is definitive collection baseball one box ram team one no trades There's the final printout hot off the presses. All right, and let's see what we got eight hits per box six autograph cards Pretty nice stuff. I know the the personal's channel at Jasper's breaks on Instagram has been a Has been doing a lot of these and I think they've been they've been pulling some really nice stuff out of here So hopefully we'll find the same this one box break and you can see the cards on the top camera right there as well Good luck. We got an out of five Ricky Henderson the man of steel Right out of the gate.  I need more Next one right off the top another thin card. It's Jordan Alvarez with a go Astros inscription in there 40 out of 50 That'll be for Jared Kay and the Stroze Another one right off the top is rookie Otto Ryan Mountcastle The Baltimore game was rained out Red Sox Orioles, I think Rained out. So let's see him tomorrow 27 out of 50 Clint with the O's Next up is patch Otto Vlad Guerrero, Jr. 2 out of 10. They beat the Yankees today An extras that goes to Toronto. That'll be for Wade now Remember ladies John because of the top loader shortage We we're gonna have to put we've been putting some of these thicker cards into toddlers that are a bit too large for them So they'll be a little loose our shipping team will of course put that blue painters tape on there So it doesn't rattle around but if you're taking the tape off or if you're switching topplers on that Just be careful so it doesn't slide out on you all right Next up is Mark McGuire That's pretty cool the full the photograph that bleeds right to the edge right there 24 to 25 Sharp-looking card for the A's Matt Lieber Same with these cards to We're putting these in 100 topplers. He's probably will go in 75s probably the best right few more to go We've got a patch Otto the big hurt Jersey and autograph 50 out of 50 for the White Sox Clint with the White Sox trust me She'll like it too and White Sox just got an ending ending double play against the Angels They're still up 3-2 on the halos a couple more to go. We've got We've got Freddy Freeman three color patch your NL raining NL MVP now These are cool because it has the MLB authentication sticker if you go to mlb.com slash authentication and type in JC 510823 You can see exactly where that Jersey was pulled what day it was pulled And then you can look up the box score and see how he did that game If he even played sometimes And how but if he plays that could that could be an extra a fun story right there We saw one of these where I forget what I think it was strata Actually, and we saw one of these where there was some pink on the white part of the Jersey He was like a Padres catcher or something like that and it had the sticker. We looked it up And it was from a game where that person had hit a walk-off homer How cool is that so that must have been Gatorade and the last one here is a big old patch It's a one-of-one patch Pete Alonzo. Wow The s of Alonzo, I guess you have to find the other letters now. It's your mission Derek with the Metropolitan's Derek Jared with the Mets All aboard the Big Head Express What a break nice one ladies and gentlemen, thanks everybody for getting in appreciate it Definitive collection baseball in the books once we get that mixer knocked out You'll probably see more of these appear on the site. Hopefully, but there's definitely some on on the personal side Instagram at Jasper's breaks Instagram live now Matt down to yee and everyone in between you've got a shot at an opening day mixer spot of $1,500 spot. Let's roll it. Let's randomize it five and a two seven times for this list name on top gets it one happy person 29 sad people one two three four five six and Seventh and final time after seven so basically from two down to 30 my apologies sad times Even the saddest time for Derek right here. Oh rough, but I appreciate everybody giving it a shot. Thank you so much I know these are hard to hit in But I appreciate everyone trying So 29 sad people and the one really happy person is Rex Wow, did I do this right Rex five and a two seven times? All right Rex. You got a $1,500 spot. There you go, man. Thanks for trying to see all it takes is one ladies Gentlemen be like Rex get into those breaks. I'm Joe. I'll see you next time for the next one. Bye. Bye


Say we have a long solenoid of length L1 with n1 number of turns and say the coil area is a1 Now there's another tiny solenoid inside. So let me make this transparent and show it to you Let's say there's a tiny solenoid inside which is coaxial They have the same axis and it has a2 area and two number of turns and it has a length L2 Now if that sec tiny solenoid is carrying a current I2 and let's say it's changing Then there will be an emf induced in the larger solenoid We call this mutual induction and we've seen before that that emf induced in the larger solenoid depends upon the mutual inductance of the larger solenoid and our goal in this video is to calculate just that So our goal in this video is to calculate the mutual inductance of the larger solenoid with respect to the smaller solenoid And a quick spoiler it's going to be a nightmare to try and directly calculate this and we'll see why but we will find a quick A simpler way of figuring this out. So I hope I've gotten you pumped up Okay, but before we begin a quick recap of mutual induction. So the emf induced in the larger coil e1 that can be written as negative Mutual inductance of the larger coil with respect to the smaller coil times the rate of change of Current in the smaller coil That's the whole idea, right? And if you are not familiar with this equation feel free to go back and check out our previous videos on mutual induction Now my question is how do I calculate this because that's what I want to figure out So what I like to do is since this is a constant we can put inside the differential equation We can put inside the differential, right? So let me go and do that So it's the same equation But why did I do that because I remember from Faraday's law emf induced in any coil should equal negative rate of change of flux And so this means this quantity should represent flux Flux through which solenoid well since I'm calculating emf through the outer solenoid This should represent the total flux through the outer solenoid And so now I can say that the total flux through the outer solenoid Should equal the mutual inductance of the outer solenoid with respect to two Times the current in the inner solenoid And so if I can calculate what the flux through the outer solenoid is the magnetic flux is I can plug it in and I can figure this out And I also want to remind you a shortcut way of remembering this is connecting this with momentum just like how Momentum which is mass times velocity is something that objects hate changes in they like to continue their state of motion They like to continue their momentum. We can say coils hate changes in flux So flux is like momentum and so mass is the inertia over there here inductance represents the inertia of the coil There we talk about speed of the objects here current represents Loosely represents the speed of charge as we can say and so if we were calculating the flux due to its own current Say if this was I1 then this would have been Self-inductance when we calculate the flux due to the current in the other solenoid That's what we're doing here. That's when you get mutual inductance. So let's go ahead and calculate the flux So, how do you calculate the flux? Well, you've seen before if you have a nice flat area through which you have a Uniform magnetic field which is perpendicular to that area Then the flux through that area the magnetic flux just becomes the product of the magnetic field and the area And if there are n such turns then you just multiply it by n But the big question is is our magnetic field uniform? Let's find out. Let's find out over here so who's generating the magnetic field in this case is the tiny coil and We have to calculate the flux through the big solenoid, right? So let's go ahead and see what the magnetic field looks like What do you think the magnetic field looks like everywhere? Well, we know inside the solenoid the field will be pretty uniform But as it comes outside it will be nice and diverging and so here's what it would look like Something like a bar magnet and you can immediately see the problem. The magnetic field is not uniform everywhere So let me get rid of this coil because now we'll just focus on the larger solenoid because that's where we need to Concentrate our flux on so if I just for a moment dim this coil so we can Completely focus notice if you now try to calculate flux through any of these coils the field is not nice and uniform Let me give you some example if I take a coil somewhere over here Maybe we'll get some nice uniform field because it is at the center of the inner solenoid and the field is uniform near the center But if I take another coil somewhere up here the field here is not uniform So the calculating flux over here would be very complicated. I have to integrate and stuff if I take another example somewhere down here Look again the field is incredibly complicated. I'll have to integrate so calculating the total flux Can you imagine how much work that would be I don't even have any idea of where I would begin in other words This looks mathematically impossible for us and that's why we will not do that. This is a living nightmare It's a mathematical nightmare. We can't calculate this So what do we do? Do we give up? We've hit the roadblock. No, we don't give up There is one amazing thing about mutual inductance M12 is always equal to M21 meaning the mutual inductance of the larger coil with respect to smaller coil Always equals the mutual inductance of the smaller coil with respect to larger coil so what we can do now is Instead of passing a current through the smaller coil and calculating the flux to a larger coil Let's do it the reverse Let's pass current through a larger coil and find the flux through the smaller coil And now you might ask and you should ask well, how does that help wouldn't that also be complicated? We'll look at that in a second before we do that Can you try writing a new equation now an equation for calculating flux in the secondary? Due to the current in the primary in terms of the mutual inductance. Can you write that equation yourself first? All right, so that new equation will be very similar now It would be we're calculating flux in total flux in the secondary and that would be mutual inductance due to the secondary basically the the tiny coil to the tiny solenoid Due to the large solenoid Multiplied by the current in the larger solenoid this time We are putting the current in the larger solenoid that so let me redraw that circuit the setup over here Here we go now We're gonna put the current through the larger solenoid and call that I1 and we'll calculate what the flux to the smaller Solenoid is going to be so how does that help well now the magnetic field will be generated by the larger solenoid Right, so let's look at what that field is gonna look like here goes Ta-da Now we see something very similar to what we saw earlier The field is nice and uniform inside and it tends to diverge as we go towards the edge But the thing is the smaller solenoid is well within the center of the larger solenoid So if I concentrate on the flux that we are calculating over here now it will be much easier Again, let me help you focus on that Since we are calculating flux through the second solenoid Let me dim the larger solenoid for a while and you immediately see how nice and uniform the field is through each coil Again, let me show you some examples if you take some bottom coil over there Field is nice and uniform and perpendicular to the area so I can just do b times a over here I take any other coil again field is nice and perpendicular Even the topmost coil is well within the center and again the field is nice and perpendicular So here the total flux will just be b times a through each coil And so the total flux would just be the number of turns multiplied by b times a nba So here flux calculation is much much easier and so we'll calculate what m21 is So now would be a nice time to again pause the video and see if you can calculate the rest of the stuff We know the flux will be just n times b times a we know the number of turns We know the area of the coil all we need to know is figure out what the magnetic field is and we have seen that before This is the magnetic field due to the larger solenoid We know the properties of the larger solenoid as well and we have derived that expression before So can you put it all together and see if you can figure out what the mutual inductance m21 turns out to be? Pause and give it a shot Okay, so the total flux through the small solenoid is going to be just nba So which n are we talking about is it n1 or n2? Well, we're calculating the flux through the smaller solenoid So it's the number of turns of the smaller solenoid. So it's gonna be n2 Times b this magnetic field. Who's generating that magnetic field? Hey, that magnetic field generated by the larger solenoid which I've like dimmed over here But it generated by the larger solenoid, right? So that's the let's call that b1 Times the area whose area are we taking? Is it a1 or a2? Well, I'm calculating the flux through each coil of the smaller solenoid So I am calculating a2 Hopefully that makes sense, right? So if you ever get confused whether it's two or one, it's easy to get confused Just keep thinking about which solenoid, which flux you're calculating and we'll be fine So that's going to be m21 Something that we need to calculate times the current i1 All right. So the only thing we need to figure out now is what's the magnetic field and we've derived that before So let's quickly try and do that. So it's going to be b What's the expression for magnetic field? Well, we've derived earlier from Ampere's law magnetic field at the center of a solenoid or inside a long solenoid is going to be mu0 times n times i divided by l So which n is this? Well, this is the number of tons of the solenoid. That's generating the field Who's generating the field? It's the bigger solenoid. So this should be n1 So let me call this n1 And which current is this? This is the current who's generating the field. That's largest solenoid is generating the field So this will be i1 So this will be i1 times a2 Equals m21 times i1 And notice the current cancels out and We have our final expression. So let me just make some space. Let me put this up a little bit Okay, so what's our final expression? So we get m21 the mutual inductance of the secondary or the smaller coils smaller solenoid with respect to the larger solenoid That's going to be let's see. We get a mu0. We'll put that over here times n1 times n2 times a2 Divided by oh whose length is this? Is it l1 or l2? What is the length of the solenoid that's generating the field in our case the bigger one? So it's l1 So this would be divided by L1 and there we go. That's the expression for mutual inductance It's basically now you can see what it depends on depends on the number of turns of both of them Depends on the area of the smaller one because that's where flux matters And it depends on the length of the larger one because of the field that's generating None of this is pretty obvious and I don't expect you to remember any of this You can always derive it in your head, but what's important is m21 is the same as m12 This is exactly the same as m12 will not prove it, but it happens to be true for any two coils Regardless of how complicated the system is and which means we have answered our original question So I guess the big takeaway over here is whenever you are asked to calculate the mutual inductance between a couple of Pair of coils or a system of coils Doesn't matter what they're asked in the question You always pick the equation where the flux calculation is the easiest Where it's the flux where the field is going to be nice and uniform over the entire area Because m12 will always equal m21 for a given pair of coils You only have one value of mutual inductance


How about now? It's the magic of electricity. Collaboration. So, I would love to, hi. Hi. Oh, which one is mine? Sorry. Talk amongst yourself. It's that one right there. Okay, it's all right. Well, this comes up. So, lately in my life, so this is me, this is actually me. I'm Gary Hirsch, and I am part of a company called On Your Feet, and we've been, thank you. Thank all two of you. Thank you. Three. All right, cool. Oh, stop it. So, we've been playing with this applied stuff since 16 years, actually, going on it. And I've had this lately, like in the last, I don't know, three or four months, this sort of overwhelming sense of just sort of crazy, deep, I can't figure it out, appreciation for my own life, actually. Like looking at what I have and what's going on and go, holy shit, I cannot believe this. So, in this work that we do, that you do, that we do, I get to do amazing things. I get to draw, I get to play, I get to play with grown-ups and make them draw.  Just nuts. It's absolutely nuts. And I get to feel exhilarated and surprised and sometimes scared. And I've been lately going, wow, how did this happen? How did I find myself in a place that this is my reality? Because it is nuts, and it is not like the reality of a lot of other people out there. It's not like the reality of a lot of people that I work with. And so I was just thinking about it more and more, and I thought, is there something I can put my hands on and go, that's why? Because honestly, and this is the truth for me, and I do believe it, this is for me appreciating my own sort of life. It's not because I'm incredibly talented, definitely not good-looking, the tall people always get success, I'm not one of them. So it's like, what's this about? And I hit on one idea, and that's the one I wanted to share with you today. And it's not my idea, it's stolen. It's this one. If you're not familiar with this idea, I learned it, and who knows where it actually comes from? I'll bet you do. But I learned it from this guy a long time ago when I took some classes with Keith Johnstone. And he says that, or I understand it as this idea that there's something big and scary out there. And at least on stage, what the audience wants you to do is to go towards it, because that's more interesting. They don't want you to leave the opening of the scary cave, they want you to go towards the thing that's in the scary cave. And I learned that as sort of learning how to become an improviser and perform on stage. But as I keep looking back at my own life, I keep seeing this thing reoccur all the time.  You just sort of reflect on it, and then I'm going to ask four people to come up and share a story from their lives of meeting their own monster. And I've never heard them, and I have no idea what they're going to say, but I wanted to have a collaborative experience as well around this idea. So when I was young, oh no, sorry, one other thing. The other reason why, that's Keith, there he is, he's there again. The other reason I'm really attracted to this idea of Meet Your Monster is because my 17-year-old son decided to adopt it as his band name. I know, isn't that awesome? So this is Meet Your Monster.  Actually, we'll move on.   When I was young, I woke up with these vivid images in my mind of the door of my bedroom busting open with this giant hand that would grab me. If that wasn't scary enough, then this monster that owned this hand would eat me. If that wasn't scary enough, he had a graveyard in his belly, and the zombies would come out and chase me around some more. It just kept going. It was really pretty scary stuff, and it would reoccur and happen a lot. So to deal with this, I would go to my father, and I would say, dad, I'm having all these night mirrors. And he was a wise soul and still is, and he said, well, come on down the kitchen, and I'm going to make you something. Would you like to eat it? I said, cinnamon toast, please, with lots of sugar. And he'd make it, and we'd sit down, and then here's the thing he asked me to do. He would ask me to take out a pencil, deliberately a pencil, and to draw them, to draw these monsters in pencil, pen, whatever you could find. And so I did. I would draw them. And then, i.e. collaboration, if that's the theme here, he and I would name them. We'd start to name them together. What's this one? Big, scary red monster. What's this one?  And these are the drawings. Yeah, it's awesome. I have them. This is so cool, because they saved them. And so we would draw these things, and this is his handwriting here. I can't really see it, but I know that I have the actual drawing. This is Lobster Monster. They get named. And I have giant boxes of these in my attic. So we would do this for a while. And then what my dad said to me one night, and I do remember this really vividly. Probably about six or seven. He said, okay, let's draw those monsters again. So I drew them. And then he said, I want you to turn your pencil around. Instead of drawing them, I want you to start to erase them. Smart. So he started to erase these drawings. And night after night, we did this. And these things slowly went away. So he didn't have them anymore. So he had me meet these monsters and look at them and confront them. And since then, I can't stop meeting these monsters in my own life.  I've got my monsters. Face them. Don't run away from them. Thank you, Keith. And do something with them. And they've evolved, and they've become these small little things that now the monsters are getting distributed a lot, because I can make thousands of them and put them out into the world and see what they do with the world. And so this idea of meeting your monster, it prevails through this On Your Feet thing as well. I don't have a business background at all. I had to actually practice how to ask for my very first fee on stage. Someone said, you need to practice saying $5,000. And I was like, I can't even say that. So I go out on stage and go, hello, mom. I need $5,000 to practice saying it. And it continues to reward me. And this talk is simply an invitation to ask you to keep doing this if you are and start doing this if you're not. And the last thing I'll say before we sort of do something with this is that it's a simple idea.  I think it can be really hard to do. It's really fun to try. And I am really interested lately in, i.e., this idea which I've learned from Kat Coppett, which is story is meaning. And if you tell a lot of stories about something, you're going to learn more and understand more about it. And in that spirit, I am really interested in collecting stories of people meeting their monster. Because I want to understand this more. It's been really impactful for me in my life. And in that spirit, I'd like to invite any of you to share with me any stories you have around this idea. Whatever it really means to you, there's no real definition. It's sort of an idea. And finally, in the time that we've got, I'd love to find a way to create a collaborative experience around it. So I've asked four people that I know, but I don't know what they're going to say, to tell us a meet your monster story from their lives that are true. And I want to do it with a stolen improv form as well that I stole. I give all my improv forms that I can't think of who to credit. I just credit Rebecca. So Rebecca, Rebecca, you probably taught me this. I can't really remember. So can I have Greg and Amy and who else? Terry and Brad. You guys, you around? Give them a hand, please. Excellent. We have six and a half minutes. It's totally doable. All right. Hi, guys. Thanks for coming up. Yeah, just to sort of a straight line here. So this is Greg and Amy and Brad and Terry. I've asked them to come up.  That's true for you in your life.  So I had to tell them. And then they're like, yeah, I think so. Maybe I'm not sure, but they boldly came up anyway. So thank you. And what I want to do is do a orchestrated story or a story weave around this. Also, because I think this is such a kick-ass form and you should be doing it if you're not. It's a great way to get stories out into the room in a way that's dynamic. So here's how it's going to work. In a moment, I'm going to point at one of them and probably actually hold the mic up for them or pass you the mic even. And I'm asking them to start their story. And whoever I'm pointing at, they'll keep talking. As soon as I take my hand away, they'll stop. I'll point to someone else and they'll pick it up. They'll take their story and start it. When I come back to a person, they're going to just keep telling their own story. So essentially, they're telling their own story but interrupted and fragmented by the other person. So some of you know this. It's cool. So here we go. Here's some stories. Let's see what we can learn about this idea of meat, your monster. So the truck pulled in and I saw him and my heart started pounding. I was behind the counter at the hardware store I was working at.  I had this fear of heights since I was really, really young. I remember vividly nightmares about a fear of heights and falling down buildings and stairs with holes in between. And also I'm not a fan of fast motion and big twisty things. So not long ago, I found myself for a work engagement at Disney World. So I was at a conference a lot like this with a lot of people who are really competent at what they do and very exciting and dynamic.  I had heard about people running marathons and I thought, wow, what is that like? I'd read about people climbing Mount Everest and I thought, what's it like to be in the death zone? What is it like to be running at mile 24 when you've been running for hours? And so I decided I'd try one. The week prior, he belittled me and I'd never been faced with this kind of bigotry openly.  In a respectful manner. And I thought, okay, okay, okay, what can I do here? How can I do this performance that I don't know what it is? Well, I could tell the story about when my kid almost died or I could tell the story about when I had to go barrel racing and I was afraid of it. Wait a minute. So I was hanging out with my cool, uber-relaxed colleague, Brad. And I wanted to be cool and uber-relaxed too. And we met this really nice lady that worked at Disney World. God knows why she came up to us and she said, hey, I think I can get you guys to the front of the line for expedition Everest. I trained. I definitely put in my training runs. And the only thing was that on this November morning it was about 50 degrees and raining. And so I headed out with a group that was on a pace to do it at four hours. And I thought, that seems reasonable. Well, I'm really interested in the narrative. And so I told myself I was really interested in seeing how they did the narrative of a roller coaster at Disney World and that somehow that interest was going to override this lifelong fear. And so I went to the front of the line. It was a great experience for me to say, what is it that I'm learning here? Wait a minute. What is it that I'm learning? And I could look at all the people that were there as being part of my assistance, my help. They could teach me what I needed to learn and I could forget my fears until my name was called. So the door swung open and I heard it. He's like, hi, princess. And I was like, come here. We're going to have a little talk about respect. And I said, look, I treat you with respect every time you walk through the door for the last year and a half.  Well, they buckled us in. I held on tight. And it wasn't as bad as I thought it would be. It was actually about 25 times worse. At mile 13, my iliotibial band started to tighten up on me because of the cold and the wet. And the pain started to be very sharp in my knee. I actually climbed into the back of somebody's station wagon and started stretching out. I hope that that person was a race official. So he looked left and looked right. There was another African-American guy standing there. He kind of looked pleadingly at him. And that African-American guy says, you better listen to what the man says. And he went out with his tail between his legs. My stomach fell into my stomach and my sweat glands started exuding sweat and my throat started to close. And I thought, maybe I'll say no at the last minute. And then I realized that I had just learned all that I needed to know to get over it and move on. And that it had to do with having a giant eraser. And that I could just erase the monster and fill that void with something positive for myself.  And all of a sudden I was passing people and passing people and passing people and passing people. And I couldn't even believe it. And then I hit the wall. And then it really didn't matter how I ran. Part of my fear I realized was not just the fear of the fear itself, but the fear of looking super afraid. And this ride pushed me so far beyond that that I couldn't even control my leg anymore. It started kind of involuntarily moving. And when I got off, I felt kind of nauseated and trembling for about 36 hours afterwards. And came to the conclusion that I would definitely rather give birth again than go on expedition at rest again. Meet their monsters. Thank you guys. Thank you. Thanks guys. Thanks for the stories. Thank you.