All right, so there's been a lot of talk about web components to this presentation, so I'm excited to be able to talk about what that means in terms of how we use Backbone and how we build our web applications in the future. So I have a bit of a click-baity title there, Game Changing Combination, but I think the technologies and web components will really try and change how we approach web development going forward. So my name is Andrew Rota, I'm a JavaScript engineer at Wayfair.com here in Boston, and I get to work with some really exciting technologies every day, JavaScript, HTML5, Backbone of course, and that's really cool. And so for the past few years, I'm constantly thinking about what's next in JavaScript, how can we apply the tools that we have today to make really cool products, but then how, going forward, can we be prepared for the future? And there was an article recently called the State of JavaScript in 2015, a few weeks ago, by a developer who was talking about, you know, what are the lessons that we've learned, and where do we think we'll be over the next year and the years going forward. And he made a really good observation and he said that, you know, components with a dedicated purpose in a small surface area are really advantageous. They allow us to take pieces of our framework, mix and match them, swap them out, and be really modular and flexible in building our applications. And I think this is a philosophy that we really share in the Backbone community. But I think about how we use modularity in the web, and there are all sorts of different ways, whether it's on the back end or the front end, but on the client side, one of those ways is simply HTML. We've had DOM elements for a long time, and they're actually really modular. And that's kind of cool. You know, for example, let's say we have an unordered list. Make sure that's big enough. Everything's big on this screen. Yeah. Let's say we have an unordered list. It's really easy to go ahead and convert that to an ordered list. Like, you just change one character. And that's nice. I don't need to worry about breaking APIs. I don't need to worry about, you know, any big changes there. You know, even if I have something that's a little more complex, let's say I have a header with a whole bunch of stuff in it, when HTML5 came along and we had the new header element, I'd go ahead and throw that in there. And it wasn't really a big deal to switch it out. Same thing, say, with my navigation. Maybe this was a list. Maybe it was a div, or maybe I had a rather complex component. But I could go ahead and swap it out. And that was really cool, to be able to kind of see something new and not have to think, oh no, I'm going to have to rewrite my entire application to get this new technology. And so in this same article on the state of JavaScript in 2015, the author made the observation that, you know, maybe it's that libraries are greater than frameworks. And I, again, think this is something that we would agree with coming from a backbone place. But I kind of, thinking about this HTML modularity, thought we could take it a step further. You know, native functionality, I think, is really the most modular in terms of building out applications. And, but that's not possible, right? We can't, like, make our own HTML elements until now. So that's what web components are about. Web components are really this new HTML5 technology that allow us to create truly encapsulated and interchangeable components that extend HTML itself. It extends the functionality of the DOM. And this power is now given to us as developers. This is a quote by the Polymer project, and I think it's a really accurate description of the impact of web components. And so web components really aren't one big thing.  And so there are four main kind of technologies or APIs that make up web components. So I figured we'll start just by going through each one of these. So we have custom elements. That's probably one of the more interesting ones. So custom elements is this idea that I can go ahead and make my own HTML elements and register them on the DOM and use them as if they were a native element. To do this, I simply have to call document.register element. I pass in the name of the element, and then I pass in an options argument that the important option there is the prototype for my element. So in this case, I'm going to go ahead and just make a new object that sets the native DOM HTML element as my prototype. So I'm going to sort of get the basic package for a DOM element. So this is going to act just like a div. But that's actually native DOM there. I can write that in my HTML once I register this element. It's not like any special library or something to transpile it. It's just going to work. One thing to keep in mind about the name there is it does have to have a dash in it, and it's something that the spec authors decided would be a nice way to separate custom elements from native elements so we don't have namespace conflicts. But other than that, I can go ahead and namespace my elements however I like, name them whatever I want, and actually create an element I can use. So that's custom elements. The next technology are HTML templates. So HTML templates are actually a new element in HTML called template that allows us to put nodes on the page that we want to be used later on. And so when we actually place a template tag, anything within that template tag is going to be inert until we activate it by cloning it to use it in our document. So don't think so much about handlebars templates or mustache templates or underscore templates. This is a little different. It's not going to have that data binding or functionality or logic that you might be used to in templates. This is simply the bare bones DOM elements. And it means that you can store these in your DOM. The image won't be downloaded here because it's going to be completely inert when it's added to the page. And then to go ahead and activate it, I can clone it with document.import node, pass in the content property of my template object there, and then just pass in the second parameter true to tell JavaScript this is going to be a deep clone. So that's HTML templates. The next HTML web component technology is HTML imports. And this is the ability to actually import documents into our application with a link tag. So no longer our link tag is just for CSS. We can use it to pull in HTML documents directly. And in this animation here, it actually is just showing the documents filter on the network tag in Chrome Dev Tools. And you'll notice that we have a whole bunch of documents here. Normally, you'd probably only just see one where actually can pull in different HTML documents directly through the browser and use the browser's native mechanisms to pull these down. It's going to follow the same cross-origin request security rules that you're used to. But it's going to use link directly to pull these in. All right. So the fourth web component technology is a Shadow DOM. This is probably one of the more interesting ones, because it means that we can actually create a tree under our normal nodes in HTML that contain other HTML nodes. And it takes a little bit to get your mind around this. But I think a good example is something that the browsers have been doing for years. The browsers have been taking complex elements and implementing them with Shadow DOM nodes underneath that we don't see. When we look at our source, we don't normally see them. And so we can actually take the video element as an example. We can turn on user agent Shadow DOM. And here we see the video element that used to be just one element now has a shadow root and underneath that are a whole bunch of divs. And within those divs are more divs and inputs. And that kind of makes sense, right? Because we have controls here. We have a play button. We have a progress bar. We have the little timestamp. So there are a whole bunch of things going on that we sort of just assume that's how the browser works. But they're actually building this up with DOM elements. And they're putting them under the shadow root, so they sort of encapsulate them. We never see them unless we go ahead and turn on our dev tools to allow us to see them. But that's kind of cool. And it's not just encapsulating the HTML. These styles are actually going to be encapsulated too. So if you're coming from a CSS background at all, you know that encapsulation with CSS is pretty much impossible. We can sort of fake it with different patterns, and we can kind of increase our specificity and try to apply styles only to a certain area. But they're always going to leak out. There's always a possibility that DOM nodes somewhere else on the page will be impacted by our styles. But with Shadow DOM, that's a little different.  I can't change the color of that no matter what I do. I can put an important and I can make a super specific style. It's just not going to happen. With the Shadow DOM, you can actually protect and encapsulate your styles under your shadow root node. And so that's really powerful. And very basic to see how this works, we have an empty div first, and then I have a paragraph tag. We refer to the DOM outside of the shadow as the light DOM. So we have the light DOM in a paragraph. We have an empty element. I'm going to go ahead and select that element and call create shadow root on it. Create shadow root. We'll attach a shadow root to it and return the shadow root. So I now have a reference to that with my variable s there. And then I can go ahead and set the inner HTML of that shadow to be a style, to be other DOM elements. And so in this case, I'm actually going to throw a paragraph under there called shadow DOM. I'm going to put some styles in there just to make it red in this case. And if I go ahead and take a look at this, my div is simply my div with my paragraph next to it there. And then within my shadow root, I have my styles. And so those actually get encapsulated just like that video element did in terms of having a shadow root and being able to put styles within it that won't leak out into the outside document. And it goes both ways, that encapsulation. So that's really powerful. Something with these shadow DOM nodes as well as that I can take inner HTML from my light DOM and go ahead and project it within my shadow. When I create a shadow root, normally it's going to take everything that was within my element there and just not display it because it allows you to go ahead and display it wherever you like. So you use a new content element within your shadow DOM to project these nodes from the light DOM as if they were in your shadow. And something to notice here as well, I have that same style tag that's making the paragraph tags crimson that will not affect the content projected within my shadow. Because that's still in the light, even though it's being projected between my shadow DOM HTML there, it's still going to have the styles of the surrounding document. All right, so those are the four technologies that we have with web components. That's it. That's what we have to work with. And you can combine them in different ways. You can use them on their own. They're perfectly useful on their own. You can go ahead and use custom elements, templates, import, shadow DOM. They don't give you a super lot. I mean, we have some kind of game-changing features, I think. I think things like the shadow DOM and custom elements we didn't really have before. And so we get some things. We don't get everything. This doesn't replace all of our web applications. Certainly things that we're used to, we don't have here. We don't have things like application structure. We're just building HTML elements. We don't have any interaction with the server. None of that's built in. We don't have things to route our URLs on our pages. We don't have any models or collections or events to react to changing data on our page. But it turns out we have all of these with backbone. And so I don't think web components replace backbone. In fact, I think they work very nicely together. So let's go ahead and look how we can take each of these four technologies and apply them to our backbone application individually. So we'll start with custom elements. I can go ahead and register my custom element like I normally would. I could do this in a variety of places. And then in my backbone view, I can go ahead and just put the tag name for my custom element in as the tag name for my view. And it's going to work. There's nothing with backbone that makes tag name special to native elements. Because custom elements work the same as my native elements, this is going to attach the DOM element to my view that's based on my custom element. So that's really cool. HTML templates. We can use these to put templates on our page. Maybe you're using script tags to throw templates on your page. Or maybe I've seen templates attached in hidden divs before. They all seem sort of messy, and template can kind of replace that for us. This is certainly not going to replace maybe your server compiled templates. But it could give you a way to access DOM nodes from the document, and you don't have to worry about them being downloading extra content before it's needed. Images or scripts, et cetera. HTML imports in backbone. You don't really need backbone at all for that, because you can use it perfectly fine, because it's just HTML. It's not necessarily a JavaScript API. This is an attached API, but that's not really necessary to use them directly. And then shadow DOM. We can go ahead and use the reference to this .l in our backbone view, which is just a DOM element, and create a shadow root. And we could do all sorts of things there. We could add nodes underneath our view that we wanted to encapsulate from the outside world. We could style them appropriately in CSS. We can even use their special CSS selectors to go through those shadow roots and break through the shadow boundary if I want to select those elements. So these are all great. I can take each one of these individually and use them in backbone. And it doesn't really require a lot of work to do so. But as we saw in the last talk on D3, there's something different between just using things with backbone and using things well with backbone. There are different strategies to combining things. Combining things is easy, but combining them in a way that's useful is a little more challenging. And it's certainly dependent on what you want to do. And the good news about using web components, maybe the reason that you'd be interested in using them, is that there are a lot of really cool web components available out there already. Using the individual technologies are really less useful than using web components themselves. Using components that other people have built, other engineers have built, other companies have built, or maybe you've built within your organization to be used between applications. And there are a whole bunch of these components available right now. Polymer is an application that Google has been working on that's sort of powered by web components. But you don't have to buy into Polymer to use their elements. Their elements are available, and you can use them as web components. Mozilla has a library called XTags, which also has a bunch of open source web components that might be useful to your application. And there are all sorts of user repositories of these components online, and they're only growing. More and more engineers are making components that can be shared across applications. And so what might this look like? What if we want to take a component and integrate it within Backbone? And the first step is going to our Backbone view. This is more about the view layer in Backbone than it is about our models and collections. So let's go ahead and take an example and see what that would look like. So this is a cool little component from the Polymer Paper Library, which is toast. So it sort of pops up from the bottom of the screen there. And it's fairly basic, but it has some styling there. It has some animation. And so the first step to considering how to consume that from a Backbone application is to look at its API. And the API is really the starting point for integrating any custom element into your application. And these APIs aren't any different than our native DOM APIs. They might be a little more complicated, depending on how the element was built. But they're the same thing. And these DOM APIs are made up of three different features. The first are attributes. So these are regular attributes that we would throw onto our tag. In this case, we have the text for the toast. We have the duration that is going to be open. We have an attribute to tell us if we want to close it or not when you click outside of the toast. And then we have an attribute that tells us if it's open or not. And so changing these attributes will change the state of our element. It will change something on our element itself.  And so these are methods that we attach to our element. We attach them directly to the element. This isn't like some wrapper. This is attached directly to the DOM element itself. So you select the DOM element natively, and you have access to these methods. With the toast element comes with show, dismiss, and toggle out of the box to either show the component, hide it, or toggle it depending on its current state. And then the last piece of this API is events. So we have native DOM events that come with these custom elements. And again, these aren't sort of a custom event. These are events that we're listening to directly on the element, not unlike any other events you would listen to on DOM elements. In this case, we have one that's core overlay open completed, which is just a long way of saying when the animation is finished opening.  This is nothing special. This is going ahead and taking all the native functionality of a backbone view and using a web component, which means you don't need a special adapter. You don't need any real conversion layer. You can just use your backbone view. And from the perspective of your backbone view, this is simply a DOM element. You don't need to know that it was custom. You don't need to know that it was built either internally or externally. You just need to know that it exists as an element on your page and the API that you can work with for it. So in this case, I'm going to go ahead and set tag name. I'm going to go ahead and use backwindupviews attributes hash. I'll actually use the events hash to bind events like I normally would to a custom element. I don't have to do anything special. And then I can go ahead and wrap any methods that I'm interested in. I could certainly use the methods directly, this.l.toggle. I think it can be useful to wrap them if you want to, say, fire your own event or do any bookkeeping or management of different methods on your component. All right, let's take another component that's a little more complicated. So this is a component from Google called Google-map. And it just includes the Google map on the page. And this is a lot easier than using any JavaScript API to pull in Google Maps. You simply have to include this on your page, and it works. It actually defaults to San Francisco here. But I can go ahead and use the API to decide what it's going to show. So I can choose the zoom level. I can change the latitude and longitude to refer to Boston instead. I can use the methods that it comes with. So .resize will kind of re-render the map on the resizing of your window because it might need to get new tiles for the map. I can clear any markers that were put on the map. I can add an event listener for Google Map ready, since it actually has to go and make an Ajax call. So I have an event that I can hook onto and do something with. And then I can go ahead and integrate that with my BackmoveView. And again, this is nothing different than normally creating a BackmoveView. This time we're just using a custom element that happens to be on our page. We've probably used HTML imports to pull this in. And then we can go ahead and consume it within our BackmoveView like it was a normal element. And you don't have to just create sort of static elements like this. You can probably start to imagine the different things that you can do with these views with the power of BackmoveView. So maybe I want to go ahead and bind to the change events on a model. Maybe I have a model for places that have latitude and longitude and zoom there. I can again set Google Map as my tag name. And now I could do something when my model changed. I can move the map. I could change the latitude and longitude based on the attributes of my element. And I'm actually just using native DOM set attribute here to change the attribute on my element. And again, there's nothing special here that I have to do. And so you can very easily build out a complete application with a handful of web components and a few BackmoveViews. And I think that's kind of cool. We don't have to worry about the implementation details of something like Google Map. We can just have our model pass in a few attributes, and we're good to go. All right, so that's how to consume web components. How can we build them? How can we? It turns out that when we build web components for Backbone, we're building them for everything. So when I say building web components, there's nothing unique here to Backbone. Any best practice you would use to build web components can be used to build any sort of components. So really basic, we might start with a folder for the name of our component. Hello, world. We might throw in an HTML file, a JavaScript file. I have a file here called bower.json, because I'm using Bower to consume my component and allow others to consume it. If I want to put it in a public registry or maybe an internal enterprise registry, this is how I could consume my component and list any dependencies. I don't have to use Bower. Bower is a very popular choice for web components. In my HTML file, I am going to go ahead and put my template tag, using our HTML templates there. And I'll just pass in my script, and I can go to my script. And this is where I put all the logic for my web component. And this is just dubbed out here. But I'll step through it quickly. So I'm going to create my element based on the prototype from HTML element. And then I have four life cycle callbacks. And this is where I can really manage the life cycle of my element. And again, this is nothing really unique to custom elements. These are the same callbacks that native elements are actually going to use. When the browser is going to implement native elements, they're going to use similar callbacks. Created from when my element is created. Attached from when it's added to the DOM. Attribute changed from when an attribute is changed. Detached when it's removed from the DOM. And that's all. And I can do things at that point. I can attach methods here. I can set attributes and work with them. I can do things when attributes are changed. I can fire events. This is the root logic of my component. And then I can go ahead and register the element on the page, pass in the elements prototype. And I'm good to go. The only step next is consuming the element. I can use an HTML import here to pull it in. And then I can use it on the page. I don't have to do anything else. That script is going to run because it's being referenced in my component. And that's about it. And I can go ahead and start using it with backbone. So how does this all fit together? Because we have these two pieces of our application. We have our backbone libraries, our views, our models, our collections, and then we have our custom elements. And I guess how I picture a lot of applications is you have your general application, which is more or less just a collection of these different components. In our normal application, this is usually all backbone. We might have a whole bunch of backbone views. We have our models and collections. Even if this is just the UI layer, it's a whole bunch of backbone views. And that's cool when we use templates and we build it out. But if we want to start consuming some of these web components, what does that look like? I think it means that we start replacing certain things that we might have done purely with backbone views and native elements with our own custom elements or with others' custom elements. And these can live alongside each other. There's no special conversion API that you need. You can wrap your components in backbone views like we just saw, and there's really nothing more that you need to do. And some of these web components might be just vanilla web components that you build or your organization builds. Some of them might be consumed from other libraries like Polymer or X tags or some other third-party component. And that's OK, and you really don't have to worry about the differences there. So what if we took this to its logical conclusion and we just made everything into a web component? People have certainly thought about this. And I think it's a valid consideration, but I'm not sure it's always the most practical thing to do. I think there's still a lot of value from using backbone, things like our application structure, our interface with our server and with our data. And so GitHub actually recently implemented a custom element in production. It's just a simple time element. And one of their engineers in an interview talking about this said they don't see ever going to custom elements for everything. And I agree with him. I think that it makes more sense to use your native functionality where it's available, and then supplement that, extend that native functionality with custom elements. So how do you make this choice?  What should just be part of my backbone app? Where do I draw the line? I don't know if there's a clear line. I think that you have to, as an engineer, look at it and ask yourself a few questions and decide if it makes sense. See if the benefits that you're getting from Web Components outweigh the benefits that you might have from implementing this feature somewhere else. And I think the key questions to ask in terms of components are really, is it component level? Is this really something that's not necessarily unique to your application, but something that could be reused elsewhere? Does it take the place of something in the DOM? I don't know that it makes sense necessarily to go ahead and take purely functional modules and convert them, for example, to custom elements. Should it be sort of portable? And that's portable between applications, maybe, within your organization or between other organizations? Is it context-independent? Can you drop it into a page and expect it to work and not require it to, say, be in the header or footer to work properly? There are certainly API implications to this, but they're also just CSS-style implications. A fixed-width component isn't really helpful if you need to throw it into a responsive design. So keeping those things in mind, even if your context is very specific, if you're making something into a component, you want to kind of remove that logic. And then can your API be represented with the methods that we have for representing an API in custom elements, attributes, methods, and events? And if these come out all true, my checkbox component here, there we go, custom element, and then we can go ahead and make something into a component. And these are just some kind of food for thought in terms of best practices. There are real no best practices yet for web components because they're so new. I think best practices come as a result of actual use. And so I think over time we're going to start to figure this out. But these are just some of my thoughts brainstorming. Keep them small. Do one thing and do it well. Make them extensible. And this means that other people, just like you might extend the native HTML element to create your template or create your custom element. Wouldn't it be great if someone else could extend your element to create their own? Keep them documented. Because the APIs are kind of unique to the components, I think you need to be very clear about how they work. The logic is kind of lockbox, so you want to be very clear about how this is supposed to work. Make sure they're unit tested. I mean, all of these best practices sort of apply to JavaScript code in general. But I think something like unit tested makes a lot of sense for a web component. The reason that is is because things are really easy to test when they're small and have a well-defined API. And so you really get a lot of this for free. Component sort of force you into a very smart interface for your components. I mean, it's very modular. Something that can be easily tested. And so a supplying unit test allows you to kind of self-document your component and make sure that you're not going to break any APIs. Hopefully, you're using some version of your components. That's also part of that. Make sure they're accessible. This is something that on the web is particularly important. If you go ahead and throw a component into your page and it's not keyboard accessible, for example, you're kind of ruining the full accessibility of your application. So maintaining those normal best practices are even more important when you're going to make something that's going to be distributed. And idempotent is another interesting best practice. And I think if we think about how the DOM works, when we put a DOM element on the page, we always expect it to work the same based on the attributes that we pass in. And idempotent method in programming is something that we can call again and again with the same data and expect it to give us the same result. And I think that's true for our custom elements here. Making sure they don't have any other side effects. Making sure they work as expected. Making sure all the effects of your element are contained in its API. All right, so the big question might be, can I use these? The answer is probably not in production. If you have to support Internet Explorer or iPhones. But that's just today. And I think that's all right. Web components are a very new technology. And the specs are actually still being figured out, which is part of the reason that even Firefox is hesitant on putting them into their stable branch. Chrome has had them since this summer when I started playing around with web components quite a while ago, maybe over a year ago now. The specs were very much in flux. And the methods that encode that was written, if you look at web components reposed from GitHub like a year ago, it's very likely it won't work today in modern browsers. So the methods have changed. Some of the API has changed. It's now in Chrome stable, which I think means that the API is stabilizing. And I think we'll see it soon enough. But if we're a little impatient, we have a polyfill. So the web components JS polyfill was built mostly out of the Polymer project. And Polymer originally used it as their platform JS, kind of based polyfill. It's now been taken on as a unique project itself. So not just powered by or built by the Polymer developers, it's kind of built by other engineers involved with X tags and other web components projects, which means that sort of they agreed upon polyfill at this point. And so that will allow you to use web component features in all browsers with some exceptions. The polyfills aren't perfect. Anything worth polyfilling is hard to polyfill. The shadow DOM is particularly tricky. And encapsulation in CSS just doesn't exist. So when you wanna add that feature, you have to kind of have some hacks to support that. And so it's not gonna be completely perfect. Things are still gonna bleed through in certain edge cases. And there may be some performance hits as well. So that's something to keep in mind, especially if you're using this in a production site. So to conclude, we're building some really cool applications in Backbone. And so thinking about the web in the future, I was thinking back to what really excited me about the web in the last few years. And HTML5 was certainly one of those. If you remember, we got all these kind of cool new elements. We got the video element. We got new input elements. We got new semantic elements since like header and footer and nav. And some of those we used, some of them we didn't. Some of them just didn't match up with what we needed in our applications, especially very rich interactive applications. And so what if the next round of components, the next round of elements on the web, came from the other direction? What if they came from the community that built these out and kind of rallied around them? And then we saw these in the browsers going forward. And I think that's part of the promise of web components. And that's what I'm excited about. So thanks. These are really good resources. And yeah.


