What's good y'all Chris from justice case breaks calm doing our first filler for the big hit express number six This is 2023 pinning the legacy football one marks break random team number 10 Giving away six of those big hit express spot giveaways at the very very under this break. No bit common ship in this one Let's do the box itself Don grab the last 16 teams the second half of this box To fill it out. So thanks again Alan Kevin Chris and Ryan with Michael T as well Thanks, y'all. Here's our 32 spots and I've 32 teams from the Cardinals down to the commanders Electrical the dice and randomized. Good luck one of five six times. Good luck y'all one two three four five and six Six then final time for the box Alan down to Alan Six times for our teams one two three four five and six Six the final time Niners down to Jets for our 2023 legacy Since this is just a filler no trade window, but I'll let y'all pause if you want to see who you've gotten this break It's alphabetize Get this all printed out There you go, Kevin with the Cardinals down to Dom with the commanders Let's uh switch screens real quick Here's our one box 2023 legacy. We'll break this bad boy and at the very end of it We'll randomize those top seven We're born the Cardinals Kevin All the way down to Dom with the commanders Let's do a chalk. Good luck Vicky here might be a Patch auto It will be last stuff. So I'll have to wait to see what we got. This case of NT football This can take it our pay-to-dine nine NF gear style for Jackson patch auto Nice sauce gardener, okay, that's a nice stuff all night, but let's do it like this So not all card ships, so it's gonna be just a chrome cards But our inserts like that are rookies and then some color like jane hyatt 66 out of 100 on the green jay one high it's gonna be for the Giants Make their first rounder for the second rounder for the Giants going to be for Allen Under the light jimmy or Gibbs on the rookie she writes on the mini of her jane hyatt Jackson's got the jigba Not numbered on that menu Christian opoe 103 out of 299 legends For the chiefs. Let's go to Don This isn't going next mini maybe Dak Prescott Tanner McKee on the chrome rookie and an orange Dak Prescott 174 out of 199 Dallas to go to Don okay, but last from the past on the legends That two autos should be one of them soon enough Points so we'll randomize that at the end of the break Take one silver under the lights Number Nolan Smith 288 out of 299 Peak here no one Smith No eagles first not it's not a showing up Think 10th pick no one Smith for the Eagles is going to go to Don True last by Mojo there. So we got points, but we do have a patch on coming up. I believe some good luck everyone Mark Brunel legend right there Legendary patch auto on the mark Brunel 76 out of 100. That's Jacksonville Jaguar is Mark Brunel Jacksonville Right off the end of our break All right, so two random matches first off. I'll randomize these 400 points What screens real quick? Let's just grab a fresh he here Circula From Kevin down to Don So the first randomizer will be for the points the second randomizer will be for those seven spots in the big hit express We'll throw the dice and randomized for both though. Good luck everyone 400 points first one and six seven times One two three four five six and seven Seventh the final time name on top is gonna be Alan. I want them to both hits So the 400 points go into Alan, but let's get to the fun stuff shall we? Six times seven times excuse me seven times For our seven spots thing let's do it y'all. Thanks again. Good luck I'll put number 11 for the legacy of football our second filler for this big hit express two three four five Six and seventh in front of time. Good luck top seven get in so eight there into 32 Sad times, but hey, we still have full spots and another filler coming up very very soon So number eight gonna be Chris all the way down to Don. Thanks all for giving it a shot Let's see who does get it congrats to Don Michael Ryan Alan Don Don and Kevin the top seven right here. Congrats y'all When I put you in it'll be as a legacy 10 So you see legacy 10 on the big hit express break this junior you went from this filler Thanks y'all congrats number 11 coming up on the site very very soon jasses case breaks calm. Thanks again. Bye. Bye


