But it's time now to pass, to go to our next speaker. Harsh is here and is going to tell us about building serverless Python applications on the AWS using this tool, the AWS Chalice. So Harsh, whenever you're ready, I leave the floor to you. Thanks, Francisco. I hope my screen is visible right now. Yes. Hello, everyone. And thanks for joining me on this talk on building serverless Python applications using AWS Chalice. And first of all, I would like to extend my heartfelt gratitude to the Euro-Python Organizing Committee for providing me with this opportunity to present my talk. So a quick introduction. My name is Harsh and I'm a senior year undergraduate from India. And I'm currently a Google somewhat of course student developer with Metacol and an intern with Red Hat. So I have been working with Python mainly around building APIs and machine learning models. And more recently into building iPython kernels as part of my Google somewhat of core project and some of the DevOps utilities using Python. In this talk, we will be basically discussing a bit about serverless computing, AWS Lambda and AWS Chalice, which happens to be the Python serverless framework on AWS. It would be a pretty short talk aiming to just introduce all of you to the AWS Chalice and how you can develop a simple API using Chalice and deploy it over the AWS resources. So with this determination, let's get started up. So before we start up, let me just introduce the agenda for this 30-minute talk. In today's talk, we will be basically knowing the basics of serverless and how exactly you can get started with serverless development using AWS. You will also get a head start on developing serverless applications with Chalice and a background to AWS Lambda. And why is it such a great choice for developing serverless Python apps? Finally, I will be demonstrating a live example about creating an all-new Chalice app, testing it locally and deploying it on AWS with a very short but sweet demonstration. If you have worked with AWS before, it would be very easy to follow up. All you need is an AWS account and you need to configure the AWS credentials or your local machine. If you have not done the same, it would be highly preferred to have it done so that we can very readily have a smooth transition into the practical example once we arrive at that particular point. So with this determination, let's get started up now. So before we jump into the entry cases of serverless, let us first discuss the standard ways that we employ while we try to deploy our APIs. I have highlighted some of the standard ways that we normally follow while you're trying to deploy our APIs on some of the popular AWS services. For example, if you want to get started by the standard way, you can use the AWS Elastic Compute Cloud to deploy your APIs. It provides a very standard virtual machine instance which you can then configure on your own to run your APIs. Deploying on EC2 or its pretty alternatives on Google Cloud Platform or Azure, it is pretty much the standard way that most of the technical teams follow to deploy their APIs in a very simplistic manner. You just create an instance, you do a secure shell login to connect to your instance and you're already to configure everything up for your deployment pretty much straightforward. More recently, many developers have been using container technologies like Docker to deploy their APIs as well. We can just create a Docker image that can act as a blueprint for the container deployment so that we can just put it over the Elastic Container Service which acts as the container deployment and the management service for us. The container setup file just called a Docker file will outline our image and provide all sorts of bell instructions for easy deployment. You can then deploy your image with just a single click over the ECS. The third way of deploying our APIs is slightly tricky but is commonly being used today to separate the need of managing infrastructure from the code and keep our focus only on the core function and the business logic that we need to develop and deploy. And as you might have guessed it right, it's the serverless way of development that is being talked about right here. When building serverless application, AWS Lambda is one of the main choices on AWS for running your application code. So let us beg our attention to one of the most pertinent questions we have. What exactly is serverless? So I will start with addressing the elephant in the room. Serverless doesn't mean no servers. In very name and terms, serverless computing means that your backend code which acts as your business logic will just run on some third-party vendor server infrastructure like Amazon Web Services or Google Cloud Platform or Azure which you just don't need to worry about. It does not mean that there is no server to run your backend logic, rather you just don't need to maintain it. Going further, serverless abstracts the phenomena of exposing the developers to the overall infrastructure. This just means that the underlying servers are being hidden from the developer and we don't have to worry about all those weird server configuration files and a ton of other things that you need to put on our application before a production level. It's a confusing term, but don't let it fool you. We have got servers where our application is deployed. We just don't have to manage, maintain or scale it ourselves. This is exactly what serverless in its entirety means. But why should you bother about serverless at all? Let us take an example here. Earlier, if we wanted to set up our application for global use, we needed to have a server up and running. This server can then process the requests coming up and render the data and logic on the client side. Isn't that what happens every time? So this was a traditional approach that we followed a few years back. Server computing was possibly the de facto way of serving applications and we needed dedicated people and engineers to maintain the servers and the backend code. With the introduction of serverless, that requirement has been completely rooted out. With a serverless platform, a programmer can just write the code and they can directly run it on the cloud without worrying about the hardware, operating systems, servers, configurations and what more. They can just write the backend logic as a code and they can just run the code without needing to be aware of the development deployment complexities. Applications get high availability through serverless as well as auto scalability without any additional effort from the engineering side. All of this can significantly reduce the development time and the consequent cost. All of these simply make serverless a very lucrative choice to get started with the development and deployment of our application. So I hope most of you have now understood the basic philosophy and the requirements behind serverless computing. Nowadays, it is completely universal and various cloud service providers like AWS, GCP, Azure, they are offering their own serverless compute services that we can basically capitalize upon. Lambda is one set service provided by Amazon Web Services. So what exactly is Lambda after all? In a simpler manner, Lambda allows you to create functions that are self-contained application in the form of functions that can be deployed through the Lambda on the AWS. So your function can be stored on the cloud and with events like let's say API calls or database modifications and much more, you can just trigger these functions and make use of the same. Behind the scene, Amazon manages running servers that are handling the function execution and the resource allocation so that it can successfully complete your function execution overall. It might sound very easy and fascinating because AWS Lambda takes care of all the needed resources and continuous scaling as a server to successfully run the functions. This simply overcomes the headache of scaling application and also we can allow or prevent the function from accessing the resources. You can just deploy your functions in a zip file or as a container image, whatever way you prefer and Lambda will allocate the resources and auto scale it. One of the biggest trends of AWS Lambda is a reduced cost of execution. You don't pay anything when your code isn't running. This ensures that you don't pay for the time when you're not actually running the code or your application is not being used. While building serverless application, we just need to take care of three things. Having a Hypertex transfer protocol gateway service, having a database service and having a compute service. Lambda fills in as a compute service that we require out of a serverless stack. If you're looking for a database service, maybe DynamoDB or RDS is the way to go. While we normally use the API gateway for the HTTP service that we most commonly use to expose our APIs, Lambda tightly integrates with all of them and abstracts all of the underlying things going on from the end user. This makes Lambda a great fit for deploying highly scalable serverless application in a very simplistic manner. Let us now welcome the protagonist of our talk which is AWS Chalice. We talked a lot about serverless, Lambda's and all, but where exactly does Chalice fits in? So as I developed the advantages that I mentioned coming with AWS Lambda are huge. We do have servers up and running. We just don't need to provision and maintain them. Our duties solely relies on providing the function that is a code to the servers with an added advantage of being only for the compute time that is being used. Under the hood, AWS Lambda is making use of a whole lot of services in the AWS ecosystem to make this happen, along with flexible scaling and high availability. And it can be the go-to service for your serverless deployment. AWS Chalice is a micro web framework that is very, very similar to Flask that allows for the development and the deployment of our API-based microservices, which is pretty easy compared to anything else except for the code part, the scaling, packaging, and the deployment are all done for us almost instantaneously. And this is what makes Chalice so great. So if you work with a micro web framework like Flask or maybe even Fast API, you will find Chalice to be quite similar. So Chalice is a similar web framework with a lot of features and syntax quite similar to that of Flask. Albeit, it runs completely on AWS resources and offers a single click deployment. The best part about working with Chalice is that we get all the functionality that we can expect from an API development framework. And it provides integrated functionality with most of the other AWS toolings like the S3 storage, the simple queue service, API gateways, and more. Chalice is completely an open source framework and it is currently being used by over 1,000 repositories on GitHub and over two dozen packages right now. And it is an actively maintained project as well. So you can check it out on GitHub, on the AWS organization, and you can even contribute or use the same. So why exactly Chalice? What advantages does it offer that the other API development frameworks don't? So Chalice comes with a very handy command line interface tool that you can download using the standard Python package manager that is PIP. And it can be used to automatically set up a Chalice project and you can test it locally and you can deploy it as well using the same integrated CLI. With Chalice, we can only focus on writing the code that matters while leaving the deployment and the management part of the AWS resources to take care of. Apart from the standard Python, PIP, and the AWS credential setup, you won't need anything to deploy your APIs. Everything can be set up from your local machine without having to go to your AWS dashboard or doing a remote SSH into a server. Chalice makes everything easy for you to build, deploy, and manage. Apart from all of this, it also provides a decorator-based API through which it exactly integrates with the Amazon API gateways, S3, SNS, SQS, and the other AWS services. So if you are entirely working upon the AWS stack, working with Chalice would be a breeze to save because you can now leverage the same services that you originally used while building your applications. So with this, we come to the practical hands-on part, and this is where we are going to do some practical demonstration. So let me stop sharing my slides and let me start sharing my whole screen right now. Yeah. So before we are gonna start with setting up our Chalice project, we just need to make sure that you have the AWS credentials properly set up. If you are not familiar with the AWS credentials part, you can just go to your AWS management console. You can go to the IAM, which is the identity access management. You can go to the users and you can just click on the new add users option and you can just configure a new user so that you can exactly use all of these AWS services.  And once you do that, you need to assign the permissions. So you can either add the user to a particular group. So I have a group called personal just for managing my personal configurations, or you can copy the permissions from an existing user, or you can just attach the existing policies directly. Once you do that, you will be getting access to a secret access key and an access key ID that you need to keep upon your dot AWS folder. So if I go to my terminal and I just have a new tab, if you just minimize it a bit, and if I just go to AWS folder, I can exactly see that I have saved my configuration and my credentials right here. I will not be showcasing my credential because I cannot screencast it because that would reveal my personal information, but you can just have your credentials right here and it would be your AWS access key ID and your secret access key. All of this would be present on the dot AWS folder on your home directory and you can directly save it right here. If you don't want to go about this in a whole manual way, you can just download the AWS CLI, which is a very handy way of configuring your AWS credential and managing your AWS resources.  So we need to have this particular thing up and going because we don't want to go to the AWS management console for deploying our app. So these credentials will be used for authenticating your user configuration so that you can easily deploy your API. So now that we have set up our credentials, we can get started with creating a Jalice project. But before we do that, we need to initialize our virtual environment. So for this, you can just install virtual ENV. If you're familiar with this part, so virtual ENV basically gives you a virtual environment and it basically isolates all of the packages and the dependencies that you're installing away from the other dependencies that are part of some other project. So you can just install this by using the pip3 install virtual ENV. And once you have done that, you can just go ahead and like create a virtual ENV on your folder. We have initialized the virtual ENV right now. It is by then 3.8.8. And right from here, we can just get started with installing the Jalice. So the first thing that we are gonna do is like Jalice by pip into our virtual environment. So we are gonna do pip3 install Jalice and it will automatically collect the Jalice and it will install it on our virtual environment. So yes, the Jalice has been installed and if we just run this command, we will exactly see how we can exactly use it. So Jalice gives us a lot of the options right here. We can create a new project, which is exactly what we are going to use at the first. We can delete this project as well. So once you have deployed your API and you just came to know that you have messed up somewhere, you can delete your project as well. You can deploy your project using the standard deploy command and you don't have to do anything. Your Jalice project will automatically get configured through your AWS credential and it will automatically get deployed as a Lambda function. You can also test it locally using the standard local command. And you can also develop and debug some of the other commands for Jalice using the def command. So let us go ahead and try to create a new Jalice project. So to do that, we will just push in this very simple command Jalice new project and we can keep a name for this project as EuroPython 2021. So as soon as we do that, we will see that a project has been automatically created, which is the EuroPython 2021. So let us just see the inside it and now if we just jump back on our VS code, we can exactly see that Jalice has automatically created a few files for us, the basically the boilerplate so that we can exactly get started with the same. So at the first, we have a .Jalice directory which contains all of the configuration that we need for our project. Apart from this, we also have got an app.py which contains some of the boilerplate code that we need right here while developing our API. So there are some boilerplate code here which we can exactly delete for now because we are not going to use it. But rest of our frequency that we are importing Jalice and we are creating a new application along with the app name and we just create a standard decorator signifying that if a user is going on the index route, they will exactly see a hello world message in the form of a JSON. We also have a requirements.txt file, but we will see that it is completely blank. We don't even have the Jalice right here because Jalice is not a part of the runtime environment. And we need to understand that Jalice is just being used for creating the standard Lambda functions in an easy manner. It is not actually a requirement that we need to use for deploying our application. So let us jump back on our app.py and see what is happening right here. So it has only one route that would assign the URL of the application to the function easily. The decorators here, they're simply wrapping the functions which makes it easy to write the code logic by breaking them down into separate routes. For now, our application is serving only a very simple JSON message, which is the hello world. Now that we have set up a Jalice project, let us move next and test it locally and deploy it as well.  This command will automatically create a local development server at port 8,000 while managing all the complex stuff with the aid of the decorators. So we can just hit the enter and we will see that the dev server has been started and right now it is serving our application on port 8,000. So if we just open this up, we will see that we have a hello world message right here exactly as the JSON that we were requesting it for. You can also do a standard curl on this. So if I just copy this whole thing, just open a new tab and do a get request. Okay, list an edge. And we can see the hello world message right here. So this is how easy it is for you to basically test your APIs using the Jalice right in front for all of you. So now let us just go ahead and start to deploy our API as well. So we have a simple hello world message right here and it is running successfully. So let us just go ahead and invoke a very simple deploy command so that this API will automatically get deployed over the AWS resources. So to do that, we will just push the command Jalice deploy and it will start creating a deployment package for us. It will create an automated identity and access management role. It will create a Lambda function for us. And as I said before, Jalice is really handy way for developing your Lambda functions and it will also create a REST API. And finally, it will deploy this on a Lambda Amazon resource name along with the REST API URL so that we can just invoke it and see how our application is working. So this is a REST API URL. Let us just copy it and let us do a curl on top of this to see like how is it working. As you can see, it is just passing a really simple hello world message right here. So if you open this on the browser as well, we will see the same message right there itself. Jalice just makes it very easy for developing, deploying and testing our application using the handy CLI that it has right there. Let us just go ahead and try to add another route and beat a very simple one because we are just running out of time just so that to see like how we can add more routes here. So one route that we can add is instead of a simple hello world, let us try to add a route for a hello name. So we will just create a decorator, app.route. You just wanna say hello and we will just keep the name within curly braces so that we can exactly use it for our case. So this is our app.route and let us create an F hello name and let us just return a hello message. Let us try this out and let us see if it works properly. So the Dev Server has been started. Let us just go and see. It's missing the authentication token which is quite weird to see but rest apart, we can just go ahead and we can see like what is happening. Okay, then I guess this might be a silly bug which I'm not able to figure out. So let's jump back on the slide itself and let's see like what are all the other stuff that we have to cover. So apart from all of this, we have just arrived at the end of our practical demonstration. If you're looking for, you can add more routes to the standard boilerplate code and you can set up standard get and the post request. You can add course as well if you're trying to deploy it for a frontend user interface as well. And as you might have noticed, Chalice provides a lot of advantages when it comes to developing and deploying APIs on AWS. With serverless popularity reaching to the moon, services like Lambda and Chalice can simplify the overall development and the deployment process but there are some certain disadvantages as well. Chalice right now is not fully mature to develop and deploy large scale APIs and for creating full-fledged application. Lambda has a limit of like a 15 megabyte deployment package which makes it exactly disadvantages for us to deploy heavy dependencies, especially if you're trying out, let's say heavy packages like machine learning models or something like that. Chalice also binds to your AWS resources and thus it can create a vendor lock-in problem, especially if you want to migrate your deployment to another option in the future maybe. But rest apart, Chalice can be really seen as a handy way of writing Lambda's and deploying simple APIs. With this, we have came to the end of this talk. Thank you everyone for joining me on the short open Chalice and I would be ready to take up any questions if there are any. Excellent, thank you so much, Harsh. That was a great presentation. I didn't know about this project, Chalice and I'm sure I will try it out in the future. Also, thank you for being very clear in your presentation, the pro and the cons and this example that you gave. We have some questions. I will copy one and show it to you on the screen. So let's see if it shows up. Okay, how do you feel comparing Chalice against other serverless frameworks? As I said before, Chalice is not fully mature enough to develop and deploy large scale APIs. So my personal use cases has been just in my personal project and sometimes just for triggering a few functions. So compared to the other serverless frameworks, I guess I would just go with them before I see like Chalice being fully matured enough to handle large scale executions for me. But if you want a simple thing to tie up with the other level of services and if you want just a simple Python syntax, Chalice might be a very good option for you. Awesome, awesome. I have, well, we still have maybe a couple of minutes. So while people type their questions in the room, I will beat them because I'm already here. And I will ask you another question about the latency. I guess, I don't know, maybe the latency that you get from a serverless application versus a fully managed server application that you manage to write and deploy and configure and scale and all that kind of stuff. Are there comparable latency-wise or maybe with serverless, there is a little bit of latency to start the services? I don't know if you have any experience on this. Yes, so this is a standard problem with Lambda and if you try to read more about Lambda, you will know that Lambda has a very slow response time. And this is exactly what we see as the cold start latency. So this is a definite engineering problem and this is why most people have a significant apprehension against going with the serverless frameworks. But there are definite walk-arounds that is being very well documented about how we can handle this latency issues with the serverless frameworks. Okay, makes sense, makes sense, very cool. Thank you so much. We are running out of time and you folks can continue the conversation in the matrix on the breakout room. We now have a very short break, four minutes break, we start again in nine of five Central European summertime with some morning announcements in Optiver. And then we continue with the first keynote for the day, Claudia Comito, and she's talking about lots of cool stuff, data science, data analysis frameworks, you know, a lot of stuff. So I will see you there at nine of five CEST in Optiver. Thank you again, Harsh. That was a great presentation, very interesting. I'm going to try this technology right now. And thank you folks and see you in five minutes.


