What's going on ladies and gentlemen and welcome back to Bitcoin daily in today's video we are doing a full market analysis on what's been going on throughout the week what's going on with Bitcoin right now what trade setups we're looking at for the weekend and we're going to do a recap of what happened throughout the week. So before we begin as always make sure to like and subscribe hit that notification bell and drop a comment. Let us know what you think of these videos. Let us know if you have any other ideas or any special requests on videos that you would like for us to make. We're always happy to hear those ideas and make some videos to help you guys out. So let's jump right in y'all. So it is Friday today the December 4th guys 2020. It is almost the end of the year. Bitcoin is at all time highs and we're just patiently waiting here for this new all time high right. So let's look at coin market cap like we always do and just kind of take a look at a few numbers here. So the first thing that we're looking at is that market cap as you guys can see it is currently at five hundred and fifty six billion dollars. And Bitcoin's dominance is currently at sixty two point eight percent. All right. If you go down here and look at what's been going on in the market you'll see that we're currently down about two and a half percent today. But over the last seven days we're up about ten percent. Same thing with theorem down about five percent on the day over the last seven days up twelve point seven percent. XRP is down ten percent today. So that's a big follow today. But it's pretty much flat on the week. Light coin down seven percent today but it's up 17 on the week. Bitcoin cash down to today up six on the week. Chain link down seven today up three and a half for the week. Cardano up down seven today but it's up ten on the week. Polkadot down five but it's up seven on the week and Binance. How did Binance make its way up here right. So let's jump into the charts y'all see what we're looking at here. What we got for this weekend. So as you guys can see we're still just consolidating in this range. We have the same pattern that we've been looking at right. So we have this this big impulse move up and then we have this consolidation here. So we're just kind of waiting here. You know I know a lot of people are waiting for something to happen here. But if you look at this pattern it's a bull flag right. So we have the impulse move up and then the consolidation after right with with lower volume and all that. We have a descending resistance zone up here. And you know we're just kind of bouncing around here. So pretty much right now we're just kind of waiting you know it's just a waiting game. I do believe we're going to break this in. And I think that this bull flag is going to lead is what's going to lead us to the break of this all time high. So we just got to be patient because there is a lot of sellers here. There's a lot of resistance. So we just got to keep fighting through that for now until we have enough momentum to break up. So once we break up then we should probably shoot up to 21. I would imagine since there's really you know this is just kind of open ground here once we get up there above 20. So so that's just kind of what we're watching right now what we're waiting for for the weekend. We're basically looking at this range that we're trading within and trying to catch something you know either the bottom of the range or breakout right. So let's let's hear. Let's see let's get the range. Let's draw the range here. No I don't want this. So basically I'm looking to enter here probably trades within this current range where it's at between 800 to about 700 right. So that's kind of where we're looking. Let's draw that there. Right. So we want to we want to really look at the bottom of this range here and try to figure out where you know we want to enter. So basically you see that we've tested this down here several times. We've been down here one two three four five six seven eight nine ten right. So we have a lot of candles that have been bouncing here. So we know this is a pretty strong support. Now what we want to do here is kind of buy in this in this general area right. So the way I like to buy is I like to buy once it's tested the support and then it's kind of bounced back up. So that's kind of what we've been watching here. We want to see a bounce here. We don't want to see this continue down if it continues down. It's not really something we want to get into because it's just it's not it's not going to have that momentum we want. So we want to see this bounce back up here on that bounce up. That's what we're looking to get in. So the way I'm playing it right now is just how it is right here. It tests it's tested this range and then now it's bouncing back up. So I want to get in currently pretty much where it's at right now at that 18800 range right. 18.8 K that's kind of the range I'm looking to enter and I do have an active trade right now. So my stop is probably going to be around the bottom of this range. So currently this is at 600. I'll probably put it more towards here that 700 range right. So that's where I'll have my stop loss. And if we break through that then I'm either waiting to for it to bounce back up into this range and then look for entry opportunity within this range again on the bounce up or I'm looking down here at these right. So I'll be interested in these to see if these holds here 18.5 and you know the low has been basically 18.1 here and then you of course have 18000. So that's kind of what we're going to be watching here this weekend. As you guys know over the weekends is there's not always a lot of volume a lot of volume but over the last few weeks we've had a lot of volumes on on Friday nights. Saturday and through Sunday. So so we're definitely taking trades and we're looking to make some profits here over the weekend. So the first trade that we're looking at here is this 18.8000 trade right. So we're looking to take entries here and write it up. The first target here is definitely 19000. So that gives you a $200 profit on your first target. So you can have either a $50 to $100 stop loss. We're using $100 stop loss. So as you can see you know we have a two to one risk reward on that first that first area where we're taking profits. That next area is probably going to be we'll be looking at the 19 one to 19 two range. So it just depends how how when it breaks through how it acts if it continues up really strong or if it starts struggling that we will take some profits before it goes back under 19 one. And if it does continue up so we take 19 two then that next range is going to be like that 19 four to 19 five range which is also this descending resistance here. So we'd be looking to basically take profits right around this range right. It'll be 19 four to 19 five will be looking to take profits within there. And then if we break through this then we're looking at 19 seven through 19 eight basically so we want to have the majority of profits by the time we get to this area of 19 eight. Because of the strong rejections here at 20 K right. So that's kind of how we're playing this position right now. Our other entry that we're looking at would be basically I would want to see a break of this right so it would probably be a break above this right here. So this is 19 thousand six thirty two. So it'll be 19 six thirty two will be a break above that. Now the thing with this that you do have a lot of resistance up here. So that's why I'm not playing that break too big. If I do set entries here they're going to be a lot a lot tighter and smaller positions with low leverage. And then I'll be looking to take profits every hundred dollars. So that means that my stop loss will be around fifty dollars. I'll be looking to take profits you know at 19 seven 19 eight etc. So so yeah and then my third and last entry here is going to be above 20 K. So that's the ultimate one if we get this breakout all the way to 20 and above 20 then I'll be selling all my positions. Once we break above 20 then I'll be re-entering with new fresh positions there because I expect a momentum to just continue taking that up. So that's how we're playing Bitcoin over this weekend. And for now you see this position that we entered in that eight that 18 eight area you see that that's kind of going up right now. So if you want once you guys watch this video if we're still in that range definitely look to take entries there. So let's go ahead and move on to the next one. Ethereum as you guys can see is Ethereum has a very very similar pattern basically the same pattern here. We have the impulse move up then we have rejection and consolidation here at the highs and we're just looking for a breakout. So the pattern you see this is a bull flag and it's the same basically the same pattern here. We're within this pennant going up and down just consolidating here on lower on lower volume. So we're looking kind of the same type of entry here. We're looking to enter around that between that 580 to 585 zone and it's currently at 581. So this is current currently an entry you see here that it went all the way down to 556 and a bounce back up. That's kind of what we're looking for for entries here. Our first take profit area here is going to probably be around that 590 range. So that means we have about a $5 stop or if you want that first take profit range to be 600 then you could have a $10 stop. So it just depends on your risk tolerance how much risk you're willing to take on this position. We're fine with taking that $10 risk and you know just holding till 600 and then that'll be our original position. Then our next target here will be 610 and then 620 and then above this 625 range. We're looking to take fresh positions or you could also do it above 620 but we've had some fake outs already. We've had two fake ups above that possibly three. So if you want the safest entry breakout entry here then above 625 that'll be a fresh high and that's something that you guys can enter. So then that's basically our two entries. You can also use the 600 as an entry but there's so much consolidation there. We're not taking that entry. We're not using 600 anymore. We're looking for a fresh breakout or looking to buy down here at this 580 zone. If we continue down then we have this 50 day moving average right here which is this yellow one. It's right at around that 560 range and then after that 550 is definitely another support and then 540 and then probably down to 520. So right now for the weekend we're looking at the 580. We'll be looking at the 600 and 620 trades basically. So we're watching these now. You can see right now they're happening right now as we go over these. So we just kind of got to kind of wait and see what happens. We definitely want to enter on those bounces though and you know go from there. So let's move that out the way. All right let's take a look at Bitcoin Cash. As you guys can see not much has really gone on after that drop. Once we had this drop here is just kind of consolidated here right and it hasn't really. It's been indecisive hasn't really chosen a direction to go in. So if we were looking to for a trade to enter here we're probably looking at this 580 at its 280 range. I'm sorry 280 range as a support entry here. But again we want to see it tested and we want to see a bounce. We don't want to just buy it as it falls down and then that next entry will be above 300 above this 300 range. It's going to be the next that next breakout entry and then above 320 is that next next breakout entry for Bitcoin Cash. So those are the plays out that we're looking at 280. And if it were to drop below 280 then 260 to 255 zone is that next support that you can play if it were to make that kind of a drop. But other than that this 280 and then above 300 is the entries that we're looking at and we're watching Bitcoin Cash. Like coin as you guys can see like coins pretty much replicating the same pattern as Bitcoin any theorem right now. As you see money has been flowing out of the market as a recent. So what we're watching right now is this $80 range right. So this $80 is a there is some resistance here. So we expect buyers to possibly come in here we're at 81 right now. So we would like to see a test of this and it's also where the 50 day moving averages. We would like to see a test of that 80 and that 50 day moving average if it up if it holds up and it bounces right back up. That's where we're looking to take entries. So that $80 mark is where we're looking to take entries with like coin and that next area is probably going to be above these highs right. So the high here was 94. So we probably take something above we'd be willing to take something above 90. You just have to be wary of these fake outs up here. So maybe a safer play will be like 92 or the safest place going to be probably above 94. So it's just up to you and depending dependent on your risk tolerance and how much risk you're willing to take. But yeah once once it breaks through there then that first target is 100 and I expect a lot of sellers to come in over here. So you have to be ready to to be selling I would be selling on the way up and then have new orders above that 100 range. So that's kind of what we're looking at for Litecoin XRP. As you guys can see we're kind of looking at the same thing here. We had this huge take off and then we've had a pullback and consolidation right. So here we had today we had a pretty big drop here. It dropped all the way down to almost it dropped to about that 55 cent range as currently where we're at right now. So I mean this 55 cent range is a possible entry. I haven't taken any entries here on it that next range that you could enter on is above 60. So if I see a bounce here and I see it heading back up and above 60 then it's possibly something I might consider entering. However right now if we look at this at the current you know bull flag pennant that we're watching here we are currently at the bottom of this range right. So this 55 cent range is not only the bottom of this range that we've been tracking here but it's also a pretty even number. So it it could be a good support here. So we like to see is kind of a drop how it's done here and bounce right back up and over it. That's an entry that you could definitely take here at 55. And then I'd be looking to take profit at 60 and above 60 you could be looking to take a fresh new entries if we continue above that. Then you have to be careful here on that 62 to 64 range because that's where this descending resistance currently is. So then after that you'd be looking at 70 cents a 70 cent breakout for an entry if it works to continue up. So those are the trade setups we're looking at for XRP Ripple right now. Next we got Chainlink Chainlink not much going on right now. It's dropping we've dropped below that $13 mark which was a support. So I'm expecting a drop probably to that $1250 to $12 range as you guys can see here $1250. Look at all the price action there and $12 price action there. So that's the range where I'd be looking to enter on a support entry and then for a breakout I'm looking for a bounce above this $13 right. So a bounce back above $13 that's a possible entry and then you're taking profits every 50 cents with Chainlink. So $1350 $12 I mean $1350 $14 $1450 $15. Alright so that's what we're looking at there with Chainlink Tezels not much going on. It is coming back to this $220 area where we've pointed out before. So $220 is where we look for a support entry here for a breakout probably above this high here this past high here. So above $255 is where we'd be looking for an entry there on a breakout. For Neo let's see Neo has it has been slowly grinding up so it has been posting what looks like lower highs and higher highs. So here we're currently at $1750 we'll probably be looking for an entry above these highs at this moment. There's really no other entry here that I like probably looking above $20 for that entry. So that's the only entry I'm looking at in Neo an entry above $20 for a breakout entry. If we do continue pulling back then maybe the $17 to $1650 area could be a possible entry there. But I don't think that we'll be entering that. Let's take a look here at Bitcoin Futures. As you guys remember we had this drop off last week when the market closed which kind of looks like what's happening today right with the market overall. It's not this crazy but we have kind of a sell off here a Friday sell off which we had the same type of Friday sell off on last week. And then you know we took off so that's why I'm saying that we could get some you know a push up but we have to keep in mind that we have this gap here. So remember we spoke about this gap and I said that Bitcoin likes filling these gaps when when they're you know in here. So remember on Monday I said that we might have to fill this gap in order to continue up. So it's definitely a possibility not saying that something that will happen but just something to keep in mind as we continue over the weekend. And that's pretty much it guys I think we covered the majority of the stuff we wanted to cover here today for this weekend. So that's kind of the trade setups that we're watching over the weekend and that we'll be looking to enter and some of them that we've entered already. So the last two weekends in a row the last two videos we've done on Fridays we've hit on 100% of our trade setups that we that we spoke about on Friday. They hit they've hit 100% on all of them for the past two weekends. We're going to make it three weeks in a row. I just told you guys all the entries that we're looking at here. Let's see how they work out and we'll do a recap on them on Monday. So that's pretty much it guys. We'll do a question of the day today. The question of the day is what are the entries for Bitcoin that we're looking at this weekend. And that's pretty much it guys make sure to hit that follow guys make sure to subscribe make sure to like this video. And hit that notification bell answer that question of the day put it in the comments and then make sure to hit that like so that once we get that 20 20 likes on this video. It will trigger that giveaway that we do which is one free month in our trade group which is a $70 value. So that's pretty much it guys. Thank you so much. I hope you guys have an amazing weekend and you make amazing profits. As always peace and love.