I think if you truly love something you have to be willing to point out its flaws and There's one thing that I'm absolutely 100% sure of about Linux is that it has Many flaws and I've talked before about how I think Linux could go mainstream I've talked about whether or not we even want went Linux to go mainstream and This video is not really about that today, I didn't want to talk about a few things that Linux could do better and This doesn't really have anything to do like I said with wanting Linux to go mainstream But I do feel like a few of the things that I'm going to talk about today Would play a really big role in making it easier for new users to actually use Linux But it would also make it easier for existing users to use Linux So let's go ahead and jump into five things Linux could do better the first thing I'm going to talk about is installation and this one really does focus on the new user and When I talk about new user, I'm talking about someone who doesn't really know a lot about computers because Linux does not serve That community well now Whether we should even try to serve the light a community at all as a discussion we can have somewhere else maybe in the comments below But if we were to serve that community, I think installation is probably the biggest hurdle for getting that community to actually install Linux because the vast majority of those people don't know how to burn an ISO and Even if they could find the ISO on a website, you know the of a distro and actually choose a distro They'd be lost at how to actually go through and burn that on to a USB or a DVD or whatever It's just not something that most people know how to do and moreover It's not something that we really expect people to know how to do if you're just a regular person And you've never Installed Windows before because you've just bought a new computer every time Windows dies Then you've probably never even tried to burn an ISO before so this would be a completely new experience And it's not the most user-friendly thing in the world now. How do we how would we fix this? I don't know That's not a great answer. I'm I'm I know that whether there's a technical solution of being able to somehow Begin an installation in Windows I don't know because we install the next version of Windows You start from a program within the Windows that you're using and then it reboots into the installer if Linux gets to come Somehow come out with something like that that'd be great I don't know if technologically that's possible because of secure boot and all this nonsense, but there has to be some kind of solution to Removing the barrier of an ISO and it's possible that I'm putting too much of a Emphasis on how hard this is I Just know that if I went out to my parents and tell them that in order to install their new operating system They had to burn an ISO There'd be in there'd be trouble. Okay, so the next one I want to talk about is something that is probably just preaching to the choir and this is less fragmentation the Linux community does a fantastic job of duplication of effort and I'm not even really talking about package managers or even distributions because I think it's great that we have a ton of package managers I think it's great that we have a ton of distributions and I understand That that causes confusion amongst new users when I'm talking about fragmentation and Duplication of effort really I'm more talking about the little things that we tend to spend a lot of time on and Those things are like different file managers that we don't really need the Linux Mint team just went through and created a bulk rename tool which I'm sure it didn't take them a lot of time, but it was a big feature in in mint 20.2 and The fact that it even exists is kind of just mind-boggling. Why did they spend their time doing this? And it's not the only example and I tend to pick on a lot for their duplication of effort, but They're not the only ones that do this. There are a ton of Linux developers out there that just seem to constantly remake the wheel things that we don't really need duplicates of and that's definitely something that we need to Fix in the Linux community because Linux has real problems audio And a few other things that I'll talk about our actual real problems We're in the middle of a transition from Xorg to Wayland and if people really wanted to spend their Development time on something they could focus on that instead of having to constantly Rebuild applications that we already have So that's definitely something that Linux could do better. The next one is better acceptance of new users I've actually made a video on this before and I Regret not being able to call it the title noobs are gonna noob I should really should have named it that but the Linux community has a tendency of being very insular and We're very much a Community of people who have banded together and don't really accept outsiders all that well And that becomes a problem if we want to grow the community when people who have never used links come in and ask Stupid questions We very much tend to tell them to read the fucking manual and I know I know I go on and on about being more Open to new users and but I really do think that this is a big flaw that the Linux community has and it's not only new Users that I'm talking about I'm also talking about Exclusion of groups within side of Linux for example gentoo and arts are two communities that are very much insular and Cultish if you will and they don't accept new users Even if those new users have used links for a long time even if new users to those things go into That situation knowing how to look things up, but still have questions Very often they're not welcome and treated with respect. They're treated with derision and That's not a great thing Even though they're technically not noobs The next thing I want to talk about is better support for high DPI displays Now this is really a technical thing that is going to continue to get better. Some distros do it better than others already but as We move forward 4k and 8k displays are going to become more and more Common and Linux doesn't do a great job right now of managing high DPI displays whether that's actually supporting them at all or Whether it's actually allowing people to manage them to make things so that they actually show up on screen It or an X in an acceptable size, you know There's tons of very small problems within this big larger problem They have to be solved and the Linux fragmentation thing is not really helping because each distro seems to have been doing this a little bit differently and it seems to have been left in the hands of desktop environment developers in Terms of how they're going to solve this and that means that KD is going to do it in one way Mate is going to do it in one way. You know, I'm going to do it in another way and that's not a Great thing is this should be kernel level It should be something that is very much a standard across all Linux distributions because Like it or not 4k and 8k is here to stay and like I said It's going to become more and more popular as time goes on the last one. I want to talk about is websites now.    I love you to death, but your website's not great and Again Arco your websites changed four times in the last year It's that's not a great experience I'm doing a Debian test on the computer behind me and Debian's website is Horrible, I don't know if the reason why Debian is so bad is because they've been around for so long They just haven't really done a very good job of keeping everything organized I that might be the problem, but their website is is Just so bad it they have ISOs all over the place Things aren't labeled properly. It's nice. It's not it's not good I can't really speak to experience with like elementary OS's website. I don't use that distribution at all, but just kind of broadly Discovery for Linux distributions is not great and the website is a very much a representation For your distribution and if you don't do that well It makes it even harder for new users to your distro to find the information They need to actually install it find the community and so on and so forth and kind of a subset of this is that The support forums that we still kind of put up with and I'm talking about actual forums Those things still exist and every single one of them is so totally over complicated that it really hurts To use them and if you've never used a forum software before, you know You probably are going to be lost within five minutes those pieces of form software have been around for 20 years and they really haven't done a great job of Moving into modernity. They've just keep piling on new features on top of a really old code And it's not great and every Linux distribution uses these old form softwares Uh, and like I said, it's not great now a lot of distributions have moved to newer ways of communicating with the community whether it's discourse or something like telegram or discord or something like that you know, they have gone through and tried to modernize in terms of how they support and Cultivate their community, but these forum things are still there and a lot of times they're the kind of the favored way of getting things, you know providing support and That software is trash.  So Yeah, websites on Linux for Linux distributions, especially just they need to get better So those are five things that I think Linux in the Linux community can do better in the comments section below I'd love to hear your thoughts on a few things you think the Linux community could do better Make sure you subscribe like and comment all that kind of stuff You can follow me on Twitter at the Linux cast you can support me on patreon at patreon.com slash Linux cast Before I go I'd like to take a moment Before I go I'd like to take one moment to thank my current patrons Devon Marcus Magland Donnie Sven east coast web Chris Mitchell mr. Fox American camp. Thanks everybody for watching. I'll see you next time


