All right, cool. Ooh, that's a little bit loud, huh? What's up, everyone? Thanks for joining the last talk of the day. Appreciate you all. If you're looking for 17 metrics, I reduced it down to seven. Make it simple for everybody. But yeah, more seriously, seven metrics that matter more than coding time. Coding time is a metric that I've talked about often. But I think there's some other ones that I really want to dive into in this session that will be more interesting for you all. But a little bit about myself. My name is Dan Lines. I'm one of the founders at Linear B. I also founded the Dev Interrupted Community. So I'm very grateful for that. I'm the podcast host. I get to talk to all these amazing people from different organizations, companies, really smart people. Usually what they're talking about is something around developer productivity or let's ship code faster. And that's the kind of stuff that I'm into. So some of the metrics that we're going to be talking about today is in that vein. And hopefully give you some tips of how we can do this better as a community. That's my goal here. Kind of an ironic thing. So our job as developers is to build, is to create. That's when I get the most enjoyment out of what I do, create something, create something new. But the thing is, and we'll get into some of the data, there's oftentimes not enough time spent on coding, especially if you're working in a professional job. Maybe it's your first job out of school. You might think, oh, I'm just going to develop some amazing stuff. But you find out that actually sometimes the majority of the day is meetings, updating tickets a lot. In the code review area, which we're going to talk about planning, retro, design reviews. And sometimes it might be a 50-50 split. But some of the data that we have, it's maybe like two and six hours. Maybe it's a little extreme, but something like that. And the thing is, there is a million developer tools out there. You can find anything that you want around the developer tool if you want to code faster. GitHub's got a bunch of cool stuff. Co-pilot, I'm sure everyone's checked it out. If you want to code smarter, IntelliSense, if you want more security, there's a million tools out there for security. Code less. There's probably too many tools, everything that you want all of the time. But what I've kind of seen is, as an industry, I think we're now optimizing the wrong bucket. There's enough developer tools out there, but there's other stuff that's going on. The meetings, the housekeeping, the ceremonies that you get into, and especially the code review process. That's something that I'm passionate about. That's where I think we need to spend a little bit more energy. So when we're at our day job, we can actually spend more time coding. And that's what this talk is about. So pull requests. Show of hands. We like pull requests. We don't like pull requests. Somewhere in between, thumbs up. Yeah, we like them. OK. Merge requests, anyone? Or are we all a pull request camp here? Pull? OK. Yeah, so it's like kind of a, it depends on the audience, but can't live with them. Can't live without them. I actually think they're very good. But there are some people out there that are saying that we should get rid of them. So it's kind of depends on the audience here. Typical day in the life of a dev, I remember being super pumped to solve any problem. Hey, I just solved this really, really cool problem. I want to go get it merged. I want to go get it shipped. That's what would make me feel really good. I can move on to the next task with a clear conscience. Does that happen all the time? So I'm saying not so fast. Does anyone have, has anyone heard the terminology cycle time before? Yeah? OK. Maybe one. So cycle time is one of those interesting metrics that's really popping up within the engineering world community. It's one of those Dora metrics. What does it measure? It depends on who you ask. In this talk, what it measures is, OK, I've created a branch. I'm starting to code. How long does it take me to go from coding to deploy to production? If you don't know this metric for your team, it can be something that's interesting. There's a few metrics within side of cycle time that are also interesting, like coding time, which was in the title of the talk. But we're not going to focus there today. PR pickup time. So when you do kind of finish your branch, you open up a PR. How long does it take to get picked up? PR review time. How long does it take to actually get reviewed? And how long does it take to get deployed? That's what cycle time is. And here's five metrics for you that I think are fairly important. But what we see in the community, where do we have the bottleneck? It's actually not in coding time. So coding time is looking pretty good. We have a linear B labs thing I'm going to show you where we get to analyze all these PRs, all this data is from the community. So coding time is actually going very well for us. In deployment time, probably depends on where you work, but it's getting better and better. There's so many tools now to help us get software out in a more efficient way, get the code out. That middle area of I need a reviewer. I need to finish my review. This is not going so well for us. It's the red areas up here. This is what's taking a long time. And so this is what I was just mentioning. So at linear B, we're fortunate enough, we do have a labs team. We're coming up on analyzing about a million PRs at this point in growing. So that's where the data that you're seeing from this presentation is coming from. 25,000, 30,000 developers in growing there. And what we find with pull requests is they're actually idle most of the time. And what does idle mean? No one's doing anything with them. They're just sitting there. I opened a PR. I'm waiting for a review. Or let's say that someone has actually done the review and maybe they gave some comments or a merge request, or sorry, a change request, then it's sitting there waiting on me. So 50% of PRs are idle 50% of the time. 33% of PRs are idle about 77% of the time. And it's not a good thing. You can think of idle as kind of being like swapped out in memory. So if I open a PR and I'm waiting and waiting and waiting, it's going out of my mind. I'm on to the next task. I don't get paid usually just to sit there, maybe sometimes, but most of the time I move on to my next task. I'm developing something. I have this PR sitting there. It's degrading. So it's a very bad thing. And in this talk, I've separated out two kinds of idle time. At the top, what you'll see in the slides is maybe like a standard flow that a PR goes through. I'll pretend I'm the first person. I open up the PR and then I wait. I'm trying to find a reviewer. Maybe I assign a reviewer. Maybe I'm posting in Slack. Hey, can anyone take this? Someone might find it the next day, get some initial comments. Maybe the PR's large and they have to take a break. Maybe more comments. Ask for a change request. Now it's the next day. I come in, I make some fixes. Maybe I make some more fixes. I say, is this good? Another day goes by and eventually it gets merged. Takes a lot of time. Now in that process, there's a transition time and there's a distraction time. I'll describe the two different times here. So in transition time, this is more natural of how PRs work today or MRs work today. I open the PR, I need someone else to review it. There's an inherent transition time. It's just a handoff. Not much maybe that you can think that you can do about that. There are some things that I think we can do. But it's kind of just natural in the process. And it happens because, and I'll talk about it a little bit later, we're kind of treating all PRs the same as an industry today, which I don't love. We're gonna get into some solutions for that. But when I say we're treating them all the same, it means I'm opening a PR and I'm waiting for a reviewer to come review, no matter what the size or what the complexity is. In large PRs tend to also not be a so good thing. They take longer to the review. No one wants to pick them up. Try opening a large PR on a Friday. See if it gets picked up.  Maybe even on a Thursday, actually. And so this transition time, it just adds delays and it's between two people. Now the other type of time or idle time is distraction time. And this is within one person. It's like, it's just me. It can happen because of interruptions. So for example, I start my PR review. It's a large review. I need to take a break. I might get pulled off to an urgent task. I might wanna go get some lunch. Now I have to do a cognitive reset, cognitive reload. I come back to the PR. Do I pick up right where I left off? No, I have to do, okay, what was I doing here again? What was this thing about? So this distraction time, it adds up and it adds up and it adds up. And these are some of the reasons why the PR process is taking so long for us. So it's like no one really wants to pick it up. There's an inherent transition back and forth between two people. And then once a review starts, especially if it's a large PR, it's not gonna just finish immediately, okay? The other thing that our data shows is that delays actually cause more delays. So it's that type of situation. If you open up a PR and you don't get someone reviewing it day one, like that same day, it's not a linear growth. It's more exponential of how long it's gonna take for it to get merged. So one of the tricks, and you might know this, you might not know this, or you might not even been thinking about it, if you're able to get your PR picked up for review within the first hour, that's best case scenario. Oftentimes, you'll get it merged the same day. And if you're unable to do that, then the time goes up and up and up. Makes sense? Okay. So here's what I want to get to. I think there's a holy grail, and I'm calling it continuous merge. And some of the concepts of continuous merge will get into them, but let's give more of the power to the developer to decide how their code goes through the review lifecycle. Other concepts of continuous merge, let's not treat everything exactly the same. Okay, let's start splitting up and we'll talk about it a bit here. Now, when I talk about continuous merge, some people might say, you know what, do we really need PRs? Do people think we need PRs by the way here? You think we do. Okay. There's some people out there that are saying, hey, we don't really need it, just use your CI, let your test pass, that type of thing. I don't think it's, I think it's smart, but I don't think it's appropriate for most situations. There are some projects that I think we could get away with no PRs, but that's not something that I'm advocating for here. So everything you'll see in the rest of the talk is saying that we do need PRs, even though I want to change a bunch of things about them. So yeah, like I was saying, I think pull requests are actually here to stay. I think they are beneficial. There is some data out there that shows that peer reviews detect about 65% to 80% of bugs. So that's a quality super, super important, should be top of mind for everyone. I do think it's a good way to share knowledge. I do think it's a good way to increase maintainability. A lot of the feedback that you'll get on your PR, it might not be, oh, this is gonna bring down production. It might be a maintainability thing. Hey, if you did it this way, or what's the test patterns look like here. And the other thing that's happening is, I don't know if everyone's noticing, but there's more and more developers entering the workforce. Like the amount of developers that are in the workforce is increasing at a fairly rapid rate. I think PRs is a really good way for that onboarding, coaching, especially with juniors. So definitely an advocate for them, not a detractor. Now, here's some of the interesting stuff and some of the takeaways. So what have we learned so far? In cycle time, which is one of those metrics that I think everybody should know, the bottleneck is in this PR process for most organizations. But there's things that we can do to optimize. So the first thing that you'll see on the left-hand side of the slide, adding context really, really helps in two ways. If you add context to your PR, you're gonna get a faster pickup time. So people will be more willing to review what you put up. And actually, our data shows that the review is done faster, the actual review portion of it. And there's two pieces of context that I think is kind of a minimum that should be there. And I see really good results. One is what is the priority or what is the ticket? Is this a bug? Is it not a bug? Is it a new feature? Are you refactoring something? Give someone the piece of context of what are they getting into? If someone doesn't know what they're getting into, they're very unlikely to just start if they have low energy. So I don't know what I'm getting into with this PR. Okay, I'm gonna do it tomorrow, tomorrow morning, right? So always provide that type of context. The other thing that I think is maybe obvious, but kind of innovative actually, provide an estimated review time. Here's how long we predict this PR review is gonna take. Is it gonna be five minutes? Is it gonna be an hour? Is it gonna be a half an hour, 45 minutes? What does that do for the reviewer? It does something really cool psychologically. Let's say for example, it's like 11 45 a.m., team's going to lunch at noon. If I know, if I put a PR onto your plate, for example, and you have an estimated review time of five minutes, you might say, hey, I can get this in before we go out, okay? And that's a way for me to get my PR picked up faster. Of course, it needs to be accurate. That's the point of it. But also it does a service. Let's say that it's a 35 minute review. Well, I actually don't want you starting that PR review. That's like a disservice to the reviewer. Oh, I'm gonna start it. Then I'm gonna get pulled away. Then I'm gonna start it again, let's say after lunch. And now I have to go back from the beginning. It's not really, you don't really pick up where you left off. So providing that context super, super important. I really encourage that. The other thing is just measure. How many, like I know, okay, let's do a raise of hands for developers in the room, devs, okay. Team leaders or managers, anyone like that? Yes, someone. What I was saying when we were chatting in the beginning of the talk here, there's a bunch of tools out there that allow your team to have visibility into where the bottleneck is. I highly encourage measuring just that cycle time to start with. Some teams that I see have a problem with picking up the PR, which again means I'm here to start my review. And other teams have a problem once the review starts, how long that review takes. You might have both of those problems. You might have one of those problems or not. So measure, so it's a good thing to talk in like a retro, hey, why are these reviews taking so long and this repo versus this repo, let's reduce it. And the last thing is around communication. So I'm gonna talk about this thing, worker B. I've been working on a suite of tools under the umbrella name worker B. So that's why you see it here on the right hand side. And one of the things that I think is really important if you don't have it today is some type of messaging service that's at least saying, hey, you've been assigned this PR or hey, this PR has been approved, you can merge it now. There's some more advanced things in there that I'm gonna advocate a bit, but at least have some, we call it worker B for linear B, but at least have something that's communicating back and forth, yeah, okay, makes sense. Another thing, and I think this is really, does anyone read the Martin Fowler blog? You all check that out ever? Okay, someone posted something. I saw someone say like maybe I read it. Someone posted this ship show ask concept. I have their name here, I'll do a disservice if I pronounce it. Ship show ask, what does that mean? It's the concept that not every single PR needs to go through. And they're actually not even talking PRs in this, but not every single piece of code needs to go through the same review cycle. So for example, a piece of code that's very low risk, maybe it's only documentation change. Why is it going through the PR cycle? In a review cycle, it's bottlenecking, doesn't need to. Now on the other end of the spectrum, maybe you have a 500 line, a thousand line, hopefully not but let's say 500 lines of code change in the PR, maybe that needs two reviewers. But for some reason as an industry, mostly what we're doing is one reviewer for every single PR. And so here's a concept to start classifying by risk type and saying hey, some of these PRs, maybe we can auto merge them, documentation only, for example, test change only. And some other ones, maybe they need more review. So this is a really cool concept that I'm into. I'll talk about it a little more towards the end of the presentation. The other thing that I wanna say, I've said it a few times during the talk, but I cannot emphasize enough how important it is to keep your PR small. Like that's, if there was one, probably one takeaway from this talk, keep your PR small. That actually helps everything in the cycle time process. Your coding time will be smaller. The pickup time, someone, how excited am I to come and do your review? I'm telling you if it's big, I'm not excited. If it's small, I think I'm gonna do it. The amount of time it takes me to review much, much less and the amount of time it takes to merge much, much less. So this is a behavior that we've seen over and over and over again in the data teams and what does large and small mean? Usually 150 changes or less, that's good. Anything over that, you're not gonna get like good performance in terms of getting your code out to production. So you definitely wanna keep your PR small. This is what I was talking about in terms of context, adding the estimated time for the review. So what our data shows, again, we're at about a million, I think it was like 900,000 PRs that we've analyzed so far and starting the climb up to the million range. What we've seen is PRs that include this estimated time of review do so much better on the pickup time. So like a lot better on, oh, I do actually wanna go review this or again, maybe I can do it before like in this five minute period of time before my next meeting or even better, thank you so much for telling me how long this is gonna take.  This is actually a game changer even though it seems simple. It's like when you read a blog, it tells you how long the read time is. Yeah, so you can determine do you wanna read it or not. This is something that I really encourage to get into all of your PRs and of course what the graph is showing is the ones that are very small get picked up really quickly. If you have like a 15 minute review time or less, you're golden. So that's what you wanna get to. Okay, this is interesting. So we talked like pretty briefly about the Ship Show Ask concept but really what it is is a concept of let's not treat every PR exactly the same. We can start having classifiers for PRs and we can take different actions based on risk, priority, where we want our efficiency to be for our team. So one of the tips here is why don't we start creating a fast lane for the right PRs? Doesn't have, I'm not advocate, like quality is number one but even if you go back to your team and you say, hey, if I'm just making a change to documentation or if we're just making a change to let's say you might even be a little more risky images or I'm just doing test coverage or test related changes, could we get those into a fast lane type mode where either they're auto merged or they're prioritized? Teams that do this, it makes a big difference. So I highly encourage, it's a little more advanced to define a risk model that would be the next situation if we could say, what's the security risk? What's the test coverage? Did the test pass, did the test fail? Are we changing a sensitive piece of code? Now I have a full model that I can decide what to do but just start with like a fast lane, right? It's like when you go to the airport there's probably not many people remember when there's like one line and there's like three lines. I don't know who has the clear but I have the TSA pre, right? So you start getting less risk it through sooner. So you should really encourage doing this. Another tip that I have is and this is a little counter-intuitive. So one thing that I do like about pull requests is I can put a PR up and maybe someone else in a different time zone or someone else on their own schedule can review it whenever they're ready. Like that's cool, I do like that. And it's great with open source, all of that totally makes sense to me. But we did find something out that's again a little counter-intuitive. If you know when your teammate starts reviewing your PR so think about this concept, I'm coding so like I put up a PR, now I went on to my next task and I'm coding which is great because we're working in parallel. If I know that my teammate has started my review, I'm not saying stop what you're doing. I'm saying be available because if we go back to that transition time, if they're commenting or asking for code changes and you're not getting to them immediately, you're getting them to the next day, it takes much longer for your code to get merged. So if you're just okay, I know that they're reviewing it right now, maybe they'll ping me on Slack, maybe I'll see an email message come in, whatever it is. If you're available to actually do, like make the changes or answer questions, that's a really, really good thing. So highly recommend it, know when your teammate is reviewing your code. So I mentioned that I've been working on a few tools under the umbrella name of WorkerB that kind of does some of this optimization and routing. I'm experimenting with a few concepts. I'll show you what's available today and then I wanna give a little sneak peek into what's coming next and then we'll close it out here. So the first thing, we have something now, it's the fast lane concept that I was talking about before. So code changes or pull requests that are only affecting one file and are five lines of code changed or less, which means you can view it in a small snippet. We started to send them in a Slack message to the reviewer and saying, hey, this is a really small one. Could you give this a look right now so we could keep the pipeline moving forward and just approve it. Now you're still going through a review. It's not an auto-merge situation. You're still going through a review, but it's so tiny. There's no reason it needs to be bottlenecked but behind these really big reviews. We've had a lot of success with this. So this is one of the things that our WorkerB includes like a chat bot on Slack. So if everyone on the team installs it, it would say, hey Dan, small change assigned to you could you just take a look at it. Bam, it gets through. Teams are really liking this. So this is kind of like I would say a version one to that idea of having a full model of classifying pull requests. And this is going great for us. Another thing that we added in, it's probably common sense, but after the approve happens, why not just get a message to say, hey, your approval went through. Do you want to merge this? And now we can actually get the code into the main line. We stopped degrading as code stays not in the main line. I think it's older and older and older. This kind of completes the flow. Also I've had great success here. This is an interest like very, I think, probably my favorite tool that I built so far with the team. It's called WorkerB for pull requests and it's a Chrome extension. It's working with Chrome and GitHub right now. And it does a few things for you. It allows you to promote your PR within Slack. So a common pattern that a lot of teams have is I don't necessarily assign a reviewer. I'm kind of asking in an open Slack channel, hey, is anyone available to do my review? Well, what happens if you have this extension on GitHub, you can click on something that says copy link. And when you click on that copy link and you post it into Slack, it opens up your pull requests in a really nice way and includes the estimated time of review. So I'll say like five minutes, two files change, two commits. And you can add a little message. It seems simple. We have teams that are like adopting this like crazy because like I said, with that estimated time of review context, now everyone can determine, oh, this looks like well put together. It's easy to pick up. I'm gonna take it right now. So if you're interested in really getting your PR, like picked up faster, providing your reviewer in more context, this is what this Chrome extension does. The other thing that the extension does is when someone starts reviewing your pull requests, it will let you know. So I think everyone's probably used Google Docs when you're both on the same file. You see those little avatars at the top. That's what it does. It will pop up. Someone's GitHub handle say, hey, this person's reviewing right now. Please be available. And this little extension is allowing teams to get code merged much faster. So that was another thing that we built to try to address some of these problems. So here's something much more advanced that I'm working on that I wanna give everyone a sneak peek into. Happy to talk about it after. So the other, the previous two things that I showed you, like they're GA, like live, you can go and use them and all of that. This is a sneak peek of something that I'm working on. We're working on creating a configuration file that teams can put on top of a repo that have some of those out-of-the-box rules that will help route PRs based on risk. So for example, if you start using this configuration, we're gonna say, hey, will I identify anything that is just a documentation change or anything that is just a test change? And that's gonna go into the auto merge category. As soon as that PR is put up, the team obviously agrees on this config file. That's just gonna get merged. Pull requests that are X lines of code and one file, you're gonna get into that fast lane where the chat bot's gonna say, hey, could you review this right now? Then you have kind of your standard PR, which is, okay, let's say it's 150 lines or less. There is some risk from a security standpoint. Let's go through the normal PR process there, one reviewer. And the other thing they'll do out-of-the-box is say, okay, let's say it's 250 or 500 lines of code. We're actually gonna recommend multiple reviewers for this. And the Slack bot will coordinate this. We'll look for the previous code owner plus the reviewer that you assigned. So the reason that I'm so proud of this, I think it's one of the first time in history that we're kind of saying, hey, PRs, they're a little bit different. Let's classify them and let's take the appropriate action. The other thing that will come with this feature set is each developer on the team can install a plugin on their IDE and while they're coding, it will let them know what lane they're in. Hey, you're in the auto-merge lane. Up, you just cross into the fast lane, but if you wanna get back to the auto-merge lane, this is what you need to do. Oh, you just crossed over into the two reviewer lane, but if you make your pull requests much smaller and you have 100% test coverage in your test pass, you can be in the one reviewer lane. So it kind of gives that instantaneous feedback to the developer based on the rules that we saw on this last screen that the team has agreed upon. So now every developer knows kind of the fate of their PR. It will also give you the estimated time of review and estimated time of merge. But this is, I just wanted to give everyone a sneak peek. This is the next stage that we're working on here. So yeah, I mean, if you were digging what I was talking about here, I kind of just have a call to action, like let's all improve. Like I said in the beginning, I am the founder of the Dev Interrupted Community. I am the podcast host. If you wanna come on the pod or you know someone that would be good to talk about this type of stuff, hit me up. If you want the Worker B for Chrome extension, that's in the middle there. You can just type Worker B for pull requests or you can go to the Chrome store and do that. Also, here's the link, it's linear B. So that's my company, Linear B. Linear B.io slash Worker B for Chrome onboarding. It'll kind of give you some information there. And lastly on the right hand side, we do have a platform called Linear B. This is four teams. And by the way, like this stuff is free. I'm not, everything on here is free. We do have a platform for teams. It will show you your team cycle time, where the bottlenecks are, where they're not. And it will give you that Worker B chat bot that will start coordinating between each developer. It will give you the fast lane stuff and it will give you that estimated time to review and to merge. So that's free as well. It's app.linearb.io slash register. And just wanted to say thank you very much. I know it's a Friday end of the day and appreciate you all. I'm open for questions if you haven't. It does, both, yeah, yeah. Yeah, sure, exactly. More clicks lead to, I'm gonna put this off to later. I'm gonna do this Monday. Yeah, sure. We have a few different modes. We can use a personal access token, which will allow you to have a little more customization of what you wanna give access to or not. So for example, if you're an individual developer or maybe you just wanna try it with a few people, you can restrict it. And then, we are a business, right? That makes money. There is a team version where you can get, it's more like the global authorization, usually an admin will be doing that. But what's nice about that is then everyone on the team is already authorized and then can just start using. So we kind of have like progressive disclosure, depending on who you are. And with the, I really recommend the Chrome extension because it's just like really, it's kind of like a taster.  We've been talking about that. Yeah. So we don't have the CLI yet, but what we've found is actually developers are all working like a little bit differently. So it's like some want the CLI, some like the Chrome extension, some like a Slack bot that's like their little buddy to remind them, some like it like in the IDE to say, actually I didn't mention it, but in the IDE in that extension, we're also gonna have a button that says open pull request now, like just open it for me, right? So we're kind of trying to go around the whole ecosystem. No, they don't have any tastes or preferences. Sure. There's two things that come to my mind. So what it seems like for you is you're having a hard time getting a review. And for example, if you try this Chrome extension, this worker B for pull request, it does entice a review because what it's saying, if you are creating small PRs and doing things the right way, hey, I really have my stuff together. It's not gonna take you that much time, but I would appreciate this review, right? So some of these tools that you can use, and even if you use the one on the right-hand side, that will actually ping your colleague in Slack and say something like, hey, he only has a little tiny review for you, could you review it now? Or it might say, hey, it's a bigger review. But, so you can do all that. But the thing that came to mind for me, I've been actually experimenting with a routing rule when I was talking about PR, a routing rule called the time bomb. And what does it mean? It means, okay, we have a rule that the PR is open for 48 hours. And anyone can review during that time, and if a review starts, the bomb won't go off. And bomb's probably not the best word, but you know what I mean, right? But if it gets to 48 hours, hey, I can do a self-review and I can merge it because I don't wanna wait. I think I have high quality. You put the power back in the hands of the developer. So one of those rules that's kinda saying like, hey, it's open to the team, I'm showing it to the team for the review, but if no one cares to get to it or doesn't have enough time, let's get the code merged and get it out there. So you might like a rule like that for you. Yeah, so we're debating whether to put that as a default rule in that YAML file or not. We're gonna come up with a few different rules. And then it's probably obvious, but you can edit the rules and you can do whatever you want with that. I can read what you're saying. I saw a sign go up. Oh, okay, one minute left. Yeah, no problem. It is a culture thing. And the thing on the right hand side, the linear bead.io, people are using that for retros because it brings data. Your culture is displayed in data. Hey, we're not getting to these PRs. Is it a good thing? A bad thing? Is everyone cool with that? Are we not cool with that? So data visibility is a good thing in the culture situation. All right, well, thank you, everyone. Guess what? My time is up.