Jai Sri Ram. Jai Sri Ram. Jai Sri Ram. Jai Sri Ram. Jai Sri Ram.  I'm Corbin. And it's just me today, um, and, uh, for, for this video, and I'll tell you why in just a minute, but you can follow us on Instagram, Twitter for more juicy content. Thank you to you over the force on Patreon. Follow us through your Twitter account and subscribe to the like button. And today we're doing a movie, insert Rick going, which is what he likes to do. Today I'm doing a movie review of the just released. I saw it just, I just got home from seeing it from Adi Parush. If I'm pronouncing that correctly, I do apologize. The Pan India film, if you will. I saw it in Telugu. That's all they were really showing here. I know it was filmed in, believe Telugu in Hindi. I don't know if it was filmed in others obviously. You guys can let me know, but it was directed by Om Raut. If I'm once again mispronouncing that, I apologize. Starring Prabhas, Seif Ali Khan, and Kreeti. Your, your main leads in this obviously is a whole bunch of other people, but it's telling of the big Indian. I got in trouble for calling it mythology the last time I get it. It's y'all's history. I get it. That's in every comment. That depicts the triumph of good over evil of Ram, Sita, and Lakash. I'm bad with these names. So do forgive me when I inevitably either don't know the name or butch it.  I do apologize. But I'm watching this. I watch this alone. A couple reasons. One, Rick wasn't available. Two, Rick wasn't able to watch, which me and my wife just did. If you'd like to go check out, we just watched and did a watch along of on the channel of the 1993 anime film Ramayana. And I, I'm actually glad he didn't, he didn't come because this film definitely makes it makes you feel that it thinks the audience already knows this story. And if you don't, you're going to be very confused by different characters about the stuff that's happening. And so he would have been very confused. I'm very glad me and my wife watched it. We really enjoyed it. Please go watch that, that watch along of it. But this is basically the modern adaptation of it, obviously infamous with the trailers and stuff that went wrong with the VFX and that kind of stuff. But and I struggle if I'm going to do a full spoiler or non-spoiler because everybody knows the story in India. I'm going to try to keep it mostly non-spoiler, but there's some stuff I want to talk about in spoilers section. But I'll try to keep it mostly non-spoiler even though obviously I know most of you know the story. And it doesn't really deviate from, at least in my opinion, what my knowledge of this.  So that's basically the knowledge that I have of this story. And it basically follows the bullet points of that story into this story. But so I'm going to do mostly non-spoiler. I'll get into it and then I'll let you know before I get into some spoils. But did I like it? Yeah. Yeah, I did. I enjoyed myself in this film. Believe it or not, because I know a lot of people crucified this film, including us, especially with the VFX. And we will get into the VFX. But overall, I was entertained for a very fast, it felt like a very fast three-hour movie. And so that you know is a goal of a movie is to be entertaining. And I was entertained. And I thought it did a good job at trying to adapt the story that I knew from the anime version into a, in 2023, in a very difficult film. And I said on Twitter, I said after the opening of Probus, when Probus came on, I said that was a cool opening. God, I wish they had a Marvel budget, meaning a $200, $300 million budget. Because this story, and I know they had a huge budget. I know that for India, right? But a movie that is 99% VFX, it's almost all on green screen, I feel like, requires to look Marvel level. And this is a Marvel level story, if not bigger, to get correct. Now, getting to the VFX before we get into that. Because that's the most infamous part. Yes, I enjoyed this, right? And actually, it was very overblown. Because for the most part, a lot of times, you're sitting there and you're like, this is really good. This is great. There is a 10% still, maybe 10% of, I don't want to call it laughably bad VFX, but majorly subpar. That makes you go, God, I wish we could have done better. And a lot of that has to do with action, whenever the VFX had to be in motion. There's a part, and this isn't giving anything away. It's actually in the intro. I saw a lot of people commenting on it on Twitter, where you meet Prabhas and in all the, I don't know the name, so I do apologize. It felt like Dementors from Harry Potter, right? I know they're not Dementors. That's my reference, because I don't know.  But when they all, they sent the legion of people to go get Prabhas, right? Or Ram. The guy that was instructing them felt like a early 2000s video game character that cut like the lead guy from all the flying characters. It was like Prabhas fighting a cartoon, essentially what it was. And that happened a few other times in the movie, where you're like, God, I wish it was better, because that's like the biggest thing you can gripe about this film is at certain times, it's like, oh man, if you had a Marvel level budget, what this could be worldwide would be incredible. But yeah, so if you saw it in the trailer, you're still going to see it in the thing. And there's some characters like there's trolls that don't really look that good. At times, there's some, once again, I apologize. I don't know these characters, because I called them monkeys in the Ramayana thing, and somebody said it was a different thing. And I apologize. I don't know what that thing is. I'm just, I'm meaning no offense. The gorilla characters sometimes look real bad in their animation, especially when they were in action. You saw some of that in the trailer, but a lot of other times it's actually really, really good. Some of the VFX I thought was actually really good was, once again, I don't know what it's called, but it felt like the Bat Dragon that Seif was writing. I felt they spent a lot of money on that VFX there. And Hanuman, if I apologize if I'm not saying his name correctly, I thought his VFX around his face was actually very, very good. I liked it a lot. And there was some cool VFX, kind of like Bra Mastur with lighting and stuff that was really, really cool. They helped themselves a lot with a lot of this guide, almost all of it, right, being at night time. And that's a VFX trick to kind of help out if you don't have the budget to make your VFX better.  I get that. But since this is a movie and the choices were either see even worse VFX or darken everything, I'm okay with them darkening it because then you can't see some of the bad VFX as much. So I was fine with that. So there are VFX problems, 100%. There are VFX problems. Wasn't as distracting as the trailer would make it out to be though. So that is a positive, right? So I feel like and maybe in the first teaser before they spent the second 100 grors that they did to help it even more, maybe it was even worse. But I think like I said, the best comic I get it definitely wasn't as distracting and as prevalent, like the bad VFX wasn't as prevalent as they would have made it out to be. So I thought they did a good job there. Let's talk about the three main leads, right? Saif actually was I thought really casted really well. I thought he plays a villain so cool. I love his when he plays villains because he has such an evil demeanor at times and that kind of stuff. I watched him to Lugu. It looked like he was speaking Hindi and they dubbed him into Lugu, right? So that was kind of disappointing for me. But it is what it is. His character was really cool though. And I thought he embodied Lakesh really, really well. They actually I feel like went a lot more into his character than anybody else's character from the anime version that I saw. I thought you got a lot more of Lakesh in this and him brooding or behind the scenes of him than any other character. So I thought he did a really good job. Prabhas I thought did a very good job as well. I liked his performance when I after I watched the anime version and then I went back to watch trailer. Prabhas struck me as a odd choice for Ram and once again the only reference I have for Ram is from the anime. Prabhas even though he has an extremely warrior presence and that's part of Ram. I was wondering you know I got from the anime I got this extremely compassionate caring like really loving presence from Ram character in that, right? Which I felt Prabhas even though he's an epic warrior and he feels like an epic warrior didn't convey that. I still felt that in the movie even though there were some times that the script writing helped show his compassion for everyone. That was the only downside to that is that I just feel like he just has such a dominating presence that I would have liked to see the kind of gentle side come out of him a little even though like I know they showed it sometimes it just I would have liked to feel it more coming from him you know. So that's finally great but I liked his performance he was epic he kicked ass he's great his screen presence is amazing and he did a really good job kind of a Bahubali style of warrior at times and so I believed him 100% and so that was great. Creedie I thought she definitely captured what I thought Sita or in this one it was called Jannaki and I apologize is it just because it's in Tolugu is that why the names are changed? I don't know but she's playing the seated character so I apologize if I'm just being dumb. I thought she did a great job. One character I really love is the guy who played Hanuma which it's a different name here and so I can't find it so I do apologize but the guy who plays Hanuma I love that character I loved him in the anime and I liked him in this I thought the VFX was like I said was very good on him and I god I just it felt like in three hours it's another downside I had to him I felt like in three hours I didn't figure out any more about these characters than I did in the two-hour anime movie. I felt like I actually learned more in the anime in terms of about them in their character than I did in this and I still liked it it's just man I thought in you get an hour more of movie I thought they'd get a little more into it um but maybe they once again they just assume you know about these guys and so they weren't trying to introduce you to them at all I don't know I just god I would love a Hanuma movie cast that actor make an entire Hanuma movie live action movie it would be epic because I love that character I love how how funny is I love how epic he is he's he's a really insanely cool and I know he's not just character but I loved his character and I would love to actually see more from his character I would love to know more about all of them because that's one of the downsides of this as I thought it was I wanted to know more which is I guess good you you want a movie to come away from a movie wanting to know wanting more right you don't want them to give you anything and they because they did give you stuff but yeah so that that was one of my other gripes I love the background score insanely epic beautiful you you're mumbling it in the beginning and I apologize if I butchered it um it just it just moved you it kept the story going it it complimented the emotion that needed to be carried it complimented the the insane battles that were happening in this beautiful songs between Ram and Sita um so I thought the the score was was very good in this um another thing I was a little let down though I can't get into that because it's a little spoilers there's stuff that just was a little disappointing in terms of anticlimactic of some battles that I was anticipating from the anime series it's not series that movie um that I was like oh I thought that would be longer and better um there were some some really good fight scenes you still have to kind of you still have to overlook a lot of the the vfx but there's some stuff that happened in that wasn't in the anime that I was like holy shit um I was like how they killed people uh I was like oh that's I was kind of insane um so I I thought the uh the direction was very good from from omrout I apologize once again if I'm saying that wrong um but I I was like I said I was thoroughly entertained through this through this thing I was excited for what was coming I'm glad I knew what was coming next because it was um the people that would show up and you they wouldn't explain and so if I hadn't already been to nerdustum I'd be like what the heck is going on who's this character um they there was very little that was changed from um the the story that I saw in the anime and so that was good I'd say overall though I I enjoyed it and I would watch it again um is it like a perfect movie no you definitely need to work on the vfx I would like to know it could you could I think what they should do and maybe they're doing it for the hindi one that they've casted alia and and rent beer and which I love those castings I think those are great um make it into a three part series man this there is too much in this story to tell in two to three hours there's too much and you want to know you want to feel with you want to um care for these characters even more and I know a lot of you like they're they're religious characters uh or people right uh and so you're already attached to them but in a movie setting I want to you want to really feel when somebody dies you want to really uh emphasize those characters and you can get more in depth if you make it into a either a series which probably for the budget you probably can do right but for like like they're doing Brahmastra make it into a three part series and then you could go really in depth really in depth and then the last one is like the last order of the rings that helms deep or not helms deep the wherever that last battle was it could be that kind of an epic thing I I think that's what they should do because I like this story I think it's a very entertaining story and if you kept the vfx up I think um a lot of people in the west could have even appreciate I think this is going to be hard for one it's not a story that they know and they're they don't really explain these characters a lot to you so I think you kind of have to be familiar with it but the vfx at times like I said probably 10 to 15 percent um but the other like there's other times with their cinematography is just so beautiful when their seat to unrom on the river when there's like there's so many beautiful things that they created that I loved but then there's also the just um oh god you could have done that better right moments but overall I really enjoyed it um let me know what you thought about it uh I do want to get into some spoilers so if you haven't seen it um please go away because I just want to talk about a few things but let me know what you thought about it down below and we're going to get some spoils here um so I was there was some stuff that I wanted to talk about um like they said that they're just kind of confusing and I actually asked my wife this one I got home the first one was in the movie once again the spoilers when when rom's brother dies or or is insanely injured by the by the snake biting right um and they they tell hanuma to go get the stuff the only person that was hurt at least to my knowledge on screen was rom's brother and hanuma went and picked up the entire mountain and I was confused I was like why do you need an entire mountain of the stuff if it's just one guy because I thought that was the motivation because there was so many people hurt in the anime version uh and so you need a lot I asked my wife and she says well in the in the comic book thing they said he doesn't he didn't know which one was which and so to be safe he took the entire mountain and so I guess that that answers that question because that would that actually makes more sense so I she I think answered my questions and once again she's incredibly smart go watch the watch along she's a very smart person um the other things that kind of disappointed me a little bit though um were the the battle so of of lakesh's lakesh right his sons the those battles which I thought were going to be a lot more epic and the big sleeping giant warrior guy I apologize for not knowing his name that was that was a pretty epic battle in the anime it it lasted like a minute and it was like a and it was gone I was so disappointed I was so looking forward to that fight uh so that was very disappointing um the end battle with with syphes and and provis was was better uh so that's good uh there was another funny thing that I that I was wondering why they did this and maybe guy rum I don't think he has super speed but you guys can tell me if he does I didn't look like he did but when sita got captured and and syphes character was taking her away on the bat thing and then the eagle came which I think it was like a a vulture in the anime but I don't know when he came and tried to save her right and they were going all through the air it's hundreds of miles an hour through these mountains and rom and his brother were running on the ground looking up like they could see what was happening but they were like they were long gone but they were running like they were keeping up with them that didn't make any sense to me I was like unless you guys tell me that I but it didn't look like because because then he could have done in the battle and hanama was the one that had to carry him in the battle so if you could explain that to me or if it was just like a they probably shouldn't have done that because if they were as fast as the eagle and the bat were traveling there's no way they they could have kept up with them if I'm wrong please explain to me I'm just stupid but that struck me as strange right um and then the other thing I'm talking about in the beginning which was a really bad vfx but a cool sequence I like the introduction of prowess under the water and then he coming up and kicking ass right I like that whole sequence I thought that was a lot of fun but the guy that was instructing him the cgi was laughably bad on that guy like the the main bad guy and when all those other things were flying around profits he was really bad and then the battle between the two the gorilla that was trying to win back his thing the it was it was computer animated vfx like 2002 vfx so that whole sequence wasn't that great um not all like I said 10 to 15 percent was probably not really really not good um all the other stuff actually it wasn't like I said I'm just happy it wasn't as distracting as I was fearing it was going to be because I was really interested in how they were going to do this story and I actually thought they did a good job uh in making a entertainer uh for for the family right um I'm hoping the next one with Ranbir and alia goes even more in depth and maybe even a little farther in terms of some of the violent and I'm hoping much better vfx all the time but uh those are basically my thoughts um I enjoyed it uh I'm very happy that I enjoyed it because you know with all the trailers even though I was interested you were still nervous going in because of some of the stuff so you guys let me know what you thought about this movie did you like it did you hate it were you happy with what they did do you think I'm an idiot doesn't matter uh please let me know what you thought about this movie down below and I can't do it any justice and I apologize for what I just did