Wait, okay. Okay. Do you have a the new Diggle? I just want to look at it. There's just one inspector. No, there's just one inspector. I'll give it back. I'll give it back I'll give it back. Oh, thank you. One inspector. It's like that It's like that


So this is the talk titled Test Senior Critical JavaScript, my name is Nick Smith, I'm a senior software engineer at Sidecar, it's a startup in center city doing machine learning, I'm on the UI side, I don't have any opinions or really touch machine learning or AI, so don't, I think it's super great technology but I know very little about it. Also personal news, I welcome to Babyboy in the beginning of September and it is incredibly true what they say about the lack of sleep you get. I started this talk when Baby was born, I thought paternity leave, this talk is going to be amazing, finished it last week, took four times as long as I thought it would. And also a lot of people have been linking at the beginning of their slides so I just threw this in here. This is at github, github slash github.com, hopefully another website, futon which is my handle and then testing critical JS. There's a link to the slides there as well as a whole everything that I show here, the code samples are there as well. So the whole point of this talk is to give you the encouragement to start testing JavaScript. Your front end, giving you a whole overview of kind of what that looks like, give you the tools to succeed in doing that and also give you some broad guidance when writing your unit tests. While you might already have unit tests on the front end of your code, this hopefully will provide some more framework around that and help you avoid some gotchas that have gotten me. Before we dive in, we're going to kind of discuss what are all these terms around JavaScript and around testing and let's define them before we dive in. The first one is JS, JavaScript will start easy. Next one is business rules which kind of got talked a lot about in the last talk. Last talk was a great setup for some things that I'll point to moving forward.  For example, if you're validated in input in the last presentation, there's a lot of talk about filling out a form. There might be specific validation for one of those form inputs. That's a business rule you're deciding, you're deciding how that form input will get filled out. URL parsing, if you land on a page, you parse the URL or you're parsing the URL for the user to go to a different part of your application or your website. That's also a business rule you're deciding. I'll slow it down a little bit, sorry, I'm talking fast. Framework, a collection of patterns for development solving a common software problem or group of software problems. The product I work on is called Connect. We have a framework of how we build React components in that framework. We have a framework of GraphQL queries that we write on the API side of that application. We have a framework of how to approach and solve those problems. There's open source frameworks like Jest that we're going to talk about today and Jasmine and React and WordPress at some point of it is a framework. Suite, specifically testing suites. There are groups of tests that verify a software program and show that it passes a specific set of behaviors. We're going to look at hopefully some great examples. Hopefully you think they're great.  A unit test. It's testing of individual functions or classes by supplying inputs and verifying outputs. Almost all tests are doing the tail end of this. Given inputs, they produce these outputs. That's what we're testing. But a unit test is the smallest part of that testing of all testing. There's also snapshot testing, which is a newer form of testing if it can be known as newer. A lot of this is hot within React where you're doing snapshot testing with Jest. But you can snapshot test your homegrown APIs that output HTML, your Angular components, you can do that as well. We'll also look at an example of this. There's a great example on the GitHub repo that I posted. Integration tests could talk a lot about the difference between unit and integration tests. But for the sake of it, we're going to stay closer to unit tests. Integration tests are testing multiple units of code together. We were a little past integration tests in the last talk. We're about to get to what tests those were. But integration tests might be testing multiple units of code together. That might be a function that calls a function as an integration test. Testing a function correctly, writing to the database, that's an integration test. And outputting data into a static file, that's a really easy integration test. A lot of the previous talk was about end-to-end testing and automated testing. So end-to-end testing is testing the entire flow of the application. We have tons of end-to-end testings on the application I work on where we, in the CI we actually have an application that clicks through the entire site, verifies that a query gets sent to the API, writes to the database, and then we then re-query the API to get those updated values. We basically make sure the whole application works. Luckily, the talk before this covered all of this. So just re-watch that video. Automated testing, also covered by the previous talk. Doing any and all types of testing automatically, that's basically all it means. People use Travis CI or Jenkins, the previous talk used Circle CI, which is another great tool. And then lastly, we kind of just want to broadly define testing, probably going to redefine it five times. But it's all going to be the same thing, we're validating your business rules. We're having repeatable outcomes against expectations. And given inputs, expect these outputs. So we've kind of entered the first half of the title of this talk, but let's talk about what your critical JavaScript is. And it's, lo and behold, all of your JavaScript, which isn't a helpful answer. But so let's break it up a little bit. It's the code you're about to write, the code you're writing now, or the feature that is always breaking. Nine times out of ten, it's always the feature that is always breaking. That's your critical JavaScript. My mom always used the analogy of a storm for any life problem that I came into. So you're either about to enter a storm, you're in the middle of a storm, or hopefully you're coming out of a storm. So take it for what it's worth, maybe a life lesson you can take away from this talk as well. In terms of where to start testing, it doesn't matter where you start. But it matters that you start now. You need to start testing some function on your front end if you haven't already set that up. But let's make sure we do it right. So start small. Don't set out to test the whole UI. At a previous startup I worked at, I wanted to introduce some type of linting to the whole front end.  I chose ESLint for that. But instead of studying out to test the whole UI and get it all linted at once, I started with one file, then worked the entire directory that that file was in, then the entire directory that that directory was in. And slowly built all the way up until it took about a year. We got the entire front end linted effectively with rules that made sense for our team. So pick a bug, function or feature. But don't get overwhelmed. It's easy to see your entire front end as untested or tested wrong or just not useful to be tested. But pick something that might not, that seems trivial and start there because it won't be trivial by the end. Love repeating myself. Start with the unit test. I think that when you're getting into JavaScript testing, it could be a single function, class or module, but just start testing it thoroughly and correctly. We'll get into the thoroughly and correctly here in a little bit. The important part is just to get the ball rolling. However that might look for you, maybe it is just a bunch of mistakes, but at least start the testing and start doing it. My, one of my other passions, which I could talk an entire talk about is getting