Hi everyone, Joe for Chaspis case breaks calm coming out to a 2021 tops chrome formula one racing Chrome pretty good stuff. We got two boxes of light and one box of hobby This is three box random team two. So it's basically a hobby light mixer all card ship There's all the the teams right there big thing to this group here And there are the teams right there So it's a it's usually the f1 team paired with like another f2 team or something like that or in all It's also paired with bw2 bwt, but You get it big thanks to this group once again for getting in on the f1 action season starting soon Let's roll it randomize it three and a two five times for names and teams one two three four and five and Will I'm gonna show you the boxes in just a second to see if we get a visual look After five we got chance or chance deekman down to Ryan case and Chance down to Ryan three and a two five times for the teams one two three four and Fifth and final time after five we got Ferrari down to McLaren All right chance. You got Ferrari Brian with Haas Ryan with Aston Martin Steven with Renault and BWT Will you got Alphatari? Michael with Williams racing Craig with Mercedes AMG will with Alpine Steven with Red Bull Will with Alfa Romeo and Ryan with McLaren Let's alphabetized by team name and there are the two light boxes right here And the hobby box sitting back there. So we're gonna pause the video when we we pause the video When we come back, we're gonna see if there's any trades and then we'll have the break stick around BRB All right, welcome back everybody. No deals were done. So that list right there remains the same Thanks for hanging with me on a Thursday night. Appreciate it So let's do the that's the hobby box. Let's do the light boxes first I wish they would Distinguish it a little bit, but I guess the light boxes will tell you that you have ray wave pair ray wave Parallels. I wish it was like a different color scheme or something. It's a little too similar Good luck, everyone. Good luck. Good luck. Good luck. Thank you. Thank you.  Can you tell by that picture right there? Do you know your F1? Wonder if the price on these boxes will is wondering if the will have a similar trajectory to last year's I Don't know. I think that I think the cat is out of the bag. I think people know F1 now Especially cuz of last year All right, looks young looks like an F2 guy says Edward riffer saying young guy. It's No, it's David Bravio For Alpine is he is he a driver? Yeah team principal looks like Yeah, currently the racing director of the Alpine F1 team. There you go. And that is for Will Driggers. Will All aboard the big hit express He doesn't kind of young that and I don't I don't know if it's a younger picture if the he's 57 or if the Maybe the plate is helping him out just Software features on the plate All right, let's go ladies and gentlemen. There's Sergio there he is again. I see it looks a little bit older right here, right? There's a lot of cart here one Let's so we'll have our shipping team sleeve and top load or top load all these just an inch to time but Let's set that guy there. There's Sergio Perez checkerboard So we've got a podium path to the podium insert Louis Hamilton George Russell who's now his Now his teammate right I think Bota's Sebastian Vettel to 399 I'm gonna be falling trying to follow. I'm gonna attempt to fall Lando a little more closely this year And McLaren Here is Max for stopping Grand Prix driver of the day We're in the oh the three-way span the anniversary Grand Prix. There you go. Nice silver there for Stephen Sebastian Vettel for Aston Martin to 49 out of 399 That'll be for Ryan another ray wave Max for stopping Lewis Hamilton pure ghastly Checkerboard or X-Fractor have you want to call it? Max for stopping for Red Bull that'll be for Stephen These are one of the exclusive parallels here. That's pure ghastly for alphatari alphatari for will Lewis Hamilton and Another ray wave of Lewis or check that Max for stopping once again for Stephen and Red Bull Mercedes is Craig Craig has Mercedes AMG. I like the the trophies that are outlined like the Like the course there's Lewis Hamilton silver Grand Prix winner in sterion Not sure where that is, but there Kind of get got a little into a little into the F1 last year trying to get more into it this year still Still a bit of a rookie, but breaks like this definitely helps me get familiar with names It's me learn Some of the drivers some of the courses and I like auto racing in general so Can appreciate the principles of Of all that a couple max for stoppings right here Lando Norris McLaren It's I think that's the team I'm supporting this year. Just I just picked one randomly Lando Norris is pretty fun He had a live stream of him playing PJ 2k The other over the weekend thought that was pretty fun. I like playing PJ 2k and we've got a green ray wave for John Luca Petkoff pietkoff for F2 compos racing 99 out of 99 Was F2 compos that is comboed with Alfa Romeo that goes to will There's a Lewis Hamilton Grand Prix Bahrain winner And that's a Silver refractor right there. All right first light box second light box coming up Yeah, that's one thing that I maybe maybe I'll maybe I'll work on that this weekend just because the You know, that's that's a good primer or that's a good warm-up to this upcoming season, right the first F1 match Saturday March What do you think? And I think we we as in a we as in Americans we America got I'm pretty sure we got two races here in the United States and I think Austin was already one of them and then Miami I think is the is the second US race. So that's pretty cool, too. I know that Netflix documentary has definitely You know has definitely just raised the profile in the interest of F1 here in the United States Guys, I have some buddies that are really into it have been for a long time and they were like, yeah, that that F1 series You know really boosted and then and then obviously pandemic came around and people were Digging all sorts of stuff, you know, so I did not watch the Kanye documentary on Netflix Is that good? There's just too many things to watch. I like Kanye, though I'll watch that. I'll find some time for that documentary Chances, they're thinking of adding Vegas next year. That would be awesome. I would definitely go to that Not not too far to travel for us here in LA Find it here, but I'm sure I can find it. I'm blanking on this on this guy's name, but I did read a great book Great great formula one book Mazpin out There's Landstroll Rey Wave more about Terry Botas We got a for F2 MP motorsport Richard a verse score. I Like this sort of X-Factor checkerboard pattern here. Oh, the book I read is called total competition by Ross Braun and Adam Parr I think Ross Braun Handle a lot of those Those shoe-mocker teams back in the day, right and I think maybe like, you know in F1 leadership now at this point That's purple Lewis Hamilton. Nice. Here's a rookie refractor Another Lewis Hamilton Sergio Perez O'Conan. There's a Lewis Hamilton in Portugal There is formula one freshest rookie car Yuki Sunoda One of the one of the younger guys out there. He races with Alpha Tari and that's gonna go to Will Driggers There's Max Verstappen and Abu Dhabi There is Lewis Hamilton purple 307 out of 399 And there's a Max Verstappen right here Red Bull racing honors Right. Yeah, so Ross Braun. Yeah legend, right? I think Adam Parr in his own right I think is is involved with the racing or is known in racing Journalism or something like that But yeah, total competition lessons and strategy from formula one I kind of blindly picked it up just because I wanted some formula one content. I sort of audio audio booked it Another refractor right here in Turkey But it's pretty good kind of kind of sort of like a a lot of great F1 stories and some and some sort of like I guess Leadership like stuff that's in there, too without being too without being too cheesy There's Lewis Hamilton ray wave For Mercedes Craig with that one Craig getting a lot of the all those all those Lewis Hamilton's add up some more than others I would guess Max Verstappen in the ray wave pattern there is another some more color for Lewis Hamilton and there's Lance Stroll Ray wave and there's Lewis Hamilton 162 out of 399 that is for Mercedes, of course, that'll go to Craig So I'll have to look that up chance Adrian Newey is the head of engineer for Red Bull and designs their cars That's a great book as well. All right, so those were our two light boxes a lot of stuff in there and now for so light has four and 16 and then Hobby has four and 18 plus the chance at autographs Not guaranteed every box, but we got a chance called how to build a car Okay, I have to look that up that sound when did when did that book come out? Yeah, it's pretty pretty crazy what goes into What goes into an F1 team building the team building the car building to all those specs I think the The tire management has always been Sort of a really fascinating thing to me because you only have like a Few tire compounds Right for a couple different situations and you only have X number of tires that you could use in any given I Think through qualifying and the actual race. I think you're only given X amount of tires, which I think For like NASCAR that might be sort of unheard of Having just a small number of tires I can use for your entire race The NASCAR races are a little bit longer too, but still I want to say most I have to see I gotta think of a better part of the field does does end up Does end up finishing the race and there's the auto and It's for F2 Carlin's Dan Tictum Autograph so maybe an up-and-coming star here F2 Carlin that's the Alpine Carlin combo. That's for Will Driggers. There you go Will Yeah, chance is right. Yeah from the races I've watched It's not like NASCAR where like in the Daytona 500 like half the fuel can get wiped out You know and out of 30 drivers or whatever, you know, maybe 40 drive There's like only 15 finishing or whatever. It's a little dramatic, but you know what I mean But I think for the most part Most of the drivers do do finish and that's one of my something my friends tell me that that that like on that show It doesn't it does really kind of overemphasize like The the drama in there to the point where they're just like, yeah I'm just like half the field gets wrecked and they're out and blah blah blah All right, some more of these sort of base Hamilton's and Verstappen's But as a percentage I'll bet I'll bet NASCAR loses more cars in races Then then an F1 I feel like I Feel like if anything it's either It's either the car breaks down and that's when you'll lose a car It's not I feel like wrecks don't happen too often I feel like the car breaks down more often or they'll just be driver error Where they where they slide off the track or something like that and then they wreck it's like these solo crashes It was Mick Schumacher Chance is also in crazing with tires this year's they're skipping compounds from medium to soft So it should be really interesting. Well, that is interesting. Wait, so what are the? tire compounds now is Just it's just wet and then hard. That's it. Is that what you're saying? Yeah, that Mick Schumacher rookie card Going to Brian Croft and Haas There's Lewis Hamilton another Lewis Hamilton. We got an orange. This is a nice one, too We got an orange George Russell For Williams racing nine out of 25 Nice low number on that Michael Estrella with Williams max for stopping refractor You got Nikita Mazepin purple We will not be seeing him this this season They have C1 C5 through C5 and for the first race hard to C2 medium C3 soft C5 And switch those up and track to track, you know, let me actually Top load it and you don't see those these low numbers too often Now remember all card ship. So whoever you have, you know, it's worth looking at like Sebastian Vettel's and whatnot It's worth looking all of these up Because you may be surprised at how some of these may go for a secondary mark at 009 at 399 That is Richard Vairscore for MP a motorsport, which will be part of the scoot Yes, good at a Ferrari combo for chance And there's Lewis Hamilton.  That was another break of 2021 tops chrome formula one Yeah, that was a pretty good box, right?  So we've got plenty of F1 here on personal breaks and all that sort of stuff So keep buying in because because we we only just started dipping into a couple of fresh cases of light and hobby Another three boxes in the store F1 season coming up a good time to collect all the stuff and then watch races with us You know, we'll be watching the races every week and we'll be talking about him So you might have some of these cards in your hands and and we can talk about them See if you know any of your drivers win Maybe increase the values of what you have should be a fun season. I'm Joe for jazby's case rakes.com and I'll race with you Next time. Bye. Bye. Bye