So let's start folks. I'll start off with a disclaimer. This is probably going to be the least of your technical sessions amongst all the sessions that you've been attending today and tomorrow. But I think Navigla is a very important topic for us as software testers. So firstly, to that extent, I'm very thankful to the conference committee for having chosen this presentation. Because I think it's all about prioritization at the end of the day, whatever we do and especially for us as software testers. So we're going to basically look at what really is prioritization. What are the varied styles of prioritization? We may all think, hey, what's new about prioritization? We all know prioritization. We do it in all walks of our life. But interestingly, there are varied styles of prioritization. So we look at some of those styles because what works for one is not what is going to work for the other. What works for me today is not what's going to work for me say a few years down the line. So we look at a few prioritization styles. We look at the scope areas of prioritization in software testing specifically, and essentially walk away with some actionable items on how we can prioritize to be better software testers. So that's simple enough in terms of the agenda.  So that's what I'm going to start it off here with. So Joe buys a brand new Lexus car. He wants to show off his luxury car to his office colleagues. So he drives it into his office. As he gets out of the car, there is a truck that comes roaring past and slams into Joe's car door. So Joe is obviously very, very furious. He immediately calls the cops. Cops come in in disbelief. They're in complete denial. They come in shaking their head saying Joe is really infuriated about the car's door which has been slammed into. Obviously, for the right reasons, Joe is extremely unhappy. But why are the cops really furious with Joe? Least has Joe realized that in the process, his hand was also slammed into, but the guy did not realize that. And as soon as the cops said that, oh my God, is it my left hand? My Rolex watch has also gone away. So priorities are very, very different for all of us, right? So in this case, Joe's priorities were being completely materialistic. He didn't care for his left hand which was slammed into, but it was his Rolex watch that was his priority. So starting off with the message that it's all about priorities at the end of the day. We're all driven by priorities. So let's start off with a couple of simple codes, right? So Dalin Oaks is a religious leader. He talks about how desires drive our priorities. Priorities drive our choices, and choices drive our actions. End of the day, our actions are all driven by our priorities. And this is something which Mahatma Gandhi had mentioned back then itself, that actions express priorities. So I believe at the end of the day, no one here is busy. If someone were to get up here and say, I'm extremely busy, I think we're just not prioritizing things well on our plate. So skill and capability is one, but on top of it, prioritization is very, very important. So a quick definition of what prioritization is before we look at some of these styles. So any quick takers, anyone wants to quickly define priorities in literally like two words. What is prioritization? It's like a word we all know, kids know. All right, did you look up online? I'm just kidding, awesome. So as a principle, it's basically doing first things first. And as a process, it basically means you stack rank a group of items based on their urgency and importance. So there are two things I want you all to walk away with at the end of the presentation, right? So how do you prioritize? Basically, look at what is the urgency of a certain item, what is the importance of a certain item. And when I say urgency, it is timeline-based, and when it is importance, it is impact-based. So there's a huge difference between the two. If we understand that, that is the first step towards prioritizing whatever we do. So let's take a very, very simple example. Again, a non-technical example. Let's say our utility bills, right? Our electricity bills, water bill, whatever it is, it is due as of today. So it's an urgent task where I've got to pay it by today. I'm driven by a certain deadline out here. So it's an urgent task. But if you ask me, is it important? Probably not, you know, what if I don't pay it today? I pay it tomorrow with a penalty, as simple as that. But the same thing, if I wait for another 30 days into the penalty period, and I've not paid my utility bills still, and at that point, I get a notice saying, by today, if you don't pay it, your connection is gonna be taken off. Then it becomes important as well, because there is an impact to it. So I understand, anytime we do a prioritization, do this kind of a basic difference first, because some tasks are gonna be urgent, but not important, important, but not urgent, both important and urgent, neither important nor urgent. Use this as a basic matrix when you do any kind of prioritization in whatever activities we do. Let's move on, right? Some of the core prioritization techniques. You may wonder, I've taken examples of all women leaders out here, but I found their techniques to be very, very exciting and interesting, that's why I picked. The first one by Indra Nui, she is the chairman of the PepsiCo group of industries that most of us obviously know her. By the way, do go watch her videos, great sense of humor, excellent points that she's got to convey. So she says her style of prioritization is scoping mechanism, and she gives a very interesting example as well. So she says, growing up when my kids were young and I was already an exec at that point in time, it was very difficult for me to prioritize my personal and professional life. And every Wednesday morning at her kid's school, there used to be a coffee meeting where the moms had to attend. And how am I gonna be able to attend those meetings as a working mom? The first few times I was extremely guilty that I was not able to attend, and the kid would come back home saying all these moms were there, but you weren't there. So initial few times while she was guilty, later on she built a coping mechanism where before the daughter comes to her, she would have collected data from the school saying which other moms did not come for the meeting. So when the daughter says these were the moms that came, Indra Nui would go, these were the other moms that did not come, did you know that? So that is one style, coping mechanism is one style, so see if this would work for you at your workplace. The second one, optimization. We all optimize, right? As software testers, optimization of our test matrices, test coverage, compatibility is basically driven on optimization. So this, yes, is a standard mechanism. We all use as testers. Third one, procrastination. So Julie Larson Green, she heads the customer experience division of Microsoft. She says procrastination is my style. I push things out until the very end, until they become both urgent and important. Now I'm not saying again that's right or wrong. I personally am not a person who burns midnight oil, but looks like that works for some people. So procrastination is one such style. A few other styles are, you know, easiest first, quickest first, hardest first. It really depends on what really motivates the individual. Some prefer to have some quick wins first. So when they prioritize, they say, oh, let me first finish off some of these quick items. Or no, let me finish the hard item. So I have a huge amount of confidence to then go and attack the easy ones. So really pick to see which is the style of prioritization that works for you. But amongst all of these, this last one is what really struck me. So this was mentioned by Adrienne. She heads the human resources for Starbucks, the coffee giant. And what she says is the power of your yes can only be as strong as the power of your no when you prioritize. Learning to say no for the right reasons when you've got to push back. I think that is very, very important. And I wanted to bring this to the room because I've personally been bitten by this as well. So when Microsoft was my client back in Seattle, I had my teams here working in India. And every time I used to get this feedback from the client, especially Indians. Again, sorry, no, nothing racial out here. What they used to say is for the fear of not wanting to say no, they would say yes. But ultimately struggle not being able to finish everything. So I think the power of saying yes is only as much as the power of saying no, whether it is a scope creek, whether it is something else that's been added onto your plate, whether that is a trespassing that's happening, a wrong resource allocation, a wrong tester allocation, whatever the case may be. Learn to say no for the right reasons. And that's a very important aspect in your prioritization technique. So now why do we have to prioritize it in software testing, right? Let's move on specific to software testing. So the first thing, what is it that strikes us when it comes to prioritization in software testing? We immediately think of defect management, right? What is the priority of a bug? What is the severity of the bug? That's the standard thing that we think, but it's much beyond than your standard defect management. And why is it increasingly becoming important for us to prioritize? Primarily because we are increasingly doing bigger and better things as software testers. We are collaborating with a lot more people on the team. The products that we are testing are increasingly complex. The technologies are diverse. The platforms are diverse. So with all of this and the increasing scope, we cannot afford to not prioritize what we are doing. And that is exactly what we will see. So far, so good. You're okay with the non-technical pace? Good. So what is that scope for prioritization, right? So I'm looking at prioritization specific to software testers under four major buckets. I'm not saying this is an exhaustive list, but I think this is a fair enough list. And if we start prioritizing under these buckets, at least we are fair enough on the right path to prioritize what we do. So firstly, at a people level, at a process level, at an activity level, and finally at a communication level. So these are the four buckets I'm basically gonna be looking at. So firstly, at a people level, increasingly testers are having the most number of interaction points or touch points on a product team. A month back when we were all in ATA in Pune, the Agile Testing Alliance, Ajay, I'm sure several of you must have heard of Ajay Balmurgadas, he had a very interesting presentation on 50 tips to increase the developer-tester interaction. I think that is turning out to be an interaction which is very, very critical amongst the varied interaction points that we have. So I think for us as testers, that should be our number one priority. Focus on that relationship that we build, the rapport that we build with developers. High context switching is happening in our interactions. You know, we are interacting with XX, we are interacting with peer testers, with people from other product teams. So prioritize your interactions based on the sensitivity as well, so as to determine what to say, when to say, and how to say.  Most organizations do have SMEs. We have SMEs at a performance level, at say an accessibility level, at a security level, but I think where we fall short in prioritization is making sure the right testers are available for the right projects when the need actually comes in. So I'll take our own example, right? So I didn't introduce myself at the very start, so I come from a company called QA Infotech, we are into software testing and quality services. So we provide quality services for clients, for varied product companies. So there are quite a few clients of ours where the work is not flowing in on a consistent basis, it keeps coming and going. So how do we prioritize the test of allocation in such situations, where we know that the client also wants the same testers, and for our own reasons as well, we know it is best to allocate the same testers to the same projects. So we have this SME pool, let's say we have about 10 testers, tester A and B are SMEs for project A. Tester says C and D are SMEs for project two, so on and so forth. So anytime a project comes in for which I am an SME on, so even if I'm working on another project, the company will take me out and put me back on the project that I am an SME on. So I think that kind of a tester allocation prioritization pool has to be maintained at a people level. If you've got to build your niche, if the project has got to do well, and you have the right amount of resource allocation without as much bench as possible in the organization. And finally, for organizations out here, I think it is a topmost priority to brand and rate people as the number one asset in the organization. If people are invested on as the number one asset, prioritized as a number one asset when the organization is certainly well on its success path. So these are some of the core two or three things I would call as top priorities at a people level. At a process level, right, I think a topic that's been beaten to death pretty much in the last decade. You know, how much should I be spending on documentation? What kind of processes do I adopt? Test strategy, test planning, test cases, test scripts, what level of documentation? So that I think still continues to be a custom choice. As much as we try adhering to the agile manifesto, agile manifesto is never saying don't do away with the documentation completely. So I think that's a very custom choice, but what is important is to prioritize the revisiting of processes with every release and make sure you're learning from your previous experiences and carrying those on a prioritized manner to your subsequent set of releases. I'll give you a few examples out here. We talked about optimization, how it's increasingly important to optimize. We do a lot of mobile testing in our organization, and these are some of the core practices we keep in mind anytime we optimize our test matrices for mobile testing. For instance, functional issues are more operating system dependent rather than the device or screen resolution. UI issues are more specific to the device or screen resolution rather than the operating system. So these are some of the bylaws we keep in mind in determining what is the matrix that I really want to build. So build such practices, basically learning from previous experiences to determine how you're gonna do your optimization. Secondly, it's becoming an increasing priority to invest in newer processes. You cannot continue to stick on with your old processes. For example, most clients of ours are increasingly asking for crowdsource testing. And crowdsource testing, as simple as it may sound, you may just say, what is a big deal? Bring in the crowd and it's all an open source community and we can just implement it. It's not as simple as that. Crowd source testing does have a lot of planning that goes into it.  So any new process that you prioritize on has its own intricacies and nuances. So prioritize the number of newer processes you wanna introduce and invest in them. I'll give you one example out here. Again, from our experience, there are a bunch of clients who ask us for crowdsource testing. But for varied reasons, we are not able to take on crowdsource testing on an ongoing basis. We still have a traditional in-house testing that is happening. But on a quarterly basis for such clients, we do take on crowdsource testing. We've built a platform for this called dub-dub-dub.bugmoney.com. So these are like bug hunts that happen on a quarterly basis, either on a client request or on an ongoing manner to participate in the community. So anyone who's interested as well can go in and register. But what I'm trying to say out here is as a company at a process level or as a tester at a process level, prioritize innovation. Innovation is going to be absolutely important moving forward. Now at a third level, right, at an activity level, combine test efforts whenever possible. We're all testers out here, extremely technical, involved in Selenium. You guys are all here for the conference.  Do you take on primarily functional testing or are there other areas also that you touch upon with your test scripts? Any other test areas? Accessibility, usability, security, anything else that you do with Selenium? Security you do. Anyone else? So I think this has to become our priority moving forward to see how Selenium, the base functional scripts or the base automation that we write can be used for other areas. There are two more people from QA Infotech coming here tomorrow. They're going to be speaking exactly on this. One person, I'm sure, is going to be talking about how Selenium test scripts can be used for accessibility testing. The other guy is going to be talking about how Selenium test scripts can be used for security testing. So I think as testers, it's becoming an increasing priority for us to not just focus on the core functional testing, but see how we can leverage those scripts for non-functional test areas as well. So that is number one. Secondly, increasingly important for us to keep the automation very, very simple, right? Because we're having a bunch of other people use our automation as well. End of the day, no one is really going to be worried or care about how complex this person's automation is, how geeky, your geekiness is not going to be determined based on how complex your entire automation framework is, right? Rather based on how many people have been able to use it, how non-business people, non-technical, your business folks, your marketing folks, increasingly they're all using your automation code. And with that, how the stakeholders are able to make that release sign-off call as well. So I think increasingly a priority for software testers to see how to simplify the automation, making it more usable and scalable across an increased number of user base. Finally, keep prioritizing your test productivity. And when I say test productivity out here, a couple of years back we had demoed this in a conference as well, saying how newer technologies like augmented reality don't just focus on testing for augmented reality, but also look at how augmented reality can help testers increase their productivity. So very soon, for instance, we may hit a point where saying a thumbs up means a test pass, thumbs down means a test fail. So leverage, prioritize on using such techniques to improve your testers overall productivity itself. And finally, balance between functional and non-functional testing. Increasingly, as I said, see how Selenium, how your functional scripts can be used for non-functional areas, because things like linguistic testing, things such as accessibility testing are going to determine the legal acceptance and the overall user acceptance of your product. So if I may say here a quick example, we did this webinar for Eurostar just couple of days back, today is Friday. So Wednesday night, I did this webinar with another colleague of mine for Eurostar. I'll give you this simple example. This was back in 1994. Henneken Beer was coming out with a marketing campaign for the 94 soccer finals. And what it wanted to do was print the labels, the flags of all countries that were finalists on its label and attach it to the beer bottle. Saudi Arabia was one of the finalists too. So it had Saudi Arabia's flag on the beer bottle, but it extremely impacted the religious sentiments of Saudi Arabians because the flag has an inscription from the Holy Quran. And to have that on a beer bottle was completely detrimental. So Henneken had to quickly pull it off. So this is an example of how cultural sensitivity and context is also becoming increasingly important in what we do, increasingly impacting the software that we develop as it all becomes more global. So balance between functional and non-functional testing and also try to see how your functional test automation can help in some of these other non-functional areas as well. At a communication level, right? So I should have, I'll probably ask the question right here before I move to the next slide. Any idea what percentage of time we all spend on emails on a daily basis? Sorry, sometimes 80% on an average, 40. Okay, so you're higher than the average study still. 20, 25. So studies say that we spend 25% of our time every day on emails, which is a significant amount of time, right? It's like one quarter. And if I think that is significant, he says, there are days where he spends 80% of his time on emails. So imagine if that is the kind of time we spend our overall efficiency and productivity. Bangalore again, if we were to take Bangalore's case as an example, I'm sure several of you would vouch that a work from home is much better, right? Otherwise we're spending a significant amount of time just on the roads. So with all of this that's happening and we as testers are increasingly social animals. We talked about how the interaction points for us as software testers is much more than anyone else on the team. So with all of this, I think we've got to prioritize communication to see how it is productive and effective to make sure it doesn't impact what we do on a daily basis. So leverage tools, right? Whatever it is, whether it's sometimes in-person meetings are absolutely important. There is significant value coming out of it, no doubt. But as much as possible leverage other tools, messaging apps, Skype, Slack, for instance, several of us in our company, we use Slack. So whatever the case may be, do that because end of the day, this is a picture which I typically show in most of my presentations. James Bach talks about the varied types of testers. I'm not gonna walk through each one of these, but if you see most of these types of testers, whether you're a social tester, a user expert, an empathetic tester, we spend a lot of our time in communication. So we've got to prioritize and balance it to understand saying, is this really urgent? Is this really important? Should I be spending this amount of time on communication? Draw that balance also because studies show that testers are increasingly social beings. So if you were to go and ask a tester, how are you keeping up with the latest and greatest of what's happening? Most of them talk about social media, right? Whether it is Twitter, Facebook, and all of these can easily get distracting, right? So how many of us actually go in there for the purpose and come out? At least I don't, I easily get distracted. So with all of this that's happening at a prioritization level, I think communication is also very, very important. So these were the four main heads that I wanted to bring to you all today. At a people level, at a process level, at an effort level, and at a communication level because end of the day, prioritization is inevitable. Whether conscious or not, it is absolutely, increasingly inevitable. Not every style works for every individual. What has worked for me doesn't work for another. Again, as I said, for me as well in different scenarios. Control your actions. Most importantly, what we prioritize is what we end up doing. So our actions are all controlled by our priorities. And at the end of it, you may ask me what's really new, right? What have I really learned new in this whole session? I think what is important is we may have been doing prioritization in a mode where we didn't really understand that we were prioritizing. But if we do it consciously, understanding the difference between urgency and importance, the timeline, the impact, the entire thing coming in together, prioritization comes into our control, which means our actions come into our control as well. That's all I wanted to share with you all today. So hopefully a decent break from your other technical sessions, but any questions, open it this time, okay? No questions? How many of you think that you really do prioritize? Consciously, okay, a few hands raised. So with that note, I'll walk out with one small example. I was just telling Anand as I walked in today. So there's an ex-Microsoft senior guy who's joined as a technical advisor for the Washington governor today. So he says, one of my main tasks, the priority for me is to prioritize for him. Because all of us out here, we can never do everything. And according to him, if there's one person who can really get to every level of detail and manage everything without prioritization, he says it's Bill Gates. So apparently, according to him, in his experience is that I cannot vouch for it, but this is going to be his job. So end of the day, it's all about prioritization. So hopefully we'll have more conscious prioritization coming up for us as testers down the line. Thank you.


