A navy suit is one of the most versatile suits you can own. It's as easy to dress up as it is to dress down. You can wear it for basically any occasion and in any season, yes, including summer. It's got to have the right elements though and in this video we're going to talk about what those are and I'm going to show you five different ways to wear a navy suit in the summer. I'm Brian Sakawa and you're watching He Spoke Style. The number one most important thing, primary consideration when it comes to wearing a suit in the summertime is the fabric. It's got to be light. It's got to be breathable. There are a variety of different fabrics that fit that bill including what we've got here which is a hopsack. Now hopsack is actually a particular kind of weave in the fabric, not the fabric itself though we tend to use those terms interchangeably. It's light. It's got some texture which makes it more casual and on this suit in particular which is from our collection with Michael Andrews, we also have patch pockets and a half lining which also contributes to the casual and airy quality making it a great fit for summer. As you can see I've styled it in a pretty classic way though definitely with a few nods to the season with lighter colors and seasonal fabrics. The shirt is HSS Michael Andrews ice blue Oxford cloth and I paired that with a great light tan linen tie by Drake's summer fabrics.  Even though this is kind of a classic look we're going with a more carefree pocket square fold. Sunglasses are by Oliver Peoples, they're the banks. On my wrist is the Vacheron Constantin Traditionale and then we're finishing off this look with a pair of suede penny loafers by Tube Boot New York. Aside from the fabric choice which remember is the most important part of the equation here we are taking a look at one of the most obvious ways to make a suit more tolerable when it's hot outside and that is by losing the tie. This particular look is so simple and so easy to do it just looks so cool so smooth and so classic in that really casual relaxed and summer kind of way. Cocktail party, date night, alfresco dinner with a slight breeze coming off the sea perfect for that. Those are the scenarios I think this would look great in now let's just quickly go over the details of this very simple look. White shirt is a lightweight poplin it's HSS Michael Andrews, sunglasses are by John Varvatos, watch is the IWC Anjanur and anchored by a pair of chic suede loafers by Bowden and Lang. Unless I'm going to someplace like the jungle I always take one suit with me on vacation Robin and I like to go out for cocktails or a nice dinner here in there and getting dressed up is a part of the experience for us. Wearing a suit though does not necessarily mean that you have to wear a tie and this look showcases one of the ways that I love to kind of walk that line between dressy and casual with my summertime suited looks. The hero piece here and what makes the outfit is this tan polo from our collection with Michael Andrews. It's in a very soft pima cotton but it honestly feels more like a merino wool more of a knit field and a cotton polo shirt. You don't have to do the collar the way I did over the jacket but for this look I like the retro kind of devil may care swankiness that it lends to it. For a vacation look like this gotta have a hat. My Panama hat here is by Homero Ortega, Oliver Peoples Banks sunglasses again. On my wrist is the Tag Heuer Carrera Blue Dreamer, my absolute favorite summer watch and then finishing this look off with the Allen Edmonds Grand Cayman Horse Bit loafers. Kind of a variation on the second look here though a little edgier and a lot more casual. This outfit is actually a great platform to bring up the issue of these categories that we like to kind of section style off into. You've got a suit, that's dressy, a t-shirt, that's casual. They don't mix, some people will say, but I would say why not? Why is it quote unquote illegal to combine tailored clothing with casual clothing? Personally, I think it's totally fine and it really encapsulates this sort of forward momentum and furthering of an acceptance of tailored clothing into more men's wardrobe. I want you guys to understand that there's not just one way to do something and that there is no wrong when it comes to mixing tailored and casual. For some people like me, it's really an honest expression of my personal style and my love for both of those styles. I'm gonna get off my soapbox now to let you know that the t-shirt I'm wearing is by Theory. The sunglasses, my Hollywood sunglasses are vintage USS frames with a blue lens that I got from Retrospects. Making a statement with the datagraph on the wrist and keeping it sporty, casual, and cool with the common project's original Achilles. Another classic suited look though, we're doing it up with a little more summer style and flair this time. Regardless of whether you consider your style to be more conservative or kind of on the less adventurous side, summer is a great opportunity to have a little fun with color and pattern. That doesn't mean you need to go overboard and be really loud and wild. Just something subtle with a little seasonal color and pattern will get the job done. Easy way to do that with a shirt is to add a light pink shirt to your wardrobe. Looks great with a navy suit. The tie here by Drake's, silk, cool pattern that's playful but not too loud, really complements the suit and the shirt and makes a great focal point to the outfit. Pocket square is also by Drake's. Sunglasses are by Oliver Peoples. On my wrist once again is the Vacheron Constantin Traditionnel. Belgian shoes, Mr. Casual, suede loafers. If you think it's too hot in the summer to wear a suit, think again. And I've actually put together a playlist for you showing you many, many, many ways to wear a suit when it's hot outside. No excuses. So click there, I'll jump into some other suits and see you in those videos with some fresh outfit ideas. And don't forget, stay tailored.


So, the research I've presented at this conference is trying to solve a simple problem, which is trying to come up with an estimate of the number of people moving from one country to another country in the Asia Pacific region in, again, a given year. And the problem is we're looking at 53 countries and migration from one country to another. And of those 53 countries, only four provide any type of kind of data, what we would call a migration flow. Other countries provide some information, partial information such as labor flows, but none of it is complete. So, our project that we're presenting here is trying to, basically, is presenting our first attempts at coming up with a complete picture of the movements across a very big region in the world so that we can understand the impacts of migration better. The four countries are Japan, South Korea, New Zealand, and Australia. And all four of those countries have excellent administrative systems to gather information on migration and entries and exits. The problem is they're not the major senders or receivers within the region, and they're not necessarily a kind of a typical country within the Asia Pacific region. So, one of the challenges, although those countries provide really good data, is how do you translate those experiences to other countries? And so, we really need big countries like China and India to gather information as well as a lot of other Indonesia, Philippines, Pacific islands. You name it, if any country could do better, it would help our understanding of migration. My view is really the best way to improve the situation on migration is to improve the administrative data collection systems, either for border control, censuses, registers, and so forth. We have strong population registers and really strong interconnected administrative data systems. So, those are, and I think all countries are moving in that direction and we will get there. It might take some time for countries that don't have many resources or expertise, but really for all sorts of ranges, even beyond migration, having good information on their populations and how their health care systems, the tax registers, and also enabling them to count how many people there are. But yeah, for migration data perspective, countries that have good population registers that pull information from lots of other administrative registers in the country have the best information.


