Good afternoon. Welcome to CMC Markets, this August Non-Farm Payrolls webcast on Friday the 5th of August. With me, Michael Houston, unfortunately, my colleague Colin Suzuki will not be joining us today because he's earned a well-earned vacation. Enjoying the Canadian summer, I would imagine. But before I get started, I have to display the obelisk tree risk warning, basically just outlining that nothing you see or hear today on this webcast should be construed as trading advice, directional or otherwise or indirectly. Go through the risk warnings for the various regions for the UK, now for the rest of the world and obviously Canada as well. And once we've got them out of the way, I can get started. Before I do get started, however, if any of you have any questions whatsoever about a particular asset that you are particularly interested in, then please feel free to use the chat facility, send a message, send a reply to this message that I'm sending out to all of you now and I will try and answer your questions as best I can. And certainly been a very interesting week. I hadn't really thought about this week's payroll as a number, pretty much until five o'clock last night because I think like a lot of people in the market, we were all preoccupied with the Bank of England rate decision and the potential outcomes of that. And they did certainly bring a surprise, they certainly caught me out. I didn't expect them to act in the way that they did and ultimately pretty much called it wrong. So from that point of view, when you do call it wrong, you just basically have to take it on the chin, dust yourself off, pretty much have another fresh look at where we go to next. One of the things I would say with respect to the decline in the pound over the course of the past 24 hours is that actually I'm surprised it's not an awful lot lower given how much the Bank of England threw at it. But now for today, this is going to be a pretty much a US dollar story. And certainly over the course of the past week or so, the dollar has taken a little bit of a nosedive. Certainly in the context of the dollar index, we've seen quite a significant decline in the US dollar on its trade-weighted basis over the course of the last few days. Certainly since mid-July we've come down quite a bit. And I think a large part of that can be attributed to the fact that first and foremost last week US GDP came in for the second quarter, came in much lower than expected. And I really don't think that's too much of a surprise given the weak payrolls number that we saw in May of 11,000. I think the US economy did hit a little bit of a soft patch in the early part of Q2. But then of course that begs the question as to where we go to next, because certainly I think in the context of some of the comments that we've seen earlier this week, certainly with respect to Charles Evans, we've certainly seen the Fed still try to make the market think that it still has a rate hike in its sights sometime this year. Unfortunately for the Fed the market doesn't believe it. And in that context I can give you an indication of the market's thinking as to the probability of a rate hike over the course of the rest of this year.  And this is WIRP, which stands for World Interest Rate Projections. I've just seen a question and I will answer that on the end in the Swiss franc in the normal course of my deliberations. I haven't forgotten you. I will get around to you. Going back to the US dollar and the prospect of a rate rise or otherwise, prospects of a September rate rise are now down at 16%. Now that's really low. I mean that's the lowest it's been for quite some time. No one I think really expects the Fed to hike rates in September in any case, in the aftermath of what I would call very disjointed economic data. Certainly the jobs report for June was way better than the jobs report for May. So the big question there is which one is the outlier? Is it the May number or is it the June number or is the truth somewhere in between? And in that context I think today's jobs report will probably give us some indication. The three month average for US jobs is around about 148,000. So if we get a number round about that in that sort of area then I think really we're not going to see that much of a reaction in the US dollar. If we get a number in excess of 220,000 or 230,000 jobs then we could see the dollar go higher. Will it also the calculus with respect to a rate rise? I'm not sure it will because we've got the presidential elections coming up and the twoing and froing between Hillary Clinton and Donald Trump and I think in that context it's going to make it very, very difficult for the fair to even contemplate raising rates but there's a more important factor at play as well. The fact that the Bank of England cut rates yesterday for the first time in seven years has now created never bigger divergence in global monetary policy. Certainly two years ago everyone was expecting the Bank of England to be one of the first central banks to hike rates. Now they're probably likely to be one of the first central banks to cut rates even further over and above what they already done yesterday. With the ECB also likely to remain in full easing mode it's going to make it very, very difficult for the fair to diverge away from those two central banks particularly when the Bank of Japan is also looking to ease monetary policy. The last thing the Fed wants is a higher dollar. So I think your perspective of what these numbers come out at today, the Fed is unlikely to be raising rates by the end of this year. It certainly won't be before December. It'll be December at the earliest. That's not to say that we won't get a very negative or positive dollar reaction in the event that we get either a disappointing number or a very positive number. But in the context of the overall rate debate I think the actions of the past month or so with respect to the Bank of Japan, with respect to the European Central Bank and with respect to the Bank of England the calculus has shifted. The calculus has shifted away from a potential Fed tightening to just a Fed holding still. And I think that's something that will probably be a continuing theme or a recurring theme over the course of the next few days, weeks and months. Now I'm just basically pulling these up because we've also got the Canadian Jobs Report which is equally as important to our Canadian clients as it is to all of our other clients. So I'm just pulling these over here. Now when we look at the jobs numbers I'm particularly interested in terms of how good or bad the market seems they are. The best barometer for that and Colin and I have talked about this before in lengthy, lengthy detail. The best barometer of a good or bad jobs report and the market reaction to it is Dolly Yen. And the question that I was asked a few minutes ago is why are the Yen and the Swiss Franc such safe haven currencies? Well ultimately you look at the Yen, the reason the Yen is a safe haven currency is ultimately because all of its domestic debt, its private debt or public, government public debt, it's domestically owned which basically means that Japan never has to worry about the kindness of strangers in funding its external deficits. Ultimately it will always be able to print enough JGBs to pay out and also the carry is very, very low. So this is a similar sort of thing for the Swiss Franc. The Swiss economy is not in bad shape despite the fact that they have negative rates. The reason they have negative rates is they want to stop people from putting money into the Swiss Franc and it's the same thing with respect to the Japanese Yen. You've got that situation whereby they're not running massive current account deficits. Neither country is doing that so they don't have to rely on external funding and that's why their safe haven currencies and that's why the pound isn't because while Japan and Switzerland to a certain extent run current account surpluses and not all the time, the UK runs a massive current account deficit and as such that's why the pound is never really treated as a safe haven currency in the same way as the Swiss Franc or the Japanese Yen. So hopefully that answers your question. Moving on, I think really the key question now is what are we going to be looking for with respect to a market response in terms of the overall market reaction? Well I get this feeling that equity markets are starting to look a little toppy. Now it may be not a view that you guys share but I'm certainly looking at the FTSE 100 which has really outperformed pretty much every other index over the course of the past few weeks and this is a chart that basically I prepared earlier and we can see that from the lows in June we've gone 1,000 points trough to peak. Now that suggests to me that we could be starting to get a little toppy. 6,800 is going to be a very, very big barrier on the FTSE 100 and I think we're only really going to see a move above that if the cable rate moves below 130 and a half or 130 we could see a test hire on the FTSE 100. So why would that happen? Well that could be as a result of potentially a weaker pound, a stronger dollar. So a potentially good payroll number could push the dollar higher. The dollar is a little bit weaker at the moment pretty much across the board. You've got cable at 131.5, you've got your adult 111.50 and you've got dollar yen 101. It's a similar sort of story when you actually look at US markets because while the FTSE 100 is continuing to make new multi-month highs we aren't getting what I would call a little bit of a tapering effect on the S&P 500 and the Dow. We're really, really struggling to make new highs but by the same token we don't look as if we've really topped out quite yet. What I would say is the key support on the S&P is around about 2135, 2137. So if we do drift lower and we don't get back above this line around about 2175 then I'm looking around about 2135 to contain any falls back. At the moment we were looking as if we were going to open higher. We're starting to taper off a little bit in terms of the S&P 500 and the Dow Jones. It's pretty much a similar story here. The Dow is probably more pronounced in terms of its declines probably because it's much more heavily weighted towards much more bigger cap stocks but again there does appear to be a little bit of a potential for a little bit of a rebound here maybe. Maybe we've seen the lows. Certainly decent support between the lows that we saw earlier this week and the highs that we saw in April. Moving on to the German DAX very, very quickly. We can see from this chart here which I've drawn that once again since we peaked in 2015 we are struggling to make headway from that downtrend line that we saw from the peaks earlier. We did have a little peak above it but if we look at the April peaks here around about 10, 480 there's a big, big top around that sort of area which equates to the Euro stocks 50. Similar sort of peak here. So again this is a correlative chart. I look at the correlations between the two. This is slightly different here. We did open above this at the beginning of the week where we've come straight back down again. So again the direction of travel does appear to be a little bit of weakness. If the Euro goes up that's going to constrain the upside on European equity markets but again here what we've got is very, very difficult to make a case for Euro dollar one way or the other at the moment. We appear to be in a broad range and have been pretty much since the end of June beginning of July. Bit below 110 offered above 112 which is pretty much where we are now but it's a similar sort of thing for the pound against the dollar now. This is a chart that I was looking at a while ago. This is a four hour chart of cable and this is the pattern that I was talking about in terms of the trend line higher which we broke out of yesterday when the Bank of England eased monetary policy. However what we haven't done is we haven't broken out of these series of lows through here around about $130.50. So a decent payroll number could see a test of the lows at $131 yesterday. We are very oversold. We could go to $130.50. If we go through $130.50 then we could go even further back towards the lows but otherwise while we're above $130.50 I'm still of a mind that we're in the range that we've been in since the beginning of July and are likely to continue to do so. Dolly Yen, similar sort of story here. We've got big, big support just below where we are now, around about $100.60, $100.70. We can look at that on the 15 minute chart. Actually let's look at that on the 30 minute chart and that gives us a better indication of where we are now. As I say, as long as we can hold above this area of support where we found support on a number of occasions then again a disappointing number could see us and we're off. The numbers are off, 0.3 average earnings, 255 non-farm payrolls, down 31,000 for the Canadian employment report so that's bad for Dolla CAD, not a good number for Dolla CAD, 4.9 on the unemployment rate. So yeah, very positive number for the dollar there and we can see that straight away in Dolly Yen. Now the big level that I'm looking at in Dolly Yen is the highs that we've seen earlier this week around about 101.70, 101.80. We've found significant selling interest through that area throughout the week so we need to be very, very careful about looking to buy into this move higher because while 255 is a good number, we have to be aware that there could be some revisions to those numbers so I'm just going to quickly check out the revisions for the non-farm payrolls numbers to make sure that we haven't been given or haven't been fed up up there and the revision is higher in the June numbers to 292 so we've gone from 287 to 292 in June and we've got 255 in July and average earnings up 0.3 so that's mildly dollar positive, certainly mildly dollar positive. Let's look at the annualized number for that. It hasn't moved the annualized number however that's only 2.6 so these are positive numbers for the US dollar. Does it move the dial in any way in terms of whether the Fed hikes rates in September? For the reasons stated previously, I very much doubt it. So we're going to move that dolly in chart to one side. Bear in mind we need to keep an eye on the peaks through 101.65, 101.70. Keep an eye on that because it's going to take quite something to move us back through that. If we do go back through that then we could go quite a bit higher back towards around about 102, 102.5. Let's look at dollar CAD. Probably won't be surprised to see a chart move higher there and that's exactly what we have seen. But again we've got several areas of resistance on the one hour chart in dollar CAD here just above the levels that we are right now. Certainly I think we could see some selling interest around those sorts of areas. Let's draw that in, 131.50. Let's now redraw it for an hour to see if we can get any further idea of trend. We've got, if I can just keep my hand steady enough, snap that to the high. We've broken the downtrend from the peaks that we saw in late July. The question now is whether or not we can break these series of peaks through here between 131.40 and 131.50. Certainly in terms of the slow stochastic there's certainly potential for us to move higher in dollar CAD on the back of that particular move. Whether we'll see it today, that's potentially doubtful. We're coming into a weekend so we may see a little bit of profit taking given where we've come from over the course of the past few days. We're pretty much back where we were at the beginning of the week, slightly positive, but no more so than that. Obviously that number is not going to be great for goal prices and that's reflected in this particular move here. But again, if we look at where goal prices have been for the past few weeks, it's always been toppy around about 13.60 and a little bit bottomy around about 13.10. I don't expect that to change. One thing I do think at the moment is that oil prices may well have potentially found a little bit of a short-term base despite the fact that those numbers are fairly positive. If we look at the way crude prices have reacted over the course of the past week or so, we can see that the slow stochastic indicator is starting to turn positive. But more importantly, if we zoom in here, we've got a bullish engulfing day and that generally tends to be quite positive. What we need to see now is a break above this level on the WTI around about 41.60. We may well get that when the rig counts come out later today. They've been rising over the course of the past few weeks and that's helped drive the oil price down from the highs that we saw in mid-June down almost 20% at one point. But we've still bottomed out around about this dashed line here. This dashed line here is the 50% retracement of the entire up move from the February lows to the June highs. Now, we've got the 200-day moving average. We've got the retracement there. We've got a potentially bullish reversal here. We can fall back here without negating that bullish reversal. But what I want to see really is a break of this series of resistance levels through here. We can zoom in on that. This is the way that I always analyze an awful lot of my charts. I drill down into the short-term detail after taking a top-down view. The top-down view here is that we've got series of resistance levels pretty much all the way just above where we are now, around about $41.80 and looking for a breakup through those levels to head on towards $42.50 and $43. We're going to see if that correlates with Brent crude because another thing about oil prices, I always try and look for a confirmation with respect to Brent prices and WTI prices because for me that's very important. You need confirmation of moves on both sides of the equation. I've looked at Brent crude and as we can see here it's a fairly similar sort of story. We've oscillated around the 200-day moving average. We have dropped quite sharply, but again we've got this bearish reversal here. Now we don't have the definitive line through the highs or the lows that we had on the WTI chart. That's not as important. It's important to a point, but it doesn't define what I think, but if I drill down again into the four-hour chart I can automatically identify a potential turning point and turning point on Brent crude is just above $44 a barrel on our cash contract. On the cash contract around about $44, so what I would want to see for a break higher on oil prices is for Brent crude to break out through $44 a barrel and the WTI to break out of its resistance level at the same time and that in turn should take both prices higher and hopefully that will then push prices up towards this sort of area here which is around about $45 a barrel which had up until the end of July supported Brent crude prices. Let's quickly look at Euro-sterling because this Euro-sterling chart is actually quite important in the context of sterling direction as well. This is a four-hour chart that I'm looking at here. It's looking very overbought, but if we look at these series of peaks on Euro-sterling all the way through 84, 90 and 85 we can see that this particular level on Euro-sterling is very, very important. It's something that I have highlighted on a fairly regular basis on my chart forum posts throughout the course of the week. On the right hand if you click on chart forums whenever you look at your charts if you want to see any analysis of a particular asset then we're not going to do all of them but certainly my colleague Jasper and I do fairly regular updates on some of the more popular products that we do. This morning's update I basically stated that we saw a sharp rebound yesterday from the 8360 level obviously down here. We've again run out of puffs at around about 84, 90, 85 and this for me I think is the key level. If we want to get back to these highs that we saw in April which you could also argue corresponds with the 128 cable lows then what we really need to see is a break through these highs here. Otherwise the risk management trade here is to sell Euros and buy sterling with a stop loss above this resistance level here. That's the effective risk management strategy rather for Euros sterling. Certainly we've seen it try and get through that 84, 90, 85 level four or five times over the course of the past day or so. It's not to say that we won't get it to do that but what I've seen thus far we've seen a lower low there and a lower low there. We could see another test hire but ultimately the low risk trade in terms of losing money relative to your potential profit which is a move back down here, the odds favour a short-uro trade long sterling trade if we get back towards 84, 85, 84, 90. That's essentially how I manage my risk the whole time. I wait for the market to come to the levels that I'm comfortable with and then trade accordingly. Now looking back at the sterling dollar we have broken the lows that we saw yesterday which now brings these series of lows here into focus and this really for me is the next key tipping point for the pound against the dollar. If we break this low here then I think it's quite likely that we're probably going to see a move back towards the lows that we saw in early July and we can see that reflected in the way that the euro sterling peaks were. The only difference here is this is a dollar move as opposed to a sterling move because we're not seeing an equivalent move in euro sterling. We're also seeing euro dollar fall a little bit lower as well simply because it's a dollar move but again we've got a series of lows through here around about the 25th of July that could well provoke a little bit of a rebound if we get there around about 110.60, 110.70. Again it's just breaking it down, breaking the currency pairs down and looking at key support levels, key resistance levels, looking at where the market's found support in the past, looking at where it's found resistance in the past trading accordingly. If I break this chart down here it's a similar sort of story if I just draw the line through the lows there, helps if I draw it in the right place but we can see straight away around, there has been decent support around about 109.50, 109.60. Again you're managing your risk once it gets to within a few pips of a certain level you can put on a fairly low risk trade with a fairly tight stop loss because you're taking a view that if a market has found resistance of support at a previous level in the past there's a good chance it'll find support or resistance there in the future. And ultimately for me it's no more complicated than that. I don't tend to overburden my charts with too many lines. Sometimes I get a bit lazy about not taking lines off when I'm not using them anymore but ultimately what I try and do is I try to keep them as clear and uncluttered as I can. Now you can argue that this chart does look very, very cluttered and who am I to argue? But certainly in the context of where we've been over the course of the past few days and weeks this chart's really got very, very few areas of support or resistance on it. It's trading in a range and we can see the bottom of the range and we can see it very, very clearly here as well. If we extend this line to the left that's the post Brexit referendum lows. So it spikes lower but we pretty much close a long, long way away from where we actually traded on the lows. Pretty much up where we are now around about 110, 111 even, 110.5, 111. So it's not really painting a particularly inspiring story but certainly I think in terms of where the line of lease resistance is on Euro dollar it does appear to be edging ever so slightly lower. I'm certainly borne out by this 50-day moving average here because if we look at the way that it's behaved over the course of the past few days it's found support, support, close below it, resistance, resistance and now we're retesting the 200-day moving average which is pretty much just below the, which is just below that line that I drew in a few minutes ago. So the moment we're trading in a corridor on Euro dollar, the bottom of that corridor is around about 110.5 and the top of the corridor is around about 112. And that's why I keep those moving averages on there. I tend to disregard them when I change to a four-hour chart. The only time I have these moving averages on a chart, 50 to 100 and 200 I only look at them in the context of daily and weekly charts. Other than that I ignore them. So even though they're on my four-hour chart, I don't really take that much notice of them. Right, before I finish up, a couple of things to look forward to next week. We've got Chinese data out next week so that could be fairly important in terms of risk appetite. But certainly in terms of where we are now, if Chinese data disappoints next week then certainly I think there's a distinct possibility that we could see further fiscal stimulus from the People's Bank of China. And that could certainly help, I think, keep a certain amount of a certain bid bias to equity markets going forward. Again, just reiterating on the main indices, keep an eye out on that 6805 level on the FTSE 100. I think it could struggle to get through there. I think we could certainly have a look at it. It certainly feels like it wants to go there. And it's a similar sort of story, I think, for the S&P. I think he really wants to try and have a go at these previous highs that we saw earlier today. So I think for the rest of the day we're going to see a fairly positive dollar story. We're going to try and push lower. I don't think we'll have the impetus even to push lower. But as we head into the end of the trading week, another thing to keep an eye out for next week is also the latest manufacturing and industrial production data for the UK for June, because that could give us an indication as to whether or not we'll get a downgrade to Q2 GDP growth for the UK, which came in at 0.6%, which I was actually quite surprised by. I thought we'd come in a lot better than that. But if we get disappointing prints on Tuesday from June industrial and manufacturing production, that could actually feed into the overall dovishness that we've seen over the course of the past day or so. And potentially way on the pound. Really I want to see a move back above 132 on cable to really make the case for a move back to the highs that we saw earlier this week. But ultimately I don't expect to see a move much below 130.50. And I think we'll continue to range straight between 130.50 and 133. Okay, so I'm pretty sure I've covered everything that I've hoped to cover. Before I finish off, ladies and gents, is there anything else that you would like me to cover? If not, I'd like to thank you all for your attendance today. And look forward to talking to you on Monday, or my colleague Jasper on Monday, where he will be hosting his weekly look at the markets at 12.15 on Monday afternoon. All right, being asked about Stirling Yen. Yeah, actually that's a very, very good point because I talked about Stirling Yen in a previous chart. A few weeks ago we saw a very nice bullish reversal on Stirling Yen and ever since then we've pretty much gone lower. I'm a little bit concerned about Stirling Yen at this point in time. It does look a little bit soggy. But I'm still of the opinion that what we really need to see now, I think on Stirling Yen, now that we're below 133.75, the bias remains I think for a retest of these lows here. But if we get back and hold above 133.75, then I think potentially we could go back and retest 135.140. At the moment I'm a little bit undecided about where we go to next. We broke below this series of lows through here at 133.75 and we've now traded sideways. My biggest concern is we drift lower and that certainly is a concern now that Cable is looking as weak as it is. And I think there is also potential that unless Dolly Yen gets back above 102 or those highs that I talked about earlier today, 101.60, 101.70, that it could drag this lower. So I want to see this get back above 133.75. Otherwise I think there's a good chance we could drift back down again. Good question. Why don't I pay attention to moving averages on shorter timeframes? The reason for that is because ultimately on shorter timeframes they're much less effective because there's still a significant lag. Moving averages by definition are lagging indicators. Shorter term time frame charts, I tend to want a quicker reaction or a quicker response time. And because moving average is lag, obviously it really depends on the moving average time frame that you use. But let's say for example you use a 10 event or a 20 event moving average, you're going to have a lag of at least two or three candles or two or three bars before you get any potential idea of a turnaround or a change in trend. So moving averages are all well and good, but they are a lagging indicator and I think that support and resistance levels are much more effective because they're certainly much more immediate. You can identify them straight away. Whereas with a moving average, you need a little bit of a sideways range to start to trade before you start to get a downward sloping moving average, start to turn into an upward sloping moving average. Does that make sense? I'm hoping it does. Perfect. Okay. All right. Well, I will be posting this on YouTube later today. But otherwise, thanks very much for listening, ladies and gents. And if you do have any questions about any of what we've discussed, you can find me on Twitter at mHusen underscore CMC. Otherwise, thanks very much for listening and all of you have a great weekend.