Toga burundi, iri kwa moerfumbili na kumina sita, mamizu asaba iwa kini mefikau kumizu amunane. Mini kwa sija kwa buki imbezi wa kotege mea nisa idiwe chakura. Wabirikacha wa kwa chi ya apu. Faw, ya niti rifatu na kutu kia wana kambiya, ando tege neza zingine ma shamba. Maizu ma shamba na mii ni kwa fukana ii, ni kwa wai kufikau.  Njo nasali na kumbuka tufanizi ya ka sukuma na spinach na kitungu. Faw is part of that delivery, where we are targeting to improve people's self-reliance, so that they can be able to take care of themselves throughout seasons and especially during this time, this difficult time. We are still encouraging our beneficiaries to continue strengthening their resilience, their self-reliance, so that they can be able to have enough food to eat, enough food to sell and improve their nutrition at household levels. This is what most faith me and my colleagues to contribute in the small parts, the assistance, the solutions, the protection to the refugees and to other persons of concern to UNRCR.


In this video, we will talk about nuclear size, particularly nuclear radius and its density. From Rutherford's Alpha scattering experiment, where he took a thin foil of gold and we can see one gold atom over here with its nucleus right at the center. This thin foil was bombarded with alpha particles. Alpha particles being the nucleus of a helium atom. It has two protons, two neutrons, positively charged and and the thin foil of gold was bombarded or being shot at with alpha particles. So because alpha particles are also positively charged, as they started interacting with the gold atom, you had some beams that were farther away from the nucleus and they underwent some deflection. Then you had some alpha beams comprising of many many alpha particles which were much closer to the nucleus and because of the positive positive repulsion between the nucleus and the alpha particle, this one underwent greater deflection. And if it is closer to the nucleus, it would then undergo even more even more deflection. And Rutherford, Rutherford was especially interested in one case when the alpha particle was directed at the center of the nucleus. In this case, because of high energy, high kinetic energy of the alpha particle, it came closer to the nucleus and nucleus being positively charged, there was a huge repulsion that was faced with the alpha particle and it momentarily stopped and then started going back. So this was a huge deflection, almost 180 degrees of deflection. Let me let me put in the arrows here to show where they are moving. Now this case, when the alpha particle went completely back to where it came from 180 degree turn, we see that all the all the kinetic energy that the alpha particle had at this point, it came momentarily to rest. So all of this kinetic energy was changed to potential energy of the nucleus and the alpha particle of the system of nucleus and alpha particle. And using the idea of conservation of energy, doing some calculations, we were able to figure out this distance, this distance which was called the distance of closest approach. How close the alpha particle of some known kinetic energy can get to the nucleus. It turned out from many experiments that this distance, this came out to be equal to approximately 3.2 into 10 to the power minus 14 meters and this number gave some idea to the size of the gold nucleus. Because the size of the gold nucleus, it cannot be more than this number and when we say size, we can think about radius, the radius of this gold nucleus, it can in no way be bigger than this number. So this number does not give the actual size or the actual radius of the nucleus, but it does give some idea, some estimate into the size or the radius of the nucleus and turned out there were many more experiments that were carried out. There was electron scattering, there was neutron scattering and with all of these experiments one common observation that was noted was that the volume of the nucleus was directly proportional to the number of protons and neutrons inside the nucleus. So you have the volume, the volume of the nucleus. This is directly proportional to the number of protons and neutrons. And the total number of protons and neutrons inside a nucleus, that's just the mass number. That's the mass number which is denoted by A. So we can write this as V that is directly proportional to the mass number. And this also makes sense because if we think about it, if we look at the helium nucleus which has two protons and two neutrons, we have two protons and we have two neutrons. So the mass number, the mass number here is four and this could be the size of the nucleus. If we take a bigger nucleus, if we take a lithium nucleus, this one has three protons and it has one, two, three, four, four neutrons. So now the mass number becomes, now the mass number becomes seven. So this one has A, that's the mass number, seven. And if you fit in more protons, more neutrons, they will take up more space. So even the size of your nucleus gets bigger and bigger. If you take a bigger nucleus of, let's say a sodium, this one has, it has, it has, let's say it has 11, 11 protons and 12 neutrons. So the mass number, mass number here is 12 plus 11, 23. So now you have more protons, you have more neutrons, so you need a bigger space to fit all of those, all of those small particles, those subatomic particles. Now another thing that was, that was noted experimentally that the shape of the nucleus, it's mostly a spherical shape. Some of the nuclei do have different types of shapes. Even the ones that do have a spherical shape, it's not entirely or purely spherical. We can say, we can, we can say that it's almost a sphere. So while doing the mathematics, we can approximate it to be, to be, to behave just like a sphere. So when we think about the volume, we can write this as four by three. This is four by three pi r cube. r here is the radius of the nucleus, not the atom, just the nucleus. And this is proportional to the mass number a. We can, we, now four by three pi, four by three pi is a constant. So that doesn't really change anything to the proportionality. You can ignore that. We can write this right away as r cube proportional to a. It's four by three pi is just a constant, doesn't really change the proportionality or affect the proportionality in any way. So now when we take cube roots of both the sides, we can write this as r, this is proportional to a to the power one by three. And when we remove this proportionality, we need to add a constant, that is r naught, that is multiplied with a to the power one by three. This expression gives us the radius of a nucleus. Here the constant r naught, this was again verified experimentally. This is somewhere around 1.2 into 10 to the power minus 15 meters. And, and there's a way of writing this, we can write this as 1.2 femto femtometers or fermi meters. And this one, one FM, this is equal to 10 to the power minus 15 meters. So this is the expression for the radius of a nucleus. We can also think about the density. If we add more protons and more nucleons, does it make, does it make the nucleus more dense or does it not affect the density? For that we can try and recall, how did we figure out the density in the first place? We know that density, density was given as rho, rho that was equal to mass divided by volume. And if we take, let's say if we take this helium atom, what, what could be the mass of this helium atoms? It's equal to the mass of this proton plus this proton plus this neutron plus this neutron. It's equal to the mass of all of these nucleons. So mass of any general nucleus, we can write this as the number of nucleons that is a number of protons and neutrons multiplied by the mass that each of them carry and turns out they carry almost the same mass that is one atomic mass unit. So this is one AMU. And one AMU can be expressed in kilograms. We'll do that in a while. But volume is 4 by 3 pi r cube. Volume is 4 by 3 pi r cube. Now in place of r, we can put r naught into a to the power 1 by 3. So when we do that, this becomes equal to a multiplied by 1 AMU. And this is 1.6 into 10 to the power minus 27 kilograms. And this is divided by, this is divided by 4 by 3 pi r cube. So 4 by 3 pi into r naught cube multiplied with a because a is already to the power of 1 by 3. So when you cube it, it just becomes a. One interesting thing that we see here is that a just gets cancelled. A just gets cancelled. Everything else is a constant. r naught is a constant. This is a number. This is a number. So it turns out that the density of a nucleus does not depend on the number of protons and neutrons in the nucleus. Density for every nucleus is constant. It's one fixed number. And turns out the value of that number, when you solve all of this, when you put in r naught, when you work out this calculation, this comes out to be equal to 2.3 into 10 to the power 17 kilogram per meters cube. Insanely high number. But the interesting bit is that it's constant for all the nucleus. It's just like a water drop. If you have a small water drop, it has some density. But if you get a bigger water drop, the density still is the same. Density doesn't change. Kind of like how the density for nucleus is behaving over here. It's the same no matter the size. So that's about it. This is an expression for the radius of the nucleus. And this is the density of a nucleus, which is the same for all nuclei.