Hey everyone welcome back to some more Python programming tutorials We're looking at the end-py screen module in the last video. We were actually checking out how we can set up this Next active form variable within our form object or parent app class You know our app object that's kind of managing the forms and the screens that we see on our screen and Now that we've actually gotten our program to be able to close Properly we can move on we can do some cool stuff Now we're finally gonna actually add widgets or at least start to learn a little bit more about them So I'm gonna save my script as zero five now and let's do Let's I don't know. Let's as usual. Let's refer the documentation to see what we can do. I Remember reading way back in the create function I know it was it was talking about that as kind of the initializer or the forms constructor By default it does nothing, but we can override it and pretty much It's the best place to set up the widgets on a form So expect this method to be full of self dot add method calls Now that's what we're gonna be doing in the form create function We're gonna actually add those self dot method self dot add. Sorry method calls So that's what we'll call and we'll add some widgets now I'm kind of curious if it gives us any examples that I can I can show you But if not, we'll just move on to widgets and their basic features. So, okay Let's do some reading before we dive in Widgets are created by passing their class as the first argument of a forms add method The remaining arguments are gonna be passed the widgets on constructor and these control things such as size position name and initial values Cool. So let's try it out. I'll hop over to my code here and in our create function We can finally get rid of this pass keyword and actually do something cool here self dot add is the function that's going to create a new widget So we need the widget name This function is going to take what widget it is and in this case for learning purposes I'll tell you that we can use title Text notice that the t is capitalized in title and the t is capitalized in text for the first t in both of those words and It is going to need some other arguments, right? The remaining arguments are passed to the widgets on constructor Their class is the first argument. So that's why we pass in title text and The second the remaining arguments are going to be given in. I wonder if we can run it without it without any optional variables or arguments and Yeah, so now we've got this little thing here no name It says and it is a text box. We can type in text here sweet Got some got some interaction. Now. We can actually do something with our program Now if I press the arrow keys to kind of navigate and move over to the okay button I can hit enter and get out of our program So let's look at more of those arguments and stuff that we can add to it The constructor arguments name you should probably give each widget a name which is a string of force We're appropriate it will be used as the label of the widget and we saw that in our code, right? No name over here was probably set by default, but if we did supply a name name can equal Let's see First name and Then we're good Now if I run this you can see first name John. It's got a value over there sweet It's interesting though if you didn't want this to be displayed No name is like it said well. It showed us before by default, but if we try to set an empty string Whoa, we get an error That's so that's something that I kind of wanted to show you and point out to you However, if you use a space character you can kind of hide it so now you just have an Empty text box just floating out in space I Use control you which is a command line shortcut to delete all that text real quickly in case you wanted to know and So sweet all move our first name Back over there and let's see what else have we got here rel x and well y these are positions of the widget on the form They're controlled by relative x and relative y integers Normally you don't have to specify them and in this case the form will do its best to decide where to put them You can specify only one or the other if you choose you don't usually need to specify rel x honestly If you do give a negative value for rel x or well y the widget will try to be positioned to the bottom right hand side of The form and of the screen if the form is resized and pi screen will try and do its best to keep the widget in place nice There are other arguments for width height maximum width and height and values even okay, so we can supply a default value so I'll say First name value can equal Joe If I run this code. Hey now Joe is filled in there, but my name is John not Joe Values plural where a widget offers the user a selection from a list of values there can these can be specified here It's the initial setting of the values attributes. Oh, there are things like editable that determine whether or not We can actually edit the widget Normally it's true hidden whether with it widget is visible or not, huh? So I mean I can just set this not display with hidden equals true I run this huh Really? I'm not I don't I don't seem to be getting that that work Nope Doesn't look like it. Okay. Am I entering the wrong way? Even if hidden were false that would mean that it would be visible. Yeah, it's still visible Okay So there we go a little bit more learning for you guys there Maybe that one doesn't have as much functionality as we were hoping for color and label color. That's pretty cool We'll get into that more Scroll exit slow scroll and exit left and exit right or at least other options for it These affect the way that user interacts with multi-line widgets so we're gonna get into multi-line widgets really really soon of course because there are a lot more to learn about them and but for now you'll know that that argument does exist and Display update you can read about these if you'd like There are functions It looks like if you were to subclass a value or subclass a widget like a title text widget And you can actually subclass and kind of derive this function when the value is edited like once you've changed any portion of The text box you can know what what's going on and what's happening so that's kind of a cool way to do it and Of course you can override this function for your own use Same thing happens when cursor moved whenever you kind of go to a different position in the text box or anything else Edit is what allows you to interact with the widget kind of works like edit with the form and Set rel y and rel x are kind of similar things That we read about earlier Titled widgets those are the things that we're actually looking at right now because of course we have title text You can see that we've got Well, it explains here that many widgets exist in two forms one with a label and one without So the one with the label in this case is what we're looking at first name or this name argument acts as our label if the label is particularly long when it's kind of a Displaying it the label may be put on its own line, so I've seen a few examples of this like if I entered date of birth It might be a little long and you'll notice that date of birth is way up there and My input is way down here Some people might not like that So there are these options here that explains use two lines if either true or false override what the widget would otherwise to choose field width How wide should the entry part of the widget be? You can determine like You'll notice if I actually typed a lot of text in here It's gonna start to scroll a little bit So it can you can determine how wide should the thing be? in your display and This begin entry at is kind of an interesting variable because you can determine at what columns with the entry part of the widget begin By default it's 16, which is why all these characters date of birth in this label is too far And it's pushing it are it's pushing our input down a line if we had tried it like See what is it called begin entry at yeah begin entry at equals let's say 25 Now you'll notice 05 My cursor is way over here and that's where my entry begins So now we're not being pushed over on a new line by our date of birth label Cool Internally entitled widgets are usually a text box and whatever other kind of widget is required You can access the separate widgets if you need to you normally don't through the label widget and entry widget attributes Okay, so we can access these things with like a dot selector in our code However, you may never need to since the value and values attributes of the combined widget should work as expected Now there is a little bit of functionality for creating your own widgets You just have to subclass the widget class and you can calculate the area you can add lines make attributes and Resize this stuff. I'm not going to go into too much depth about that right now at least for this video I want to show you the very very basic introduction of a widget and kind of the arguments you can give it and pass to it Reminder hidden equals false or hidden equals true isn't working the way we expected note the interesting functionality of Multiple lines and if your label is too long or where you can begin your entry at a column that sort of stuff and Title text is just one of the many widgets that we can use I just want to use it as a gateway to teach you the constructor arguments and what more you can do with them So cool. I know this is probably a long video and I was just kind of guiding through the API reference But that's what a lot of this stuff is it's kind of exploring and seeing what you can do with it So thank you guys for watching. I hope you enjoyed this I'm certain we'll get into more cool stuff as we get further and further along in the series But it's his building blocks man. These are these are baby steps All right. Thank you again guys. I'll see you in the next tutorial