Before we get started, today's shout out goes to our friends at BeaverBitcoin. BeaverBitcoin.com slash Trucker Josh is where Canadians can go to stack Bitcoin. It's a non custodial site, so you buy Bitcoin from them and they put it directly into your own personal wallet. Go check them out, the link is down below in the description below the video. Let's get back to it. So good morning everybody. We're in Canora, Ontario, Canada. Put that up. Up here where it belongs. Put everything where it belongs. Put that up there so it doesn't fall on me. I'm already cleared to cross the border. I'm going to be crossing from Fort Francis, Ontario into International Falls, Minnesota. I want to brainer Minnesota with this load. As soon as I get myself D-geared.  I'll be ready to go. I should get unloaded later this afternoon. And it looks like I've got to reload in Wisconsin. Appleton, Wisconsin. I've got to be there tomorrow. 8am. So we don't have too much time to waste. Let's get going. Proceed to the highlighted route. It sounds like there's something that happened at the shipper. I mean, but that's what happened at the Quebec shipper too, right? A few weeks ago. Something similar must have happened there. I don't know, maybe it was just an excuse to cancel the load. But at least I hadn't made my way that direction yet, right? Whereas in Quebec, I had gotten within five minutes of the place. And I did get paid for the truck not used. At least I got paid for my time that day. Today it didn't really affect my day at all because I hadn't even started going there. I haven't even gotten unloaded on this load yet. Buds on these trees. But it's summertime and everything's green. The sun's shining. The grass and the ditches is green. Tarping, un-tarping, tarping, un-tarping, tarping, un-tarping. And tarping again and un-tarping again. I'm kind of glad we're not going to Wisconsin. Whoa, whoa, whoa, buddy, buddy, buddy, buddy. Okay. You didn't see me coming, but you could have hit the gas a little harder there when you did see me. Still doing under the... Okay, okay. A winter storm advisory for the day when I'm filming this. Supposed to be over, like just the tail end of it by the time I got there and got loaded tomorrow. But it would still be very messy. Probably a lot of snow all over the place. Probably slippery. I'd rather avoid that. I'm done with winter. I mean, we never had another winter again. I'd be totally fine with that. Won't hear me complaining about it. I can live with those snowmobiles, snowboarding and skiing. Well, the thing with snowboarding and skiing, I don't do that anyway. And I don't live near the mountains. But even if I did, there would still be snow up in the mountains, you'd think. You can go have your fun up there. We do need a lot of snow for Christmas day and Christmas Eve. So if we could just get, like, four feet of snow on, like, Christmas week. Just before Christmas so that... Oh, here's a cop here. Look at that. Sneaky, sneaky. Not gonna catch me. If we could get it so that it's nice and clear and the roads are all cleared for a Christmas Eve, Christmas day. That'll be perfect. And then right after Boxing Day, right after Christmas, it can all melt. If we could talk to our guys up in Alaska there with their weather-controlled devices. If we could make that happen, that'd be great. I haven't been here in what, like, two weeks now? I missed you. You miss me? Come on, just a little bit. A little bit. Come on. You miss me a little bit, right? What I should do after I'm empty. But I believe that sound you heard was them. So once I stop, I'll be able to read that. Maybe they gave me... Just gave me directions. I might be going back to Canora. First things first, we gotta get unloaded. Until we get this stuff off the trailer. It's kind of in the way. It's weighing me down. I know my back all day. We got our trailer unloaded. I got my tanks full of fuel. Got my GPS set back to Canora. So it's been sort of up in the air what my reload will be. I'm going back to Canora for another one. That's the final word. So we're headed back up there. We should be there tonight. Be ready for it. First thing in the morning. Same thing as today. So we fueled up at Casey's here in Brainerd. It's actually more expensive here than back in Manitoba again. That fuel tax holiday back home has been very nice. You know, they're drawing our business back home. But that fuel tax holiday is only there for the first quarter. Or no, for one more quarter. So for three more months. Maybe they'll extend it. But eventually they're going to have to bring their revenues back up. Right? And put the gas tax back on there. For now, it is nice. So when possible, we'll be fueling back home in Manitoba until that fuel tax goes back on. And then we will be fueling elsewhere again. Now, if only we could get our Manitoba Premier to join all the other premiers across the country and oppose the federal carbon tax. We could get even more knocked off the fuel prices. Which means even more knocked off of all the goods that you buy that are transported by truck. Because then we don't have to pay extra costs on our fuel. That's pretty crazy. The majority of premiers, like 70% of provinces are against the federal carbon tax. Yet they still keep going forward with it. Oh, there's a dog there. Oh, someone's going to go get him. Okay, good. It's a big thing across the country right now. There's nationwide protests against it again because it went up by another 23%. It's just crippling business. And it pushes all the business out of the country, right? You've heard me talk about it. All my business goes to the US because they don't have a carbon tax. So all that money that should be going into our economy up north just goes into the US economy. Which is good because they're good friends of ours. So it's not like it's terrible, but it wouldn't be nice if we'd spend money back home. Businesses back home would like that better, I'm sure, but no, it just drives business out of the country. Including mine. Give her, bud, give her. Not you. Not you. It's not Podette, Minnesota. Into Rainy River, Ontario. There's no toll there.  So hopefully it goes smooth and quick. We'll see what happens. If I got to pick up this load, I'm in Canora, Ontario. I got to take this load down to Brainerd again. Another run down there.  Probably won't make it there to unload this afternoon now. That's okay. I'll unload first thing tomorrow morning. We'll take it from there. Hope you guys are having a good one. I'm going to continue this vlog on a little bit here as I wait to get loaded the following day here. It's hard to tell if my glasses are scratched or just dirty. They're really dirty right now. I don't touch them throughout the day. It's just amazing how dirty glasses can get. They're also scuffed pretty bad. Mostly just dirt, right? This month, oh, in two weeks actually. Less than two weeks. A week and a half. I have an eye appointment. Getting a new pair of glasses. These ones got scuffed. Actually here when I was tarping a load, one of the tarp straps snapped or slipped. And it went around and came and bonked me right in the glasses. That's why we have to wear glasses at places like this. The good thing I hit the glasses is not my eyeball, but it's scuffed my glasses now. So I think I'm going to keep these as work glasses for places like this. So that if they get scuffed again, no big deal. But I can still see. And my new glasses, they're going to be kept in a very special safe case and only cleaned with like these special wipes that are designed for lenses. And I have to be very, very careful.  I've never had glasses before this. And everybody warned me to be very, very careful not to scratch them. So I thought I was being careful. Turns out I wasn't being careful enough. These six are scratched like crazy. And it's all scratches for me cleaning them. Using the wrong things, using a microfiber towel. I thought that that would be good at first. Oh, it'll be fine. It's just off microfiber towel.   It's terrible. So my next pair of glasses, I'll be a little bit more equipped in my head of how to take care of them from experience. That's the way I have to learn everything, unfortunately. It seems that way. Going through life, I get tons of advice. My parents growing up who shared a lot of wisdom with me. A lot of great pointers of how to do things correctly, how not to do things. Most things I still have to learn myself. I'm just that kind of guy. Until it happens to me, it just doesn't seem to stick. So thanks for hanging out with me here, everybody. I'm next in line to get loaded now. We're going to start tomorrow's video right here. I have to wrap this up. So it was a quick trip there and back. You can barely make it on your hours of service if you start here and then come back. But if you start there and go back, you can't make it there and back because hours of service are different in the US, right? So it's about six hours down, six hours back. So 12 hours of driving to do this route. But if you start in the US, come up to Canada and then run back down, you can only run 11 hours per day in US hours of service. But in Canadian hours of service, you can run 13. And as soon as you cross over to the border from the US into Canada, Canadian hours of service takes over. So on US hours of service, you can't make it. But on Canadian hours of service, if you end off in Canada, you can just barely make it. Does that make sense? I'll take a whole other video just to explain hours of service. I should do that sometime. I've been saying that I'd do that for years now. I need to break it down for everybody just so that you guys understand hours of service and truckers and when we're allowed to drive, when we have to stop. Things like that. I've got to wake myself up now though. It's time to get to work. I'll see you tomorrow. Don't forget to subscribe, hit the bell. Leave me a random comment down below either related to the video or completely unrelated to the video. Surprise me. I look forward to hearing from you down below. I'll see you tomorrow.


