Nid oedd yna'r dros. My name is Malcolm Young, I'm on Twitter all the rest of it as Malcolm Young. I'll work at CAP Jam and I and I want to talk to you about CoGov view. Why it's a good thing to do, how to do it, a few bits and pieces around it, and hopefully it will help you to improve your teams. … coordinates time because I know in the last few years, in my experience, a Codew accidents has been a massive help in improving not just the quality of the code that we are delivering but the skills of theIX … code. I think one of the important things with code view is all about asking questions and I don't claim to know all the answers and I'm not going to attempt to give all the answers in this talk. Ond oed i fi ddim bwysig i chi'n gweithio y cwestiynau ym mhwydd. Yn ymddangos, ydych i'w gweithio, ddim gweithio i'w gweithio i'w wneud i'w bwysig i gweithio? Yn ymddangos, mae'n gweithio i'w fod yn tu'r gweithio i'w gweithio, yna? Fy hwnna, mwy ffwg... Bwysig i chi. So we've had some technical bother which means I'm running on the two laptops so please forgive me if I'm looking like some terrible DJ. So yeah as I was saying it's all about asking questions to this code review business. So if you do have questions as we go along please feel free, shout out. And the first question that I want to ask about code review, pretty basic one, what is it? ..egdshaf o'r tyfn o sydd y clyw yna'r rhaid iawn yn hytyllfa'r ansiyl. Felly yn ystod oes yn hyfrifio'r cyffredin. Fe yna'r enthysgol y maen nhw'n gwertho i fynd i wneud, ac bydd y gallwch gion wedi ffyrdd gan goll ti. Mae chwebwch yn y mach i chi, ac mae'n gweithio'n gwneud. Rylan o bobl y mae'r rhaglen armennill o'r syfrifio. documenting it.So I feel I'll have to go with the tradition on that one. That the difference between good code and bad code is all about how confusing it is in a lot of times. But this idea of a team of people sitting together staring at code together, it's not great. I'm thankful I've never done it, but I imagine it's pretty time-consuming, pretty tedious, pretty inefficient. So is there a better way of doing it? Yes, there is. So these days, I guess, most of you are hopefully familiar with using Git, different branching models. So, when you're working on something, standard process, if you're in Git, would be create branch, commit your changes, and then create a pull request into the main branch. And that pull request allows people to see what those changes are and review them. So you get something like this. And with a quick search of Flickr, the first image of a pull request that came up was on the jubilar. So it feels kind of appropriate for a jubilar talk. So what you'll see with a pull request that you're not familiar with is a red line showing you here's a line being removed, here's a green line with what's new. And so you get members of the team, senior, junior, everyone. Let's have a look. Are we happy with this change? If so, merge it in. In case you're not familiar with Git branching workflows, there's a very good pull tutorial by Atlassian. So yeah, if you're not familiar with it, I'd very much recommend that. And so that's the basics. But before I go further, I want to say thank you to Mr Outfought. So we've got a lot of reasons in the Drupal community to be thankful to him. So I was lucky enough a few years ago he worked with us at CaptureMini. I can see a few familiar faces in the room, and I guess they would also share this view, hopefully. He was a very big influence on our team, and I think on the community as a whole. And in particular, in this area of code view, he was one of the guys that really pushed for that to be a massive part of our workflow. And set a very high standard, making sure I see some nodding down the front of your hair. High standards, pedantic, picky, call it what you like. But there's a lot to be said for having those high standards. And obviously he's no longer with us at CaptureMini. He's become one of the core maintainers of the Drupal projects as a whole. And I think he probably does even more code review now of patches than he used to back then. But yeah, I want to say thanks because I certainly learnt a lot from him. And I think I wouldn't be doing this talk if it wasn't for what he'd helped me learn. So why are we doing this? So you might get some pushback from project managers. You might get clients thinking, ah, you know, we need to get these features out the door on time. We need to rush things through. People breathing down your neck. That perception of is it just a waste of time for developers to sit round talking about code? And I would hope that I would very strongly push back on that. Because everybody makes mistakes. Even Alex, even, it doesn't matter how senior you are, how much experience you've got, you're still going to make mistakes. Sooner or later, you'll press a key before hitting the commit button. You'll find some problem. So it's much better to get those mistakes spotted. So, obviously, most teams will be doing some kind of QA, some kind of testing. But one of the keys, I think, especially when you're in larger teams, is to get really fast feedback loops. So ideally, the fastest feedback loop of all is before you commit anything, you look at the diff of what you're committing. If there is a mistake, hopefully you spot it there. If you do commit and push it up, once you see it in that slightly different context, the red lines and the green lines on the screen that we saw earlier from the pull request, seeing that different context is hopefully going to see that code in a new light. You hopefully will spot potential problems then. And to come back to that point that Project Manager might suggest to you that code reviews a waste of time, it's a false economy. So not reviewing code is going to cause you more problems in the longer term. And anyone that says it's not good value, I would suggest showing them this graph. So this is from a few years ago on a very large project. At the time we were using SVN, and this is from my colleague Tom Feddian's blog from, I don't know how many years ago. But the two graphs we've got here, this top one is the percentage of our custom code that had been reviewed. And this bottom one is, along the same time axis, the number of new defects that were getting raised. So it's pretty clear to me, as you increase the amount of code view that's going on, you decrease the number of new bugs that are getting created. And if you care about quality, and you should, you should be doing code review. And in my opinion, it's almost as important as testing. So spotting and fixing those problems as early as possible, and improving the efficiency of your team. If you can spot that problem before you've wasted the time of let's do a build into the test environment, let's get either our automated tests or manual tests to look at that, you're going to be much more efficient as a team. And hopefully that will end up with happy clients, happy project managers. So yeah, number one reason I would say, prevent bugs. Second reason for doing code review is to improve the maintainability of your code, to stop yourself ending up with this big horrible tangled mess. I guess you may have all seen these projects where it goes on for a little while, someone adds their little bit of code, someone else adds their little bit of code. And before you know, you've ended up with this enormous function that's really a nightmare to maintain. So as you're putting those changes in, code views this opportunity to say, well, could we be doing this a better way? Could we be refactoring this into separate functions to make it more maintainable? And most projects go on for a fair while. And the cost of maintenance is going to outweigh the cost of build. So you're going to come back to that code that you wrote before, or your future colleagues will come back to that code. And if you've taken the time to review it, to make it more maintainable, your future self will thank your present self. And so will your colleagues. We'll see. Reason number two, code maintainability. And the third reason why I think code reduce is important is learning. And somehow my notes have gone crazy, bear with me a sec. Yeah, so learning. I've mentioned it a little bit at the start. So personally, I think I've learned an enormous amount from code views. And that's not just people looking at the code I've written and saying, this is wrong, this is wrong, this is wrong, which they have done and they still do. But it's also about what I've learned from other people's code. You get the chance to see different ways of approaching problems that you might not have thought of. And this, excuse me, this ties into this idea that I mentioned before, that it's not just about you write your code, you create your request, the senior most developer on the team looks at it, passes judgement from on high. Everyone on the team has something to contribute.  It's not just about the senior people telling the junior people how it should be done. Everyone might be able to think of better ways of doing things. Everyone might have something to contribute. So yeah, great learning resource. So hopefully you're with me on this idea that it's a good thing to do it. So how do we do it? Most common things that we might use, GitHub, Bitbucket, obviously there's things like GitLab as well more. So these are the big ones that have hosted Git repositories that have built-in reviewing tools in the pull request mechanisms. So I've mentioned the branching model before, and like I say, if you're not sure about that, have a look at that at Lassian talk I mentioned earlier. But basically before code gets merged into your main branch, you're going to get it approved. So I guess most people have probably seen something like this before. Here's the pull request. You look at it and say, yeah, I'm happy for this to go into production. And that is an important step because it's not just about here is one individual who wrote this code. As a team, we're all responsible for the quality of the product that we put out. And when a person says, right, I approve this code, you're putting your name to that as well. You're sharing that responsibility. And you can't later just look at Git blame and say, OK, this guy wrote this line of code. It's this person's fault. We'll take that responsibility as a team for maintaining quality. So as we're doing what is it that we want to be looking for? So some of this stuff is going to be specific to Drupal, some of it not so much. But I think the main things that we want to look for first one, will it work? So is this change that we're making actually doing what the client wants it to do? Are there any edge cases that we might not have thought of? Are there any potential bugs in it? And part of that, obviously, this is going to be specific to your project and your requirements. So there aren't going to be general rules to that. But know what you're trying to achieve, check that the code is actually going to achieve it. And oftentimes, the best way to do that is to check out that branch in your local environment and just test it for yourself. See if there's anything that doesn't work quite as expected. Are there any edge cases that you might not have thought of? I know Lullabot built this tool called tugboat that lets you, every time a pool request gets created, it can spin up a whole test environment that you can get the QA team or the client or yourself to look at it. That's a fairly high tech solution to this. The lower tech solution is, as a developer, check out the code yourself. See what happens. A few other main points to be looking for. So security. Are you making the site vulnerable to any attacks, cross-site scripting, SQL injection? Performance. Are you potentially making the site slower because that's going to cause problems for your clients and for your users? Accessibility. So are you potentially causing problems for some of the users of that site? And I touched on it already. Maintainability. Are you causing problems for your team in the future? So those are the main areas and I want to go through each of them in turn very briefly. Will it work? That depends on your projects. I can't really help on that point. But security. I definitely do not claim to be an expert on this, but there are some general rules of thumb, things that when I'm doing a code review I would always try and watch out for. And first rule I would say is trust no one. Definitely don't trust someone that gets a tattoo like that and wears their phone on their belt as well. So, yeah. In the context of websites, never trust user input. Anytime you're seeing input from the user being handled, as you're in the code review in that pull request, think about, okay, how's this user input getting used? Is there any possibility that an attacker can inject JavaScript into the page or they could potentially write SQL injection attacks? Because if they can, if you're just taking, here is some raw user input from a query string from wherever, an attacker could potentially take over your site, cause you all kinds of problems. So, yeah. Sanitise everything. Now that would be a whole separate talk to go into and I don't have the time to cover that, but there is a lot, and also I'm not enough of an expert on it. Drupal docs about writing secure code, various different sanitisation functions that there are slightly different docs for seven and eight obviously. So, on top of user input, the other thing I would think about in security terms on a code review is, are we changing the types of data that we're getting from users? Is that sensitive data? Is it personal information? If so, how are we storing it? How are we transmitting it? Do we need to encrypt it? Basically, any time you're changing the data structures that you're using, think about that data that's coming from users and what you need to do with it to make sure you keep it safe. Next point on performance, keeping things fast. So, again, enormous subject. I'm not an expert. I think from a code review point of view, one of the top things I would want to look out for is I'll be creating any unnecessary sessions because in Drupal, especially if you're using reverse proxy caches, as soon as you're creating sessions, you're making things less cacheable. You're making the server do more work. So, if you're seeing code from a colleague that's saying, all right, get this data, store it in a session for an anonymous user, is there a better way of doing that that means you don't need to create a session? So, yeah, keep things cacheable as much as possible. Are you writing any inefficient loops? Sorry, this whole two-screen setup is confusing me a lot. So, like I say, performance massive subject, but definitely one to keep an eye out for, keep an eye out on when you're doing code reviews. Next subject. So, I don't know if you guys can see what's going on here. This is down by the south bank. So, here we have some steps, and here we have a realm. So, accessibility. Again, another massive subject, far too big to go into here, but in code review, especially on the front end, there's a few sort of checklists, ground rules that you can bear in mind.  Again, you can check out the branch in your local environment, you can test it out. If you're writing CSS, you can always think about any time you're applying a hover state, what about focus state?  So, if there's text that we'll show later, think about how is that going to be handled by a screen reader? A general rule, if you're looking at display none, you're going to be keeping it out of screen reader users. So, look at accessible private techniques, hover and focus are mentioned. Pretty useful checklists from the accessibility project to have a look at if you're not familiar with it. Again, it's something that you could really dive deep into. And then the next one, so maintainability. So, looking at how your team is going to work with this code in future. So, you want to make your life easy. You don't want to cause yourself too many problems. So, as you're seeing new code come into the system, think that, are you writing more code than you need to? Is someone doing some crazy custom thing that they don't even need to do? Are they using API as appropriately? Don't be afraid to look at the Drupal docs. See what functions already exist. As well as that, unit test coverage. So, how much of your custom code can be unit tested? If it can't, should it be? There's a possibility you could look at making it, breaking things down into smaller functions so you can test it. And comments. If your code is hard to understand, that's a sign there might be something wrong. So, are there enough comments? Are there too many comments? Sometimes, if you've got too many comments, it just becomes noise. And on the subject of code maintainability, there's something in particular. Larry Garfield talked about it at Drupal on London a few years ago. And that's code smells. So, what is a code smell? So, it's a sign of possible problems. So, Larry did a great talk, I think it was, what's that, six years ago. And that was, I think, the first Drupal event I've been to. Really good talk. I would very much recommend checking that out. But as you're doing code views, think about some of these code smells. So, they're not rules, they're kind of guidelines of here's something that might be causing problems. So, in his talk, Larry mentioned seven common code smells. The first one was and. So, if the description of your function is does this and do that, it's doing too much, break it down into separate functions. Or does your function sometimes do this, sometimes do that. Again, bad sign. So, as you're reviewing code, keep an eye out for these sorts of things. If. So, do you have a lot of conditions in the same function?  Testability, we touched on them a minute ago. Can your code be tested? If it can't, should it be testable? Documentation. So, again, are there enough comments? Are there too many comments? Tight coupling. So, is this part of your system, does it stand alone? Could you take it out into a class and use it somewhere else? Or is it too dependent on other parts of your system? And the last of Larry's seven smells, impurity. So, does your function have some side effects plus return values? So, all of these would be things to look out for in custom code that you're writing. Obviously, with Drupal, we're in a lucky position that there's a lot of contributed code out there. So, we need to think about, you know, there's a module for that, people say, but is it appropriate to use that module? So, when you're adding custom modules, when you're adding contributed modules to your code base, don't think that just because it's published on the internet means it's perfect. You know, there are bugs in contributed modules. So, as you're adding them, review them. You know, if you spot problems, obviously issues on Drupal. But also, as you're adding those contributed modules, ask yourself if that's the right choice. Similarly, as you're adding custom modules, ask yourself, is that the right choice? So, contributed modules, often they're a bit like Swiss Army knives. They serve a lot of different purposes, but they might not be optimised for your specific purpose. So, that ties in with the performance questions we talked about earlier.  They can maybe make life more confusing for your site editors than it needs to be. So, sometimes you just want something very specific to your purpose. So, yeah, if you're creating a custom module, think about should we use a contributed module instead? Or perhaps should we use, should we take our custom module and turn it into a contributed module? Equally, when you've got a contributed module, is it the right choice? Any time you're writing a custom module, think about could you make it more generic? Is it something that you could contribute back to the community? And that's something that we do try and do at Capgeminar. We've got a few examples of things we've built for clients that we've thought, okay, well, yeah, let's make this generic, let's put it back into the community because other people will use it. This slide, I just like the picture really. So, I think one of the big challenges on any project is communication, doing enough communication, doing clear communication, and CodeView is another opportunity for communication. So, yeah, speak your mind, I don't know about the first horseman. So, be open and frank and honest with your colleagues. If you see a problem, speak up. Just because you're a junior or new to the team or unconfident doesn't mean you can't ask questions or spot problems. And if you don't understand what a piece of code is doing, it may well say more about the code than it does about your abilities. So, if it's hard to understand for you now, it's going to be hard to understand for the team maintaining that in the future. So, yeah, everyone on the team has something to say, and you shouldn't be afraid to say it. On the other hand, don't make it personal. So, you're reviewing the code, you're not reviewing the person that wrote the code. Back in the start, I talked about everyone makes mistakes, and that's how we learn. So, writing bad code does not make you a bad person, and being a good person doesn't mean you always write good code. So, CodeView isn't a competition, it's not a chance to score points off the other people on your team, and you are a team, so support each other. Help your colleagues to improve. If you see someone doing something that you think isn't the right way of doing it, don't just say, this is wrong. Explain why you think it's wrong. If you've read an article that helps you to see why that might not be the best way of doing things, share a link to that article. Share ideas. I've talked a lot about mistakes and bad code, but CodeView isn't just about that. It's also an opportunity. If you see here's someone who's written something to solve a problem, and it's a really nice way of solving that problem, point to that example, share that with your team and say, I really like this way of doing it. It's very easy to forget that we're all humans and we need a bit of support from time to time. Get the whole team involved, be supportive, don't just criticise where you see negative things, be positive at where you can. We're all humans, but machines can be better than humans at some things. Where machines are better, use them. For instance, coding standards. Really important. I'm a bit of a pedant on this subject about sticking to Drupal coding standards in Drupal projects, in other projects, sticks to whatever standards are on that project. The important thing is having that standard so everyone's writing code to the same styles. If you're in a pull request, writing comments saying, put a full stop at the end of this comment, have the right amount of white space, that gets pretty tedious. Get the machines to do that for you. The appropriate level of automation is going to vary depending on your team. Cagliam and I were a pretty big team. We've gone to a level where, for instance, when someone creates a pull request, Jenkins is going to run PHP code sniffer against that. If you're introducing new code and standards violations, that pull request isn't going to get merged. It's going to run the unit tests. If the unit tests fail, the pull request isn't going to get merged. We run PHP mess detector. If you're introducing enormous levels of complexity, the code isn't going to get merged. Smaller teams, if you're working on your own, that might feel like overkill, but you can always set up your development environment. Some docs on Drupal.org about how to get PHP sniffer integrated with whatever it is that you use so that, as you're writing the code, it's picking up any places where you're not matching coding standards. You can also set up pre-commit hooks so that, before you even push your changes to the repo, a machine is going to check, are you breaking any coding standards, etc. And, like I say, there's also Jenkins continuous integration, so there's quite a nice template that some of the people have put together. We're using that on a couple of projects to get Jenkins to check the status of the code before you can merge that in. A lot of these points that I've mentioned, it's about spotting bad code, and it can be a bit like needle in a haystack. So, when you are looking for a needle in a haystack, try and keep that haystack small. In the same way, talking about code smells, long functions are a code smell. They're a sign that something might be wrong. Similarly, big pull requests are a sign that they might be something wrong. With git branching is easy. If you've got a big feature, have a feature branch for that, have pull requests going into that branch, review them as they go along, because it's a lot easier to review small changes than large changes. There's a tweet that I quite like from a while ago. If you see 10 lines of code, the people on your team are going to spot 10 problems with that. If you have an enormous pull request, people will read the first file, they'll read the first couple of files, but after a while they'll suffer from attention fatigue. It's pretty difficult to review these large changes, and if you give people too much information, they're going to struggle. There's this cognitive load that people will suffer from if they're trying to review large changes. Also, if you've got a large change, it's much more likely that you will spot problems, and then it'll go around for another loop, and then you'll spot other problems, and then you'll lose track of where you are. It's difficult to spot problems in large changes, and doing code review properly is something that requires concentration, and it's pretty difficult to concentrate for a long time, and that feels like an appropriate place to finish. Thanks very much. Here's some places where I got some images from. Here are a couple of blog posts that I wrote on the subject, and here are the slides for this talk, and that is our engineering team blog. Also, we've got a stall out in the foyer there, so please, if you do have any questions, if you want to have a chat later, come and say hello. Come and talk to us, there's quite a few of us. We have some lovely t-shirts to give away, so yeah, come and say hello, and thank you very much. Yeah, if anyone does have any questions, fire away. Either that or come and say hello. Yeah, okay. So you mentioned that code review is not just for your CEO at this time. What's the process going on, deciding who does the code review? Should it be everyone, should it be a selected team? Yeah, there's that line, I think it's kept back, where any answer to an interesting question starts with, it depends. So, yeah, it depends on the project, and it depends on the area of the project, so certainly with Zipbucket and with GitHub, you can, as you're creating a call request, you can assign reviewers. So you might think, okay, well, here's a CSS change, so let's assign the front end guys to look at that, or you might think here's an area of the code that I know such-and-such a person has worked on. What you might also want to think about is the fact that not all reviews are equal. So I know certainly with GitHub and Zipbucket, you can set it up so that before it gets merged, pool of tests has to have a certain number of approvals. With GitHub, certainly it can be, unless those approvals are from people with right access to the main repo, you know, if you're working on forks, they'd need right access to the main repo. So effectively, there's your senior people who, when they approve it, it's a big green tick, when people without that right access approve it, it's a great tick. So yeah, you do need to make sure that the right people are reviewing it, and you also probably want to make not have an enormous number of reviewers. It depends on the structure of your team and on the structure of your project, I would say. But yeah, I would always want ideally a couple of people to look over code, because if you come from that thought of, well, everyone makes mistakes, you might not spot a problem. So one reviewer may not spot it. So it's definitely worth getting multiple eyes on that. What's much a question that there's a comment wanting I've heard is like, as soon as you start a grant for an issue, you can open a call request on it after the first commit, then anyone assigned his reviews will get notified any time it's a question, then you don't need to take in like 500 lines or 500 files, or once you see something growing, and then along the way say, oh, don't go any further with this, I think we need to read this how we're doing it, because if you wait a week or two or three, it can be too late to change direction that way. Yeah, that ties in with that idea of having the feature branches and having small requests into that. Yeah, we've tried on a couple of occasions doing that, create the pull request first, even when it's, you know that it's not ready to merge. Personally, I'm not a big fan of that. I think I would prefer to have some conversations about the general approach, because you've got this pull request. Yeah, are you going to actually approve it?  At the point where it's really big, you might not remember how much of it you've already reviewed. So effectively, you would need to spend the same amount of time reviewing the whole thing, I would say. That's just more a window of the stuff in progress that's just coming along. I've definitely heard that proposed. Personally, I would prefer, here's this thing that we know is going to be big. Let's have a lot of pull requests into that. And then when we think it's ready, a big pull request from that branch into the main branch, because that way you get that extra level of confidence of, right, well, we know that these changes have all been reviewed. So that final pull request can be a bit more of a just a quick skim down it. Has the international code review changed the way you estimate the question? So has it changed the way we estimate? So I think most developers are guilty of underestimating stuff. It's very easy to think, okay, well, I can write the code for that. That'll be half a day's work. And you don't think about, okay, well, we also need to test it. We also need to write documentation for it. We also need to deploy it to this environment, that environment. We also need to put it into production and so on. So, yeah, definitely code review is something you need to factor into that. I think bigger picture, I definitely believe it doesn't increase the overall amount of time that it takes to build something because you're getting that extra confidence that once it's in the test environment, it's more likely to pass first time. But, yeah, it is definitely something you need to take into account. What do you believe in the institutions like the new configuration management process? Those pull requests are going to be pretty large. There's not really anywhere more than that. Yeah, I think still just review it. You're going to see in those pull requests a lot of green lines, but you still do need to look at them to make sure nothing crazy is going in there. Yeah, so the question was about, on this team they do, is that like with the tug boat type? Yeah, so Jenkins ends up small. So that is another way of doing it. We do it in series rather than in parallel. My personal view on that is if you create the code with the pull request and then get the other developers to review it, it's possible that everything might change. And if everything does change, then the testing will be wasting their time testing this code that hasn't been reviewed. So, yeah, we tend to work with one initial test environment and then a more stable release prep test environment, and we would only get it into the initial test environment after it's passed that code review status. But, yeah, I think that main point for me was the not having the possibility that the testers are going to waste their time on that. Yeah, so in our scenario, client sign off would be after our own internal QA, so it would be devs testing for themselves locally, code review, potentially devs testing other people's code locally, then merge that code into the main development branch, get that into the test environment, get our own QA team on that, and we would only ask the clients to look at it after it's passed our QA, and then, yeah, after that, clients sign off and then production deployment. Yeah, I mean, certainly the projects that I've been involved in a lot of times, the clients don't want to spend that much time directly involved, they just want to see the fruits of the labour. So, yeah, again, kind of with the early point about not wanting to waste our QA team's time, it's that not wanting to waste, even more so, wanting to waste, not wanting to waste a client's time, because they would be even more annoying. Yeah, I haven't, really. What I would say on that front is, if you ever find yourself in, if you're still in features, I suppose it's the same with you, Trudeau, actually, of where the code and the site have got out of out of sync, I would always want to do, right, here's one commit and one pull request to get the feature back in sync with what's in the database, and then a new commit and a new pull request to be, right, well, here's what we're actually changing to try and minimise it, but in terms of trying to reduce the mental load of those large pull requests, nothing I'm aware of, but if anyone has got those ideas, I'd like to hear them. A software as a service idea for someone? Yeah. Then you can use separate commits and then, if you rather than a whole pull request view, then pretty good commits, so if you instruct people to commit their config export, for instance, for Drupalade into a separate commit, you can then separate and just review separately the non-config and review the config as a separate... Yeah, that's a little bit. And yeah, certainly GitHub, there's a query string, I forget what it is, that lets you ignore whitespace divs. I imagine there probably is one on Bitbucket as well, I don't know. You've got several people working on a branch together that then have one pull request, would that have one pull request at the end of everyone's work, or do you have people doing pull requests of their bit into it? Yeah, I would normally recommend doing the individual pull requests into that shared feature branch. So would that be done with private forks or separate branches from... Again, so we've got some projects that use private forks, others that have separate branches, doesn't make an enormous amount of difference, I don't think, in terms of the way you handle that. Yeah, if you're all on branches, you do have that option of everybody pushing into the same branch, you know, you might have the CSS changes and PHP changes, and you might want to put them in the same branch. But I would still prefer, in order to keep the pull requests small and easier to review, I would prefer to have them as separate pull requests then going into a feature branch if you think that that feature might not be ready for the next deployment from your main development branch. Well, thank you very much for listening, and yeah, come and say hello.