Hello. Hi, everyone. I'm Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. This is day 49 of Salesforce Learning Bootcamp. And in this session, I'm going to cover three topics. First is wrapper class. Second one is APIC security. And then I will discuss about APIC's best practices, right? So this is the second last session of APICs and trigger and tomorrow I will be having one more session than this topic will be completed. So let's wait for a couple of more minutes so that everybody who like watch the sessions live, they can join. And then I will be starting the session. So hi Praveen, hi Revati, hi Srinivas Acharya. Welcome. So okay, so numbers are increasing slowly. So this is just the beginning. So just wait for a couple of more minutes so that more folks can join. And if you have joined this session for the first time, so you can go through this slide so that you know about the instructor about me. And I hope everybody is focusing on these on this learning best practices. So this is very much important. And if you want to learn all the topics properly, so you just need to practice things regularly. So I can see more folks in the chat. So Arjun is there. Hello Arjun, Ankit, Nikhil, Nusrat, hi everyone. Shubham, hello, good evening. So lots of people are joining and I just see some posts in the YouTube comment section. So lots of people are watching the recordings as well for practice for learning if they miss the live session. So they're watching the recording. So that is good. So I'm just assuming like you are following all the best practices and be consistent because consistency is the key and do regular practice if you want to become expert. And like today, it will be an interactive session. So from the beginning, if you have any doubt, you can ask questions. So maybe today's session will be less small because we have very few topics remaining and tomorrow everything will be completed. And then from next week, we'll be discussing about the apex test class, right? So now topics will be completed within a week. So this week, like tomorrow, I will be completing the apex and trigger part. And next week, we'll be having test class sessions. So this is very easy. And then after that, we'll be having a synchronous apex, right? And we visual force and integration you requested. So I just added those as well. Okay, so this is the next six weeks timeline. And after that, we will be having like prerequisite HTML, CSS, JavaScript, then few sessions on aura and lots of sessions on LWC, right? So after all these six weeks, you will be having lightning aura and lightning web component phase of this boot camp. So actually, this boot camp is running in three parts. First part was admin. Second part is this apex trigger test class, async apex VF integration. And next part will be lightning aura and LWC. Okay, so now I'm moving forward with the slide. So if you have not followed Sanjay Gupta Tech School on these social media platforms or do so so that you can follow everything and you don't miss the important notifications. And as per your request, like last yesterday, I shared a few PDFs related to development related interview question and answers. So if you have if you have not received, so I just shared them in telegram group and on LinkedIn, right? So just just have those with you so that if you have any interview scheduled, so you can just prepare yourself. Okay, and share this channel link with everybody, whoever wants to learn Salesforce. And someone is asking about cybersecurity bootcamp links. So actually that is there in the Salesforce session tracker. So if you go to Salesforce session tracker, so here now you will find two tabs, one for admin and development and one for the cybersecurity. So here is the sheet. So we are working on it. And this will be utilized for cybersecurity. And lots of people are asking, is it related to Salesforce? So I would say yes. In Salesforce, we have cybersecurity career. So it is totally related to Salesforce. And other than Salesforce and other ecosystems, also, you can get a job as a cybersecurity expert, right? So moving forward, so let's discuss about the first topic. And it is wrapper class. So today's topics are very easy to understand. And more theoretical explanation will be there. So for wrapper class, I just have an example that I will be discussing. So first we need to understand the requirement of wrapper class, like why wrapper class is there and how it is fruitful. So basically, a wrapper class is an object created in Apex. The data lives only in the code during transaction and does not consume database stories. So when I say it is an object, so it doesn't mean like actual object in your org will be created. So that object will be created in the Apex only for that particular transaction. And you can also say like it is a data structure on an abstract data type. So generally what happens if you want to contain different objects or collections or off objects as its member. So basically, you can create a wrapper. So sometimes what happens if you are implementing a class and through class, if you want to return two or three different type of values. So through a class, like if you implement a method, so method can return only one type of value. But if you want to return many type of values, so what you can do, you can wrap them in a wrapper class. So a wrapper class member can be primitive collection or S object. So I will show you an example so that you can visualize how we can create a wrapper class and how we can use that wrapper class so that different type of values we can club together and that we can return easily. So if I go forward, so these are some benefits. It helps to combine different types of data together and the wrapper class can be used in LWC or an visual force, right? So now jumping on to the developer console. So here I have one example for you that we can understand. So in this example, you will see class name is account wrapper demo. And here we have a method. So method is this, which is highlighted here. And after that, you will see a wrapper class. So this is basically your wrapper class. Okay, so inside a class inside account wrapper demo, we have a method. And after that we are creating one class. So this is basically class inside class. And this will be known as wrapper class. Now in this wrapper class, what I did, I have created two variables. One is ACC record and one is contact list. And both are having different type. This account record is basically of type account and contact list is of type list of contact, right? So what you can see here are two different variables of two different data types are available. And this is basically a constructor. So through constructor, this value will be initialized. And we already discussed about this. So this is basically referencing these two variables which are declared here. And in the constructor first line, we are also using the same name, right? So they are written here without this keyword. Okay, so whatever value we will be passing into these constructor, those will be assigned into these variables which we have declared above. Right now here, what is happening? We are just creating list of this wrapper. We are creating list of this account wrapper. And we are fetching account along with context. Now I'm iterating on account here. And that account record, we are setting into this new account wrapper. So this way new instance will be created. And its constructor will be called and constructor will be receiving this account record as a first parameter. And that accounts, all the contacts will be received as a second parameter that will go to this contact list. Okay, and that newly created instance will be added into this list. So this way, we are just creating instance of the wrapper class. And that we are adding into this wrapper list. Okay, so if you want to create a collection of different different types of variables, so you can just create a wrapper class like this, you can create a constructor and you can initialize the values. And then that wrapper class you can use above in any method for the processing. Right, now if you want to execute it for testing purpose, so this way you can implement the code. So right now what I did here, I just created a list of this wrapper type. So you can use account wrapper demo. This is the name of class. And this is the wrapper that we created. So we are going to create list of this wrapper type named as account list. And we are calling that method. So that method is basically returning the wrapper list, which we are creating here. Okay, so it will be stored into acess list. So here I am just using system dot debug, so it will be rendered. And if we iterate on this, so here you can see again, I'm using that wrapper that wrapper is part of this account wrapper demo class. So that's why we are using it like this. And ACC will be having a count record, first value, and a contact list as second value so that we can fetch. Right, so this way, like the idea is if you want to create collection of different type of variables, so for that purpose, you can create a wrapper class. Okay. Yes, Jenna, it is also known as inner class, because it is created inside another class. And here we are using with sharing that I will be explaining after this topic, which is related to APIC security. And this statement you can ignore because whenever you call your APICs class through lightning or a component or lightning web component, then generally we use this annotation at the rate or I enabled, right? So you can just ignore it. Whenever we will be using our apex class with aura and LWC, then you will see these statements. Okay, so now let me take questions. So Manjunath is asking, can we we can use switch on trigger with events instead of trigger contact context variables? So through events, we cannot switch on or switch off triggers that we can do three through context variable only. Otherwise, we have custom metadata type that we can use, right? And movement is asking about real time projects. So I have already explained a project and admin. So the same project I will be picking for development stuff. Thank you, Nusrat. Thank you, Shubham. I appreciate like my effort are going in the right direction, whatever I'm explaining is being asked in the interviews as well. Okay, Shubham. So like these two topics, we'll be covering in the next two weeks. So I think then you will be able to understand them. Okay, Manjunath, share this thing trigger dot operation type. So this is something different. I never used it. So just explore this. And this is not an event. Events are total seven. Right. So it might be some method or something like that. So I just need to explore it. I don't know much about this. Yes, Jana, we can create the wrapper class just below the curly basis of the main class. But generally, we create wrapper at the end, because in the beginning, we just want all the method. And at the end, you can create the wrapper class. So this is just as per the best practice. Because the wrapper will be used in above methods. So we don't write wrapper above, it will create confusion. So in the beginning, you will have all the methods and then you can write the wrapper class. Right. So we have few more questions. So, okay, Shrivali is asking what different type of data it's using. So if we talk about that type of data, so you can just go through the last line. In wrapper, we can have primitive, we can have collections like list set or map, and we can have s objects. So these types you can use in the wrapper. And if you want to see the example, so here it is. So here we are having these two variables. First one is of type s object account. And second is of type s object collection. Right. So this way this wrapper class is created and above it is used here. So in line number four, we are using wrapper class. And here also we are using this wrapper. Okay. So this was about wrapper class. Now I'm just moving to the next point. So next is APIC security and sharing. So let's understand it. It is very easy. So here you saw in this example, I'm using public with sharing. So it is basically related to this sharing. So if you remember in sharing and security, we have two things. One is record level security. And one is other one is object and field level security. So if you want to enforce record level security, like if you have created any sharing rule, and if you want to enforce that, so for that we use with sharing. So basically the with sharing keyword lets you specify that the sharing rule for the current user current user means the logged in user are considered for the class. You have to explicitly set this keyword as APICS code runs in system context. So if you don't write this, if you don't write this, so it means your APICS code is running in the system context. If you don't write anything, it means the logged in user will be able to access all the things. But if you want to apply, like if you want to enforce sharing, record sharing, so you can just write with sharing. So if you write with sharing, it means the records which are accessible by the logged in user, only those records will be available to the to that user. Right? So this is very much important. So you need to remember by default, it is system context. If you want to change, then you can apply with sharing. Then next is without sharing. So if you want to specify, so this is another keyword that you can use. And if you use it, it means like your sharing rules or security won't be enforced. And third one is inherited sharing. So it is different one. So just understand it carefully. So APICS without a sharing declaration is insecure by default, right? Because it will be having the system context. So an APICS class with inherited sharing runs as with sharing when used as so in any APICS class, if you write inherited sharing, so it means with sharing automatically, if your APICS class is used as an auto component controller, visual force controller, or if you're using it in APICS rest service, or any other entry point to an APICS transaction, right? So with another feature, if you're using APICS as a support, so in that case that inherited sharing runs as with sharing, right? So the this is very good interview question like what types we can specify with the first line of the APICS class. So you need to specify with sharing, you need to specify without sharing, and you need to specify inherited sharing. So further, there is a distinct difference between an APICS class that is marked with inherited sharing and one with an omitted sharing declaration. So omitted sharing declaration means no sharing declaration is available, right? As we did earlier, like we didn't provide any sharing declaration. So if the class is used as the entry point to an APICS transaction, an omitted sharing declaration runs as without sharing. However, inherited sharing runs as with sharing. A class declared as inherited sharing runs as without sharing only when explicitly called from an already established without sharing context, right? So if you have created a class, which is declared as inherited sharing, and that class method you are calling into another class, where you have specified without sharing in that context, your inherited sharing will be working as without sharing, right? So in that way, like you will be able to use inherited sharing with one and without sharing with other. So you might be thinking in what scenario we will be using without sharing. So in this last point scenario, like if you have two classes, so by default, inherited sharing will be means with sharing. But if you call that method into a class where you are using without sharing, so it will be shared as without sharing, right? So these points you need to remember as part of interview. Now this is also important to remember. So sharing setting of the class where the method is defined is applied, not of the class where the method is called. This means that if a method is defined in a class declared with sharing is called by a class declared with without sharing, the method executes with sharing rules and forced, right? So it is important where the method is defined, not the where method is called. So if your method is defined in a class where with sharing is available. So if you call that method into another class where without sharing is available. So even then there your method will be working as with sharing, right? So this you need to remember. And this is very good interview question like what keyword you will be using and what will happen when you use that particular keyword, right? So one more thing that you need to remember. So when we enforce the sharing things. So if you are logged in as a user, so two things will be impacted. One is SOQL or SOSL and another one is DML. So when you use with sharing, so it may happen like you are querying data and you are retrieving less data if you compare it with system context. Because in system context, sharing won't be applied. You will be able to access all the records. But if you write with sharing, so in that case, sharing like all the sharing settings will be enforced and whatever records you have access to, only those records will be fetched. And then we have DML. So an operation may fail because the current user doesn't have the correct permission. So if you if you don't have proper permission, so your DML maybe may fail. So this you need to remember, right? So till now, whatever we discussed, it was about record sharing. So if you talk about with sharing, without sharing and inherited sharing, so that is basically specific to record level security, right? Now if we talk about object and field permission, if you want to enforce that security, so that you can do while applying SOQL. So if you apply SOQL like this, select ID name from account with security enforced, right? So basis on the logged in user permission data will be fetched, right? So if you have access to account, then only you will be able to fetch the data. If you have access to ID and name field, then only you will be able to fetch that record. Right? So this way, you just need to remember everything as per interview preference. Okay. So before moving to Apex and trigger best practices, let me just see the questions, whatever you have asked. So there are a few questions. So what is platform event? So maybe I will be explaining that tomorrow. And Shubham is asking what is heap size? So heap is a runtime memory. So whenever you apply any SOQL, or you just create a data at runtime, so that data is basically stored in a heap, right? And like limit heap limit, you can just see in the log. So if you if you go to the log, so there you will be able to see that. So let me open the logs. And if I scroll to the bottom, so here you will see. So maximum heap size is this, right? So here you can see all the limitations. Okay, Jana is asking, what does it mean get set? So these are basically representing getter and setter. So here in this wrapper. So whenever you create these variables, you need to apply get set get set means these variables can get the data and like they can set the data. So getter setter means they can store some value and they can throw that value to other methods as well. So it is it is as part of syntax. So you just need to write it like this only. Okay, so I already showed this code, so you can just see it. So this is the wrapper class. And if I go above, so here you can see the method. Okay, so can wrapper class take the permission of parent class? Yes. So it is totally dependent on the parent class. How many wrapper classes in main wrapper class? So I think you can create any number, but we don't create much. We generally create couple or one wrapper class as per the requirement. So what is system context? System context means, you can say as admin. Yeah, so it is it is more of same. But I just explained one point where like if you use inherited sharing, so if your class is having inherited sharing, and that class method you are calling in the without sharing, so it works as without sharing. That doesn't happen with sharing. This is the major difference. And generally we prefer with sharing if you want to enforce security. And if you don't want to enforce, we can go with without sharing as well. But there is third one you should know about inherited sharing as well. So this batch batchable epics and capable epics, we will be discussing in asynchronous epics. So that will be next to next week. So last week of this month, we'll be having these topics. So when a like with sharing doesn't go with the field level security, if you are asking this question, so you can just take this in consideration with security enforced. And I think if you don't have permission, so it will throw an arrow. So this you can try once. You can just log in with the user. We already created two users in our org. So you can just assign one profile to that your second user, which is non admin, and just try it out. So very good event. As I already explained the wrapper class, let me just go through again. So wrapper class is very simple here. Like if you want to create collection of different type of value, so you can just declare them and through constructor, you can initialize them. So this is part of syntax. And whenever wherever you want to use it. So what you need to do, you just need to create it. You need to create instance. So here we are creating list of that wrapper class. And here I'm creating an instance and I'm adding that into that list. So this way you can use it. Okay, so I hope it is clear now. So moving forward next, we need to discuss apex and trigger best practices. And these are very much important to understand. Okay, so total 15 best practices I have noted down. So I will be explaining them one by one. And if you have any doubt in any of the best practice, so just note it down or you can just throw it in the chat so that I can discuss it again. So first best practice is you need to use proper naming convention. So proper naming convention means if you see here, name of the class. So in name of the class, you can just notice here, we have three words account, then we have wrapper and we have demo. So this like you can see each words first letter is capital. Right. If we talk about the method, so in method, first word is totally small. And then second word on words first letter of each word is capital. Right. So these are basically camel case notation that you need to apply by implementing your apex class or apex method. Right. And if you're creating variable, so variable and method both apply same naming convention. So variable also like first word is small and second word on word first letter of each word is capital. So this way you can just apply the naming convention. Okay, and use meaningful names so that if you are working as a developer and you leave the company and any other developer on your place working, so they just understand the working of the method through the naming convention. Right. Whenever you are using list, so add list because if you see all the example where I implemented anything, so I just use like opportunity list. Right. Here also OPP list and wherever I'm using map, so I'm just appending map. So this way, what type of process you are implementing. So you just need to append. So if you are creating set, so you can just add set. So here we are using ACC ID. So what you can do you can write ACC ID set. This way you can just use the naming convention. Right. So this was the first best practice that you need to remember. Don't use any name XYZ ABC to define variable or method. So that is not part of best practice. Then we have bulkify your code. So always remember whenever you are writing apex code or trigger. So always remember in real time your code will be working on more than one records. So you need to bulkify your code. So here you can see in each handler, we are iterating, we are iterating a process. No matter whether you are testing it for one record or many, we are iterating on bulk off records. Right. So if you go to this trigger, so in trigger also this trigger dot new old old old map, like these are list and map, which will be having lots of data. Right. So always remember like your code will be bulkified and like you need to implement it in keeping you need to implement keeping in mind like this code will be working on the more than one records. Right. Next is we need to avoid ASOQL and DML inside loop. So we have a term called as governor limit. So there are two governor limits for ASOQL it is 100 for DML it is 150. So in a single transaction, I repeat in a single transaction, if you have more than 100 ASOQLs, then your code will break or in a single transaction, if you have more than 150 DML, then also your code will break. Right. So in a single transaction, not in a project, in a single transaction, let's say you're creating any record and on that record creation process, if you have more than 100 ASOQL, your code will break. So why you should avoid ASOQL and DML inside loop because loop is a iterative process and it can work more than 100 or 150 times. So if you write your ASOQL and DML inside the loop, so it may break. Right. So this unit to remember the next is we need to avoid hard code IDs. So never hard code IDs because in Salesforce, whenever you will be working on a project, so there will be lots of environments like right now we are using developer edition, but in real time, we'll be having copies of that org. Right. So what do you need to do? You need to deploy code from one org to another. So in one org, there may be different IDs available for particular record and in another org, there may be different IDs. So never hard code IDs. No matter you are using Flow or Apex or Trigger, you need to remember you never use hard code IDs. Right. Better to query. Right. So we saw one example where we need to use record type ID or maybe profile ID. Right. So what we did, we queried that we didn't use that ID directly. Right. So if you if you need any ID, so you just need to query the record and then only you will be able to use it. So this is part of best practice and you need to apply this. If you don't apply and you write hard coded IDs, so whenever you deploy your code from one environment to another, your code will break. Right. Next we have use one trigger per subject. So I already explained you like implement a trigger in such a way so that it will be managed. So here you can see in this trigger, we have called all the methods. No business logic is available in the trigger. So this is a manageable trigger and it is suggested always have one trigger on one S object so that you can manage and the sequence which you define here for method calling, it will be intact. So you can change it anytime. And if you have two triggers on one object, then an order won't be guaranteed. Okay, so try to implement one trigger per S object. Next best practices are so basically these best practices are mixed for apex and trigger. Right. So next is use inline SOQL for loop. So inline SOQL for loop means in the for loop in the first line you will be using SOQL like this. Okay, so this is basically inline SOQL where in the first line of for loop we are using this SOQL. Now, basically the benefit of using this SOQL here, it basically saves your heap. So if we write it above, if we write it above and store it into a list, so what will happen? All the data will be queried and that will be stored in the list. But now here what is happening? It basically works in chunks of 200 records. So first 200 records will be queried and that will be processed. Then next set of 200 records will be queried and that will be processed. Right. So this way less heap will be occupied. So this is suggestive. But if you use that process like above this loop, if you write SOQL, so that is also good. But best practice says whenever you need to write any SOQL, so you can write it in the first line of the loop so that you can just save heap memory. Then next is modularize your code. So modularize means whenever you are implementing any trigger handler, so there will be separate methods like for this prevent deletion, we have separate method for update account, we have separate methods. So this way, whenever you are implementing your trigger handler, so you need to implement it in modular form. Don't write all the logic in a single method. So break your logic into different methods. And whatever method you need, you can call them in the trigger at appropriate position. Okay, so don't write large methods, break them into pieces that is basically known as modularized approach. Right. Next is querying large data set. So you need to apply where clause never write SOQL without where clause. If you miss where clause, it means all the data which is available under that particular object that will be queried, and it will be a huge problem for you. Right. So always apply where clause like minimize the data that you are querying. Then avoid business logic and trigger use trigger handler class instead that we are already using from the day one. So I tried to show you all the trigger scenarios with this approach only. So we used to call the method in the trigger only and the business logic was available in the trigger handler class. Right. So business logic means this code, the method, whatever is containing it is called, it is called a business logic. And if you go to the trigger, so in trigger, we don't have any logic. Here we have just one liner. And these one liners are calling the methods directly. Right. So implement trigger and trigger handler separately in trigger, you can call the methods and trigger handler, you can define those methods having separate business logics. Then we have context, specific handler methods. Right. So it says like define specific method, don't mix two methods having two separate context. Right. So whatever business logic you have as per that business logic, you need to define that handler separately. So these are five more best practices that you need to remember. And this is a very good interview question. So generally in interview interviewer can ask you like tell me apex and trigger best practices what you need to remember while implementing apex and trigger. So these points, these total 15 points you need to remember. So we already discussed 10 points. Now next five points are also available here. So first says test multiple scenarios. So you need to check your record through different ways. So while implementing trigger, I already told you like test it through one record, test it through bulk records creation. Right. You can create bulk record through code and you can create one record through UI. So you need to test it from positive and negative scenarios as well. Like sometime you can fill the data in the field, sometime you can blank it out. So positive negative all the all the cases you need to test. And next week we'll be understanding how we can test our code through code. So we will be understanding apex test classes. So there also we will be writing test methods. So this is part of best practice whenever you implement any apex class. So you just need to test it manually. And if you know how to write apex test class, so you need to write that as well. Because generally in projects what we do, we work in the sandbox environment, which is copy of production environment. So in sandbox, if you implement any apex class, and you want to push that apex class to your production environment. So without test class, you won't be able to push your code into production. So if you implement any apex class, so you need to write its test class as well. Right. Next we have avoid nested loops use map instead. So if you have nested loop situation, so you can just avoid that nested loop, and you can implement the map. So in one scenario, I think I already demoed you how you can remove nested loop with help of map. If you have not gone through that video, so you can just go back. And I think last week I explained that. Then use database class methods while performing DML operation. So I hope you remember in DML statement, like if any record is failing, so all the list will fail. But if you use database class methods, so you can pass a parameter known as false. And if few records are failing, so only those records will fail. Other successful records will be committed to the database. So you can prefer database class methods over a DML statements. And if you are using DML statement, then you need to write exception handling, because if DML statements are failing, so through exception handling, like through try and catch, you can handle those situations. So what will happen? Only that piece of code will be breaking other functionality will be working fine. If you don't write exception handling code, and your DML statement is failing, so whole process will fail. And apply proper security and sharing an apex code wherever it is required. So these are total 15 best practices that I figured out related to apex and trigger that you need to remember as part of interview. Right. So this is all I prepared for today's session. I know today's session is very short because we have very few topics remaining. So few topics I will be covering tomorrow. And if you have any doubt, you can ask if you don't, you can just leave and join tomorrow's session. And day after tomorrow, we'll be having cybersecurity bootcamp session that also you can join. So everything is listed in the session tracker. Right. So like tomorrow, I will be covering all these remaining topics and don't miss this cybersecurity bootcamp launch because whatever doubts you will be having, no matter you attend all the bootcamp, still this first session will be important to understand. And if you don't go in the cybersecurity part, then also this bootcamp is important because we are related to tech, IT field, IT industry. So we need to know what cybersecurity is, what are the different tools technologies available. So you should be aware of that. Right. So that anytime if you see any like fraud is happening with you through digitally, so you can just stop that. Right. So it is totally free at different time. So if you don't have time to watch it live, you can go through the recordings as well. Right. And if you want to see the list of content, so it is available here in this tab. So here all the topics are listed, we are redefining it. Right. So this is tentative. We'll be updating it time to time. So we'll be starting from the beginning so that the beginner can understand what cybersecurity is. So here you can see all the network related concepts will be explained like request, header response, then installation configuration. So step by step, Sumit will be covering all the topics for you and he is having 10 plus years of experience. So I think it will be good for you. And here is the link which is available. So you can just RSVP this link so that you receive a notification. And it is like 21 days bootcamp planned as of now as per your feedback and responses, we will be like adding more sessions into it. So this is phase one and soon we'll be having phase two. So let's see how it goes. So coming here so Anuradha is asking single transaction means so another single transaction means suppose you are creating a record. So if you are creating a record so in that record creation process, your flows, your approval process, your trigger may be working. So once your record is created, that whole process will be known as single transaction. Right? Next is in apex class, we have option security where we provide access based on profile, how which sharing is different than security in apex. So Sachin basically the security means on on profile profile is different thing profile controls like your object and field level security and this with sharing without sharing is controlled is controlling your record level security. Right? So like if you already implemented sharing and security through profiles and sharing rule and you implemented a class where you have not mentioned anything with sharing without sharing. So irrespective to your sharing and security that logged in user will be able to access the records. Right? So that's why if you want to restrict you can apply with sharing and for field and object you can apply with security enforced in SOQL. Yeah, Jana it is fixed like 200 records batch will be processed. So please explain one more time best practice 10 point. Okay, number 10. So I'm going back number 10 is context specific handler method. So it means like whenever you are implementing any method, so it should be specific to one problem. You don't need to mix two problems together. Right? If they have common like I just merge before insert and after sorry before insert and before update, they were having exact same business logic then I just combined them. Otherwise you need to implement methods separately. So best practices means like the way you need to implement the code and order of execution means how different different features will be running in the background that is different. Right? Both are totally different. So order of execution means how different features work which are available in Salesforce and which order they will be executing and best practices means like you just need to implement code in efficient way. Yes, first, like few best practices are related to test class, but for test class will be having separate best practices. Tomorrow's second or tomorrow session time is same. From next week timing will be different. It will be one hour prior to like this week. And throughout the boot camp we were having session at 830 PM IST from next week onwards it will be 730 PM IST Salesforce and 9 PM IST will be your security one. So Ashok nested loop means if you use a loop inside another loop. So that is basically nested loop. So this with security and force I already explained like it will be respecting all your object and field level security. This strip strip plan line accessible. This I just need to check because I rarely used it. So I will check and get back to you. Yes, I'm here. Sumit will be showing his face life. Actually, if you see his LinkedIn profile, so there he used that profile picture because he belongs to cybersecurity. So it is kind of related to that. So that's why his actual phase is not visible in the picture. But surely while we'll be having live session, so we will be together, you can just see him. Yes, our trigger will be executed in system context. And then if you call any Apex class that decides what sharing you are using. Yes, if you write try and catch with every DML so it is better because you never know in which DML you will get an error. Right? So if you're working on a real time project, so in every DML statement, you need to write try and catch. So Jana basically wrapper classes we use when we implement visual force page or LWC or aura. So maybe there we can have proper example. So this wrapper class we will be calling in aura or LWC component, then you will better understand the use of wrapper class. So single transaction means creation of record through different processes like trigger, float, etc. In this single record or multiple records are created. Yeah. So in in simple words, if you are creating a record and in that record creation, different processes will be involved. It can be trigger, it can be flow, it can be validation rule workflows, etc, etc. So once all those steps will be completed, so that is basically known as a single transaction. And if you are creating multiple records, then also all these features will be executed in the background. So that will also part of one transaction. So record creation, updation, deletion, undeletion, these creates a transaction. Yeah, so Ashok, it will process 200 records in one batch. If we have more than 200 records, so it will be processed with different, different batches. Okay, so I hope I answered all all your questions. There is one more question, can we call a pick through flows using invocable method, we'll be covering this. Yeah, so I think there is one video that you can watch for this, Arjuna. If you go to study Salesforce, so here I think in a pick scenarios, you can find these examples. So you can go through and whatever doubts you will be having. So maybe you can ask in the telegram group, or separately as well. So I won't be covering these because if I cover everything, so it will be very long bootcamp. So I'm just focusing all the concepts tomorrow, which are remaining. These you can go through yourself and try to understand. If you have any issue, you can ask separately. Okay, thank you. Yes, Jenna, for DML statement for sure, you need to apply exception handling. Other than that, if you see in your code, there is any runtime error can come. So you can apply try catch there as well. So it depends whether in your code, you will be seeing any issue or not. Right, so it depends on that. If you have more question, you can ask. Otherwise, I can just end the session because I just completed everything. And tomorrow, a picks and trigger will be completed. And next week, we'll be starting test classes. So if you have any more question, you can ask and please share your feedback or reviews. If you have any suggestions, and this will go with cybersecurity as well. If you have any suggestions, so you can share. If you don't have any questions, so I take your leave. And tomorrow, same time, we'll be having the session. Thank you so much for joining today's session. Have a good evening, good day. Thank you so much. Bye, everyone.