What's up everyone? My name is Alex. I'm one of the co-founders of MyInvestingClub.com and I want to let you guys know about something special we're doing for our viewers on YouTube. So the most common question we get asked is, you know, how do I start day trading? So what me and my mentor about is we create a free two-hour mentorship course for the brand new trader. It's going to be available at MyInvestingClub.co. The link is going to be right here. This is a free webinar that reveals our 12 secrets that every single brand new day trader should know before they start. I also want to let you guys know about something that's very unique to MIC. So if you have any questions about trading or you're curious about trading or you don't know if MIC is the right fit for you, now you can text our head mentor, Tosh, whose number is going to be right here and he'll answer all the questions that you have in less than 24 hours. Thank you and enjoy the video. What's up everyone? I just wanted to make a weekly video for you guys. I have a cool kind of topic or not cool but just a different topic this time around. I wanted to talk about what I've been kind of calling opportunity cost and what I mean by that is you know in trading it's like a known thing that you know if you like in a lighter terms you know if you blow your load too early you end up missing the move that you wanted and suddenly I was struggling with this week you know the market has been providing such good opportunities lately and range and like I've just been luckily enough nailing a lot of them and trading well and then last week came around the end of last week and I was just early all the time because I think I got into this mindset of like I couldn't lose and even as I was trading a little sloppy like even with big size like I just was kind of getting out of everything and like things were paying out right because like even on a stock like this like this is um I know you know if you were even a little early at 11 you know you gave yourself the range you know you could have made you know dollar a share plus whatever but kind of what ended up happening to me last week was I just was so anxious at the open to nail everything because I saw so much so many people banking like all the time so I just like felt like I had to be a part of it so um something I'm gonna work on going into next week I actually said I'm taking like a solid month off even looking at like Twitter or any of that and I'm just gonna focus on MIC and focus on you guys and myself in the chat and posting my progress here because you know I think as traders especially when everyone's doing so well you know you start to get this idea of like I don't want to say jealousy but that's kind of what it is it's like you just see these people banking and like as much as you want to I've been doing this a long time and as much as you want to say like oh you know I'm doing well too and like you know good for that guy whatever it's hard sometimes just competitiveness and this feeling that you need to do better but again just because you see someone making five ten thousand dollars a day does not mean that you're there you know you can't compare your chapter one to their chapter 30 like you know bell always says so you know as you know going in the next week just really sticking to my my niche and staying in my lane so I talked about these trades and like what I mean by opportunity cost so so in the morning I have a rule you know like I usually like when I start tanks that open like SSR I'm not like you know if I'm going to scalp VWAP right here I'm using no more than my 30% size because my thesis is like it just didn't give you that move you know we want meat on the bone so we would have wanted this thing to push for you to you know use your 30% and then add as it confirms but what happened here was I just you know I attacked the VWAP which is fine you know a tank at the open I attacked VWAP I think it tanked you know 30 40 cents and I'm like okay that's a good tank so I'm gonna short VWAP right but 99% of the time I stop out on the break of intraday high so like right here so I was short with a 1090s average you know intraday high was like 11 so I would have taken like a less than 10 cent loss on on starter size right which would have been fine because then I would have been patient enough I would have been down nothing you know like barely you know over $100 and I would have been able to sit through this and wait for my for my entry right which was like usually on stocks like I know like I always wait for these stuff moves or these rejections off highs and give you that bounce to get in risking you know this line or whatever but what happened was I didn't stop out you know and I didn't put a hard stop in so then I said okay you know now it's at this line maybe I'll add and I added a little bit bigger which now because I was 30% here I was bigger here 50% maybe so by the time I kept going you know I had to take the loss as it broke kind of this this resistance right here so you know it just shows that like you know if you don't follow your same process every day you know like the odds are you're gonna lose and the one time you don't you get lucky it creates a bad habit right like this was a clear cut reason to stop out a reclaimed VWAP on a little bit of elevated volume you know broke intraday high and broke all these resistances right so you know this stopout even was it was okay but I was more than my 30% size on the front side of the mood move I didn't stop out at the levels I really should have so you know it's just frustrating to see and I want to give you another example of that so CAPR this is a stock that you know I I'm not mad about this trade necessarily but I want to get into exhaustion so so the way my thought in the morning was you know there's resistance at the 720s and then like you know 750 whole half dollar and then eight or my thoughts right I no way in hell like it just goes to show like no matter how long you do this like you never gonna know everything because no way in hell I wouldn't have bet any amount of money this was going to nine looking back I realized that it really was kind of like a volume trap where it traded so much volume the past few days so you know people still had to get out so squeezes could go further you know and the problem is my niche is between two and five dollars on stocks between two and five and anything over that I just always always always have to remember that there is range that you have to account for right so and you know look at how much money there is from nine to seven fifty is a dollar fifty so you know using even a thousand shares which is nothing that's fifteen hundred dollars right so you got to account for the range and play the range like what bow does right whereas like you know I'm trying to play you know this range still using you know three or four thousand shares like I'm you know I'm looking for this home run idea but you know I'm forgetting that you know these things like you know if you have 20 30 cent risk it can go 20 30 cents like nothing so what happened in the morning was you know I made a short of the push of 727 50 had like a 730s average added on the reject so now I'm still sitting in the 730s you know I covered into a lot into VWAP because I just felt it it wasn't breaking down went up you know I had my stop kind of above this level here right in there and I added as it looked like it made that lower high so I like I'm like okay this trade's gonna work this is gonna break down VWAP and I'm gonna kind of look to cover down the 650s but then I looked up it held and I so as I said that's weird like that's not normal then I saw this you know higher low and I'm like I'm getting contradicting signals so my thought is I'm usually just gonna get flat when that happens so as I was looking to get flat you know we just got this push and I stopped out on the break of this lower high so the problem is I just exhausted myself like I ended up like pretty much break even on the trade or maybe I was even a tiny bit green I this is the day I also lost an INO so I was like right on the day but like at this point I was like so flustered I was so flustered that that I just had kind of worked myself on this loss and I don't know maybe from taking the loss and I know I was mentally exhausted so I missed this whole move because I just had to get out of here you know I just felt like like stressed and like and in reality like I know like we probably got this top off 870 I probably would have tried that you know and and let me kind of show you guys you know you know as I spent all of Friday like pretty pretty annoyed I'm taking a bunch of I'm told I'm not doing Twitter I just need to use my pictures here like when I go back and look at my edge this is what I'm what I notice right look at this when the stock is under VWAP right the only time that I actually really like shorting front side is two scenarios or not even front side just like kind of shorting like into the strength is in two scenarios so either when the stock is broken under VWAP pre-market and it's giving you these levels to play off of you know so now you have VWAP as your risk you know that's why I like stopping out of VWAP because you know VWAP is usually coupled with the line close to it and that gives you that that edge you know look at this you know it was under VWAP got the short strength and cut in short as it was breaking down like look at that dollar range right you know that's that's my edge is like you know when a stock's broken down you know shorting into what was already caused resistance the only other time that I like to short into strength is and this is a this is a tricky one see these are all like shorting into strength but with predetermined lines you know like I'm like I'm just throwing starters out at the predetermined levels to get in you know I did that on on SIPA right predetermined 440 line so gave me that confidence to play it because obviously you know everyone's chasing to break this line and while it was rejecting you can get in another example of where edge is if you look at SIPA I mean look at this like if you avoided all of this nonsense right in here right like this guessing the top or whatever look at what it broke under VWAP it broke under VWAP on volume and you had from 380 to 340 that's 40 cents of clear backside trading and you're not guessing where to cover look at you have your levels there's support at 350 and then support down here so you know these levels everything's drawn out for you you know and just having that patience to wait another example is this right I know the other day you know when it broke under VWAP I took that that starter and was shorting just using VWAP as my guide right and look at how it worked you know I had from you know 1230s 1220s got to cover the low 12s and I ended up losing on this but I lost I think well because I was looking for the first red day I stopped out when it reclaimed like very well so so I'm noticing as time goes on it's like you know it's funny you hear people tell you this so constantly like my edge is just so much revolved around waiting for the VWAP break you know and I don't mind shorting frontside because I think I'm comfortable identifying when you know it's okay to but again if you're shorting frontside you have to have to stick to the 30% rule because it's not worth taking those mental exhaustion paper cuts yeah you know if you're small size and you're taking these small cuts it's okay you know but even then you know like what I did over the weekend is I printed out all of my my charts that I just showed you and then I printed out my trades that I've made the most money on right and it just shows like if you can just be patient and wait for your desired entry and like where you have the most edge you know the odds are in your favor and like that's when it's not afraid like it's not scary to use bigger size like I said going into next week I'm gonna focus on not exhausting myself early on and just sitting tight and waiting for that that desired entry and then so I'll let you know how that goes I'm gonna recap my trades next week so enjoy the rest of your day guys thank you so much for watching our video you want to see more of our videos please subscribe to our YouTube channel by clicking the button here we do our best to post a new video every single day if you have any questions about MIC or any general trading questions please text Tosh using the number here also stay up to date by watching some of our most recent videos right over here