Do you know what your problem is? Even when you have an opportunity to flirt and to connect with other women, you like, punk out a little bit. No, you think I don't know your tricks? It's not a trick. You give them the free lane, so that when I do do it, you're gonna be like, Hey, not that one. No, that's not true. Okay, so Jared shot a music video. First of all, you shot music videos with three different women. Yeah. And every time you've been kind of weird about it. Have I? Yes. For example, in his last music video, him and the girl Nessa, Shaz Nessa, she's a dope dancer, super incredible and an artist as well, too. Yeah, she was vibing. You guys were vibing on like a brother and sister vibe, and not even like a dope brother and sister. No, we was vibing. Do you really believe that? Yes, there was friction and chemistry and just... Yo, I want everyone right now. Do me a favor, go and watch that video. Let me know if you feel like not even like a uppercase vibe, just like a small in brackets vibe. Maybe if you felt that a little bit of something. My lovers and friends, today I'm joined by Jared Brady. Jared Brady. My fiancée.  Why? It's so like... That's what it's for. I don't want to feel snooty. I just wanted to be... Who's your fiancée? It should be a word like... Fiancée. Pre-hub. No. Pre-hub. That's why. There is a question that all of you asked over and over again, which funny enough, when we told our friends and family and we were engaged for two months before we announced it on YouTube. And so whenever we told people, you know what question they never asked? Ever? Like not even our parents ever asked? Is it going to be an open marriage? Nobody asked us that. But online, that was the question that we were asked over and over again and so we decided to address that today. So I happen to know for a fact that like, we have never really officially answered this question before in a point blank way. So I just want you to lay it out there in a kind of three. Are we going to have an open marriage? One, two, three. Yes. Well, no. No, but yet. Kinda. Sort of. Little-ish. Maybe. We're not going to change anything about our relationship style. I think that the way that we started our relationship and the way that it progressed really just suited both of us and it allowed us to get to this space. So making a massive adjustment in how we love each other and what values we hold on to. It really wouldn't make sense as we progress forward. Like what, if it ain't broke, don't fix it. But yet, the term open relationship doesn't necessarily serve us, nor does it really describe us.  And I think when we said open relationship, that's what people jump to. And I think our relationship is more towards a traditional relationship than anything. I think that we do have a little bit more of a wider boundary or borders, I guess. It's hard to describe a relationship with one title because everybody's gonna have their own little version of what that is. One of the things that I deeply regret about using the term open relationship to explain what Jared and I share is that it has alienated me from so many of you. It created this like you versus me and I can't connect with her. When in actuality, the reason I even got involved in intimacy education and sex education to begin with is because I wanted to be, you know, I joke about this, the Walmart reader. I wanted to be the person who was accessible and who was comfortable to a lot of people. And I feel like by pigeonholing myself as an open relationship girl, I've put myself in aisle 14. It really worked against what I thought my calling my purpose was. I was grateful for it because it started with a lot of great conversations and it allowed me to be a part of a really fascinating community that I learned a lot from. But in actuality, I don't know if that title best describes our relationship and I don't think it best serves my purpose and my career. A title is supposed to let people know what we are without even knowing us. And so if you don't know us and you're not close to us, you're probably not at the level to understand what it is past the surface.  When we use the term open, what me and Jared really mean is it's open to your decision. Not necessarily that we are engaging in that or that we have engaged in that, but it is your choice and this is a long life that we share together and we're not about to put restrictions on one another because it's just not necessary for our relationship. But when people hear open, they think sleeping with multiple partners, not prioritizing their own relationship or having a bunch of side relationships. And don't get me wrong, that could be the case in the future, but at this present time, that couldn't be any further from the truth from what we share and what we have shared from the very beginning. And so for that reason, I just don't think that that label has done the service to our relationship that I would have liked it to have. So that's why I don't really think I want to use it anymore. I'm not uncomfortable with it as long as people understand what we mean behind it, but I would just rather just say marriage. I do want to say, because I love being advocate for the kind of values that we share. I think that we do have a choice-based relationship. There's a long, long life. And I think that if you want to go and experience something or you want to go get to know somebody or you want to go, you know, flirt or whatever it may be, like do it. Never feel like because you're engaged to me or never feel like because we're, you know, growing together, you're excluded from anything that you want to go do. I also have to point out that I'm sure a majority of you don't do what me and Jared do for a living. Maybe you do music. There might be more of you, but less of you probably talk about sex and relationships. Everyone does music nowadays. So for example, I'm writing a book this summer and part of what I'm doing is working with six women who are awesome, but really, really struggle when it comes to dating.  We just went out flirting, made connections. Like that's what we did. And I worked on a show that was called Your Perfect Date where I was testing out different psychological principles on first dates. And I went on 30 different first dates while me and Jared were in a relationship. So naturally, as a result of what we do, they're just, it doesn't make sense to hold each other down to strict monogamy. This is the best relationship that I've been in other relationships. I felt like I was doing something wrong or I was a bad person when in reality, like I don't think flirting is bad. I don't think that it's ill-mannered. I don't think that it has any bad intent behind it. I think it's a way of two humans connecting with each other.  Like our relationship hasn't even gone to that place yet. So it's just like we're getting hung up on for what ifs and it hasn't even happened yet. Not a lot of men would give me that space and that trust that you have given me. And that to me, like there's a billion different things that make you so special to me and that make you a cut above the crowd and make you perfect for Shan Booty. But that's one of the elements that I know I'm not gonna just find anywhere else in the world. I know I'm not gonna walk outside and meet another Jared Brady. It's not a coincidence to me that with you, as soon as we got together, everything in my life went up with somebody who gave me the freedom to trust the space and the love to be my best self uninhibited and who trusted my decisions, I was able to start trusting myself more. So, you know, thank you for that. And thank you for like the opportunity to be loved the way that you've loved me. It's been perfect for me. Lovey-dovey, gushy-mushy. You don't like it? No, that's cool. I love it. I want everybody to know that it is rooted in love. It is rooted in freedom and it is rooted in trust. So it's very, very, very normal, I think. I think so too. So everyone that's trying to alienate us and make us feel weird for, you know, whatever you guys wanna do, whatever you guys wanna put us on or tell us that it's not love or tell us that it's you millennials just messing up everybody or leading people in the wrong way. Like, whatever, man. Well, I hope that you're saying that out of a place of happiness. If you're leaving a negative comment, I hope that when you do criticize other people's method of connections because you're so deeply connected in your individual way that you want everyone to experience that. But I would focus less on the mechanics of what something is and just look at the beauty of does it work or does it not work. And if yes, maybe their system is different than yours, maybe their process is different, but the output is the same. And that's all I hope for all the viewers out there.  What's most important is that you feel celebrated and you feel happy and your help is not being impinged on in that relationship. And everything else is just semantics that really could fade to black for all I care. Yeah, like, it doesn't matter. All the extras don't matter. Unless, like she was saying, unless you want to engage with somebody.  That's not who this video is for. Who is for? We don't make videos for the trolls. We make videos for people who are curious. We make videos for the supporters, for those who are curious. We make videos for those who want a further conversation and those who want to take this video to spark a discussion on their own end. We don't even listen to the trolls. The first I do. I just want to take a moment and thank you guys for so many years of support.  You guys never met me. You've seen me on Shan's channel. You have a lot of opinions about me, but you've never said anything negative about the music. And that's really just kept me going. And I just would appreciate it if all of you guys just went over there and checked out the project, checked out the music video, told me your feedback, and let me know how you felt about it. And that's it. I thank you guys so much. Peace.