Baseball's back in the drama that we all wanted to see unfold is finally unfolding as the Dodgers face the Astros This one's brought to you by DraftKings for those of you that don't know the context behind this the Astros beat the Dodgers in The World Series while they were cheating so Joe Kelly's on the mound Braggman's at the plate. It's a three-run game and Joe Kelly cannot find the zone He falls behind 2-0. He's gonna fall behind 3-0 here And now you can kind of see his wheel spin and we're like, all right three runs I only need two outs and probably just hit this dude. He goes the first. We'll get the double play or I'll get two outs Okay, yeah, I'll just throw at this dude behind his head 96 miles per hour Braggman hits the deck.  I turned to while he's yawning then to make matters even worse He's just gonna try to hit him on the pick-off throw. This is this is a strategy some pitchers do like all right I'll scare you there now.  You seeing this Braggman's like, hey guys, hey cardboard cutouts.  So now with Karey up. He's like screw the fastball I can't throw it for a strike. I'll go off speed off speed. Maybe that's on purpose as well He's like, hey, I wanted to hit this dude with my fastball, but I got no idea where it's going Karey's like, uh, dude, that could have hurt me. What's up?     What? All right All right That's kind of it. They kind of break it up Dusty Baker got a little upset. He's protecting his guys for the first time So shout out Dusty. I mean color spray is a great a weirdo We all know that but I think he handled this situation pretty well Braggman handled it pretty well and Joe Kelly. It was on purpose. Hey, you knew it was gonna happen It happened. This one was brought to you by DraftKings download the DraftKings app use promo code John boy go grab Joe Kelly if you're on his side Go grab the Astros if you're on their side put them on your squad earn some money have some fun baseball's back It's better than ever. What a time Low behind the scenes as this happened.