I can see clearly now, the rain has gone Bum bum bum build up I can see all obstacles in my way In my way, in my way, in my, in my, in my, in my, in my way Drinking rum out of a Mickey Mouse glass Just kidding On Instagram Instagram And Twitter Twitter And other platforms Other platforms that we stand on and look down What did you sound like? Um, thank you for supporting us on Patreon Yeah, thanks for the support And following us on our official Twitter account Be an athletic supporter Wait Gross But today we're reacting to, I don't know if you've heard of it It's been requested, but he's a talk show host Coffee with Karam Yes, I hopefully He was in that Ali Aba video The guy who was asking the question Yeah, who had the joke about the hole Yes Yeah He's an actual host Yeah He's an actual host and he's actually The show that it happened on He's an actual host Yes But this one Sir Lampeau Is called Rapid Fire with Deepika and Priyanka Ooh So you're gonna see I'm ready We're gonna get both of them together And I think that they just ask a bunch of questions Sometimes inappropriate So Might be explicit Sultry, sexy, exotic My first guest tonight Was two parts of Equal Ablon Actress and singer Please welcome the movie star Who's not only known in her city But also globally Priyanka Chopra Hi, my chat Priyanka Chopra in the house Welcome back to season 4 Coffee with Taran Thank you very much Thank you for being here yet again Yet again My fourth season straight Can I ask you a question That may not offend you?  Because I saw you in the song in Ramleela That Ramchak Yeah Moving sex machine song I thought it was like completely sex In the wild What do you know where the sex move comes from? Um It's just the way it is I've never known anything otherwise Other than being sexy Other than being sexy Yeah It was not like a dry and dry It's how It's just how you were born The Ramleela song was a dinosaur's conception Yeah What I did with it was I know the one The dinosaur that you actually close You don't open I don't open You shut it That's what I loved about it I want to know That you've been walking two paths like I said You've been doing actress and singer And going between like LA and Bombay And it's all been fun It's all been fabulous It's difficult It's um You know I've been traveling ridiculously You know that's fine But You know Where in Bombay or in India I'm you know an established actor To be a complete ranked newcomer In another field In another country altogether It was is extremely challenging And it's a completely different culture And they use her for better watching I know That's difficult Well They watch I know Performance of last year But our next guest tonight Is definitely doubted to be the performance of this year Shall we bring her on? Absolutely Alright My next guest tonight He's got some gene doesn't he? From a non-performer To being an absolutely stunning performer in Celluloid She truly has come a long way Ravishing, raging at the box office And touted as being one of the top actresses of her times Please welcome Divika Padukko What? Divika Padukko Divika Padukko How? You just said it really fast I was like The film You felt bad? I called you a non-performer In your earlier work You agreed with that analysis Or you think Parak Khan will kill us both I don't think I can judge my own performance But No, I didn't feel bad You didn't feel bad Now you're over that whole What happened with last time And what happened on that couch Are you over it? I'm over it It all went It was all good Everything was sorted out Did you take a while for you to sort it all out after that?  I was talking about With Chintu Ji, Neetu Ji With Ranbir I don't think there was ever an issue there I think people made it An even bigger issue Yeah For me personally I don't think there was an issue Definitely not between Ranbir and me for sure Right And even if there was Another reached me Right I think which is why We can even do a film like Yejavani Haidivani And still have that kind of Chemesis Understanding and chemistry Which I think if there was even A slight bit of any kind of I don't think that experience would have I don't think that film would have Turned out like that The way it was Yeah So good So all is good in the hood You've been favorite part of the show It's the rap I need to be I was just going for the film Okay PPC I think because you've been on the show More times Yeah, yeah, yeah So are you ready? Good luck Okay We are good A life-size poster of themselves Reacting one word to the following people Paranithi Chopra Tisha Okay I'm not ready to pick that Oh my God You can I just completely forgot that I had to do it Alright Who looks best shirtless? Ranbir, John, Samman or Rithik? Hold on what? Who looks best shirtless? Uh huh And who is it? Ranbir Ranbir Something I think it was Ranbir, Ranbir Ranbir, Ranbir And Salomon He said Salomon Khan, right? Did he? I don't know And Rithik Oh, Rithik And Rithik I mean it had to be Rithik, right? Shirtless I don't know Look at her face in the freeze frame right there I know who she's going for Well, I mean they all look really good shirtless I think we've seen everybody Not Ranbir, we haven't seen Ranbir Shirtless You're right It either be Ranbir or Rithik Yeah, she's going Oh, she's going Run Vir or Ranbir I mean he's a good looking guy Yeah But Let's see What? Yes, only one person will Have you kissed someone and regretted it? No Gone skinny dipping with your boyfriend? Never I'm currently the number one actress in Bollywood True or false?  Is that why you kind of kept it a little I'll talk about your performance Let's talk about the stir in your life You know, that you created The stir in my life Well, it's all sorted It's all good It created a stir in your life? Of course it did What kind? There was a stir Oh my God It really caused a stir Fine, like you were talking about I'll tell you what I think it's just Sometimes when things are set in humor We tend to kind of over-analyze, over-react We sometimes lack a sense of humor Okay All right Well I was hoping for more rapid fire Yeah, I was hoping for There was like three rapid fire questions There was kind of when I watched the The content I was like I thought it was going to be like Rapid fire, rapid fire Yeah, Ellen does Ellen does Yeah, with the hold up the yes or the no And it's embarrassing And it's I mean they're both adorable And they're both awesome I love them But yeah, if there's other ones Because I know he's really popular This whole show is really, really popular I can see the comments already That wasn't his best segment, you idiots Why'd you choose that segment, morons? And so he's ended We don't know