Next question is from Becca Clemenson, in 20 years, where do you see yourself and mine pump?  I mean, I'll be, we'll be 60. Impossible to find, hopefully. Yeah, 62. I'll have, my hair will look like Adams, that's what I predicted. Yeah, 20 years is a really long time to try and predict where that is. Yeah, I predict, let's see, 20 years from now, you're gonna see, I think we're gonna see. Catch me in the metaverse. You know what? That's true. That is so true. Fighting it. That's so true. From the inside. Yeah, I tried those Oculus goggles that you have and that really was weird because I literally warmed for five minutes. That's today's tech, so 20 years from now, who knows? Yeah. And I had them on and I was playing that game a little bit and I could see how you could get totally enthralled with it. And then when I took them off, that was only after five minutes, the real world felt very strange to me because I had already adjusted to that world. Yeah. So I could see how metaverse world is gonna make people not want to be in the real world. Is fitness gonna be all like that? I mean, I could see that. I mean, I still stand by my prediction of that. We're gonna have a very clear split in our society. I think there's gonna be, and it's gonna be pretty even. I think it's gonna be. Now, where do you think we'll be? So we're mine pump 20 years from now. We're gonna be on the unplugged side. So honest, where do you think like we're always trying to reach people where we see there's potential issues? So I think we'll live in both. Yeah. So I think we'll try to sort of evangelize within the metaverse of like how to be able to move or maybe we'll create products or things in there to help aid in the physical. Yeah. I find that we'll be somewhere in the middle. I think that we'll take advantage of this new growing space that will create something, some content in there potentially. But I don't see us being like, everything's going in there. We're gonna be like that. I just don't see that. And I don't see most fitness people. Yeah. Being like that. I think most fitness people are into actually moving in real life and going out there and interacting with other people and doing physical things versus this like metaverse. Yeah. I'm gonna go out in a limb and say that we're probably gonna see more medical breakthroughs in the next 20 years that we saw. Then we saw on the last 200 years. We're on the cusp. I mean, like this new genetic, these genetic technologies is RNA technologies, the way that we're using psychedelics and studies for helping people with their mental issues. Yeah, modifying bacteria to be able to do things for us. I think in the next 20 years, we may actually find ways of solving obesity through Western medicine. Now, that's not going to solve all the problems. But the obesity issue may very well be solved with something that Western medicine comes up with. Oh, that's really going on. Well, it is. But I see what the sciences looks like. Well, 20 years from now, you got to see how far we've come just in a few years. It's it's accelerating right the whole was it Dunbar's equation or I forget what it is. But like, oh, Moore's law Moore's law. Thank you. Yeah. Dunbar done. It's a different equation. Don't ask me to describe it. I just remembered the name. But yeah, yeah, I just I just think that everything is accelerating to a point where like I every science fiction novel I've read every movie and TV series, like, it's so crazy to me that we're so close on a lot of these different ideas that were thrown out already to see 20 years from now. That's a long time to see like what society is going to look like. Yeah, it's I mean, we're now we're starting to get into like what we think the world is going to be like versus where do we see ourselves in mine pump like Well, how do we navigate it? Well, I feel like I remember we're going to be 60. So by that, by that time, I believe that we will have built and set ourselves up financially that technically nobody has to work at all, or we'll ever have to work again. And we will do be doing only the things that we absolutely love to do. And we love to podcast. I think we all have a passion for that 20 years from now. I don't know if we still will, but let's talk to you guys. Yeah, I mean, but I do think that we will have distilled what we all have worked. I don't think anybody in this room, okay, including dog, I don't think ever sees himself fully retiring. So I don't see myself retired just because we have financial complete financial freedom. What I see us doing is distilling down the things we do and based on this, the things we absolutely love to do. And I think that's what work would will look like. It'll be less about managing people and scaling. And it'll be more about, oh, I just love doing this. And we'll be doing those things. And right now, those things look like podcasting because we enjoy that part. But I don't know 20 years if it'll exactly be that way. You don't think Max is going to be sitting in your seat? I was just gonna say, I was going to be sitting in my yeah, my that would be my dream. I mean, you're right. It's 20 years. You know, my dream would be like one of my kids, right? It takes over. But I mean, that's unlikely that you know, that would almost never works that way. But that would be pretty cool, you know, to have you know, the younger generation and kind of teach them.  Oh, I totally believe we're moving in that direction much sooner than 20 years. I mean, I think this idea that we have with the kind of the MP homes, right? Then moving him into this like kind of destinations and experiences. And you're talking so I think that's in the near future. And wouldn't be that far fetched to think that one of the investments we do would be this massive property or cool place that everybody could come and meet once a year or whatever, like it's so hard to think 20 years in the future though, because like I said, when I look at the the science around longevity, it's weird and fascinating the science around fat storage, fat loss, how the body, how we can influence the metabolism and inflammation. It's gonna be really weird. And we're going to be at a crossroads if we do in fact get to the point, which I think we probably will in 20 years where we literally have exercising a pill for lack of a better term. People are going to take it or do whatever. And they're going to look the way they want to look. But they're not going to get all of the other profound benefits of going on the journey of fitness and it's going to be a very strange situation where Wow, I look good. I'm not obese. That's good. But you know, I still kind of feel lost. I don't feel as great like what's going on. Maybe they won't notice because they never were in the first place. But a lot of the benefits you get from a lot most of the benefits you get is the journey of the learning journey and how you develop the relationship with yourself and with your own ego and with exercise and nutrition. Once you take a pill that does all that for you, you've lost that all you've gained are the physical results, which there's benefit to that. But I think it's going to be put people in a very interesting position. Similar to how we imagine how much this is going to change if we lived at 120 or 130, you know, or our kids, I mean, that's going to just that's going to shake up so many things. It's similar to what we see with celebrities when they get all this money and fame and power. And then we hear about them committing suicide. Like, how could this they had everything? I thought that was the end result. They Yeah, because you're in this position and you're like, why am I not happy because it's not about that all the time. It's usually about other things. So it's gonna be interesting. I think we're going to get to a position, not just with fitness, but with everything where we're going to have everything that we want. And then we're going to be like, why isn't this enough? Like, why don't I not feel fulfilled, be preparing people fitness wise for outer space outer space. That's a good one. Make sure they go to Mars. Hey, if you enjoyed that clip, you can find the full episode here or you can find other clips over here and be sure to subscribe.