Hi Vanessa. This is Ashley with Oxmore Toyota. I wanted to send you over a quick video greeting. That way you can see who you're working with. Thank you so much for recently talking with me about your interest in Sequoia. If you are able to stop into dealership, please just ask for me. That way I can get you with the sales representative to help you out. If you need anything, please feel free to give me a call. My number is 502-247166 or you can also email me back. Thanks. Bye.


Hello everyone, Dylan Schumacher, Citadel Defense, and we are back with part four of Minuteman Tactics. So today we are gonna take a slight break and we are gonna talk about safety. Because safety is important because you don't want to shoot your own guys. Now, in general, there are kind of two different ways to think about safety, right? There's, you know, on the range safety and then there's what we're gonna call operational safety or, you know, when it's out, we're out doing goon stuff because China invaded and it's red dawn and you gotta run around.  What kind of safety measures are we going to use to an order, in order to ensure that doesn't happen? So, let's discuss a few of those. Now, I differentiate between range safety and range safety and operational safety because on the range, right, if you go to a class or you're at a shooting range or whatever, it's everybody's pretty meticulous about it, right?   So, we're all online, you know, and everything's like perfect, right? Because we're on the range, no one's shooting at us. We have time, there's no reason to not do that, really.  You can do that on the range. When people are shooting at you and people are moving and there's screaming and smoke and whatever, you're not gonna get that, right? Not only that, but it's just bad tactics to stand right next to each other in a perfectly straight line so that you make a nice, big, easy target. So, how do we achieve safety in that regard? So, let's talk about some helpful guiding principles and rules that we have in order to be operationally safe. The first one is trust. This entire thing hinges on trust. You need to trust the other guys in your crew. Whether it's just one other guy or a couple other people, you need to have a high amount of trust that when they're shooting with you and around you, they're not going to shoot you. And if you don't have that trust, you either need to train them to a level of that trust or they're off the team. It's really that simple. Either you can trust your own guy to not shoot you or you don't want to be on a team with them because there's nothing worse than when the bad guy is shooting at you, having to worry about your own guy shooting you. That's obviously not what you want. So, everything I'm gonna say, trust is the undergirding and overriding principle that has to guide all of this. You've got to trust your guys. And on a small, minute-man team, again, we are not in the military. We're not working with 19-year-olds. We don't have direct officer oversight. As we've mentioned in the previous parts of this series, so that trust has to be high. These are guys that you choose to train with. These are guys that you choose to associate yourself with. And so I really hope that you have that high level of trust. And if you have any concerns about their safety, now's the time to have that discussion. So, what kind of rules or things are we gonna implement in order to ensure that we have that trust? Everybody's working to the same standard of safety. Well, the first one is the four rules. I wrote these out of order. But the first one is the four rules of firearm safety, which I'm sure you're familiar with, right? Those should be ingrained in your soul and ingrained in the soul that people you're working with. All guns are always loaded or treat all guns as if they're always loaded. Never point your gun at anything you're not willing to destroy. That one's a big one in this department when we're talking about doing what we're talking about. Keep your fingers straight and off the trigger until you're ready to fire. And then know your target. It's foreground and it's background. Also a very big one in what we're talking about here. So, if you follow the four rules of safety, then which were handed down to us by the great Jeff Cooper and I think the 70s, right? Then obviously you can avoid and mitigate 99.49% of accidents and that's what we want. So, at the very base level, if the guys in your crew or someone on your crew doesn't have a solid understanding of the four rules of safety, that's a big problem. You need to explain that to them and they need to just do it, right? I've had friends of mine that have had to rehabilitate and now I completely and utterly trust them and that's a good thing. In the book, he talks about safety angles and he talks about three different angles that he kind of uses as safety. The first one is the 45 degree safety angle and training when you're starting to get used to this, right? So, again, if this is 90 degrees, right? And this is 45, like my rifle never gets within 45 degrees of anyone else, right? And that's a good starting point for a safety angle. After people have been experienced a little bit and kind of know what they're doing, he suggests using the 33 degree angle of safety, right? So, if that's 45, maybe 33 is kind of right there. And then he talks about once you're super experienced and you have a high level of trust, again, it always goes back to that trust, you can cut that down to 15, right? 15's pretty close, that's pretty close. And these are the safety angles that he uses and recommends. I'd like to add some other things to that. So, I think this is a good, helpful guide for understanding general safety angles. I think one of the biggest principles for being operationally safe with you and your guys is earn the shot to get online. Earn the shot to get online. We'll talk about some good examples and we'll talk about some bad examples. Say you're traveling in a wedge formation and you're traveling this way, right? And you take contact from over here. Well, this guy can shoot, right? And this guy can shoot. Because let's say there's about 10, 15 yards of spacing, they're within our safety angles that we just talked about, that's totally fine. Those two guys can shoot. This guy cannot shoot. And this guy should not shoot, right? What should happen is this guy needs to work to get himself online. And this guy needs to work to get himself online. They have to earn the shot. They have to physically move their body to a place where they are able to take the shot. That's what we're talking about. When I say earn the shot, that's what I mean. You have to do work to get to a place where you are allowed, from a safety perspective, to take that shot. We call that earning the shot. So, that's a great example of earning the shot. Now, bad examples. You see this in police shooting videos all the time. I'd say over 80% of body cam footage videos you see, you will not see cops earning the shot. Often in police videos, you'll see this, right? There's a bad guy over here, there's four cops here, and they're all shooting that bad guy. Now, the problem with that is this guy is cutting it super close, and so is this guy. If this front guy decides he needs to move in one direction or the other, he's in a lot of trouble because he's gonna run directly into the fire of one of his comrades, right? But you see this all the time. Cops are just in a semi-gaggle, they're just pulling out their guns, and they're sending rounds down range, either because they're afraid, or they're not thinking, or they haven't been trained, most likely to earn the shot, and so they're thinking, oh, it's fine, I can do that, and they'll just shoot that way. You also see this in a lot of SWAT, which are supposed to be more trained videos, where guys will shoot from the back of the bus. Shooting from the back of the bus. Say you have a bad guy here, you have a shield guy here, right, and you have a little stack of guys, well, this guy will just step right out here, here's your shield guy, and he'll start shooting the bad guy, and he'll think, oh, I'm fine, no big deal. Why can't I shoot from here? I can see him, and then they find out in the after-action report that about three rounds struck the back of the shield. That happens, and it happens more often than you think. If all of these guys were to earn the shot, then they would need to get up here and get online. Then there'd be nobody between them and the target, right? Know your target, it's foreground, what's between me and the target, and it's background. Cops don't ever check their background either, but that's a different rant for a different video. So I really think that this is a very large principle when it comes to safely shooting on teams, is earning that shot and getting online.  They have to get used to the idea of physically moving to get to a place where they can then shoot. If you have guys who are just used to shooting where they're standing and not bothering to move, that's gonna increase your likelihood of accidents through the roof. This applies out in the field when you're spaced five, 10 yards apart, and it applies even more so when you start to get into CQB classes or CQB environments, right? Which in general we wanna avoid, but again we'll cover that when we get to the CQB stuff, but you need to have SOPs for how is a guy going, if I'm shooting right here and I'm standing in a doorway, how is another guy gonna get his rifle over my shoulder and in the fight, right? How are we gonna do that safely so that I'm not getting muzzled?  There are very safe ways to do that and there are very, very unsafe ways to do that. And so we need to work those SOPs out with your team. If you wanna know more about that, I teach classes about that, come take a rifle class with me, it'll be a lot of fun. So there are two drills that you can do dry that I think are super beneficial to practice getting online. The first one is you can just get your guys out in the field, you can just have empty guns, you don't need loaded guns at all. And you can just practice getting online. And you can just say contact left, right? And everybody steps up and gets online left. You can say contact right and then this guy comes over here and everybody's online right and you can all safely shoot right, right? For the wedge, contact rear and contact front are pretty simple cause everybody's safe already. You can put your guys in a diamond formation, right? And do the same thing, contact left, contact right and this guy can come over, or this guy would actually come down here or this guy can come down over here depending on which side you're on, right?  Just walk out in the field in formation and then start saying contact left, contact right, contact rear, whatever and have everybody physically move to where they would have to be. Then when everyone gets set, stop, look around, examine, yep, this is right, know this is wrong and then just do that for about a half hour, hour and your team's gonna get a lot better at getting online and remembering to get online. And that's a dry drill you can run for five, 10 minutes every time you go out with your guys. The other one that you can do is for working more in that CQB-ish environment we talked about earlier is just take a plot of ground and mark it off like 10 yards square, put a bunch of random targets and debris and whatever pieces of cover in here. Have your guys stand in that 10 yards kind of randomly scattered around and then just say, hey, contact left and everybody has to move to a piece of cover and not flag their guy or anybody else and get their rifle up, right? So you're still just doing the same thing but this way you have to move around obstacles, you have to move around your buddies, you might have to share cover, you're gonna get used to working right next to someone safely, not flagging anybody. Again, you do that for five, 10, 20 minutes every time you go out and you're gonna get a lot better at navigating around obstacles, knowing where all your guys are and then getting online, right? You have to have a high level of situational awareness to know where all your guys are. If I know where all my guys are, I know my safety angles and I know I'm online, I'm clear to send it. If I'm not sure where my guys are, then how do I know if I'm online or not, right? So again, this breeds having that situational awareness of where your other guys are because let's be honest, you don't have enough guys on your side to accidentally waste them. Again, this comes back to trust.  The last thing I'd like to mention here about safety because I think it's important is IFF, identify friend foe. This is a good spot to think about having some kind of standardized uniform. Now, two caveats about that.  They could be in multicam or woodland or greens or whatever, but you know, that's Bob. I've known Bob for six years. I know what his outline looks like. I've worked with him a bunch. No, I know what Bob looks like, okay? That's one point, and I think there's credence to that. I kind of generally fall in that bucket. The other perspective is, look, things are chaotic. We're not sure. You don't ever want to misidentify your guys. So it's helpful if you have some kind of IFF marker.  That becomes, the larger your unit gets, the more important that becomes, right? When you might not necessarily know everybody, that becomes a really big deal. So having IFF markers on your team and starting to build that habit is only gonna serve you and it's only gonna help you. So I would recommend that you think through some kind of IFF marker, identify friend foe, as a both additional safety net and just it's not gonna do you any harm. So why not think through it? I hope that is a helpful perspective on operational safety and how to best conduct that. I look forward for seeing you for the next round of Minuteman Tactics. Two brave deeds, and endure.