It's interesting when you look at the misconceptions and myths around drug driving They're very similar to those that were around 30 years ago when people looked at drink driving. A lot of the people then as now say My drug intake doesn't affect my driving or I'm a very experienced driver. I only consume a little bit I can tell when I'm impaired Some people actually say I drive a lot better after consuming my substance Unfortunately, what we are seeing is that the strike rate is more prevalent these days In terms of drug driving for the amount of tests that we're undertaking In comparison to drink driving with drug driving for every two tests that have been undertaken by officers We are having a positive return in driving. You need your reactions. You need your perceptions You need to be able to coordinate the body. You need to be able to think and plan ahead One of the worst things you can do is mixing psychoactive drug use with driving There's a high prevalence for cannabis being detected in the saliva and methamphetamine based drugs on top of that Cannabis uses their responses to situations such as breaking and hazard perception is much slower More increasingly detected on the roadside is methamphetamine. You find that people are much more aggressive in their driving There they take many more risks. If you are consuming illicit drugs You are more than 10 times likely to be involved in an accident if you are driving Unlike alcohol where you have a discrete measured dose of alcohol in a container or a drink There's great variation in these illicit drugs So what may occur as a time frame for one person may be very different for another person So effectively if you are driving you are operating anywhere from two to three tonne of glass rubber and steel If you are consuming drugs and you are involved in an incident you are making extraordinarily poor choices and The impact reaches beyond you and reaches out to other people whom you may either Injure main permanently or in worst-case scenario Result in a fatality if you are under the influence of drugs do not get behind the wheel