What's going on guys? So we're gonna do a little quick a live trading on bitmex to give you guys an example of How it works and what it is we do so Just to update you on what's been going on Bitcoin dropped into one of our price targets where we like to enter One of the supports that that we had That we've mentioned in our market analysis and our trading rooms as a buy opportunity So we're gonna end we we deposited it into a new account of about Think point one Bitcoin Around there And we're we're gonna we're gonna trade with it live here to show you guys, you know the possibilities of what you can do When trading on bitmex, so let's Let's look at what we have here. So we bought six thousand dollars worth of Bitcoin at 10x leverage So we're basically risking six hundred dollars We're risking six hundred dollars on this trade if we were to get liquidated But we have our stop loss set as you can see right here. Let me make sure you guys can see that. Yep So we have it set at around 11,000 own hundred and eleven the reason we chose that price is because if you zoom in here Let's go down to like the one hour. It's actually zoom in a little bit more Let's get down to the nitty gritty 15 minute mark Even five minute mark When we're scalping trades, we like to get to really zoom in To get a view of what's going on so right here You see where the low of the day is right now. It's around 1124 So really anything below 1124 is fine with us. We just happened to choose this price range We just liked all the ones 11111 seems like a good luck number to me Because I always see 1111 at all times of the day So I felt like that's the number that I wanted to set that at But anywhere below the low of the day is fine Our entry price is 11213. So we're currently about break even right now but we're just gonna watch this and And see see what happens here With this with this entry. I don't want to make this video super long either so we're gonna watch for a few minutes and And see what happens if we can make a quick profit on it. So let's let's Zoom out a bit here and see what's been going on with Bitcoin So you see here throughout the day. It was at around 11,400 It broke out right here. Let me see today at around 9 a.m. and it hit 11,000 Yeah, it looks like it got rejected 11,600 and it's just dropped all the way down So it hit 11,200 it jumped back up to eleven thousand three hundred fifty five and Then it got rejected again Back down to eleven thousand one one twenty five So we tried to enter so we entered here We had made a little profit and then it dumped back we entered on this candle. We got stopped out We had our our stops a little too tight Then we entered again on the second candle once it got back above 11,200 We just really like that price as long as it's above it.  We're still in the trade. It tried to stop us out It got very close to us. Let me see Our stop was one one one one it went down to 115 so 116 I'm sorry, so it was very close if you had your stop right up right below the low of the day You would have been stopped out That's why I always like to put it a little bit below because the market does this on purpose They always go and test that low of the day They push it a little bit because they know that they'll stop out Lots of people during that cycle and then they push right back up So now the price is back at eleven thousand one hundred seventy five point five. We're currently down About two point eight percent and we're still in the trade though. We're still holding this contract So let's see what happens here and what we'll update you in a little bit Hopefully we can turn this one into a profit right, yes All right guys another check in here. So as you can see prices back up to eleven thousand two hundred and twenty two You can see at the pop right here So that was a good nice little pop We need a pop over if we get over two fifty then that could probably take us back to the three hundred area But so far so good now an update on what we did as you can see now we're at eight thousand dollars So what we did we bought when it was a little bit lower down we we kind of averaged our position down a bit We wanted a entry closer to eleven thousand two hundred. So we bought two thousand more Two thousand USD more worth of our position So and then we use the same exact Stop so we just place the stop at the same exact area, which is eleven thousand one hundred and eleven dollars, which is about a Currently about just a Little under a hundred dollars stop our reward is two hundred our reward because our first target is eleven thousand four hundred Which is up here? So we get a proper One two or two to one risk ratio. I mean what risk reward on this? So we're still watching it, you know, we're still in the trade doing not really doing much We're up one point six five percent right now. Just yeah, why is it changing when I do this? But yeah, we're up one point six five percent right now, which is worth point zero zero one one XBT And we're just gonna continue holding here. Let's see if we can get to our target Which would be very nice for this video. We can hit it But like, you know, every trade is not a winner. So we'll keep you guys updated Alrighty guys, it is that time of the video question of the day. Let's jump right into it Remember question of the day every video will have a random question about something in the video The question will always be in a random area of the video find a question Then find the answer post your answer in the comments for a chance to win a free month membership to our trading room Winners will be picked randomly once the video receives over 30 likes. Remember guys, we got to get the video to 30 likes Good luck. All right, here we go. You guys ready question of the day is how did we decide where to put our stop loss?  We went over this in the video. So get the answer put it in the comments like the video follow us Tell your friends to your family to your grandmother to your friends and your neighbors while you give them sugar. Peace What is going on guys doing gonna do a quick update let me turn the tunes on here we go. All right, so So it looks like we caught the bottom here All right, so we've been bouncing back up nice and slow that we're still looking at the five-minute chart All right, so we're Getting back up there nice and slowly. We're currently up five percent on our position We're at eleven thousand two hundred and sixty three dollars. Remember our entries eleven thousand two hundred and six Our liquidation price is ten thousand two two two. We don't got to worry about that We have stops way before then at eleven thousand one hundred and eleven So we're looking here This was a nice break right here Above this this little area, which was eleven thousand two fifty We can get above The eleven thousand three hundred mark we should shoot for eleven four hundred So so that's basically what we're waiting for right now. We're at about six percent profit Point zero zero four Bitcoin profit right now That cover that covers, you know any stopout losses And yeah, man, we're just still in the position. We're still just being patient waiting. We still have eight thousand contracts And that's pretty much it for now, we're gonna keep waiting here seeing if it continues in our in our direction and And we'll let you know we'll keep you guys updated All right. See you guys in a few What is going on guys? Just checking back in and do another update as you can see not much has been going on here It's been pretty much just kind of barely it moved up a little bit almost got to eleven three And then got pushed back down so I'm hoping that it the 11 to 50 level can hold it here and continue this short-term uptrend right here If we go into Look at the bigger Going to the 15 minute And it's looking pretty good We caught that bounce right there as you can see it's been going up We just needed to keep to continue up basically at this point Get us back to that eleven four hundred, which is our our main first target If we zoom out a little bit more to the one hour You can see the big red candle That where we basically entered in Then we got one big green one and hopefully we see a recovery here at it to our target So we'll keep you guys updated on any other moves This trade is taking a bit longer than we want But you know we can't control we can't control when the trade happens or how long it takes to happen We can only look for the opportunities and that's what we did here look for the opportunity and now we just got to be patient and Be confident in our setup and Hopefully it goes our way All right you guys keep you guys update Hey All right guys here is a quick update. So we have now broken up and Above well, we just went a little little below right now, but we've broken up and below Up and below we're at eleven thousand three hundred every time I say that we're above it It goes right back under so we're currently at three eleven thousand three hundred resistance We're up eight percent our position For a profit of point zero zero six two Bitcoin We're still holding this position We got about a hundred dollars more to go as you can see here the high went up to eleven three fifteen so We see we can see this to continue push up to our Target which is eleven thousand four hundred We might consider taking some profits here at eleven thousand three fifty We might consider to begin taking profits in this range eleven thousand three fifty to eleven thousand four hundred range Just because it's it's bitcoins been a bit unpredictable lately, and we want to make sure to secure profits But right now we're still just holding All right, so just an update on that because we did go above eleven three hundred We're just gonna continue to hold here though What's up guys welcome back I am here to give you guys the final update of the day as you guys can see We are up fifteen percent on our trade of eight thousand contracts The price is currently at eleven thousand three hundred and seventy nine We are up Point zero one oh nine, so we're about a hundred and twenty five dollars in profit on this trade As you guys can see we have our first target right here We have a we have the order already set so we can actually bring it down and take profit in this range Because as you guys know it like we always tell you Training is not an exact number. It's just in the zones. So we're ready in the zone to take profit So we could definitely take profit here The way we take profit is that we always use about take about twenty five percent of The position that we have currently we take about twenty five percent off and then what we're gonna do is we're going to Trail use this trail stop. We're gonna move it up probably tell about Thinking about this range right here It's probably the range. I think I'm gonna we're gonna put our stop losses for now and of course if We could get rid of one of the two thousand since we're gonna take profit So we could bring this one up as well Boom so we've moved up our trail stops with the remainder of the position plus we're taking profit with Two thousand so that's twenty five percent of our positions. We're gonna take profit now that we're already Fifteen percent in profit and that's basically it guys. So I hope you guys Learn something here You know, we wanted to give you guys a live trade so you can see exactly how it is that we do it step by step Everything it is that we do here It's not that difficult.  Alrighty guys. Thank you for tuning in. Make sure to follow the channel. Make sure to Hit us up in the comments and leave an answer for the question of the day till the next one, peace


A video posted on social media shows the moment a child was rescued from a dangling cable car in Pakistan on August 22. Seven students and one teacher have been stuck in the cable car since 7 a.m. When they were traveling to school in a remote mountainous area in Badagram, about 200 kilometers north of Islamabad, officials said. Pakistan's military has rescued two children out of eight people trapped in the cable car after a line snapped. The cable car became stranded halfway across a ravine, about 274 meters above ground, and was dangling by a single cable after the other snapped, Sharik Riyaz Kotak, a rescue official at the site told Reuters.