Hello kids, welcome to macroeconomics 101. My name is Professor Che and today we're going to be talking about Supply and demand so make sure you guys have your notes ready and let's just jump right into it All right. So first off when you come to supply and demand There's gonna be tons of photographs to consider you're gonna have to do your x and your y coordinates and make sure you label them And at the same time you're gonna need, you know, your this line them slope equals y and x for c That's a lot of information, but I hope you guys got your notes Well, remember there's gonna be a quiz tomorrow and class dismissed AI, can you believe that professor?  Talks too fast.  Anyway, you guys know what's happening today We're talking about how to take notes in college now. This is a super highly requested video Everyone wants to seem to know how I'm taking notes and to be honest I am not the best note taker, but I will say I wish I was a better note taker And that's something I'm going to be improving and working on throughout the year But it is such an important skill for any college student even high school students to take efficient and practical notes So that when you go back to your room to study that you have a clear outline of what was talked about in the lecture So you can best prepare yourself for any kind of tests and quizzes or essays that's going to come up Now there are a couple different ways people like to take notes in college. There's a traditional notebook and pencil There's laptop. There's tablets. There's audio recordings. There's a bunch of different stuff Which I will kind of dive into today now as you guys probably know I am a very tech savvy person meaning I love to have my ipad pro in just about all my classes And take notes that way using my apple pencil and my apple keyboard I just think it's a way more efficient system and even though people say that Oh, you're not going to retain as much information since i'm still writing it using the apple pencil It just saves me a lot of time and i'm able to access it from anywhere I'll dive into a little bit more of that later But if your preference is handwritten notes, then let me give you my tips for that first off is have a good notebook I can't emphasize the importance of having a strong durable plenty of pages college with or even wide ruled notebook Personally when I used to write handwritten notes what I would do is buy the three subject notebook Or even just like one subject for a hundred pages per class that I had The downside to that is you're carrying around three or four different notebooks Rather than one cohesive place where all your notes are and it just it can just get a little bit messy if you're not organized However, I will say that there are a few benefits of taking handwritten notes First off if you have clean handwriting then you can doodle and you can make it as clean and as pretty as you like But if you're someone like me who doesn't have the best handwriting Doesn't have the time or the energy to take the notes with all the different colored pens and all that crap I will say though that you need to figure out some kind of system when it comes to taking handwritten notes There are way smarter people than me that have come up with actual ways to take notes There's like the team method and just a bunch of different stuff if you do your research You'll find plenty of them online But make sure you have an organized system regardless of whatever it is that you're doing So something for lecture notes something for seminar notes something for your vocab Another thing that I don't like about taking handwritten notes is that it's hard to move stuff around Meaning that you can't just copy and paste like you can on a keyboard You have to physically either like cut it up and paste it on a different page If you want to move it to a different section and it just gets a lot of hassle that I don't like to deal with Which is why I'm going to move on to laptop and tablet note taking This has obviously been the way recently everything's gone digital everything's on your laptop The downside to this is that you know students get distracted. Obviously, I'm a victim of that I will be texting or surfing the web while I should be paying attention in lecture However, I think that the speed and the convenience of typing on your laptop is Unparalleled meaning that my hands can type way faster than I can write Listening to what a professor is saying. Although I don't recommend typing word for word what that professor is saying What I like to do is I pay attention to the professor hear what he's saying and then Synthesize it in my own words and write it down in my own notebook That way I have my own definition of what that professor is saying rather than just paying attention to what he's saying So I can type it up fast enough and then not pay attention to the actual Lesson that he's teaching although it's hard at first figuring out what's important and what's not It's going to save you a bunch of time after you start developing these skills Because then you just prioritize what you need to know and you can use that later on when you study Another great thing about taking notes digitally is that you can add on to them after class So you know how when you're taking hammering notes and you fill up a page and you have to go to a different page Well with one note or with notability. Those are the two apps that I use You can expand your pages as long as I need to be you can insert graphs You can insert photos and it's just it makes it a lot more convenient going off the software that I use There are a couple different ones using them for different purposes in different classes The first off is one note. This is a microsoft app. Most likely it will be included with your university's email And I personally have used this for a bunch of my classes You can create different notebooks depending on what course you're in So if you want to do by sections or chapters, it's up to you And then even within that you can customize it even more The app is also integrated with the one note app on the ipad So when I need to do handwritten notes, I will Write them on there and then I can see them on my computer as I'm writing and then use that for another purpose Notability is a very popular software as well I think it looks a little bit more aesthetic than one note. It's a little bit easier to use However that I personally just use when it comes to handwritten stuff Not the typing stuff because I don't think it's as fast and as intuitive as one note But when you need to write stuff or draw stuff or graphs or any kind of representation where you're going to be doing physical drawings I recommend notability now my final software that has been a huge game changer for me lately Is called pdf element, which is the sponsor of today's video when it comes to college There are going to be dozens and dozens of pdfs that you're going to get That's the most convenient form for professors to you know pass out lectures or notes or homework And it's just a big hassle to have to go to the library print it out and then mark it up and then Scan that back and then send it back to your laptop when in reality using a software like pdf element is going to make that workflow Way easier So at Princeton we have a lot of classes that require p sets which are called problem sets and their weekly Assignments are uploaded to a website where you have to download or print it out and then fill it out on a separate sheet Now what I personally do is I use pdf element to import that and then I can either Mock it up circle underline highlight anything that I need to do because the versatility of the software is Unlike anything I've ever seen and when I found out that it could actually do the some of the features that I was trying out I was like wow, this is pretty incredible If you aren't very tech savvy and don't know a lot about pdfs They're really hard to edit meaning that you have to import it into a separate program And a lot of programs don't have the features that this one does the fact that you can highlight text and Actually edit it in the same font in the same style insert pictures edit links That's really hard to do in a pdf format and this software just makes it so seamless Another great feature is you can combine and convert pds with this software meaning that if you need to take maybe page two And page four of a big presentation and just combine it into one single pdf It can easily do that within that software and it's if you haven't done it before trust me It's a huge hassle having to upload it online and then have to download it and compress it and then Download it and rename it's like trust me. This software is going to save your life if you're a college student Now for a limited time pdf element express is available for 50% off I've linked it down below make sure you guys go check them out If you're a college student I can't recommend a software like this enough because it's just going to save you so much time And that's the biggest thing when it comes to note-taking college Is that you want to be the most efficient and productive with the amount of time that you have because when you're in lecture You want to retain as much information as possible Still take good notes and use them later on when you're studying for anything else Now my final tip when it comes to note-taking is the option of audio recording now This is kind of controversial not super controversial But like something you should look into with your university because some professors may not allow you to record in their lectures But it is a good option if you are a slow writer or slow listener The way that you can do it is just set it up on any kind of voice recording on your phone On your voice memos or something and then just let it record throughout the entire lecture And that way you can go back to your dorm room and listen if you missed out on a key part Or just want to listen to really listen to the whole lecture the downside and the reason that I don't personally do that is It's just too time consuming. I already sat through an hour lecture There's no way I'm gonna have time for me to go back to my dorm room and listen to it for another hour Because I was dumb or fell asleep and didn't pay attention the first time Other great tips when it comes to taking notes is create study guides as you go Now this has been a huge vital tip for me and when I started doing it It just increased my workflow when it came to final season or midterm So what I mean by that is every few weeks or so Compile all the notes that you've taken from the past few lectures and start putting them into one google doc Make sure you're formatting it as you go have some sort of way to list out your vocab definitions The key terms of what was talked about in that chapter If you add on to this little by little every few weeks or so once you get to finals or midterm season It's going to make your life a breeze because you don't have to waste the time to go through and compile an Actual study guide because you've already done it throughout the semester trust me on this one You can thank me later, but you guys know I got your back now obviously note taking is a very important skill It's a skill that needs to be developed and like I said, I'm still working on it And I hope to have better tips that I can share with you guys in the future This is just a crash course on note taking obviously there are tons of videos that go more into depth But this is just from what I personally do and from what my friends have done And you know when it comes to note taking you got to do what's best for you If you're a hand writer then go with handwritten notes If you like typing then go with that at the end of the day Whatever you need to do to be best prepared is going to be the best option for you That about wraps up for this video I hope you guys enjoyed this back to school series once again I keep emphasizing September 1st this book is going live I'll make a whole video talking about all its features later But I just went through the final edit today and it basically takes you all the way from freshman year to senior year to writing the Applications letters recommendation financial aid scholarships, you know all the way up into your actual freshman year since I've had that experience I wanted to share that with you guys pre-move and acclimating mental health physical health Finding extracurricular is balancing your academics picking a major I've outlined it every single step of the way for you guys So September 1st market calendars that's it for this video and I'll see you guys next time