All right fellow traders, my name is Fausto from Cybertrain University. I'd like to thank all of you for being here today, this wonderful afternoon. And it looks like everyone here is basically looking like logged in from everywhere, from all over the world. It's always nice to see. My thing I want to be able to talk about is why we hear what's going on with the market. How can we actually benefit? How can we actually make money on this market? Most importantly, how can we stop losing money at this market? Like for example, I just told you there's a stock that's moving right now. I want to show you right now in the F-towers. And this is what we're going to basically cover. I hope I'll be fix it here. All right, so here's the stock. I don't know if you guys want to see it. I don't know if anyone saw a QK. Everybody see this stock today? Just made a nice little move. Ran from $1.65 right now. We went to a high of $2.75. Does everybody see that right here? Right now, we're looking at the stock. Nice little runner right here at F-towers. Stock literally just went from $2.15 to $2.75. If you do the math, that's 60 cents. 60 cents on a thousand shares on a less than a $2,000 investment. That's a $600 profit. Now, could anybody tell me why did the stock stop at $2.70 and came right back down to the price of $2.55? Can anyone answer that question? Why did the stock go all the way up, decide to stop specifically at $2.78? Anybody have any clue? Any idea? Resistance? Okay, Gary's saying. Anyone else? Bob is saying sellers. Okay. Oh, how about this? Maybe a RSI can explain it to you? How about that? Does that help? How about we add in a bolager band? I think some people like to read some of that stuff too, right? How about a bolager band? I heard a lot of good things about that. How about how about a moving average? That might help us, right? Does that help you? Or how about if I just tell you that there was a 270,000 shares seller sitting out there and you could see them as bright as red and that stock literally went from $2.50 came right up to that seller and another seller came at $11,000. How would that help? Is that better? Or do you feel more comfortable looking at all this spaghetti? So fellow traders, that's why we're here. We're here to learn why these stocks go up and down the way they do, how to go out there and trade them. And the beauty about today is I'm going to invite every single one of you at the end of this presentation, basically everybody, how these stocks go up and down the way they do. And you're going to see it live at the end of this presentation. You're going to get one full week and I'm going to show you why Cybertrain University has been in business for 25 years and basically has been endorsed by every brokerage firm from Thinkorswim, Trade Station, Charles Schwab, every school out there that no one got that endorsement and also AAA rating at the Better Business Bureau. But I'm going to cover that. A lot of people like you have the spongy lines, Fausto, but I like Fausto's trying the method. Well, thank you very much, Karen. I'm going to share that with everybody. That is just great. Thank you so much for that. So before we get started, risk disclosure just to let everybody know this is going to be no guarantees today. Okay. Things varies from student to student. And I basically going to basically am I making any promises or anything? So please don't get your hopes up high. I am here specifically for educational purposes. But what my goal is this, I know a lot of you out there want to do this, but it's not for everybody, right? So let's find out what the real truth is. What do you say? All right. So this is what we're going to learn. We're going to talk about determining how these stocks go up and down. We're going to talk about what is level three and level four. We're also going to talk about tape reading and we're also going to talk about, you know, is this a full-time job? Is it a part-time job? Now, with that said, can anybody tell me here? Let me get to know a little bit about everyone here. Can everyone tell me what kind of trade you are? Are you a swing trader? Are you a day trader? Are you an options trader? Day trader, swing trader? Okay. Okay. Options. All right. Perfect. Now, the thing is this, this is how you got to answer this question. If you're not making money within 60 to 90 days doing whatever you're doing, you've got two ways of fixing that problem. Number one, you're probably being trained by the wrong person. Or number two, it's probably not for you. Okay. So the thing is this, it doesn't take that long to learn how to trade. And that's where everyone has to understand something. Now, I love day trading. I'm a swing trader also. I do very little options, do some crypto. The thing is, I like specifically what we're going to do right now is because I just follow the money and I make a day's pay and I sleep good at night. That's really what it comes down to. Now, the thing is this, to be very successful as a trader, you're also going to be very well known. And, you know, I don't know if you guys ever watched me on NASDAQ, but NASDAQ, the exchange, has me as a guest speaker on their show because they, what I specifically teach is what they are trying to get you guys to understand how to trade these markets very successful. It's not that complicated. Okay. To go out there and trade the market, you just have to know how to play the game and you just got to know how to use the proper tools, which I'm going to talk about. And it's all about following the money. And for some of you, if you haven't read my book yet, I'm also the author of How to Beat Market Makers at Own Game. How do I know that? Because I was a market maker.  Now, how I got started is very important before we start getting to the fun part of this. Okay. Ford's magazine wrote a big, great article about a bunch of kids tormenting Wall Street. Now it was basically one of those kids. Basically, and we used to make money on that little stinking 15-inch monitor right there if you look at it. I don't know why people need to have six, seven, 10 monitors. The more they have, just the more confused you're going to get. It's all about one simple indicator. Buyers and sellers. And everybody out there makes things more complicated in what it is. And it's not really that hard to do. So what I'm here to teach you and tell you a little bit about it is how I learned how to do it. And then when you guys come into my trading room, you're all going to basically see that some of you've been trading blind the whole time. And how did I learn this? The greatest advice was from my parents, my first generation Italian. My parents came to this country in America because for a better life, obviously after the World War II, I mean, obviously you're hearing it right now what's going on in Ukraine. Looks like they're going to have some of their own, which is a terrible thing. But my dad taught me, says, listen, our family was very successful in Italy. The way you become very successful is you surround yourself with successful people. You surround yourself with people that are very good at it. And that's what's going to make you good. You know how you're going to fail? My dad also made a comment. You hang out with troublemakers. You end up becoming a troublemaker. So if you want to be rich, hang out with rich people. And that's how it goes. So that's basically what I did. Being here in New York, we all know this is a financial capital world. And basically I learned from the best, I got a job. I learned from the best traders in the industry. And let me tell you what you're about to see, which I just showed you just about a minute ago, for some of you missed it. I was basically showing them that there was a stock that had a big run up right here. And it stopped at 280. It just started at four o'clock and made a nice one for literally about 60 cents, 60 cents on a thousand shares of $600. Do that every day. It's a hundred thousand dollar a year salary. How do you basically do that? That's what I'm going to cover. But it all started about following and learning from the best in the industry. And I think that's what helped me about having a great relationship with my family, being married for almost 23 years. But the most second part of my family, which I'm looking to do today is hopefully you guys are going to be part of this family. Because that's what trading is all about. We are a community. We're a community of traders. And what's great about this photo, you'll notice that everybody in here looks very similar like yourself. Now, so let's get right into it. How do we follow? Has the following ever happened to you, basically? Now, stocks starts, gets off at a great start. We have a good, good run. We get a good entry. We trade some expensive stock. And then all of a sudden, the stock goes, boom, just tanks on you, $85. And then it drops all the way to 55. I mean, how did that even happen? Why? Why me? It's like, what did I do to deserve this? Well, which comes down to it is that it just didn't stop at from 90 down to 60. It ends up going down to $33. By the way, this is in two days. And guess what? This could happen, right? Because imagine being in a stock from 90 and it goes down to 35 in two days. Well, the big thing you have to understand, you're not here. You don't want to lose your shirt when it comes to trading. But that's everybody's biggest issue. They always hear people talk about the winners. They never hear anybody talk about the losers. So biggest rule that we teach at Cybertree University, you have to make a decision. You can't mix and match. You can't do day trading. You can't, and you can't mix it to become a swing trade from a swing trade to an investment. Because, listen, here's a stock right here, went from 50 down to $10. Isn't all stock the one from 64 down to 40?  So you just got to know how to play the game. And the game is what drives these stocks up and down are buyers and sellers. It's not that complicated. So now what I want to do is I want to educate all of you on exactly what is these buyers and sellers and why people have the wrong tools and why they blow up their account. So we're going to talk about level two, we're going to talk about level three, and we're going to talk about something called level four. Now, some of you be like, wait a minute, I don't understand. I never heard of these things before. Well, guess what? You didn't hear from it because you were never trained by a market maker like me, like a floor trader. This is the data we work on. Now, before we move on, question to everybody. Who here has level two quotes? Anybody here have level two? Yes, okay. Raymond, you have it, Chod, you have it, Rich, Michael. Good, good, good. All right.  Let me talk about what it is really quick. B stands for buyers, S stands for sellers. You got three columns. Okay. First column is a four letter abbreviation of the brokerage firm. Second column is the price that the brokerage firm or the exchange like NASDAQ, New York Stock Exchange want to buy it. And the third column tells you how many shares, everything there is multiplied by 100. Whoever wants to buy for the most amount of money is up on top. Whoever wants to buy for less money is down at the bottom. Whoever wants to sell their shares, the least amount of money is up on top. Whoever wants more money is down at the bottom. So basically what you're looking at is a negotiated market. So basically a big chat room. Okay. Now the issue with this is that you're not seeing all the orders. That's why people don't like level two. This has actually been outdated since the 90s. And that's, and not only that, but it moves very, very fast. So what do we do? We go to something called NASDAQ Total View. Now, have any of you ever seen me on the NASDAQ show talking about level two, NASDAQ Total View? If you haven't, when you log out of this meeting, it's going to play for you. It's about 10 minute video. I think you should watch it. So let's talk about level, let's talk about NASDAQ Total View, which I call level three. Now remember we, I showed you that right here. This is NASDAQ. Okay. Now follow me carefully because we're going to get very interesting. See this right here? NASDAQ wants to buy, there's somebody using, that's on the NASDAQ exchange, wants to buy 100 shares of this Fox CAN at $14.85. But what about at $14.85, about $14.50, what about $14.13? Aren't there other buyers on the exchange? On level two, you're not going to see that. But when you hop over to level three, you will. So now what you're seeing is about maybe 50 to 100 times more data than level two. So where you're only seeing the best bid and the best offer. Now you're seeing all the buyers, all the way down here, all the sellers. You see what's happening? You have to understand something and let's hopefully think this could sink in. You have a seat on the exchange. You have a seat on the floor and now you're seeing every order out there.  When you go to sleep at night tonight, you're going to think of Thalstow keeps telling me to say this. Thalstow keeps telling me to say this because I want you to realize that next time you lose on your trade, Thalstow is going to tell you, told me why I lost. And this is the reason why. Stocks go up due to supply and demand. Did you see those buyers and sellers in the stock? Did you see that supply? Did you see that demand? That's what we need to focus on. So let that sink in for a little bit because as we move forward, you're going to realize that it's easier to follow the money than to work on something that's delayed. Now let's be very clear here. Some of you here were taught something called support and resistance levels. Now let me be very clear. There is no such thing of a support level unless the buyer is out there. So as much as you're focused on the past, it's not indicative of the future. The only way you could see the future is to see the orders out there. Now support levels obviously can trickle into the future, but that buyer that was in the past needs to be in the future. So right here if you'll notice, this stock BITF started around $6.50 at 9.30 this morning. Once it got around 12 o'clock, it went all the way down to about $5.88. Hit it went up and finally around 12.30, it didn't want to break 12.88 and shot all the way up and went to $6.75. Now that's a pretty substantial amount of money. When you think about it, if you bought a thousand shares of that stock, you sold it at 6.70, you're talking about almost a dollar. Or is that 80 cents, I would say? 80 cents on a thousand shares is $800, fellow traders, $800. Do that every day. You're talking about a quarter million dollar salary. Who doesn't want that job? Now the question is, how do we know who's going to stop at $5.80? Well, when you look over here on level three, what we're looking for is buyers. Remember, buyers make support. And right here, right around $5.88, you had a $52,000 share buyer and there were 10 different orders around the world that made up that buy. So think about it, $52,000. Listen, there are a thousand share buyers, $52,000. That's a hell of a lot of buyers. No wonder. That's almost 50 times to 100 times more than the average order out there. You think you know more than that guy? Yeah, right. Tell me how that works out. How about on the sell side? How many of you ever bought a stock and are like, damn, I should have sold and took a profit. Why is it going down? Well, what makes resistance, fellow traders, is sellers. So you need to know where the sellers are on the future. But unfortunately, a lot of people keep focusing on the past. So what we teach at Cybertrain University is I am looking for traders that could find stocks that I'll teach you how to do it and see it because there's no software out there that does this, fellow traders. There's no indicator. There's no robot. There's none of that. And right here, if you'll notice, when I work my way on the seller, what I'm looking for is a very substantial, what we call here at Cybertrain University, an iceberg order. 53,000 shares, 21 orders are out there. Listen, you got 250 shares, sellers, 1,700, 19 is not bad. But hell, if it's not anywhere close to this 10,000 and 53,000, you're talking almost 63,000 shares. No wonder why this stock shot up and went all the way from 590 all the way back down to 510. You think you're smarter than that guy? You think you could out smart someone that wants to sell 53,000 shares? Do you think that market makers, institutions, dark pools, algorithms don't see that? How many of you here, think about this for a second. How many of you here would probably make smarter and better trading decisions if you were able to see those orders? Think about it because let's go look over here. Since we've been talking, remember that stock I showed you earlier? When it started at four o'clock, it went from 215 and it stopped right here at 280 because there was a 27,000 share seller and then another 18,000 share seller. Well, guess what? Did you see that? There was a 22,000 share buyer just came in, hit that buyer, and now look at it. Now it's up, now it just literally bounced about 16 cents. You see, it's all about following the money. Let's look at this for example. That's a great, I'm glad that you brought that up fellow trader because when it comes to, let me just share that with everybody. You can't beat them. Just join them. Here's an example. We're looking at the stock INO. Now, can anybody tell me, is this stock going up or down? Is this stock going up or down? Actually, you know what? Let me do something better to make a little bit easier. How about I do a poll? Poll is always fun. All right, let me launch a poll. There we go. I don't want anybody to break their fingers. See how you guys answer this question? Just wait for everybody to fill it out. All right, so let me share this out with everyone and see how everyone filled it out. Basically, 91% of you think it's going to go down. Okay, well, you know what? Congratulations. You're correct. It was that hard? If you thought the stock was going up, and I don't know why you maybe thought it was going up, but you were serious, don't take this in a bad way. You should definitely quit trading. Sometimes that could be a little brash. Sometimes that could be a little arrogant, but you know what? I hate seeing people lose money, but if you could explain to me what made you think the stock was going to go up, I have no idea. Okay. All right. Now, my next question is this. What is going to make the stock go up? Because remember, listen, you're in a position, right? And you lose money. Sometimes you're like, oh, do I sell it now? The market is down. I mean, what do we need? What do we need to get this stock to go back up? That's right. We need buyers, buyers. Where we're going to find buyers on level three? And guess what? There was a 219,000 share buyer at 12,060 cents, and there was 73 orders out there that made up. What do you think is going to happen when we get close to that 1260 fellow traders? What do you think is going to happen? Exactly. It's going to probably go up and it's going to probably stop there, right? Because you know what? I don't think 149,000 share buyer is going to make this thing go up, but this guy right here, we're talking about $3 million worth of stock. Yeah, I think so, too. I'm on definitely on your side. Guess what? Came right down to that price and went right back up to $13.80. Not because of Fausto said so, not because I'm a genius, okay? Not because I have a crystal ball. It's because of this buyer. Now, does that seem hard, fellow traders? Did I lose anybody yet? So I assume all of you would like to see this live, right? There's almost 200 people in here. And if you think this is not impressive, well, remember what I told you when we first got started? How many of you here are making six figures trading? And if you're not, how many of you would like to make six figures? Or how about this? How many of you just be happy to stop losing money? Because you're sick and tired. You see everyone else making money, but you can't. It's because you're not following the orders. There's no crystal ball. There's no heat maps. There's no special indicators out there. There's no leverage. It's all about following the money. Will has a good question. Is there a way that they can hide these orders? Yes. We didn't get to that yet. Okay? And hide them is a very illegal word to say. All right? But they do something called shakes. They do something called refreshing, which is they update their quotes a bunch of stuff. Okay? Let's look at this stock right here. CFBI. All right? CFBI is basically doing great. It's going up. Can anybody here tell me if you saw this stock and it was going up? And the first thing you always think is about taking a profit, right? Where would you think taking a profit would be, what price would you feel that we should sell it? Exactly, right here, at $1370 for 162,000 shares. I mean, look at this, 200 shares, 10 shares, 1,000 shares. You're talking 162,000 shares, fellow traders. Is this who you think you're going to outsmart? I don't think so. Now, does a chart show you that? Traders? Does a chart show you that big seller out there? No. The chart tells me it's going up. And probably every indicator is going to tell me it's going up. And every analyst is going to go up. Well, you know what? Why do you keep focusing on the past? Well, maybe it's time to focus on the future. And the future is following the orders. Because if you didn't follow that order, stock goes from $1380 all the way back down to $1290. Why? Because maybe you got greedy, maybe because some indicator told you it was going up, whatever it may be, it all comes down to this. There was 162,000 shares seller out there. That's how you do it. Now, that easy enough? Kathy has a question. How does level three show the exact time moment for the sharply increased orders? Kathy, that's a great question. Would you want to see this live? Would that help you? Well, what you need to do is you're going to wait in about another 20 minutes because I'm still not fully, I still haven't fully convinced certain people in here in this room because they still think what they're using is working. But you and everyone else that is seeing this right now are going to see it live for one whole week in live market conditions. And not only that, Kathy, but you're going to see people like yourself that we train how they think for themselves and how they work to get like a team because that's where it comes down to it. So that's the power of buyers and sellers. Now, let's go hop on over here to level four, which I showed you just earlier, but let me show you a couple of screenshots on this one. What's nice about level four is that this is basically level three right here, right here. All right, see all these numbers. Level four is showing you the orders. How long the guy was out there? Did he get executed? How many shares he had? Because right now we're all the way down here, right? So I don't know what this order was here. And I don't know if he got executed.  And that's what this guy's been up for a while. So we're seeing the consistency of how long he was out there, which probably is answering your question, Kathy, where a chart shows me none of that. Zero. So knowing how long the guy's been out there and how he was doing something called consolidation and how he kept on doing something we call here the latter effect, where he keeps lowering his offer and lowering it and lowering it. He's like, when you ever wonder like, who's pushing the stock down? Like, why does it keep, it stops, it goes down, it stops, it goes down. You have no one talking about fellow traders.  Now maybe, maybe it'll start going up and like, damn, it went down again. They're like, oh, maybe this is it. This is it. This is over. And damn, it goes down again. Because somebody wants to get out and they keep lowering their price and lowering it. And when they lower it, it's not a little, it's a lot of shares. And if you don't see that, this is what ends up happening. You just keep losing more and more and more and more because the guy came back again and more. And guess what? And more. Are you done yet? Are you finished? Are you still hoping? Because you all know what I'm talking about. You've been there. You've done that. Well, enough's enough. It's about, it comes to a time right now that what you're doing is not, if it's not working, or you're not meeting your goals, well, it's because you are too focused on what everyone else is saying other than seeing what the street is doing. Gloria, this is level four that we're looking at right now. And I'm glad that you're seeing it because a lot of people don't know it even exists. Because they're not traders. They're not market makers like me. Now, anybody here use something, anybody here use Thinkorswim? Anybody here use Thinkorswim? Have an account with Thinkorswim? Because Thinkorswim just finally came out with level four on their platform. If you go on our YouTube channel, I actually made a demonstration how to set it up, how to get it, all that stuff. Yeah, the Canadian version is the same. Absolutely. But please don't buy anything because I need, I got to show you how it works first. Okay. Now, Fausto, my indicators told me the stock was going up. Okay. Well, remember I showed you this earlier? What chart is it to read? Chart number one or chart number two? Exactly. Chart number two. Right, Will? Right, Mike? Right, Bill? Pretty funny. Any here from you, Bart? Carol? Gordon? Mark? Don't think I don't see you guys. Listen, I am here to educate you guys to kind of make you realize that you took the time to be here. And I am here to convince all of you that if you want to do it right, you got to follow along and you got to answer questions. Because if you don't, all that tells me is that you're confused. All right. Well, thank you very much for that joke. I love Woody Whippeck on myself too. He was a big fan. All right. So, Trader's using the case because the chart only tells a fraction of the story. There's something that we call the KISS method. Keep it super simple. You know, a lot of people get discouraged when they look at a professional platform like so many numbers, so many... Listen, it's not that confusing. When we teach our Traders, we just start with one window. And then when we add time and sales, then you'll know what that means. Then we add a watch list, then you know what that means. Then when you see level three, you'll know what that means. Obviously, when you implement a chart, you know what that means.  And whoever trained you, did they coach you? I mean, did they physically talk to you on the phone and set up your platform and reviewed your journals and see why you lost money on certain positions? I mean, does anyone do that for you? Because that's what we do here at Cybertrain University. Listen, you do it right, or you don't do it at all. Because going out there and being self-taught only makes things more complicated for you. This is a great job, fellow Traders. It pays a very good salary, probably more than you would ever make. But you could lose everything tomorrow. Why? Because of ignorance. We all went to college. Some of us didn't, some of us didn't, whatever. But I know we all went to elementary school. We all had jobs. We've all left jobs. We also had great jobs, and we had people that worked there that put us in harm's way. And we're glad we got rid of them.  What is it? After you get through the 98 employee, you finally find a good one? Ever hear that, ever hear that phrase? I know a lot of business owners here know what I'm talking about. We're not all a good fit. But doing this job, my point I'm getting to is this. You want to do this right. You have to surround yourself with good Traders, successful Traders, and a brand that you could trust. A name that is known. Someone that has a triple rating at the Better Business Bureau. You only have some funny two. I did a search. I had one of you here I spoke to yesterday. And somebody, and I'm not here to knock any business, because that's not good business. But someone told me it took a training course with someone. Did you ever do a search on Google, on the company you did business, that you were considering to do business with? You probably won't find their Google writing. They won't even have a directory up and running. You know what I'm saying? Why is that? Why is it, but we're there with a five-star rating.  And that's why Cybertrain University has been endorsed by someone, just to name a few. I mean, it's probably over 50, but these are some of the brand names out there that we were endorsed by. So what I'm offering to you all is this. I'm offering all of you the opportunity to me to show you all this live in the market, because we practice what we preach. And if you want to go out there and you like C-level 4 and you want to see these stocks that we traded that up 30, 50, 200, 500% in one day, this is going to be your opportunity. But I'm not here to talk about the winners. I'm actually a bigger fan about the losers, because we want to show you how few we have and how we get out of them, because that's where you learn the most, but how we trade side by side with our traders. So everybody here is going to get access to what we call our cyber group trading room. Now, this room has been up and operational for over 25 years. It's the oldest running trading room. Now, why it is? Because I started one of the first schools in the industry. So here's your opportunity to see what it's like to be in this room with traders that we've trained. Now, just to tell you, we basically, we start live audio commentary at 9 a.m. to 10 30. And then we do an afternoon commentary from 2 30 to 4 o'clock. Okay, so basically, we're not trading all day. But if you can come here in the morning, can't make the afternoon, you're going to have the best of both worlds. And every Tuesday, we do a Q&A trading workshop, which did that today. So if you come to our trading room, if you missed it, you'll have access to the recording. Now, there's just a couple of amazing things that the cyber group offers you, but we got something else that we also give our traders. We also give an alert service. So you could actually access the trading room and get text alerts through our app, if something is moving in the market.  We don't need to do that. We just want to keep you engaged, because you're going to miss probably 95% of all the big winners out there, which is okay. She's still got 5% to get. But listen, there are over 25,000 stocks out there every day is a new adventure. So that's basically what we're offering.  Now, this is all we're asking for. We're asking for a application fee of $9. That's it, $9. Now, you're going to get all this one week in the trading room, traders talk. Let me change the slide here so you can see it. We have more here. Oops, there we go. You're going to get a daily watch list, a Q&A, and if you're the first 20 people, you will even get a coaching class with me. All of that for $9. Now, some of you will be like, wait a minute, there's a catch. $9, all this. You're going to teach me this?  That's it. I don't know who you are, where you came from. We just don't let anybody in the room. Honestly, if you can't afford $9, we don't want you in the room. That means you can't afford to trade. It's a lot of work to talk to you on the phone and do this. Now, you're probably wondering what's the ultimate goal? The ultimate goal is this, that if you like what you see, then you're going to let us train you the right way and that will take a little bit more time. It's like a diet. You can't be in shape in a week, but if you like what we do, you'll be a client for hours forever. If things get so good, you're going to be able to teach other people. If you're not happy with it, I'll give you your $9 back. Now, does that sound fair? Perfect. All you got to do is they posted that link right there really quick. Just click on that link for $9. What I want to do is I want to ask some questions, but just to remind everybody is this. There is a questionnaire. It's going to ask you about five questions. Please fill it out to your best of your knowledge. Let us know a little bit about you. It's like you get taking your blood test or when you fill up that one piece of paper, but it's really not that long. It's only five questions. When you go see the doctor, the more we know about you, the more we can help you to obviously bring you to the goal of training in today's markets. Now, does anyone have any questions in the meantime? I know I passed a couple of them. I need to ask a question. I've learned more this week in Fausto's team inside Retreat University. I'm a new trader and I just recently joined Fausto's group. You're going to pick up your grandson, but let me just share that. You're going to meet Nina in the room tomorrow, but thank you so much for sharing that. That is a great, great testimonial. What platform we use? Don't worry about that. You don't need a platform. You don't need nothing. All I need is you in the trading room. That's it. You don't need any money. You don't need a brokerage account, nothing. Michael, don't worry about the day trading world. That versus $9, I'll take the $9 all day. There's ways that you could still trade, not worry about $25,000 a day trading world. Karen, I was wondering about the trial access period. Will we also learn about how you create a watch list? Yes, because you're going to see a live Karen in the trading room. We're going to show it to you. We're also going to show you how to dissect it. Let me do a couple of shout outs really quick right here because we've got a couple of questions. Alex, I just got your registration. Alex, Ricker, Cleave, I just got your registration. Hope, who else they got here? Richard M, I got your registration. Welcome aboard. Warren S, I just got your registration. All right, appreciate it. Guys, it's $9. $9. Look at this. If you were these suckers that saw this stock make a run and didn't see this order out here for $2.80 and you bought it, thinking every indicator was showing that and now you're stuck at $2.10 and you just lost $0.70 on $1,000, $700, you tell me $9 a lot of money. I just saved you literally almost $700 just on this trade if you didn't see this order. You see traders, you want to learn how to follow the money. You want to learn how to trade with a market maker. You want to learn to see how Wall Street traders, algorithms, dark pools, what else you got? Hedge funds, mutual funds, brokerage from where they placed the order, now's your chance. How do I know that? Because I was one of them. Raymond says everyone, it's a no-brainer. CTU is great. You know what? Thank you very much for that, Sharon, Rich. Let me explain something to you. Just to give everybody a heads up, a lot of you here are going to register and you're going to realize that trading might not be for you. You know what? We might even tell you that. Wouldn't it be better if we told you the truth than somebody going out there and not losing $9 but losing $9,000 on one trade? That's where it comes into. Well, Karen, regarding that, Karen, you could listen. You could always take it again. One thing you have to understand, Karen, I know you're too busy early regarding about spring break and everything's coming up and all that. I get it. It's never a perfect time. But you know what, Karen, you're going to eventually have to, you know, we're not going anywhere. Okay, I've been here for 25 years. Stock market, I could guarantee you one thing. It's not going out of business. All right?   So whenever it's the right time for you, it is. But you could always do the trial. You're all going to talk to an education advisor and when you're done, you tell him what you want to do. Oh, yes. Another thing is this. We are not going to charge you anything after the $9 trial. No. First of all, we have no interest in there. For what? I don't need the money. I hate to say this. I don't need it. I'm looking for traders that I could teach this style to so we all could trade together. All right? Let me do a couple of... No, Karen, you're more than welcome. You're more than welcome. Let me see what we got here. Stanley, S, we got your registration. Patel, we just got your registration. Alec Brick, we just got your registration. Let's see everyone. Fellow traders, please remember, make sure you fill out that questionnaire at the end of the presentation so we know exactly a little bit about you know, a little bit about you. Is that it? Someone says, Rich, could you please show the video of level four and think or swim? Rich, is that the link right there? See, that's a link right there. I'm just going to click on it and see if it's the right one. Yep, that's it right there. Three minute video. Besides even that oldest video, I just posted. It's got 1400. There's another one here that got almost 3000. You can see all the videos that we posted right here. Let me just mute this right here. All right. Any other questions? All right, fellow traders. Listen, thanks for listening in. I hope you guys learned a lot. Look forward to seeing everybody here. Just take the opportunity. $9 money back guarantee. Let me teach you level three, level four. Let me show you what it's like to be with a 12-time world champion. Most importantly, why don't you see how other traders think for themselves? Because that's really what we're there. And not judge us on the winners, but judge us on the losers and how few we have. And here's your opportunity. So don't lose that opportunity. Go out there. Stop pretending.  Some of you guys realize Social Security is not going to pay enough. You're about to retire.   You've got to build on it. And there's no better place to do it. And after seeing everything that's going on in this world with Russia, Ukraine, the virus, what else could I go on? The inflation, it doesn't stop. But unfortunately, these catastrophes make opportunities for you. All right, so let's go out there, make money together. I look forward to seeing you all tomorrow morning in the trading room. Thanks for listening, everybody, and be safe.