If you are looking for a little bit of hand-holding to get you through a knit sewing pattern or maybe a jumpsuit sewing pattern or both, you are in the right place. Today, ultimately, we will be cutting out our fabric. So exciting, so scary. Before we jump in, be sure to like this video so other people will see it. Subscribe and click the notification bell. If you're new here, I'm Lindsay. Hello and welcome. Leave a comment introducing yourself in the comments section below. Sew along videos like this one go up four times a year every couple of months and I cannot wait to get into this one. Also, this video is sponsored by Aliso and their brand new TG1600 Pro Plus iron. I'll be talking to you a lot more about this later on in this video, but let's talk first about choosing the right size for your pattern. All right, so first things first, we need to figure out what size we are going to cut. I always, always use my fast fit system. You can get this off of my website. I will have a link in the description box for you, but I filled out there's instructions and everything with the workbook, but I filled everything out and I came up with a bust size of 18, a waist of 20, and then a hip of 22. Technically, my hip should be a 24, but because there is six and a half inches of ease in this pattern at the hip, I know I have a little bit of wiggle room there. So I'm actually going to size down to a 22 and do a small little full seat adjustment because a lot of what makes up my hip is not necessarily the full circumference. Like I'm flat in the front at my hip, but I have a bigger bum. So I know that that full seat adjustment will make up for the sizing down. I also, the other reason why I want to do that is because I don't like jumping more than one size when I'm grading. So I have an 18 to a 20 and then a 20 to a 22. If I did 20 to 24, things get a little bit iffy there. All right, so now we need to press our pattern pieces to make sure we get all these little wrinkles out. I am using the new Aliso iron, the TG1600 Pro Plus. I talked a lot about all the additional features that this one has in episode zero. So be sure to check that out if you haven't already. But when you are pressing pattern pieces, you obviously don't want any steam and you don't need that much heat either. I love that with this iron, you can easily adjust those settings. You can go ahead and press your fabric as well. For that, you'll need lots of steam and only the heat that your fabric can withstand. My fabric is made of polyester with a little bit of rayon and spandex blended in. None of those fabrics like heat. So I'm going to leave my heat at the higher end of synthetic and let the steam do most of the work. Finding an iron that has like a lot of steam, a lot of good steam without a lot of heat is actually kind of tricky to find that balance. But I find that Aliso irons do a great job of handling both of those settings together, like relative to each other. Check the description box for a link where you can get $40 off your iron and free shipping. And then we need to take a look at this pants pattern. I always take a few measurements on my pants. This one is no exception, even though it is a knit and again, a little bit more forgiving. But what I do is they have the crotch line marked here. So I find the crotch line for size 22. And I measure up to find the like rise. And then I also measure over to the like crotch point in order to find the crotch depth. And then I compare that to my own measurements. Actually pretty happy with this. The other thing I want to point out though is the shape of this curve is very flat. I have this little bendable ruler that I've like shaped. Like I ran this underneath my crotch. So this is the shape of my bum and this is the shape of like the front of me. And this little rubber band is the middle. So if I put the rubber band at that crotch point, you can see that my bum is a lot wider than what this calls for.  But I don't love just like whacking two inches off of the curve. So I will pencil this in. I will trace this onto my fabric. And then I will decide after I can do my first fitting how I like how this is fitting.  So so we will repeat this process for the front and double check that crotch as well. The only other thing I wanted to check was the inseam because this one looks really long to me. Our inseam ends up being 30 and five eights. So that I need to chop off roughly three eighths to half an inch. I will need to shorten. So to do that, you find your length Lincoln and shorten line cut through this. And I'm going to shorten by this very, very minuscule amount that we have over here. Not a lot. I could probably just take a deeper hem. All right. So now I take my I have a paper rotary cutter. I'm about to blow y'all's minds. I know it and I'm going to use that to cut out this pattern. So I'm just going to cut along size 22 and then grade into a 20 at the waist, which is up here. So um this dot is roughly my hip and that is a 22 and that is a 20. So we will come in something like this. You just kind of rotate it around until it gets eased in nicely between the two lines. And that will be my new hip measurement. All right. And there is my back pants. I will repeat that process for the front. The front does not get a full seat adjustment though, but I will grade at the side seam to accommodate my size 20 waist and 22 hip. And then for the bodice front, I'm going to be grading from a 20 to an 18 that because this is like a square and it's all straight lines. You just take your straight ruler and you grade it out just like this. Lost my pencil. So we're going to do it with this marker, but something along these lines here. Right. And then all through this we'll get the same size 18. We will double check this on my ditto form and you guys that don't have ditto forms will titch you fit on your own bodies here in a second. We've got a beautiful pocket that's going to get sewn into the waistband a little of that. So that just gets cut out as is the over back, the over front and the bodice back all get that same treatment that I just showed you with the front from the greeting out.  So all right. So I got her the pattern pinned up on my ditto form. This is an exact replica of my body. It makes tissue fitting and assessing some of these things a million times easier. Basically I went in for this body scan. It's like a 3D thing like a spun around on this kind of like a Roomba looking thing. And then they use that to digitally create this dress form. It is completely pinnable. Obviously I have my bust line, waistline, hip line, center front, center back all marked on the ditto form. She is just a real powerhouse and makes adjustments like these and assessing patterns so much easier. All right. So I've got her up on my ditto form and you can see I have a little bit of gaping here in the front. But when I turn her to the back, nice and flat. So I know it's not an issue with at the shoulder. Instead, the issue is just within the front. The center front angle is just not necessarily sloped right for the shape of my breast is really all it comes down to. So I will pin out this little itty bitty wedge. It ends up being about, I don't know, a quarter of an inch or so. So I will pin that out out to nothing at my bust line. All right. Speaking of my bust line, you can see that the bust point is the circle with the plus sign through it. And that is hitting exactly at my bust apex. That makes me so happy and so excited. So I love that the line from my high point shoulder down to my bust point is spot on. All right. So then we want to check for the waistline. And this is when things start to get a little funky monkey with this pattern. It looks like the waist. So here's the patterns waistline. Here's my waistline. And if we look at the pattern, you can tell there's no intention of it to be blousing over. So I don't think we need all of this extra length through here. So what I will do is I will grab this marker. And well, ironically, it happens to be right at the length and short line. So that makes it really easy, but I will just draw on the pattern where my actual waistline is. And then I know when I get back to my cutting table that I need to remove whatever distance this is. Obviously, you will be adjusting that in the back as well. The front is a little bit wider than the back. You can see how much this is sticking out where this is like hanging close to my body. So it's causing the side seem to come to the front a little bit.  I know a lot of this is going to get brought in. So I'm not too concerned about it. This were like a fitted like a fit and flare with no elastic at the waist. That would be a concern. But I'm going to leave this as is the only other thing that I like to check for and because especially because this pattern is sleeveless is through here. Let me come around to the other side so you guys can see through the arm side. How much space do we have here? The last thing we want is to be wearing this and then you can see into our garment or into like into our body. This one back here we kind of need in order to like round our back and move around. But this one here makes me a wee bit nervous because it is such a gaping hole. So to fix that similarly to how we did in the front and it's probably related to the same issue in the front with there not being any bust starts on this pattern. Same similar situation you just fold a little pleat and now it hangs closer to the body.  So I'll take you back to the table where we can like transfer them over one. So the amount that needs to come out drum roll please is yeah right at well it's like one and seven eighths of an inch. We can draw in our new length and shorten line which has to be perpendicular to the center front. So I know this looks a little funky now and then I'm going to go ahead and draw up one and seven eighths of an inch. All right cool and then cut through one and then bring all of that up to the second line that we drew and then we're going to tape this in place and now we have a bodice that is shortened by the amount that we need. So for the side seam it's as easy as putting a little piece of paper down through this area. Tape it you don't need to tape down here but you can tape through here and then grabbing your ruler again and we're going to go from the size 20 to the size 18 just like we did when we were cutting it out. Now all of this that I am doing to this bodice front and what I'm doing to the bodice back as well has to be repeated on the overlay piece. All right and then for the back all we're doing in the back is the lengthening and shortening. It goes the same way as I just showed you here and I just want to point out one error when you come across your facings your facings will say a, b, and c but you do not need the facings for a and b because we have the overlay um and it's illustrated correctly on the cutting layouts it's just marked correctly or incorrectly on that pattern piece. The other thing that I want to say about cutting out this pattern is that don't feel like and I mentioned this a little bit in last week's episode in episode zero don't feel like you have to use your fashion fabric for the bodice front and bodice back the overlays yes absolutely but you will not see the bodice front and bodice back you will only see the overlays so I'm going to be using the tree co-winding for the pocket and the jersey for the bodices okay so you do have some options there all right let's get cutting this fabric again all we need is over front a and b we don't need the pocket we don't need the actual bodice we don't need any facings and then just our pants so the layout here is the one that I'm following um folded completely in half with the selvages matching and all I need is five six seven and eight so that's what I'm going to cut out of that I'm just going to lay these on my uh fold lines both of the both of the bodice over fronts and over back the what do you call them the bodice overlays I guess we can call them that get placed on the center front and center back here you probably can't see off camera a little bit and then the pants get placed in this area here um and then cut out the other pieces from your lining fabrics and we are good to go for today a lot of information I completely understand if you guys are like wait what um but this is what it takes to kind of prep your patterns and quite honestly you're not spending this much time on them that is when you tend to make clothes that you're like oh it's okay or you know I'm really proud of how the construction turned out that fits not the best um which is why I just take the time to do this every single time so that I know I can end up being super successful in the description box we have lots of information for you guys there including a link to my fast fit workbook that you will need to figure out the size um the same way that I did we will have a link to the eliso iron we will have a link to ditto form and her scan schedule um lots and lots of information down there so be sure to check the description box if you didn't watch episode zero of this so along I've linked it here for you it goes over the pattern online and in-person fabric suggestions and the notions you need and a lot more I'll be back tomorrow for episode two where we will sew the bodice but that is going to do it for me today y'all thank you so much for watching I will see you all very soon bye