What's everybody Jason over jatsby's case breaks dot com 2020 hip parade football limited edition series 22 10 box hobby case break Roundtree number one just sold out and again. It's a repack product from hip parade member one incredible autograph per box They had number of these boxes. They do a hundred so 10 cases And we got a case here contains one autograph featuring some of the best stars Again including John Alway Breeze O'Dell all the way down to Murray and Alvin Kamara and much more guys Never really a checklist per se, but the cell sheet is right here. So some of the bigger hits you can pull out of here very very nice ones So let's do the randomizer first guys you get one team With one spot Talon down to Nick and Cardinals down to the Redskins. Let's roll it or Washington football team six out of two six in the two sorry eight times one two three Four five six seven down to Ryan eight times one two three four five six seven Alice Cowboys out of the Jacksonville Jaguars So that me of the Cowboys Danny with the Titans Ryan with the Texas Joel my Eagles rich You got the dolphins make with the Panthers right with the Packers make with the Rams air with the Patriots Allen with the Saints town with the Lions Jeremy with the Bengals Ryan with the Vikings air went with the Broncos and Richard the Buffalo Bills Ryan with the Jets Benjamin with the 49ers Jarrell with the Steelers J with the Giants of insanity with the Browns Danny with the Seahawks Robbin the Ravens Benjamin with the Chargers Jeremy with the Redskins Benjamin with the Chiefs Nick last by Mojo Bucks Juan with the Bears Gary with the Colts Jeremy with the Cardinals Aaron with the Raiders Megan with the Falcons and Ryan with the Jacksonville Jack So if there are any trades now is the time Proposal trade make a trade If no activity in the next minute, then I will close it Very nice Mac a PSA 9 is not that I take a 9 over PSA 9 over a 9 in BGS Sure Not great at the Rui. Yeah, I'm starting to be okay with PSA 9s now. I first like I hated it I know it's what I'm saying, but I don't know. I just feel like a 9. You're like, uh, yeah But I guess it's better than looking at a BGS 9 When you would think so, yeah, I think it's like 9 BGS 9 PSA and then 9 5 and then 10 and then pristine and then Black Yeah Yeah, what's I'm saying if it's a thicker cards, I can't really Yeah No, yeah, and like you said sometimes you don't notice what's under like the microscope Scratches Yeah, I see no I know I seen a listing it was like a Luga base or something like that or chrome and the guy goes How the how is this a PSA 7? Can you see that and he's like is there something I'm missing here some guy goes well There could be like scratches you're not noticing I saw someone get graded a Luca and it came back a PC or a BGS 4 and a half I'm saying like unless you notice that it's like ripped or like owners are damaged It's a first seven Lawless spots. I any trades guys Daniel or Seahawks for Browns anybody want to trade who has the Browns I've been sounding I don't know if you're listening and Raiders if I die that Raiders big Vegas what is that you can see this was open up Do that one yeah one more time all right the bedding sit like don't the big TV anything just looks sick Oh, yeah, that's true All right guys, so this is limited edition series 22 we got case 3 out of 10 There was a couple of them yesterday see Frank Gordon here. No idea who's he playing for For All right guys, well, I couldn't pronounce the literary I'll print it out. I'll get some paper, but there you go Stayed the same Juju or Venice. Yeah, well the beauty of this is that look every team is represented I don't know how many hits per team would have but I at least have one And yeah, it just kind of Start thinking about you're like, well, it could be a badass. It could be a Rothesburg or there could be this there could be that That's kind of the fun part of this Obviously the not so fun part is only 10 hits so obviously low percentage of you hitting but You do get a hit. Hey, it should be a nice one that should easily pay for the spot price So that's kind of the cool thing about this Now when it gets a sapphire edition when it's like only three hits in a whole break That's obviously super super high-end stuff But this is actually a good price point, I think Especially the price for a random team The hit should be pretty nice, but obviously not every box is gonna Be the best Our first box is nine out of 100. I have another Gary box to No, I don't have it today, but I'll get it tomorrow Rocky over. I don't do it. I know it's probably way better sleeping Oh sequam Barkley. Very nice That is a 66 out of 90s or no 96 out of 99 Is that a rookie? Yeah, be consider rookie I guess There you go for the Giants who has the Giants Jay with the Giants Very nice It's a nice way to start it off flex upon Barkley stuff hasn't probably been going for as much as should All right box 36 out of 100 now Tyreek Hill iconic ink 26 out of 99 Kansas City Chiefs, that is going to Benjamin box 42 out of 100 Otani Walker O'Dell Walker for the Wildland It was a big card guys It's auto relics 2006 15 triple threads 21 out of 36 Ladanian Tomlinson and Melvin Gordon. I don't even know Gordon's name I guess I just didn't notice the Tomlinson on top. They go dual auto Relic booklet that'd be a Melvin Gordon rookie Both going to the Chargers very nice Chargers, that's going to Benjamin very very nice George Kittle out of 49 From signature series This must be from Chronicles 49ers that is going to Benjamin as well Having a good break 18 out of 100 and Miko Harman, Jr. Rookie ticket contenders optic 29 out of one 99 another one for the Chiefs and Have yourself a break Benjamin Chiefs Chargers and 49ers. I think the three spots he has in this break all the teams have hit so far Halfway through guys five more. Oh, this is a sell sheet here. I believe the Sean Watson. That's a rookie patch autograph from Spectra 62 out of 99 I believe that is a sell sheet hit Very very nice Yeah, it's right there who has the Houston Texans Ryan C Colwell, there you go. That is a nice one right there Didn't he just get paid And Dakka's just looking at all these players get Get paid Still hasn't got a contract. I know Benjamin. I would like At this point, I don't think so Benjamin Grated It's a 9-5 and it's Kenny Gholaday from Panini encased 37 out of 75 9-5-10 Detroit Lions That's Talon. Oh Lou Brock passed away Like today. Oh man.  Oh, yeah, tomorrow's David. That's right. Maybe Tuesday. I believe yeah Yeah, I think it's I think with us is kind of tough because the city of Hermosa is a little Tough and since we have so many employees, I don't even think we have enough people that can actually come in and shop There's like a limit to how many people can come in here Gary with the Colts though, but you break tomorrow. Yeah, I'm breaking off. Yeah, we'll be I Don't know if we'll be open for a curbside tomorrow But I mean we'll be able to break so here tomorrow, but I believe our projected. It was Tuesday. That's still to be determined I think we're gonna go to the city and see what we can do about that And we just don't want to get in trouble.  Whoa. This is actually a rookie. Nice That's a rookie AJ Green for the bangles Jeremy with the bangles. I think he was he was a rookie in 2011, right? Yeah. Yeah, it's a rookie very nice Bangles Joe Burrow much Joe Burrow than actually beat the Chargers The legend our last box guys and it's a spectra patch autograph of Portland sudden three-color patch One out of 60 Denver Broncos it's going to Aaron Pettit And there you go everybody. That was the break so again I know it can be a little rough break, but some very nice hits if you did get a hit Barically one-to-one Marshall Falk Kenny Galladay the case hit of course to Shawn Watson Miko Harmon George Kittle do autograph booklet relic of Gordon of Ladanian Tomlinson That was hit parade football addition if you do like this stuff guys We do have basketball addition sapphire is a much more High-risk high reward, but that's that down to 17 only three hits coming out of that one I have a baseball one down to nine that one's similar to this one where there's 10 boxes And then of course a lot of other breaks on the website guys Appreciate it. Jasper's case breaks.com