Team keeping clean y'all knew this was coming right y'all knew as soon as Marcus Peters got released as soon as it even was said last night That he could possibly be released. You know, this was on a lot of Baltimore Ravens fans mind Oh, should they bring them back? Should they just reignite the flame? That was once there between Marcus Peters and the Baltimore Raven and it's funny because when the news broke that he was officially cut Within 60 seconds. I got these three messages. Shout out to my guy Marcus. He said I got to say it Peters back to Baltimore. Oh my god, Joshua Williams. He said Marcus Peters got released. Should the Ravens re-sign him? My god David M. He said in Graven. This is not a drill as of right now The Raiders just cut Marcus Peters if he were to clear waivers Do you think the Ravens will negotiate a contract with him to come back? So should the Ravens bring back Marcus Peters? Well, um, let's think about it And then we're gonna get it into why Marcus Peters was even cut in the first place because that's something that we got to think About two but even before we get there right now the Ravens secondary They in pretty good shape. They really are you're about to get Marlon Humphrey back after the buy and you know what last night During that charges game. I was like Marlon Humphrey ain't gonna play and didn't about away the game was going I was like, oh, yeah, we missing Marlon Humphrey big time now But the Ravens they made the right decision because they still were able to win the defense was still able to dominate even without a Marlon Humphrey so that was really really nice to see but anyway The one thing that I really appreciate about the Ravens secondary and then just even their cornerback specifically Something that I've seen and you can of course, let me know if you agree or disagree because I really do want to hear from y'all about this in the comments The tackling has been pretty good overall They have been some times where they miss hearing there But overall this year in my opinion the tackling and not even just from the secondary But the defense as a whole has been really good And it's really been up from the past couple of years it's been a drastic change in my opinion and I think that's something that cannot go unnoticed and But it's something that we we got to make sure we talk about because it's very important because when you tackle well You stop a play you stop a play in his tracks because if you don't tackle well a Play can go from being a five-yard game to being a 15 to 20 or 60-yard game and us Ravens fans We know from Experience because we've seen it happen plenty of times when it comes to poor tackling But this year has been so much better and we remember when Marcus Peters was when he was with the Baltimore Ravens Even when he was doing his thing getting all these interceptions pick sixes and all that Marcus Peters is he is excellent at film study. He's excellent at diagnosing plays and whatnot. He got great instincts but tackling just Wasn't his thing and there will be times when we've seen it playing time with Marcus Peters He would make he will put on a suit put on a shirt and tie and he would make some business decisions now We love Marcus Peters But it was like sometimes that'd be a little rough right there So he was not the most physical corner and then every corner is different But his thing was getting that ball his thing was making sure that you ain't get the ball He his thing was him turning into the wire receiver when he matched up Now Ravens do play a lot of zone coverage So that would benefit Marcus Peters because that's his thing. He's not really a man corner like that He's a zone corner. So he would fit right in with that But the tackling that's where I would be a little bit concerned and then when you look to see why They released Marcus Peters. It said Peters who's 30 years old was signed This is from the athletic by the way He was signed to a one-year $3 million contract to be a leader in the secondary and did have an interception return For a touchdown in week eight against the Detroit Lions, but has been a huge disappointment His tackling was poor including a whiff in the second quarter against the Chiefs and his effort was questioned Hmm effort was questioned That's interesting right there because when you hear stuff like that That can be really tricky because I know and speaking from my own personal experience There's been times when I've been at a job. I've been at a company where I just I wasn't feeling how they ran things I wasn't feeling how they did stuff and I'm like, man I'm showing up, but I wasn't giving my all and I knew I wasn't giving my all and it was clear that I wasn't giving my all My managers knew that what that I wasn't giving my all so we'll have conversations and whatnot like hey Well, what's going on? You're not feeling it. What was the problem? What's the issue? Like how can we fix it? Management changed leadership changed and everything changed for me Like I really started putting forth way more effort because I saw that things were different I saw that there was actually a lot more hope Than what I had known before under the previous management under the previous regime So I wonder I really wonder with Marcus Peters if that could be it because with the Baltimore Ravens They obviously on a different track not even just right now But even just recently the way that they do stuff there They're on a much different track than the Raiders are and I wonder if Marcus Peters being with the Raiders and especially with them Just losing loss after loss after loss I wonder if that mess with his psyche and he just been like a man. I just don't feel like it I just don't feel like it. I've been a Raiders fan for my whole life But this this move just this didn't work out and I wonder if he just if he mentally checked out from the Raiders right now now and the reason I say that it is tricky to is because we've heard this about players before and Sometimes they just need to change the scenery one play I bring up is Jadavian Clowney Jadavian Clowney a lot the same all this same stuff that Is being said about Marcus Peters the lack of effort? And just yeah, him whiffing on stuff him missing stuff Tackles, I mean this same stuff, especially when it comes to effort. It was all said about your Davian Clowney, too That he wasn't a leader that he was Overrated that he was just in it for the money. He wasn't hungry is this that and so much you heard so much stuff about Jadavian Clowney and more Look how he's doing now Jadavian Clowney. He played with the Texans. He played with the Titans He played with the Browns. He played with the Seahawks and When he played with those teams, they weren't really having much success They weren't all terrible, especially when he was with the Texans or whatnot, but they weren't having this crazy amount of success He comes to the Baltimore Ravens, especially after after they haven't been on the Browns for the past couple of years Comes to the Baltimore. It was even said that you David Clowney had an attitude because I remember Last year at one point it was said that you David Clowney He was upset because he didn't want to be looked at as the number two guy to Miles Garrett And I was thinking like hold up man, like anybody any past Russian that goes over there. You gonna be number two to Miles Garrett, but anyway So after hearing on that stuff and when the Ravens first start talking to David Clowney a lot of people like no No, we don't want them. We heard too much bad stuff about this dude Look how he's doing now Jadavian Clowney has been amazing and what what was all Jadavian Clowney needed? The right situation the right situation Now with Marcus Peters Because that's what I'm thinking that it is man I'm thinking it's just one of them things where it just may not be the right situation. It may not be the right fit But if he came back to Baltimore, I just I don't feel like there would be a Place for him like and think about this too What is Marcus Peters role? What would his role be with the Baltimore Ravens if he would have come back right now? What would it be? Because you got Marlon Humphrey You got Brandon Stevens Even got a Ronald Dolby. You got Kyle Hamilton playing in the slot. You got your two safeties Geno stone Marcus Williams Where's Marcus? Peters role gonna be Like I mean you you could bring him back. I mean you gonna put him on a practice squad You could do that and that have him be like a stay ready so you ain't got to get ready type of thing Could be one of those sort of Emotion of those those sentimental type of deals like we're gonna bring you back cuz we love you We got a lot of love for you You were here with us through a huge transition as we transition from one quarterback to the next And you were here we traded for you in the middle of the season in 2019 And you made an immediate impact and you you were really a big part of everything that we did that first playoff victory that Lamar Jackson got You were a huge part of that and you closed the deal for us with that but For me, I just don't feel like There's a spot. There's a place for Marcus Peters on the field emotionally There's always a place for Marcus Peters for sure in our hearts definitely But on the field, I just don't feel like it would be a good fit