What do you notice about these candles? There seems to be a wall of resistance. Volume bars show aggressive buying and volume dots show where the transactions happened. For every active buyer, there's a passive seller. But when we turn on the liquidity heat map, the order book is surprisingly thin. So who's taking the other side of all this buying? It's an iceberg order. These hidden orders are typically placed by large institutional investors. The iceberg indicator confirms a fill of over 2,500 contracts. We don't know the reason behind it. They could be entering, they could be taking profit, they could have a one hour time horizon, or a one month time horizon. They could be simultaneously hedging in different instruments, or entering a naked short position, and will become trapped if the market moves against them. So, how can you use this information in your trading plan? One strategy would be to scalp in the direction of the iceberg, using it to manage your risk with an extremely tight stop. You could also back test a breakout strategy, as when the iceberg is fully filled, there's often a surge of momentum through the level. Or else, you can just use the iceberg to add context to your existing setup or bias.


Bugly I checked out the definition this morning. It actually means but ugly So but I had it as buggy and ugly but What I want to do is just share a hard truth with you always that fundamentally we build extremely buggy web applications and we as in you and There's many reasons for it. There's many reasons for it. One is Logging is so complicated. So we build a big fortress and put applications behind it and Features behind it and Because it provides some sort of sense of security We go from building apps really to building really large fortresses You know you go through of this big gate this moot this security Gate and then all of a sudden you've got access to everything That creates an extremely slow archaic large Want to be web application, which is really a website with a whole bunch of proprietary Glutton inside it They're expensive extremely expensive and as an architect at ING we have this discussion all the time. We want to Refactor but refactoring comes in extreme cost We want to move from one framework to another and it requires such a big move that we end up having Really a Frankenstein of frameworks many of them. It's not really this one. It's not really that Also, it's extremely slow because it's so large And if you take a look at the websites that are being built today and even the ones that already exist They're extremely large and disruptive So it's not good news actually, it's so bad that That there are people in the community that actually have websites that track your websites One for example is Aussie outages calm This is a community where they are monitoring the availability of websites and the Essentially the bad experience of websites in the finance industry and the top four banks in Australia Collectively only offer 91% availability. That's 33 days Where they're out in a certain year 33 days you can't bank in the country That's scary, right? 33 days, it's huge And the best part of it all is that they tell their customers on Twitter. I guess what we're knocked out for the weekend So plan ahead God help you if you get a date or something like that. You're in trouble because sorry, baby I just got for $40 So this is part of the problem and and it's almost like it's okay It's almost like it's all right. We're using jQuery. It's fine It's okay because we're with we're using Redux or whatever we're using embo or something like that And what I'm trying to highlight is that all of that largely is fundamentally from a business point of view irrelevant But if you take a look at the growth in the transfer size You'll see that most of our applications and essentially our pages are growing Dramatically, there's an organization called HTTBA archive who actually trends your stuff, believe it or not there are people that actually find this stuff fascinating and The size of a page now a total transfer for a page because these aren't single-page applications It's the same size as doom the game who played doom You've all I know you all played doom all right and Doom ships with its own 3d rendering engine believe it or not has its own weapons and a whole bunch of stuff There's some really good nuggets and Easter eggs inside it. All of that is actually 2.4 meg That's the size of a page that we're downloading today every time a customer goes to a banking application or any application to be honest with you Because if you take a look at these guys, that's what they're saying It's a doom every time strange But that's okay. Guess what there's more to law If we can't fix it CPUs will It's okay. The customer will get a new phone that will go faster on their phone and actually There is some science to it. There is some truth behind it because as you can see here some Organizations have been publishing benchmarks for for the new iPhone 7 and it does perform extremely well but for every law there's an anti law and What's law? I think some people say it's pages law and gates is law. I don't even know Fundamentally saying that the software efficiency due to codecraft feature. I just a whole bunch of other stuff Hives every 18 months anyway Actually, there's another reason it's fundamentally because we build applications to build our resumes What we do is like bubblegum we go and we say okay. Here's a new framework I'll chew on that for a while and when the taste goes. I need a new one I'll get a new job with someone else and leave this big application here Yes, yes And so what happens is we end up with this big fat monolithic monster in an organization That the new developer looks at it and goes I need a framework Note the loop and it obviously ends up having excessive refactoring. We have a Frankenstein a proprietary opinionated Implementations it's extremely not shareable It's silent. It's a mess and fundamentally to be honest as front-end developers There's a law called Conway's law and you I'm sure you all know it We all read it all the time But basically says the communication channels of the organization will fundamentally reflect in your application Yes, we try to solve everything in the front-end So the front-end gets bigger more frameworks and blah blah blah But when we talk about architecture fundamentally, we're talking about Code organization, whether it's MVC or something else. We're always talking about code organization, but the unit of change is still the application Mergers are expensive. They're difficult to share. It's extremely complex Composition is difficult and we end up with the mess So let me give you a real example Let's take four scenarios banking scenarios account opening move money bills and transactions The company says okay, we want to do a project on move money. That's okay And so we do an assessment we take a look at the channels the front ends We take a look at some of our services We take a look at the core at the back end then possibly we take a look at some platforms and some some operating Systems and we come up with yeah, this is an approach. We're going to do it this way But what we discover in which we all knew is that the core makes assumptions about platforms The services make assumptions about the core and then the channels make assumptions about the services and fundamentally We have a really big big project That's okay.  Let's adopt another framework. I'm going to build it a modular framework Which dr. Carlos Brown in a book called design rules actually did one of the biggest assessments on modularity and Fundamentally came to the conclusion that we all intend modularity, but it's really a monolith And then we end up going with different opinions because as time progresses We we end up adopting different opinions it becomes buggy and then we wait for the new event and that new event typically is when the developer leaves or A new framework comes out and then it comes really really fast so Is the problem the the languages or is the problem the platform and as sir Alex Russell says the problem is Fundamentally about the platform and I'd like to add the source of the people So the web needs you The web needs you to get serious about being a web Developer and if I'm doing anything what does it what does it mean? What does web mean? It's actually means that you're a standards-based developer so you need to take a look at new use cases and once you find new use cases work with those new use cases and Basically converge on certain agreements on what those primitives could look like and also abstract them out so that we can start using them with polyfills or something like that and then when the industry body Sees and understands the value we create they move them into primitives and into standards But we have to let go and go to the next one not continually for fight over and over again And the things like the extensibility web manifesto is actually starting to do that and promote that type of language in that type of thinking So what does it mean? It means that true beauty is on the inside It's not just about how it looks, but also about deep inside how it works. It has to be performant So at ING we take Google Rails seriously so serious. It's actually become the criteria for our non-functional requirements Yeah, so we now have very specific criteria that the responses have to happen within a hundred milliseconds Applications have to be less than one meg They need to be secure. I won't go through this security standards, but what I will do is this Guys security headers.io scan your websites and take a look if you don't get an F. You'd be surprised Seriously banking sites most of them and I've scanned most of them get score an F And F couldn't mean a few things depending on how you take it Also build your applications to be immortal and what we mean by immortal is that it's not just that it's bulletproof in the sense That it never dies, but it's also long-living So adopt and embrace standards Use the platform for what it is Push the state to the client not in the server Because the ultimate state is the user build offline first Unplug your cables turn off your Wi-Fi and build like that and try to make sure it works offline first handle failures and be and go with the progressive Applications but also when you're going with modularity Understand that we want it. What does modularity mean? It means that we have to make it design time independent that I can work on this thing independently of the of the whole But at runtime it's got to work interoperably So it frees me at design time, but at runtime it works really well as a member of the wider community of components So now the unit of change is the component. It's not the application. It's the component And when the component is the unit of change we assemble applications based on components We don't develop applications anymore we develop components and From those components we can assemble very different business functions For example at ING we say that the customer service team that answer phone calls Need to see the same experience that the customer sees on their mobile or on the web To me it sounds like sharing components Yeah, the only difference is one component is embedded with a telephony so that with telephony features so that they can answer phones The other is not so our definition of done This is what we put down as a quality criteria for a component Every component in the bank must have its own repo It must have its own lifecycle and it has its own repository. It's built with internationalization out of the box It's built with accessibility out of the box. We no longer debate whether those who have partial Vision or vision impaired are some sort of subclass customer We expect it to be accessibility compliant day one Also, the tests are baked in day one the thing works There's even a demo and I would go so far as to say that we need to move towards some sort of Demonstration driven development not just test driven development get the demo in the hands of the developers as quickly as possible Show your stuff works We've even gone so far as using blueprints to mock the API's at the back so that custom elements now have a one-to-one relationship with API's and We've actually produced a documentation and this is clear criteria for what we call ready based components for consumption by the next developer So when we take a look at the architecture most banks and organizations were or are still unfortunately in the big blue box and Some are having discussions about moving towards a client server based mainframe still back-end database scenario and The rest of the world is stuck in this hole now where they're taking a look at the middle the middleware and API's and so are and having discussions about microservices, etc. But we see an opportunity We see that the opportunity is Potentially we see the micro service movement, but our ing we've gone one step further We've predicted that the world will fragment even further and our architecture needs to look like that We want to have custom elements with the main base services at the back and Those the main base services can be part of that customer element that custom element scope and now It means when you ship a custom element to another team. It also comes with its API's Not only the API's for component interaction, but also API for back-end interaction It goes a little bit further We also have to take a look at the way we do API's because we want to minimize the number of chattiness between components and back-ends So our responses are now rich responses and it means that when I move money I Also get the balance back and the list of accounts So I don't have to do subsequent calls to get hey, what's the new balance and what is the latest accounts of the customer now? With the response I can do some data binding and then publish the the new balance to all the components that need it and Fundamentally means 50 50% less IO, but it also means I now get to use data binding the way it should be used So how does it look? It's a technical summit. So let's talk about it Fundamentally we produce the API's Automatically because we have mocks and and and and interfaces We have them very clean We know what they are and we now have an outside-in model where we work with our business and say what do you want? The API is not driving the application or the component the requirements of the business and the user is driving the API And we generate the API's because let's be honest. It takes forever to wait for a back-end person to give you an API Yeah, so stuff it would just build it ourselves Conway's law and When we get the API's the response from the API's very simple We update the the variables in our store and you can see they're all custom elements and the data binding then becomes available to all the components that are listening and The process repeats itself over and over again And if you notice the actual system is extremely simple. It's so simple that When you think about it, it's actually an end-to-end working system of a collection of components our entire digital front-end particularly in In ing if we take a look at the Australian scenario is completely web components and custom elements. There's nothing else There's no frameworks. There's no additional libraries, etc. Etc. It's fundamentally just a whole bunch of custom elements and we use BFF which is back-ends for front-ends in order to To abstract those those API's and make them bound to the to the custom elements But what's important is that our API's are not cattle We're not stressed about the API's themselves that way you have interface and contract based Experiences the API's fundamentally reflect what the customer requirement is So they're not pet. Sorry. They cattle API's fulfill the demand of the experience and we come to the understanding in the agreement that poor back-ends also equal poor front-ends So you have to fix your back-ends as well You can put a nice custom element in front of an Assistant and give that in the hands of the customer, but if your back-ends are crap, then your front-ends are crap So believe it or not I've heard Taylor and Matt say over and over again doesn't element for that doesn't element for that Well ing there is there's 350 of them that are being used and our friends all over the world Including the Netherlands and Germany and Belgium, etc. Are building custom elements for the group to use over and over again The number of API's we have that are being used. Honestly, I've lost count and to be honest I really don't care so long as it returns the data that I need and it's bound to the custom element We're fine If you take a look at it there every application that you build at the front end needs some visual components and rich visuals some Navigation utilities and customer features most of those we want to source from the market We don't want to build everything ourselves whether it's a telephony component with Tulio or it's a Charting component with VAR then it doesn't matter if it's available in the market. Go get it Ship it as a custom element and we will build the pieces that are in the gaps the stuff that's specific to us banking So we're assemblers first and That's the key message We are assemblers first being an assembler means going to the box of Lego find the Lego piece you need and then put it Together don't go build your own and most developers love file new and we need to move away from file new and go into the box And go to the repose and find one that makes sense read the markdowns There's a reason why we've written them and We're craft people second if they're not there then we craft So what does it look like at runtime? Well, fundamentally, we have single-page application That's HTML 5 and we have two files our entire application is two files index.html and ing.js Only data ever traverses the network. So all you ever see when you look up the The network you see the X HRs just going across state essentially managed and into the client and All the business logic what constitutes business logic is in the back in the data center And there's a reason because data centers have 40 gigabits per second networks So we push all the service aggregation and service composition into the data center where it's faster So the front end is extremely light and extremely thin So you need to break Conway's lure a little bit and have a conversation with the people in the back And if they don't want to respond then do it yourself What is our runtime metrics look like we've been running? We've been working with polymer since point five and we love it And when 1.0 came out we were ecstatic and now in this current state This is what it looks like running a runtime the industry average if you look at GT metrics for page speed is 81% ing is at 98 Our page load industry average at 5.8. We're at 2.3 and that's not good enough as you can as you know from the Google rail discussion Our page size the industry average you heard earlier is the size of doom ours is 538 kilobytes. That's the whole app That's everything and The request industry average for requests believe it or not is 69 and with htp1 htp1 It's actually at 2 so it becomes even worse in terms of serial requests and ing it's 9 So now what does that mean? Let's go back to this scenario when we do move money and We do the transactions project. They're not coinciding and they're not contending for resources Bills can also go in parallel as well and have more concurrent development. In fact, we can have a lot of concurrent development Because the architecture is broken up. We don't have a monolithic per se a monolith per se But the real advantage of all this is that we have a culture of motivation people are autonomous Because they can do it inside their component They have purpose because they know they're working to a business end in a business goal And they're also masters of their domain because they can use the right technology for the right function But why web components? I get this question a lot ing bet on web components really early Apple said something along the lines that They are the web standards are the web Yes, there's lifespan benefits. There's parallel delivery as I said earlier time avoided There's also the value of business options the fact that you can mix and match and imagine what scenarios you could do If you can take one component into another business stream But really from my side, I actually want to talk about the facts Again the polymer team has been saying over and over again that use the platform use the platform use the platform So we went to github and countered the lines of code. I've thankfully they actually offer a function that does that and I Think the chart speaks for itself There's four times more markup With polymer than any of the other frameworks that are available and there's 10 times less JavaScript This is over three years Or three years since the inception of polymer That tells you volumes If you want to be a JavaScript developer and you want to solve platform problems with JavaScript You will have a problem with polymer But if you want to solve true customer problems with the web then polymers your choice So final slides Learning and unlearning What we found is more people are framework developers than they are actually web developers So we had to teach them HTML 5 again. Sorry, but it's the truth. They don't know what immediate queries We don't know what sections are and so on and so forth Also, you need to build a lot of automation with your tool chains to make their lives a little bit easier You need to offer samples and guides But probably the most important thing is get them to assemble something first not craft something assemble Build their first component second and then finally evolve it if you can't solve it. Thank you