Welcome to the Tick-Mill Update. I'm Kiana Daniel, the founder of the Invest-Deva Movement. On Monday, we found out that the UK is aiming to put the Brexit laws before Parliament on Friday. That means the bill would aim to put the terms of the deal agreed between the UK Prime Minister Boris Johnson and the Eurozone into law and the government is confident of going on to secure a long-term free trade agreement with the bloc. Today, I'm looking at the QEM pair, which has completed a double bottom bullish reversal chart pattern that we identified last month. And it helped the pair bottom out at the key support level of 66. Now, looking at the pair on the weekly chart, we noticed that the pair is just about to hit the lower band of the weekly Ichimoku Cloud, which is also the level and it falls on the 61% for Banachi Tracement level. This means that the pair's bullish momentum could slow down after the past four weeks of back-to-back gains. The new medium-term support levels are set at 71.64, 70.50 and 69. Of course, trading in the financial markets involves a risk of loss and you should only trade the money that you can afford to lose. If you liked this video, give it a thumbs up and subscribe to the Tick Mill YouTube channel. I'll get back to you with more updates tomorrow.


How do you feel timing-wise and at the plate and, you know, how ideal or not ideal is this? I feel good. I think those games are really good. Brush it up for me to get going this weekend, so I feel good. The timing's there. And I'm glad I could get back for those. OK. Jean-Claire, to your right. Jean-Claire, what was your takeaway from your playoff experience last year and do you think that can benefit you this time around? Yeah.  We're going to make some mistakes, but it's kind of the battle of the least mistakes and, you know, just be precise and just understand every little thing counts. Do you look at the playoffs as kind of an opportunity to put the regular season behind you and those frustrations and kind of change the narrative of the whole season? That's over. That's over for everyone. We won the division. The season's over, so in a sense, everyone can't look back anymore. It's all one day at a time, one play at a time, and it starts tomorrow. So nothing but preparation from the season can help us now. You're on a team that traditionally relies on the home run. Was it unusual now facing a team that has hit even more home runs this year? Yeah, it's interesting. I mean, it's cool what both our teams were able to do with the home run and along with the rest of the league, but yeah, it'll be cool, cool dynamic, and, you know, big punches thrown. Kristi? You went into the playoffs last year, a first time, big expectations for you. James Paxton's kind of in that same situation. What would you tell him as advice or what to expect tomorrow night? Just being his own, you know, play his own game, you know, not try to do something he hasn't done before, not try to be something different, prepared differently, you know, the stakes are higher, but at the same time, if he didn't perform the way he would, he wouldn't be in this situation. So, you know, just prepare like he normally does. Okay. Marley over in the center here, Giancarlo. Giancarlo, can you describe the atmosphere in this stadium last year, what you're expecting tomorrow? Oh, it's nuts. It was nuts. They really bring the heat and make it tough on the opposing team. So, it's great. I'm looking forward to just as loud, just as rowdy as last year and it's going to be fun. Okay. Anything else for Giancarlo? All right. Sweeney in the front and Jack right after. Giancarlo, with all the injuries the last two years, you, Judge Sanchez and even Encarnacion have not had a lot of opportunities to be in the lineup together.  Yeah. Yeah. I mean, this is the best time to all be back. And, you know, we all know what we can do individually in parts of the season. So, now we're all together and, you know, we just got to bring that big force and, you know, make sure we take care of it. Okay. Jack. Giancarlo, you had to be very patient and endure a lot of rehab to get to this moment. How did your confidence level change or did it ever change as you were working your way back to know you could have a day like tomorrow night or a night like tomorrow night? Yeah. I mean, that was terrible for me. So, I just use it as this is what I built it for. This is what I'm doing all this for and just visualize what I can do.  It was all looking forward to this. So, now we're here. Okay. Just one more in the back there. Hey, G, obviously, CC not on the roster. Did he say anything to the team about the ALDS and what you guys should do going forward or that overall mission you guys have preached since day one? Yeah. Yeah. I mean, just from everything we've gone through all year, just that we're ready. You know, we've taken enough punches and we're ready to go out and battle and enjoy this month.  Okay, great. Thanks, John Carlar, for the time. Really appreciate it.