What's going on, everyone? Sam here with late in sports cards. We've been 20, 23, Bowman Chrome Baseball hobby, 12 bucks, full case break. Number 20, pick your team star, read off the list of our names and our teams. Alvin S, Yanks, Padres, Anton H for the Guardians, Brad R, Diamondbacks, Brian M, Red Sox, Charles A, Rangers, Dustin M, Royals, Glenn W, Rockies, Twins, Guanji W, White Sox, Jeffrey H, Astros, Giants, Mariners, Jeremy S for the Cardinals, Jim B, Nationals, John C, Angels, John B, Metz, Josh H, Marlins, Ken S, Ray's, Kevin F, Pirates, Kyle I, Cubs, Kyle H, Tigers, Mark Anthony H, Reds, Rick E, Brewers, Roger S, Athletics, Xiaobo W, Blue J, Sean P, Phillies, Terry F, Braves, Tim J, Dodgers Orioles. Let's get into it, everybody. Here we go. Lisa, picking up a random player spot. Thank you, Lisa. Lisa's always in those 10 cases. Appreciate you, Lisa. Yeah, I don't, I can't sit here and say I mean Kyle are talking about splitting a spot for it, so we'll see if we end up doing that. Probably will happen. We got so dusted on 23 Bowman, the 10-kacer we did, man. Oh, man, you got smoked on it. I'd say Shimmer of Anderson De Los Santos for the Orioles, De Niro Miller. De Niro, aka De Niro Miller. Guys, money. Base Auto is Andy Perez. Nice one, Rockies. Gratz, Colorado. One of the last teams taken. Still available in the next one as well is the Colorado Rockies. John, totally inside. Yep. Drew Green, James Outman. This card's four, Outman. Nice one there to 99. You want to come in here, throwing your sticks around. Oh, buddy, you got another thing coming, pal. There's Raffi Devers. All right. Another thing coming, Jay. There's Diego Cartaya, Camila Diaz, Derniche Valdez. There's Noel V. Marte and base. That's part of my studying when a new product comes out. When I study the checklist is, oh, what shtick am I going to make? We started just firing off on Bowman, obviously. That is a Gold Kazuma Okamoto. I believe he's going to be a random to all. 12-50. Nice one there. I'll double check that, but I believe that will be a random. Gold to 50. Not bad, dude. Not bad at all. Base Auto. Jesus Bougarin. Nice one there. Rockies. Rockies another high-volume team in Bowman, Caron Man. High-volume team in this product. De Los Santos, Miguel Blase. That is a Francisco Alvarez. It came to the league. Dominguez, Luis Jordan. Invicto, Willy Fannas, Delgado, and Axel Sanchez. That is a Shea Langlears, Refractor Rookie to 499 for Oakland. Jesus Cabba. Zach Veen and William Bergoya. William Bergoya. All right, again, just eight to go in the next one. Everybody here is your link to that again, I believe, right? Nope, that is not your link to it. Bergoria the Burglar. Oh, man, that's... Rockies gone in 21 and 22. Josh, thank you, buddy. Down to seven. We are down to seven. Seven to go in this PYT, number 21. Find it. It's nowhere to be found here. Two, three, four, five, six, seven. Two go. Seven to go. Seven to go. Seven to go. There you go. Rich over on Fanatics Live as well. They pulled a Gold Ethan Salas non-auto for the Padre spot. So congrats to whoever hit that, not sure who it was, but that is a nice card. I can't really complain on Ethan Salas Gold. I'll be real with you there. You know what I'm saying? That is a shimmer, Jackson Holiday. Nice one there. Happy holidays, everybody. Bass and bass. Refractor, Luke Berryhill. Nice one there. Houston to 499. Glenn, Metz and Twins gone. Glenn W, we're down to five. Glenn, thank you, my friend. Appreciate you as always. Glenn's always picking up some awesome teams. Congrats, man. That is a Vladimir Restitutio to 199 on the wave. We are down to five to go in number 21 now. That is a Aaron Joe, Jai Connick, Luciano, Jonathan Mejia. Prospects progress, or yes, process, whatever. Elijah Green, you get the gist. That insert, that insert. The prospect insert that has like three guys. NASCAR insert. Yes. Anderson De Los Santos. Too much like they're stumbling over too many letters in that one. Prospect process. Yes, too many letters. Anthony Rizzo, Refractor to 499. Bass and bass. That is a Abner Uribe for the Brew crew to 499 on the Refractor first. Thought, congrats on that Milwaukee. Yo, Andrew Vargas first and Ariel Castro down to just five to go now, everybody. Here's your link again, five to go. Get that. Tweeted, five to go. Two go. Okay, keep it moving. Spencer Jones that came to the league for the Yankees. Invicta Yankeel for the Rockies, Yankeel Fernandez. We've got a gold coming up. That's Freddie Freeman. Nice one there for the Doiers. Grats. LA. LA Dodgers with a Freddie Freeman gold to 50 and Brady House. Jeez, dude. We need to work some words, buddy. Just wait, dude. Bryce Harper, Purple, Brian Acunha. Baby Acunha to 250. Bass and bass. That's a bass auto of Dario Barrero. Nice one there, White Sox. Again, White Sox on sale on the next break as well. Congrats, Chicago. Valdes, Osavito. Here's Corbin Carroll came to the league. Jet the Met and James Wood. Cade Horton, Invicta. Refractor, Spencer Steer, Rookie to 499 for the Reds. You think Cade Horton here at the home? Oh, we had, we're way past that. We had that in Bowman Draft, pal. That was in Bowman Draft, pal. You are about eight months too late. First things first. On the realist. I came. That's going to be Luis Guanipa. First shimmer fell in Celestine. Only came back. True, true. Got to give me a little bit of slack. Purple, Chris Newell.  It's Chris Newell. Nice one there. Congrats on that Dodgers. True purple to 250. Bass and Walcott first. Teal of Vapor Wave to 125. Daverson Gutierrez. De Nero Miller. Got his money. That is a Bryce Terrain Fuchsia to 299. Rookie for the Brewers. Nice one there. Congrats on the walkie. Tank Terrain. Tank Terrain. Tank or Tank Terrain? Tamar Johnson. Jayce Young. Young, Wild and Free. That is a Mason Wynn and Jungsauk Shin. Okay, on to the next. That is a Atomic Jefferson Quero to 150. The Brewers. My AF first. A Refractor. Spence Kaufman. Nice one there. Going to the Padres to 499. Spence Kaufman. Chris W with a couple of random spots. Thank you, buddy. Yeah, just five to go on the next one, everybody. That is all we've got left in number 22. Riley Green, or 21. 21. Ivan Melendez. Hispanic to Titanic. Such a cool nickname. Rookie Sasaki. That is going to be a random two all at the end, I believe. Right to 499. Rookie. Nice one there. He's a stud. So we'll do Nick Gonzalez. Basically, I'll put all the teams in. Top team's going to get the gold. Second team will get the Refractor. So everybody has a fair chance at both. Shema, Kevin Perrata. There's a base auto. Daniel Guillarte. Going to the Brewers. Nice one, Milwaukee. Congrats, Brew Crew. Spencer Jones, Jackson Merrill. Refractor, Welbin, Francisca. To 499 for the Guardians. First, Gunnar Henderson. And base. Adley Rookie on top. Elijah Green. Prospect process. There we go. Prospect process. Prospect process. See, now it's in my head and I'm just going to start messing up every time now because I'm going to be thinking about it too much instead of just saying it. Prospect process. A 20, my favorite. I'd probably have to be Maella. Probably Maella. I'm a Yanks fan, so Maella is like the big Yanks guy. And this one, Shema is Ariel Castro to the Twins. Edger and Rodriguez. I'd probably have to go with that. Base auto is Peyton Williams. Congrats, Blue Jays. One of the more inexpensive teams there also, I believe, available in the next one. Yeah, in the next break, we have the White Sox, Tigers, Royals, Reyes, and Blue Jays all available. That is it. That is it in our next break, everybody. Refractor, Nolan Aronado to 4.99. Wilbur and Francisca. That's all folks. That's all folks. Francisco Alvarez, Iconic Riffy. That is Los Romantes Prospect Process. There you go. There it is. We got it. We got it. Cookin' now. Noel V Marta. Jackson Merrill. We got Roy, we cookin'. Oh yeah, absolutely. We got Green. Green is Kazumo Akamoto. That is to 99. Another random. It's not the third team. We'll get this one. Everybody's going to have a fair shot at all of them. That's how I do those multi-card randoms here. Jesus Bastidas for the Yanks to 4.99. Refractor, First Prospect Auto. Congrats on that, Yanks. Holiday and Lantigua. That is a Francisco Alvarez, came to the league. Henry Chavilly. Rice Harper, Iconic as a national. As a wave, Asturi Ruiz to 100. The Maya first, Andrew Jones. Chrisian Vecchero. There's the box again, guys. Five to go in the next one. Five teams remain. Five to go. That is a PYT. All PYTs this morning outside of our division, divisional break, which is sold out. We also have plates and patches, football at the end of the day, and it's going to be four to go on that. Got to get that sold out, everybody. That is a Fuchsia Shimmer, Kevin Iru to 199. Joey Ortiz, going to the Orioles to 4.99. Refractor, Guerrero and Duna. That is a Wave, Logan O'Hoppe to 100 for the Angels. Thank you. Mike Trout Iconic. Trout's 0-9, Bulman's picture there. Oh, yeah. Adley Rushman Rookie. Brooks Lee, Prospect Progress. Process, I don't know. Same thing. Same idea. Mason Nguyen and Vace. Orange is Randy Rosarena. Nice one there too, 25 for the Raze. Randy Randy. That is a base auto of D'Angelo Sarmiento for the Mets. Congrats, Mets. That's one there in New York. Mets. That is a Anthony Volpe at Camdolique, Brandon Maia, Andrew Jones. Good Yankees back there. Casey Schmidt, Bowman Ascensions for the Giants on the Rookie. I like the Ascensions. They look good this year. I didn't love them last year. Braylor Guerrero for the Raze to 499 on the Refractor first. Nice. Mike Trout I forgot what Bowman is that this comes from. Adley Rushman Ascensions. It looks like something you'd see in Bowman's Bass too. It looks like a Bowman's Ascension. Oh, old Bowman. Why don't you just switch trashes if you see what I'm saying? That's cool. That is a Victor Isturiz to 199. Really badly damaged James Wood behind it. Sorry about that. National. Today's just a base guard, luckily. Base auto, Joey Estes, or Estes. Going to the As. Nice one there. Congrats, Oakland. Here we Estes. Whoa, God, dude. He's hitting the camera here. Jeez. Okay, where did 21 go? There it is. 21. Again, just five remain. Five to go. Got it sold out, guys. Breaks next. Keep moving. Another Orange. Drew Jones on the Bowman Ascensions. Congrats, Arizona. Three at 25. Nice one there. Let's see if you could probably mag that one because that's like a shorter print. Oh, we got an Arizona Fall League. That is Andy Pahes to 25 on the Orange as well. Two-color Patch. Nice one. Dodgers. One of their top guys. Envys. Manacunha. Falling in Celestyn. Smashing Walcott. That is a Refractor of Nolan Aronado to 499. Genaro, aka, Denaro Miller. Got a Yellow. Diego Mosquera to 75. Congrats to the Metz. I think there's a mark on that. I'm going to have Jay wipe down the top. You could see it up above the Bowman logo. If that does not come off, Empty Box and Rapper, if it does, then we're good. Congrats on that, though. Metz, Riley Greene, it came to League Rookie. An iconic rookie. Is that on there? Yeah. All right, we'll send that Empty Box and Rapper. Jordan Lawler to 199. Just got called up. Get it after this last pack here. Massavito. All right. Oriol was spot today. Thank you, Oriol. In our spectra and mosaic mixup with a good old forest. Drew Gilbert. Shimmy. Rainer Arias. Nice one there for the Giants. One of their, probably their top chase. Congrats on that, uh, San Fran. When you also Alex Ramirez. Pride, assume so. There's Yasser Mercedes to 125. Because he looks exactly the same. They look really similar. Riley Greene, iconic rookie. Jackson Churrio. Jose Salas. Vladimir Restotillo. Nice one there for the Rockies to 250 on the Color Match. Congrats, Colorado. We got a green Ludwig Espinosa. Going to the Cubs to 99. Congrats, Chicago. Nice one there that congrats, Cubbies. Ludwig Espinosa. Holiday at Cam to League. Mason Auer. Yondri Vargas. Ariel Castro. Refractor of Casey Schmidt to 499 for the Giants. Lazaro Montez. Again, just five to go in the next one, everybody. Let's get it sold out. Five teams remain. That is it. That is all. Five teams remain. That is a base auto. Ben Metzinger. Nice one for the, uh, brew crew. Congrats, Milwaukee. Roger Garas and base. Juan Benjamin. Shimmer. Missing a card in that pack. Might be an extra somewhere. Yellow Alfredo Duno. First for the Reds to 75. That's Sinti. Jadam and base. Beatty Icon. Lee's Jordan Cannard del Gallo. That is a Jackson Merrill. Prospects Progress or Process. Got a Jefferson Quero and base. There's a Andy Acevedo. Going to the Nationals to 125 on the Aqua. Base auto. Brett Wisely. Nice one there for the Rays. Congrats Rays. There's some dings on that. I'm going to send an empty box and wrapper and splotches after this box here. Yoshida Cam to League rookie. Edwin Solano and Raymond Mola. Henry Bolt. This is my guy. I really like him. Henry Bolt for the Ace. Who's, uh, was he a Bowman draft? I believe he was. Gabriel Gonzalez. Refractor. Chew 499. I'm with the others. Nathan Salas first and Hans Montero. Let's go with the Rays. Yeah. On to the next. Here we go. Again, just five remain on this next. PYT everybody. Still some good teams available. Definitely worth taking a look at. Marcello Meyer. Refractor. Chew 499. Base is Wilfredo Antuniez. Nice one for the Guardians. Congrats Cleveland. Lazaro Montes and Junior Caminero. Yoshida. It came to League rookie. Jacob Reimer. Atomic Raindon Cone to 100. No, 150 on the Invicta for the Dodgers. The last year's Bowman Chrome guy. Pulled his super first auto. That is a Welben Franziska to 199 on the Fuchsia Vapour Wave, I should say. Nice one there. Congrats, Cleveland. Johan Rojas and Yossir Mercedes. We need a super, Jeff. We need a super. We need a super Luster.  Finally, Junsock Shim. Nice one there to 99 on the Green Shimmer. A lot of people like that kid for the Pirates. That is a Brian Rencone. Nice one there to the Phillies. Congrats, Philadelphia. Brian Rencone. Luciano and base. What's up, Timmy? Blue is Brian Acunha to 150. What's happening, Timmy? Are you really? What's the last one you need to lose this? Do you have the Gold Vinyl? Let's say that would be the hardest one to get, so hope so. Roger Garias. Oh, the 101 Black Dot.  It's the Don Ross, got you. That's pretty solid, though. It's pretty awesome. Hell yeah, Lucius. You got it. All right, again, we've got just five to go, everybody, on the next one. Five to go. Breaks next. Also, you've got Rich over on Fanatics Live. Ripping more Bowman Chrome. If you have a team that you don't see with me, you could always go grab it with him. You also have Forest. Tonight, Bowman Chrome, Basketball, and Football can be fun. Gonna be fun, for sure. A lot of Bowman. Oh, that's awesome. One of the best days of the year, always. Axial applause to 250, because you never know who's going to be the next star, dude. Base Auto is Luis Guanipa. Going to the Braves, congrats. Atlanta. Jesus Cabba. Gavin Cross. That is a Refractor. Yoshida. That is going to be the variation. Congrats to the Red Sox. Nice one there. Masatake Yoshida. Goi, Luis Angelicunia. Bobby White Iconic. Royal Carter Young. That is a Brady House. Prospect process. Yeah, Yoshi signing the autograph. That is a cool picture they used. It's like Bobby White in Top Trome Update. Him and Seya, they used their debuts or them signing autographs, which is kind of cool. That is a Minidiamonds to 299, William Burgoy. Ethan Salas first. I was going to sign Ethan Salas Auto in this pack right here. Ethan Salas Super. That is Base Auto of Dylan.  Nice one there. Congrats, Milwaukee. I had that one since last moment. There's Yoshida. I knew about him before I knew. I mean, not new about, but how it up tone. How you doing, buddy? Sterling Thompson. Good to see you, man. Yeah. Happy Friday, dude. You're doing well. Just fine here. Refractor, Caminero. Nice one there for the raise to 499. Gutierrez, Dionne Jorge, Mason Nguyen, and Adren Rodriguez. Good. Yeah, good to hear it, tone. Glad to see you as always, my man. Good to see you. Last pack here, or last box here, I should say. Overall box. That is a Green Kevin Parada 299. Purple BJ Cook. Nice one there. This man is cooking to 250. Congrats on that. Spencer Jones letting anybody in here, I guess. Good lord. Chris with the White Sox in the next one. Thank you, Chris Rich with a mixer spot down to four. Four to go, everybody. And number 21, four to go. That is ma'am Chateau Iconic. Four to go. Four to go. Got it filled up. Orange is Alec Thomas. Nice one there, 225. For the D-Bex, Luis Serna. First of Ethan Salas. Last box of the break. Very good luck, everybody. Jason Shurio to 199, Guardians. Basado, Brian Betancourt going to the Rockies. Congrats, Colorado. And Rockies' great volume team in this product. Jet the Met and James Wood. That is Yosi Golan, 2-4-99. Rajgari S. Devison De Los Santos. Jason Dominguez. Process, or prospect process, Jackson Shurio. Hannah Delgado. Last pack. Good luck, everybody. All right. Got a couple of randoms to do. It's going to be, the way this will go is the, first one we pulled is Acomoto 250. We've got the Rokie Sasaki. That'll go second. And the green Acomoto. That will go to the third team in the random. I'm just going to do it in order of what cards we pulled. I'm going to get all the teams in. We see. Random. All right, everybody. Again, doing the random for the three World Baseball Classic inserts. Again, they don't have teams, obviously. Going to roll the dice. So after eight times, whatever team is on top gets the gold. The team in second gets the refractor. And the team in third gets the green in order of how we pulled them. Good luck. One, two, three, four, five, six, seven, and eight. Are you ready? Rokies getting the gold. The Marlins get the refractor. And then the Rangers will get the green. So again, there you go. Top three. Meant to be eight times, eight times. Let's do a quick recap here. We add Image Variation of Yoshida, Gold Freddy Freeman, Orange Arosa Reina, Alec Thomas, Andy Pajes. Base Autos, we add Brian Bettencourt, Dylan O'Rei, Luis Guanipa, Brian Runcone. That is Wilfredo Intunes, Wisely, Ben Metzinger, Rainer Arias, Joey Estes, D'Angelo Sarmiento, Peyton Williams, Daniel Guirote, Dario Barrero, Jesus Bougarin, Andy Perez, Abner Uribe, these are refractors now, Jesus Pastita, Spence Kaufman, Joey Ortiz, Luke Berryhill, to 250, BJ Cook, Chris Newell, to 99, Ludwig Espinoza, to 75 is Diego Mosquera, and Drew Jones, Bowman Assumptions, Orange to 25. I'll do it for the break, everybody. Thanks again for the fill. Up next, number 21. Let's build up.