Hello, and welcome to YouTube News for January 28, 2015. I'm your host, Alex, and I'll be walking you through some of the most important and interesting news topics revolving around the YouTube platform. First up, three famous YouTubers interviewed the President of the United States, Barack Obama, on Thursday. The interview earned over 88,000 concurrent viewers when it was live, and generated over 700 million impressions for the YouTube Ask Obama hashtag on Twitter. Amongst traditional media outlets talked down about the interview, most viewers seemed to enjoy it, and believe the questions asked the President were thought-provoking. In case you missed it, and you want to see the interview for yourself, I'll leave a link in the description down below. Next up, it looks like the MCN Fullscreen is launching a film division to develop feature-length movies using YouTube stars as the actors. While there are a lot of details on this new development, it is said that all movies will be released across all screens, and even potentially in movie theaters. Do you think this is interesting, or something an audience would be interested in seeing? Do you think freedom should be interested in developing something similar to this? Tell us in the comments section down below, and we'll be sure to read them. Lastly, the new online video platform Vessel has launched into beta. For those of you who don't know, Vessel is a platform for creators to publish their content to their audience early for a subscription fee of $2.99 per month. They tout that their CPM will be in the $50 range for the first 72 hours after a video is released, but since the platform is so new it is yet to be seen. I was personally invited to test out the Vessel platform, and from what I've seen, it's very modern and well-designed, but it lacks a lot of the features that YouTube has, and it's rather closed off to creators that don't have millions of fans. So for now, I think YouTube is the best platform for both creators, small and large, and only time will tell whether or not Vessel actually becomes a competitor in this space. Anyways, that's it for me this week, guys. Tune in next Wednesday with the latest in YouTube news. Thanks for watching.