So I know it's been a while, but this time around we're going to be discovering both discriminated records and variant records, and that's because essentially variant records just build up on discriminant records or conversely that discriminant records are a more simplified version of variant records, but they are a essentially the same thing Let's just jump right into it, and I will cover what these would be used for as we go So to start let's just begin with the Get which language I'm using Okay, we need the name first, so let's do example is record and Then and record and then we can put something in here. So let's just do Okay This is just a basic record. I just want to show getting the value out of this first Just as a little refresher. I'm gonna need to initialize one of these first. So I don't know if I'll be up here. I can't have it just once, so we'll do this So then if we run this Okay Pretty straight forward there. Nothing really special going on. Where we add a discriminant is Through this so Let's just call it B. It can just be a care sure Forget no language again. It's not care. It's character and add a but yeah So you'll see immediately if we try to build this again That it's going to complain and that's because for all intents and purposes Anything inside of the discriminant can be considered one of the fields of the record So you can kind of view it like that Conceptually that's sort of How that works but the other thing that making it a discriminant causes is that You have to actually initialize that along with the And I have a syntax highlighting here, but along with the type No values slide for discriminant V. That's on line nine. Yes, it is. Oh I forgot about that so If you're doing a full initialization of a bailout the variable That actually has to be here and now won't complain and as you can see getting the Getting the I field out of that works exactly the same getting the V field would be the identical because like I said, it's Essentially just another one of the fields within the record. It shouldn't be considered any different as far as getting values out of it If we want to do another one of these, so let's just call this EA And then we'll do an EB And this one we're not going to initialize immediately. We're just going to describe the type as you can see This is what I had tried to do before because I forgot that the when you're fully initializing it goes into the Aggregate, but if you are not fully initializing it, you have to supply a value for the discriminant regardless and that's because for all intents and purposes the discriminant makes it so that The same type but a different discriminant are incompatible with each other so if we try to do something like this where we say EB is equal to EA Or EB is a sign the value of EA rather If you are not familiar with discriminants, it would seem like this should work because both are the type example as you can see though It does not work They are essentially different types and in a way this can be viewed kind of similar to Different child types within a class hierarchy being fundamentally compatible with each other similar idea, so we need to actually Do this legitimate or yeah fully fully assign that legitimately and Let's just Because it's already got one No, I know how that works So if I remember correctly if we try to reassign V to anything else it's going to complain Yeah, I Think you can Set it the same character, but there's a sort of better way to do it too. We set V to default Does that work? No, that doesn't work, but we can do EB V And that should pull in the same value Yeah So what what I was playing around with there real quick You want to Essentially copy the value of V from whatever it was before You can hard-code it like I had done before where I put in the V character itself That gets tedious especially trying to if you have a bunch of these and are trying to remember what was what I Really don't recommend that So you can copy that over like that or in this case just because it's such a small one You know, we're really only assigning one value within the field You can just do it through assigning the value The field directly so either one of those options work. This is pretty much it for discriminates Like I'd kind of hinted at these become useful when you need What is essentially the same type to be incompatible with each other For a certain reason Discriminates are a little bit more restricted as far as what can actually be used as a discriminant goes For example, you can't use a string and you can use unbounded strings though And the reasons for that are a little weird, but essentially you can't use any type of array There may be a few other restrictions there that I'm not aware of but I know arrays are the big one Luckily the NAT compiler is good about giving error messages about what's actually valid So if you run into that kind of issue, it's going to be very clear what the actual issue is and What is appropriate for actual use as a discriminant? And next would be the variance, so let's just tweak this into a variant I don't remember if these work Hey, I really don't remember range's work for that Opponent may not follow a variant part. Oh, yeah, so Any of the fields that will exist in every single variant have to be at the very beginning No value supplied for component B. Okay, so as it turns out you can use the ranges in there I like I said, I completely forgot if that was allowed or not but as it turns out it is and as you can see here because the The variant we supplied the capital A is you know within this range It expects that this field to be there and Because in this one again, we did a capital B that's within this range It expects this field to be there So we need to supply value for that and so while we're doing that let's create one That's actually it in this range as well. So we're gonna need a value for being this one Let's just do and so you're going to need Let me put them be there just to show what happens Just It kind of makes variant records make a little more sense if you see the error that's gonna happen Okay, it looks like I got another issue there By for discriminant. Let's be static. Oh Why did you work before but not now? It doesn't want you to possibly change it because it's a variant record now. I get it. I get it Ah So that instance what they need to do then is Okay, so this is what I was talking about for was Wanting to show you this error Component not present in subtype of example So if we see that's on line 21, that's where we try to access the B field of EC which if you remember The Discriminant provided here is a lowercase c which would mean that there's going to be an a field And no B field That's important if we change this to using an a field and Then you know, obviously of the correct type this works that's because variant records are essentially a Impossible list you don't have to have this of common fields which apply to every single variant as well as I mean, if it's a variant record you I guess arguably you could not have any of these but it'd be stupid it would just make it a discriminant record with a case structure in there that doesn't need to be there but Practically there needs to be something in here that provides some level of variance and In our case It's it's just a simple example. It's not practical by any means, but it does show what needs to be shown Based on the discriminant you're going to have either no additional field Or one of these two additional fields These are useful for Situations where you would have kind of like a very simple class hierarchy that the functions Methods if you're working with classes really wouldn't really have that much of Of a difference between these variants and it's essentially just Having some additional data tag along Any of the variants within the methods could be very easy to write I'm talking very simple class hierarchy. These may actually be a better option I do use them sometimes for that reason so Yeah, I don't really think there's anything more to show there. It's just it's a fairly simple concept Next time around we'll be getting into tagged records which forms the basis of object-oriented programming Unlike in other languages object orientation is rather broken up into discrete parts that you can Optionally take use of it's not like an all-in to object-oriented programming But you certainly can go that route for now though Hopefully you found this video helpful if it has considered giving a thumbs up and also consider subscribing Comment with questions all that kind of stuff that you pretty much already know to do but apparently these kinds of things serve as a good reminder Until the next video have a good one