Hello, I stand here today, or not standing, I'm sitting here today in crappy lighting to tell you guys all about this next page requested review, which was Voyage of the Shadow Moon and it was requested by Moritz Fuchs, actually now that I'm thinking about it I think it's supposed to be Moritz Fuchs, but you know, either way I read this book and it was fine. This is the introduction song, it's not very good but it's not too long. If you missed the last one of these I did, basically I'm not doing Patreon requested reviews anymore, at least until I can think of a new way to do them, so I only had three more to do and this is number two, so after this there'll only be one more. If you want more detail watch the Eye of the Oracle review. But basically Voyage of the Shadow Moon is, well, it sounds kind of like a regular epic fantasy story on paper and in a lot of ways it is. It's basically just, okay, a band of adventurers go off on a quest to stop some sort of major evil dude, like in this case it's basically just this emperor who wants to conquer basically everything and who has this crazy powerful magical weapon that'll allow him to do it. And the main thing that sets it apart, at least a little bit, is that this one is more ocean focused, like I'm not sure what the name for this subgenre would be, like pirate fantasy or something like that, but rather than being mostly people on land doing land based adventures, it's people on a ship who are, you know, they're very experienced sailors and it's mostly about them sailing from place to place and it's nautical themed, nautical focused, however you want to put that and so it does give the setting at the very least a little bit of a different feeling to it, which as someone who hasn't read a whole lot of, again I don't know what you'd call it, but pirate fantasy is what I'm going to call it for now, but as someone who hasn't read a whole lot of that, yeah, it was kind of nice to get something that was at least a little bit different. And beyond that I think that this book is fine, you know, it doesn't have a whole lot in there that really stuck out to me all that much, like I read it and enjoyed it, it's fine, it was all right, but I just, I don't have all that much to talk about really. So an issue that I have is that the beginning kind of falls into the trap of starting off with a bang in that you start off with an action scene. Now it could be a lot worse because I have seen much worse examples of that where it's just like, oh this person swung sword, this other guy swung sword, then gun go off and someone's shot and the problem with that, at least in book form, is that I don't know these people and I don't know what they're fighting about so I don't really care that much. And I've seen worse examples than in this because in this it basically starts off with there's a city that's under siege, it's been under siege for a little while and then there's like a big battle to finish it off, but it doesn't focus on the fighting itself too much, so much as like the people who are in command of one side of the fighting and why exactly they're doing this and what led up to this moment and then the final destruction of the city, or not destruction per se, but the final victory that they achieve, let's say. So while yes, I still didn't care all that much about what was going on at this point and so while this is a big dramatic moment that had it come later in the story would probably have had my attention a little more, it's still not too awful here, you know I've seen so much worse than that and at the very least it does start things off pretty quickly so other people might be more into that, I don't know. And as for the main ship that most of the characters travel on, the Shadow Moon, I think that's also pretty fun you know it's like at first it seems like oh okay it's just some regular old nondescript ship that no one really cares about, it's really small so it can't carry that much cargo or that many passengers, it doesn't move that fast so like no one cares about it, but then as the story goes on you learn oh okay it's actually much more advanced than that and even though the crew is small they are all at least a little unique in terms of characterization like the captain is kind of his own thing and then pretty early on they bring in a passenger by the name of Loran, I think that's how you're supposed to say it and he, I've seen this trope done before but I still really like it, he is a vampire who's been around for hundreds of years but he still looks like he's a 14 year old boy because he was turned when he was very young and you know I've seen that before like in interview with a vampire Kirsten Dunn's character was you know she looks like a little girl but she was actually much older than that or in a skyrim there was that I want to say her name was Babette, I don't remember though and she was a vampire who was turned when she was 10 years old but she was over 200 by the time the the game starts and I don't know why but something about that is just really cool to me like this body that looks like it should belong to someone well you know who's a child they're they're innocent but they're they're clearly not you know they're vampires they fucking kill people I don't know I just I really like that and I think that's cool and you know we have a couple other characters like that on there and they're they're all fun you know that they all have a little bit of personality to them I remember at least something about all of them that was that was kind of cool it I I have kind of the same issue with this that I had with Zenith it's not to the same extent but if you remember my review of that a few months ago in that one I was a little upset that there were only four members of the crew because part of the fun of having a ship like this is in stuff like say Mass Effect or Firefly where there's a much bigger cast and they all again have their own personalities they have their own goals and dreams they have their own in some cases they have their own unique ways of fighting or uh you can also look at the relationships between all of them which is pretty cool when it's done right like having a bigger crew allows for more of that and in this we only have a couple of characters so that was that was a little disappointing but you know not too big a deal I also thought that the villain the emperor uh was sovereign war sovereign something like that uh I thought he was kind of fun you know he's kind of just an evil dude who's doing evil stuff because he's evil but he had a neat backstory I enjoyed watching him have to not only just be this evil guy who sends his armies at the main characters but he also has to deal with some political intrigue on his side and having to keep his allies in check and avoid being stabbed in the back by his wife you know that that was all kind of fun I enjoyed that and it's rare for political intrigue and political maneuvering stuff to be done well especially in fantasy for some reason like I don't know what it is but they're just most fantasy authors are not particularly good at that which is usually fine when it's not focused on too much but sometimes they focus on it way too much like well like the back half of Wheel of Time is a good example they spend a shitload of time on that and it just feels like yeah I don't want to get into that but basically all the political maneuvering stuff in here that was fun I enjoyed it and you know I just don't have that much specific to say about this you know like like the world is kind of fun you know it's fine it has a little bit of a different feel to it than most other worlds I read about because again it's nautical flavored but it doesn't stand out all that much it's still kind of like oh yeah fantasy world the characters I remember some of them pretty well I there's a bunch that kind of fade into the background because this has a relatively large cast which is unfortunate but you know it does happen and I remember a couple though and those were good you know the way this book is paced and the storyline all that is good the actual prose the writing of it is good and it's it's kind of a simple read for is the thing like there's only so much detail I can go into regarding why I liked it and well yeah I just I just don't have that much else to say this is a fairly long book so if you're just expecting a quick like oh this would be a little swashbuckling adventure like no it's not that you're not going to get that like this is trying to be epic fantasy in a lot of ways so it is fairly long but I did get through it relatively quick so I I don't know just keep all that in mind if you decide to check this one out I I'd recommend at least reading like some sample chapters on Amazon or something if it sounds like something might that might peak that might peak your interest and if not then you're reading it's probably not going to change your mind but overall yeah voyage of the shadow moon I thought it was all right I enjoyed myself special thanks to all the names you see here these are all my patrons and especially thanks to my ten dollar and up patrons oppo savalainen olivia ran brother santotes carolina clay christopher quintan echo great grebo joel karkat kitsune k r stevensson leisel rudakova lord tiebreaker madison lewis benet microphone moritz fox sad martigan samuel nevin tobacco crow tom beanie and vei victus as well as you know everyone who's watched this far if you want to get your name on here or get access to stuff like early access to my videos and voting on what topic i'll cover next then consider becoming a patron if you don't want to do that then you could also just subscribe and like this video and share it around or become a youtube channel member really there's a lot of things you could be doing to make my life better and that's really what this is all about it's all about what you can do for me so uh get on that bye