Hi and welcome to the session. Let us discuss the following question. Question says, a maplix sphere of radius 4.2 centimeters is melted and recast into the shape of a cylinder of radius 6 centimeters. Find the height of the cylinder. First of all, let us understand that volume of sphere is equal to 4 upon 3 pi r cube where r is the radius of the sphere and volume of cylinder is equal to pi r square h where r is the radius of the cylinder and h is the height of the cylinder. Now we will use these formulas as our key idea to solve the given question. Let us now start with the solution. Now we are given that radius of sphere that is r1 is equal to 4.2 centimeters. Radius of cylinder that is r2 is equal to 6 centimeters. We have to find height of the cylinder that is we have to find h. Now we are given that sphere is recast into a cylinder. This implies volume of sphere is equal to volume of cylinder. From key idea we know volume of sphere is equal to 4 upon 3 pi r cube and here radius of sphere is r1 so we can write volume of given sphere is equal to 4 upon 3 pi multiplied by cube of r1 and volume of cylinder from key idea we know is equal to pi r square h. Now in this formula we will substitute r2 for r to get volume of this given cylinder. Now we can write volume of sphere is equal to 4 upon 3 pi multiplied by cube of r1 is equal to pi multiplied by square of r2 multiplied by h. Now substituting corresponding values of r1 and r2 in this expression we get 4 upon 3 pi multiplied by cube of 4.2 is equal to pi multiplied by square of 6 multiplied by h. Dividing both the sides of this expression by pi we get 4 upon 3 multiplied by cube of 4.2 is equal to 36 multiplied by h we know square of 6 is equal to 36. Now dividing both the sides of this expression by 36 we get 4 upon 3 multiplied by 4.2 multiplied by 4.2 multiplied by 4.2 upon 36 is equal to h. Now we will simplify this expression we know 4 multiplied by 9 is equal to 36 and 3 multiplied by 1.4 is equal to 4.2. Similarly we know 3 multiplied by 3 is equal to 9 and 3 multiplied by 1.4 is equal to 4.2. Here also 3 multiplied by 1.4 is equal to 4.2. Now multiplying these three terms we get 2.744 is equal to h or we can simply write it as h is equal to 2.744 centimeters. We know h is the height of the cylinder so we get height of cylinder is equal to 2.74 centimeters. Now this is our required answer. This completes the session. Hope you understood the solution. Take care and keep smiling.