We're back. Bitcoin is up 6% so far on the day as we continue on this bounce back from a 27% pullback the last couple weeks. Now, with the option contracts out of the way, finally, we can continue on our way back to new all-time highs. Today, I will show you guys how to make the most of this bounce back opportunity with the exact trades that I will be taking. Stay tuned. Hey, what's up? Jay here and welcome to Bitcoin Daily bringing you guys the best tips, tutorials and ideas to help you guys become profitable and successful investors. The goal of this channel is to empower you guys with the knowledge and resources to take you up to that next level. So make sure to smash that like button and if you guys are new to the channel, don't forget to subscribe and turn on the post notification bell. Ding, ding, ding. Get it? That's you turning on the notification bell. So first off, let's go ahead and cover those trade setups that we gave you guys on Monday's video. So that first trade setup that we gave you guys was at $54,000 entry, which we really liked. And as you guys can see, if you would have taken that entry, which happened right around this range right here, you would have been able to write it up all the way to about $57,000, which of course would have been a profit of about 55% if you use 10x leverage like we did. That next entry that we gave you guys was that 55k entry. So if you guys use that one and wrote it up to 57, you would have been able to do about 36% profits. And if you guys took profits and then when the price shot down, you guys grabbed this bounce and took profits again, you would have done that 55% and 36% two times. In Ethereum, guys, Ethereum has been relentless. As you guys can see here in the chart, just grinding higher and higher and refusing to come down, right? So if you guys took that first entry we gave you at $2,500 and wrote it up to the top where we are now, you would have done about 60% profits if you use 5x. If you instead entered at $2,600 and wrote it up, you would have done about 38% profits. And if you entered at the previous all-time high at the time of Monday and entered above $2,650 up to $2,800, you would have done about 28% profits if you use 5x leverage. If you guys missed any of these trades, do not worry. We have more trade setups for you today. Alrighty guys, so we spoke about this move that's currently happening right now on Monday's video. We pointed out that this exact pattern, this exact move, what we saw it before here. Look at this. If you guys looked back into February and looked at this drop and then this big green candle, guys, look at this. It's the same exact thing, the big drop falling wedge pattern and then a big green candle. We're basically doing the same exact thing that led us to new all-time highs. So guys, that's what we're expecting here. We're expecting this move, which we saw already. Then we saw this consolidation right here, consolidation right here and then a continuation to the upside. Right now we're in that continuation phase, I believe of this move. So I think that we could be testing 60K this weekend. You can see here that the RSI is in neutral territory, so we're all good there. Nothing to worry about because it was reset with this drop. If we go ahead and zoom in here to the four-hour timeframe, you guys will see here that we had this bull flag here, which we did get out of, but then we bounced back up at that 52K level and this was after this dump. So if you guys didn't know, this run up here was because of the rumors that Facebook had bought Bitcoin. Then as soon as it was found out that it was not true, then that's when you saw this huge dump off here to the downside. So that's another typical, guys, buy the rumor, sell the news. It's very, very common in the crypto world, so you guys always have to be prepared for any rumor type things in the market. Then we also had the option expiration contracts today, which happened this morning.  If we zoom out a bit back to March 26 when we had the previous options expiration contract, you will see here that we had this huge green candle follow on that same day and that was a 7% move. Today, we've had a 6% move and you saw after that, it just continued up. We consolidated a bit and then continued up. That's when we set the previous all-time highs. I definitely think that it's a possibility that in the next two weeks, we could see a new high. Remember, right now, we're just following exactly what the price has done in the past. You can see here in Ethereum, it's just been pushing and pushing and pushing. Nothing's been able to stop Ethereum for the past week, even the past two weeks. Although it had this 20% drop down, it literally jumped right back and it's continued on its way to just set new all-time highs day after day right now. Of course, that next resistance right now is currently at that $2,800 area. It's crazy to say because on Monday, we were just at $2,500. Today, we're at $2,800. I definitely believe we will be hitting $3,000 in the next possibly week or so. If there are any pullbacks here, the levels that we're going to be watching is at $2,700, $2,625, $2,424. The biggest level here is going to be this Fibonacci level, which is the 23.6% level, which is right around that $2,300 area. We're just going to be watching for those big whole numbers in Ethereum. Next, we're going to jump into some trade setups that we're going to be watching this weekend. Again, I am bullish on the market for the weekend and now that options contracts have expired, there's no more selling pressure for the next at least two weeks or so. That's what the chart patterns have been telling us for the last six months. So for these next two weeks, I'm very bullish on Bitcoin. Now, in order for this to happen, though, you guys must be subscribed to the channel and you must smash the like button. If you guys have not liked this video yet and if you do not subscribe, I will call, I will phone Satoshi Nakamoto and tell him to pull the plug on the whole thing. Yeah, Satoshi, pull the plug. Just kidding, guys, but please do like this video and make sure that you're subscribed if you're new here. Alrighty, guys. So that first trade that we're going to be looking for here, currently, we're at 56.6K. So we're going to be looking for a break above this 57K area. Now, we have gotten rejected currently, right? But I'm still looking for that trade because notice that this right here is a Fibonacci level, right? So check this out. If you go all the way back, look at this Fibonacci level. Look how many times there's been price action at these levels, right? So because of that, I am going to be using that 57K entry. Even though there's going to be a lot of price action there, I'm going to be using this as an entry to take some profits this weekend. I definitely see Bitcoin once we get a clean break of 57. There should be nothing else in the way between us and 60K at that point. So that's the first setup that I'm looking for. Now, the next trade that I will be looking for is a break above $60,000, guys. So on a break above $60,000, that is where I'll be taking my second trade if we broke 57 and continued up to 60. Now, in the event of a break down, I'm looking back here at that 55 to $54,000 range. This is where I'll be looking to take some new trade setups throughout the weekend in the event that we pulled back for any reason. All right, guys, in Ethereum, we are looking for a break above this $2,800 level. That's the main trade that we're going to be watching this weekend. We want to see a break above it. A break above it should help it continue up to that $29,000 to $3,000 area. If we see a pullback here, then we're going to continue to use this $2,700 area as a pullback bounce entry. And when I'm saying bounce entry, remember that I'm buying as it bounces back up. I am not buying on the drop down. And if we test anything below that, then $2650 is a possible entry, but I feel a little bit safer at $2,600 on any type of pullbacks here in Ethereum. So I hope you guys enjoyed this video. I hope you wrote down these trade setups because we're going to make some money in the next two days. And hopefully in the next couple of weeks, if you guys enjoyed this video and if you made any profits this week from our calls on Monday, make sure to smash that like button and let us know in the comments which trades you took and how much profits you made. If you guys are here for the first time, thank you for joining us. Make sure to subscribe and turn on that notification bell. Guys, have an amazing weekend. I will see you on Monday. Peace and love.


and then you've got your messages so remember with communication oftentimes it's done by email now so we've got the default messages when we send out the email default email message sent you've got deer and then you can have full name first name company name and so on this is for the purchase order email please find purchase order attached to this email so you can change the the default if you so choose email me a copy so you can put that there if you want to have a copy the cc and so on if you want to have those as well so i'm going to say say obviously the cc is visible and i think the bcc is not visible so that so that you can add it without you know someone else seeing that you added and so on