All right, good to go. All right guys, thank you for your patience, technical difficulties are always fun. So we're going to continue this track. Amanda Folson is going to be talking about how you can use open source even if you're, or participate in open source, even if you are a close source company. So without further ado, let's get started. Thank you. So sorry for the delay. So fun stuff, we're going to run this off of two laptops.  How many laptops does it take? So I'm not breathing into it. All right. So just to get started, who am I? My name is Amanda Folson. I'm a developer evangelist at pager duty. That's a fancy way of saying that I am a professional conference attendee. I pretty much go around to things like this. Yeah, basically, and give talks just like this. My job is to interface with people, write documentation and things like that. I grew up around computers. My dad was a developer in the 90s. So I kind of grew up around like visual basic and some, even some C sharp in the early years, things of that nature built my first computer when I was around seven with some help from my dad, of course. So I've always kind of been into the computer thing. I've always been tinkering with things. So I would say that I am also a professional tinker. That's also a huge facet of my job. In middle school, I was making websites as you do. I was on neopets and a few other things and learned some HTML. And I was like, you know, I really want to make my own copy of this. I had some problems with neopets.  Why does this work this way? How can I make my own? So I figured that out, found PHP, made my neopets clone. Funnily enough, I still have the source code for that. It is the most awful thing in the world, but it still exists. So it's kind of cool. I really kind of owe my career to open-source software, too. I continued doing PHP, eventually found IRC channels, which is great. Got involved in some IRC development and worked on a project called ANOPE, which if you're not familiar with IRC, it's Internet Relay Chat, old school chat system. And ANOPE is a set of IRC services.  Started hacking on that. And found some weird issues, particularly with a MySQL issue that I ran into. And I was like, hey, you know, this is broken for me. Can I submit a patch to it? And they were like elated that anybody in the world would want to submit a patch to this thing. It was really cool. And eventually they gave me commit access. Oh, God. No. Okay. This is going to be a fun one. Yeah. So started making changes, got commit access after submitting several, several patches to this thing and just was kind of able to do whatever I wanted. Fixed on MySQL issue that was causing a crash. Turns out it had been causing a crash for a lot of other people. Just no one was reporting this bug. So I found it. I fixed it. It was great. And from then on I was kind of addicted to open source communities and kind of explored, you know, hosting websites and things like that. And eventually wound up exploring a whole bunch of other technology. I needed a web server to host my crappy Neopads clone. And eventually got a job as a tech writer, which exposed me to even more stuff. So it's kind of, kind of been all over the place. Kind of been doing this open source software thing for a while. And like at pager duty, I work with Jekyll. I work with Ruby. I do some JavaScript stuff, even doing some PHP stuff. And simply wouldn't be here today without some awesome open source software. Forgive me while I change this in two places. So what is open source? There's actually a lot of confusion around what open source is and what it's not.  And that's simply not true. There's a ton of licenses. This isn't releasing something as open source. It means releasing it under a permissive license for the greater good. It allows people to adapt and re-release your software. Open source initiative and get hub, break down the licensing thing really well. I'm not going to get into that because it's just a crazy subject. And that could realistically be its own talk. And you're sure to find one that will work for you, even if you're worried about IP law. There are licenses that cover intellectual property.  And licensing, super, super important if you want other people to use your code. Whether that's including your project in their own or building on top of it or whatever, without one, they technically can't use your software without your permission, even if the source code is put up on GitHub. So licensing, super, super important when it comes to open source software. Putting it all out there, like I said, allows people to adapt and re-release your software. You know, people will do bug fixes. They will fork it, add new features, do their own releases. I don't know if any of you follow the Node project, but that kind of split and then re-merged. That was a big deal. So things like that happen all the time. Wouldn't be possible without, well, licensing and releasing the source code. And all of this can be done at a global scale. So if you open source your project, you're getting access to literally millions of people. I'm not saying millions of people are going to work on your project, of course, but you know, you might get a few thousand. So you can go from five people working in-house on something to 5,000 people. That's actually not that unrealistic. Some of these larger projects, they have thousands and thousands of committers and thousands and thousands of commits every month.  Some people are hired to work on open source full-time. Can absolutely make a career out of it. Other times it's just people using a tool who want to make changes upstream. And honestly, very few companies can afford to hire the amount of diverse opinions you will get on these projects. Very few companies can afford to hire 5,000 developers. But by open source and something, you kind of get that for free with very little overhead on your part. Come on. So what open source isn't is not giving it all away for nothing. You're giving it away in exchange for out-of-house development. And that affords you so many awesome things, which I will get to in a second. Some people think that giving it away is giving away your bread and butter and your company is going to go bankrupt and all these things. That's really not true. Anybody familiar with OpenStack in here? Okay, a few people. So that's a relatively large project. Rackspace started it and was basically like, here you go, and it runs part of their infrastructure. And there's still a billion-dollar company, despite releasing that. You can basically spin up your own version of Rackspace if you wanted to using this utility, and they don't care. They're like, have it. And they've actually benefited from people taking it over and adding new features and things like that. It's become this huge, huge ecosystem. Parts of Windows and Azure, they're open source. Microsoft is still fine. They're still doing all right. Apple has started releasing things. They've really swift. They're still doing okay. So granted, they are a hardware company, but you can release various aspects of things and not go bankrupt. So like I said, you're exchanging the source code for rapid development. And this is especially true at larger companies. If you're at a company that's got some serious firepower, you're a well-known name and you release an open source project, you're guaranteed to get a few hundred people interested in it immediately. Thousands of commits per month on some of these projects, and you can't always buy that. Maybe you can if you're Microsoft, but if you're at a smaller company, you can't buy that kind of publicity, really. So giving it away to someone who can use it and modify it to suit their needs. That's huge. That's key. Letting people scratch their own itch, so you don't have to. Essentially, you're getting people to come work on this thing for free. I like the scratching gesture. And you're not giving away your business. So there's so much more to a business than the source code you release, of course. There's marketing, there's sales, there's how you market your thing is super, super important. So never underestimate the power of Lazy. Lots of people can't and won't self-host projects like this. Especially if it's a project that's really hard to set up. Lazy makes a ton of money hosting Jira and Confluence and things like that because people simply don't want to put in the effort to host it themselves. And that's huge. So never underestimate that. So I talk to people and they're like, oh, well, we can't do that. And my first response is, well, why not? They're all like, oh, my gosh, we're going to lose control. We're going to go out of business. All of these bad things will happen. Our competitors, they're going to steal our stuff and we're just going to go bankrupt. And that's really not usually true. So I'll give you an example. At PageDuty, we have this messaging pipeline. It's pretty robust. It's very reliable. And it's kind of our secret sauce. We could realistically release our web panel. Nothing super secret about that. So there are times when you do kind of want to keep things closed source just to kind of protect your trade secrets, things that competitors absolutely would benefit from if you released them. If we were to release our web panel, it'd be kind of great because it would allow people to fix their own pain points. But if someone wanted to steal that, if they really want to steal our front end first of all, they kind of can anyway because it's HTML and JavaScript. But also they'd have to build the entire back end themselves. And most people really not going to be bothered with that. If there's an existing tool that works and is cheaper than putting in the dev time, they're just going to, they're going to roll with that, guaranteed. So talk to a ton of people and they're still not convinced. Oh, well, there's no value to open source software. And you just, all I can really do is shake my head. And they're typically telling me these things from their Windows PC or their MacBook, both of which can send open source libraries by the way. Or they say it on Facebook and Twitter, which are making use of like PHP, Scala, Ruby, Apache, Nginx, all those things. They're saying it on their, I actually saw someone blogging on a WordPress site about how open source software was not valuable. And I just wanted to be like, we need to have a little talk. You are benefiting immensely. You are allowed to spread your opinions by virtue of open source. And if you hear this, I encourage you to challenge people on it, by the way. Call them out on it because I think we have a lot of work to do in terms of telling people how prevalent open source software is, just as an aside.   Same with HTTP magic. Like there's all sorts of things that everyday devices are taking advantage of. Absolutely encourage you to call people out on that. Another point, we have to hire someone to maintain it. Well, so what? It's still cheaper than multiple in-house engineers working on something or contractors or anything like that. If you're open sourcing it, I mean you have access in theory to millions of people. There are millions of potential developers that will hop on this project. And of course, if you build it, they're not necessarily going to come to it overnight. You might have to put in some marketing. You'll have to get it off the ground. You'll have to nurture the community that kind of evolves around it. But for the most part, you know, if you have to hire one person to gain access to literally thousands of people who can potentially work on it, isn't that worth it? Yeah, absolutely. So it's not true that you will always have to hire someone to maintain something for you. You know, you might find that the volunteers will do the heavy lifting for you. And this is true at a lot of some of the projects that Red Hat does. You know, there's a ton of volunteers that are just committing code. Some of them are Red Hat employees, but a lot of them aren't. So they kind of manage the direction and do a lot of the feature implementation stuff so that you don't have to, and that's awesome. But it's not uncommon to see community managers or developer advocates or something in a position like this. Basically to kind of guide the community and guide the project in the direction that it should be going, but also to kind of interface with the community and bring that back within the company and say like, hey, the community thinks we need to go in this direction. Maybe we should try that. Maybe we should listen to them because they're probably in a better position to tell us that than we are to tell them what they need to be doing. So you just provide the community with the guidance and take it from there. You don't necessarily need to hire somebody. So if anybody's like, oh, well, we can't do open source because then we have to maintain it. It's like, well, yeah, but also, no, not so much. And then my favorite, but what about my bottom line? People love their money. They want to hold on to their money. And this is probably the number one thing that I hear about when I'm talking about open source and in particular giving this talk. People are afraid of losing money, which is absolutely healthy. You should be worried about losing money. They want to know that they'll stay in business. Also a pretty healthy opinion to have, right? But if your idea is good, people are going to build on it. The best part is even if they build on your idea and don't release the source, you still might benefit from that. You can see what the market wants through the work of others immense value in that, immense value. You might run into some leachers, some people who just want to take your code and mess around with it and not actually give back, or maybe they want to rip your code off, use it as their own. But they're really not that successful with it. I don't know a whole lot of stolen code projects that surpassed the parent project that they were forked from. You don't really hear about that a whole lot.  You'll see them modify it. My favorite is when people, they will fork a project and then mass delete all of the headers with the licensing information, but all of that history goes into GitHub so you can actually see them deleting the comments and the copyrights and leaving that history of that behind. I love it when people do that. It's like, are you really? So yeah, most of the time they're not successful. Their project is likely not going to make waves that are bigger than yours. Going back to Rackspace, they're selling you an experience. There's so much more to the product than the code. They're selling you their quote-unquote fanatical support. Everybody's seen those ads where it's like some dude that's like, I've been a racker for 16 years and I provide fanatical support. That's really what they're trying to sell you. The infrastructure, that's important, but at the end of the day, it's a server in a rack somewhere. Anybody can kind of do that, really. Well, mostly. So even if someone takes your code and creates a competing business, there's actually no guarantee that they can provide the same experience that you can. Experience is huge. People are an important factor in this. It's not just the source code. So if you're worried about your bottom line, there's so much more involved in worrying about your bottom line when it comes to this stuff than just releasing your source code and assuming that someone's just going to steal it and put you out of business. Someone will steal my idea. Well, I've got news for you. I can't tell you how many times I've heard this from people with just ideas that are really not that original, not that good. Your idea is probably not that unique. If you're creating a cloud on OpenStack, you're joining literally thousands of other people who are doing the same exact thing. Some control-metal stuff might be different at the end of the day. Like I said, it's just a server in a rack somewhere serving some stuff that's not all that unique. Facebook isn't unique. Social networks were run long before Facebook was in the picture. That's been a thing pretty much since the internet. Photosharing was a thing before Instagram. Search engines existed long before Google was ever a thing. So never underestimate the power of marketing and positioning when it comes to open-source software. And I think Red Hat does a pretty good job of this. They have lots of money to throw out the marketing and development of these things. And it works for them. You can pretty much get anything that Red Hat does for free unless it's support. But yeah, it's free. If you want to set it up, you absolutely can. But if you don't have the time or the patience, they have people that will help you do it. Another spoiler. Nobody really cares about your idea as much as you think. If they did, they'd be out there building it themselves. And it happens from time to time. But in the end, one project usually pulls ahead of another. Good example of this. Linux versus Herd. Who do you think is winning that? And value is very subjective. What you value may not actually be all that valuable to someone else. So if you're worried about someone stealing your idea, first of all, your idea probably not that unique.  Someone might say, hey, why don't you try going down this route or try going this way? Maybe you need to implement this feature. And you just never know what's going to come out of that. So in addition to code, you know, the bug fixes and things, you get some other benefits by releasing your software out there. People can get in. They can get answers. They can get on with their life. This is especially true of technical people. They don't want to talk to sales engineers or anything like that. Not interested in traditional sales and marketing. So in my experience as a developer evangelist, you know, you run into people who they just want to go in. They want to tinker with it. You give them documentation and they just want to go do their thing. Most people who are playing with this sort of thing, they really, they're not all that interested in getting your marketing pitch or anything like that. If people have some visibility into your product, you're opening yourself up to more feedback. So one of the things that we do, which I will cover in a little bit more detail, is we invite people to give feedback. Rigorously. We send them emails. Anytime someone creates an API key, I email and I'm like, hey, what are you building? Do you have any feedback for us? And the email campaign in particular has a 20% response rate, which in this industry, pretty much anything above 3% is phenomenal. But if you're building some transparency, people will love to give you feedback and some insight into how they're using your product and what they're doing, what they hope it does, what it's not doing, that's hurting them, things like that. And you win either way. If you make a sale, great. If you don't make a sale, hopefully you've got some really good feedback from that interaction. And we're, as a collective, the technology community is pretty vocal about what we like and what we don't like, especially what we don't like. So you're extremely likely to get the holes in your project figured out as you're talking to people because they're going to be like, well, it doesn't do X, Y, and Z. I really need X, Y, and Z because of A, B, and C. And that feedback is super, super valuable. But if they're in their tinkering and they see that it works for them, then you might make a sale. And you might make a sale through some non-traditional sales funnel. Like someone just might be like, OK, well, I see, I can get this information out of your API. I can put this information into your product via this API. That's good enough for me. I'm going to sign up. I'm going to do my thing. Leave me alone. That's great. So when we know what to expect, we're a lot happier as technologists. I don't think everybody's first instinct is to go to the documentation. But definitely if we're tinkering with something and we can kind of pull bits and pieces out of it that we like, we're typically a lot happier. Another important thing when talking about open source is that one size doesn't necessarily fit all. It works for you. Not necessarily going to work for someone else. As one person, open stack is complete overkill for me. Maybe I just need a Zenbox or maybe I just need something like Vagrant. Maybe I just need a couple of Vagrant boxes to spin up. I have the freedom to explore all of my options, which is great. As a result, I know more about these products, and especially in my line of work, exposure to different things is key, and I can help other people find solutions for themselves. It's a very positive thing to have software diversity here. If the source is open, I also have the freedom to tweak it, which is how I really got into this. I was playing around on IRC. Something was not working for me, and I was like, okay, well, you know what's wrong.  I'm good to go. So I started making modules for functionality that I needed, and now the users of the software, since these modules got incorporated into the core, you know, they're all benefiting from those changes too. So, and it was something, the MySQL thing, like I said, they didn't know that that was an issue. People were not reporting that bug. Turns out once that fix was released, then suddenly a whole bunch of people were like, oh my gosh, thank you so much for fixing that. That was driving me nuts for months. I've been trying to get it to work. Didn't understand why it wasn't working. So it was great, and they should be able to tweak it. Their changes might even benefit you. I can't even tell you how many things that I've touched that get continuous updates that are then better for me. So like I said, once I might not fit all, it might fit many, and you might find that out just by releasing your software and having people tweak it. And if it'll fit many more, a few users can establish quorum on what they need. So you can get people talking. We have a community site. Some people have gone back and forth on it. And they kind of reach a consensus on some of the prioritization and the features that they need within our product, which is really cool. So kind of the community and the customer base gets to decide really what we're doing, which is kind of cool. And some of the changes we roll out, they might only benefit one person or they might benefit thousands of customers. You just kind of never know with that sort of thing. Another benefit that I think is really overlooked is information transparency. So too often we're stuck in our own silos and develop like these huge blind spots in our product. So we're so focused on one thing that we kind of get tunnel vision. And we don't necessarily notice the holes in our product. So trying to stay ahead of the market can result in some serious tunnel vision. So like we know what we want, but we don't always know what customers want. Even if they give us feedback, are we acting on that? So letting the customers have control over product direction is actually an extremely good thing. They often know more than you about their own needs. So letting them have control is kind of giving them what they need in order to succeed. So as you're trying to apply some of this open source stuff, just be mindful that even if you're leading a project, you don't necessarily know what's the best thing for that project. You really need to listen to your customers and figure out what they want from your project. And besides, sooner or later, someone will make an open source alternative to your product. Even if you make a good product and keep the source closed, someone's going to be like, you know what, I don't like that this is closed source. I'm just going to do it myself. That's kind of the world we live in these days, and it's great. Open and Libre Office are great examples of this. Microsoft Office is pretty much, or was pretty much essential for business needs. You had to have Excel, you had to have PowerPoint, had to have Microsoft Word.  We're not going to accept anything else, no PDFs or anything like that. And there are open source social networks. There's an open source Facebook. I feel like open source Twitter APIs are becoming more common. So I deal a lot with API design and give a lot of talks on that. And almost all of the examples I see these days are either a four-square clone or a Twitter clone. So there's even open source alternatives to those. If you want to set up like four-square for just your group of friends, like you can absolutely do that. You're probably not going to overtake four-square at all. But the point is, really, you can do it. There are even open source operating systems that can look and feel like any Windows or Apple's box. I'm sure we all know of one or two or five. So these projects, their big selling point is that they have market share. So it may as well be you from the start that gets that market share. You know, go out there, release your thing, launch it, get people to love it, which of course is easier said than done. But you can get that market share from the start. And that's really kind of your competitive advantage when it comes to open sourcing your software. So, okay. Let's say I failed to convince you to open source your software at your company. It happens.  I mean, that's kind of a huge thing for us. We've invested, you know, thousands of hours of engineering time. Reliability, absolutely a competitive advantage. So we don't want to release that. But we do some things internally that are actually kind of cool. So one of those things is internal transparency. We maintain a wiki. And so before coming to PagerDuty, I hated wikis. You know, they're never up to date. They get kind of stale. They're spam magnets. Anybody maintain a wiki here? No? Okay. I can't hear blessings. But they tend to be kind of awful. But PagerDuty actually has one that's relatively good. And occasionally, you'll find some crafty information on there. But for the most part, especially in, like, the product and engineering side, everything's up to date. You can go in there. Like, I'm not an operations engineer, but I can go in there and see some of the remediation steps for when specific alerts come in. Things like that. It's really cool. We have this concept of demo days. So if you want to see what's going on with the product, you can come to a demo date. Everybody in the company is invited. They are recorded. There are notes that are drafted up. Things like that. A lot of the meetings are just open to everybody. So especially in, like, product and engineering and marketing and even sales, you know, if you see an invite on someone's calendar and you're like, you know what, that actually sounds pretty interesting. You can pretty much invite yourself to that with very, very few exceptions. We also have a policy, at least on my team, of no meetings over 30 minutes. Anything over 30 minutes requires an agenda, and even if it's under 30 minutes and doesn't have an agenda, you are allowed to decline it, no questions asked. Or you can hit someone up and be like, hey, I really need an agenda for this before we can actually, you know, talk about it. So we also do open training. So it doesn't matter where you sit in the company. We have scrum training. We have Kanban training. Things like that. You're allowed to come to that. Regardless of whether or not you're working on product or engineering, if you just want to learn about Kanban, like, have at it, we will teach you Kanban. We will get you a certified scrum master certificate if that's what you want. We're really big on that. And another cool thing is executives have office hours. So it's not necessarily a complete open door policy, but it kind of is. It's a scheduled open door policy. So anybody can come in and be like, hey, I want to sit down with the CEO and talk to him about our product roadmap. And you can do that. And he will be receptive to it. It's absolutely great. So I mentioned open information. This is actually my Kanban board at work. So I had to blur the things out because some of them contain customer information and the sort of thing that you don't really want to open source. I don't want to tell the world who our customers are. But this is public to the entire company. Anybody at the company can open this up and be like, oh, OK, well, here's what Amanda's working on. But it's kind of cool. So you see the guy with the green avatar there. That is an intern on another team that answers to someone else entirely. He asked what I needed help with one time. And I was like, oh, you know, go look at these tickets and see what you can take care of. And so since I'm an evangelist, I send a lot of t-shirts and stickers out to people. It's just one of my routine day-to-day things. Reply to a lot of emails. So Godham started working on some of those. And then there were a lot of, like, little code sample tasks that were left over. And he was like, you know, what would it take for me to be able to do these? And I was like, well, you know, he pretty much hit me up. He's like, OK, what specifically would I need to learn in order to be able to do these things? So we taught him JavaScript. And so this is a dude who didn't even know something like a terminal existed who is now a shipping code. He's got some little code snippets running in production now just because he saw a Kanban board at our company, which is really, really cool. So he's working towards becoming a junior dev, which is great. So through open information, he learned new things and now he has some stuff in production. That's something he can put on his resume and take to another company, right? And this task that's over here in the done category over off to the side was something that someone else decided to do over a weekend. It was just a little documentation fix. I didn't ask her to do it. She just up and decided, like, hey, I am blocked on this. I want to do it this weekend. And she just went ahead and did it. And I didn't have to do anything. It was great because my board's open. Not to say that I want to encourage people to do my work for me, but it's kind of nice when people can collaborate on these things and, you know, pitch in and help, especially I am currently the only evangelist at PagerDuty kind of swamped, especially doing all the public speaking and things like that. So it's really nice when people can step in and be like, hey, I know you're out on the road, but I really need to fix this documentation right now and then just go do it. So we're also big into cross team functionality, which you just saw. These people, they're not even on my team and they're contributing JavaScript and documentation fixes. So anybody can contribute anything and learn the things that will allow them to contribute via the training or the outside study or whatever. Absolutely not saying that anybody can be CEO for a day. There are certain things that, you know, use some common sense here, like, don't let your intern be the CEO for a week. Obviously, definitely not condoning that. You know, not saying that everybody is allowed to go to the board meetings or anything like that. It is okay to have some need to know things. Even open source has some need to know things. It's just like, it's okay to not release your bread and butter. You can absolutely give back if you're using open source software and not open sourcing your stuff, you should absolutely be giving back to the communities that are helping you out, especially if they're helping you make a lot of money. So the teams own the projects. They establish specific guidelines. I own the documentation at PagerDuty. I have a few simple rules, which are pretty much no force pushes. I don't want to see any of that. They're actually prohibited through GitHub, which is awesome. No deploys until a test pass. Yes, we actually have tests for our documentation. If you're not doing that, it's fun. I'd love to talk to you about it. And everything must be edited and signed off on before going out. Little basic things. And people follow these rules all the time. If somebody, they had some sort of like issue with things getting clobbered in their repo and I was like, hey, don't do that anymore. And they were like, hey, yo, I'm so sorry. They rolled everything back, fixed it. It was good to go.  So the force push thing, not a huge ask from people. So I handle the bug queue, review the pull requests, merge things as needed. But many other people are involved in making that project run smoothly. And that's something that we do.  So we have public blog posts about things that have gone sideways. But internally, we recognize everyone makes mistakes. This is one of the scariest parts of transparency is letting everybody see when you screw something up. It's scary.  People are going to be angry. And yeah, you know what they might. As I was showing Captain Intern something, I took down our entire developer portal and now he knows not to do that.  So you never know when things, when people are going to learn from something like that. We also have a concept of blameless post-mortems. No one is blamed, no one is attacked, no one's fired unless you're just blatantly reckless, which most people are not, most people are reasonable. And really, no one should be fired for a bad deploy in this day and age. It happens. Hopefully you have some tests that are running, but sometimes, stuff happens. We all know that. These failures are just great opportunities for us to improve and they're treated as such. Like I said, we even released them to our customer base. Like, hey, we ran into this weird thing with Cassandra, like this stuff happened, it sucks, but here's what we did to triage the issue, here's what we think happened again. So it's absolutely great. And if you could take one thing away from this talk, it would be this, really learn from your failure, adopt a policy of blameless post-mortems, stuff's going to happen, everybody can learn from that. So what are some other things that we can open source? Like if we're a company, we're a SaaS based company and we don't want to give away our entire SaaS product, there's all these other things that are kind of attached to a company that you can actually open source. So documentation, super important. We have API docs, tutorials, things like that that allow, and we allow other people to contribute to them. We've had people add their own code samples to our documentation which has been great. Things that we hadn't even heard of. I just found like an Erlang library for pagerduty and I was like, hey, you know, you still maintain this and he was like, yeah. And I was like, okay, I'll add it to the documentation and he just went ahead and did it himself. It was awesome. I didn't have to do anything, he was just like, okay, I'll add it to the documentation and it's great. Because it allows people to kind of dictate where the documentation goes, they know what they need, so why not let them help out with something like that. There's a whole bunch of libraries and tools. These are usually not secret sauce that you can release. Other people might find them useful. Things like I wrote this really crappy Perl script like six years ago to help me manage my DNS zones and some dude was like, hey, this is a great thing and it's now maintaining it himself. I'm like, great, that's awesome! Go do that thing that you want to do. People might find them useful. Even something like we released an open source cron thing. People have managed their crons and that's great. But they might find utility and are particular cron utility. And they have been. There's a bunch of stars in the repo and things like that. You never know what sort of things people are going to find useful. of your bread and butter, I guess, just release them. You really don't have a whole lot to lose in cases like that. SDKs, also key, again, the people who need this should be able to tell you what they need or modify it themselves. It's great when you see, you roll up to a new utility and you see, oh, they've got this API. Well, I'm a PHP developer, do they have a PHP library? And then they do, and then it's a nice PHP library because the people developing it are actually PHP developers, not like some Java dude who has lived in Java land who is trying to do the PHP and doesn't necessarily know the nuances of the language or whatever your language of choice is, right? Frameworks, same sort of thing. Absolutely release your frameworks. I would sort of put OpenStack in that category where it's part of their business, but it's not necessarily the most important facet of their business. So go ahead and release stuff like that. Same with modules. There are people that release all sorts of modules for all sorts of things and it's one of those things. Again, you never know who's going to benefit from something like that. So we got started a little late. Thank you so much for your patience with that. Hopefully you've taken something awesome away from this talk. I would love to hear your thoughts on it, so please feel free to reach out to me. Changing things in two places. So thank you so much. Are there any questions? No questions? Okay, we'll start over here. Sure, so the question was, are there any sort of utilities out there to help you release certain portions of your project? And the answer to that is maybe. So there are different package repositories. There's RubyGems and things like that that you can release or you could get into Composer with PHP. So there's all sorts of things like that that would help you. The downside is that you have to kind of modularize your things in order to ship them to people. But yeah, definitely. Or depending on how your app is architected is really gonna kind of determine how you do that. In the back, have we found that it helps us recruit? Actually, a little bit, yeah. We get people all the time. We actually have a core chef contributor on staff and he was like, yeah, this is kind of cool. Pedro is using chef, let's get a job there. So yeah, absolutely. Huge, huge recruitment tool. And I would encourage you, if you are interested in hiring developers, open source something and let them go nuts over it. There's another question right here. Some parts of the code might be covered by patents. How would you deal with that? That's really gonna depend on your company. I feel like that's getting into legal territory and you probably wanna talk to a lawyer about that. Would definitely encourage you to talk to a lawyer about that. But if it's your intellectual property and you've got a patent on it, patents are good for X amount of years. In theory, you should be able to release that and be covered by virtue of your patent because if somebody starts releasing stuff that violates your patent, you can go after them. And you see that all the time, people fighting over rounded corners and whatever in name crap, right? So yeah, you should be covered. Hopefully you will not need to sue anybody, but you might, would definitely encourage you to talk to a lawyer about that. Another question? So he's saying he has an issue with submitting patches that just kind of get into a black hole and how I would approach that. Getting permission to work on an open source project. So I have a policy of I don't ask for permission if it's open source, like I'm gonna submit a PR or I'm gonna hit a mailing list with a patch or whatever. And yeah, sometimes they get ignored. I've definitely been ignored by projects. Something that has worked for me is I just keep submitting something until someone pays attention. I get at people on Twitter, I will highlight them on GitHub or whatever, find the Slack channels or IRC channels that they're hanging out on and just kind of, I don't wanna say harass, but aggressively point them in the direction of my patch or my contribution. And that typically works pretty well. But yeah, sometimes it's unavoidable, especially if it's like a project that's not really maintained anymore. That's gonna be a lot harder. And that's probably getting into fork territory at that point. Do you have like a specific example? Oh, okay. Do you have a comment on that or? Okay, huh, good to know. Yeah, so specifically, good to know. Yeah, so specifically fighting your legal team to be able to contribute to open source. Honestly, in something like that, I mean, I can't very well say like, oh, we'll just go find another job. That's not feasible, it's not realistic. I would just keep pushing.  I feel like I have spoken to people, particularly at larger corporations where that's a thing, where the company has a policy that says, any source code that you write at work, even if it's in your spare time and touches anything related to work, like they have ownership of it, and they just keep fighting. And eventually some people will get an explicit like, no, you know, we own everything, you can't do anything, or we'll give you permission in writing to do what you want to do. Yeah, no problem. Any other questions? Last chance? All right, thank you so much.


Hello everybody, welcome back to another mid-journey tutorial. In this one, I'm going to show you how to take an image of yourself or anyone else and turn yourself into either a cartoon, an avatar, an oil painting, a charcoal drawing. I'm going to do it in about 60 seconds. A lot of tutorials out there, but they take too long. So let me show you how to do it. The first step here is you want to go to your Finder or your Explorer. Grab the image that you're working with. I'm going to use this one here. This is an image I just took off of Pexels.com. I'll put a link in the description below. I chose it because the image, the face of this person takes up most of the image and it's a neutral expression. You don't want to have a, if you're smiling and you've got an image of yourself smiling then it's hard for it, for the mid-journey to turn it into a frown or harder part of me. Okay, good. So we've got our image, the second step. I'm going to hover over it. I'm going to right click on it and I am going to go down here and select copy link. Once you've done that, you now go to the prompt line and type in forward slash image, imagine, space bar. Once you've done that, now you hit command V on a Mac, control V on a PC and we're going to copy in that link that we just copied on that image. Next hit space bar and this is the easy part now. You just hit space bar and then you type in what you want. So in this case, I'm going to go like cartoon avatar and hit enter. And while it does that one, all you got to do for something else is just go forward slash imagine, command V or control V, space bar and then charcoal. And then you get a charcoal drawing and it will do the charcoal drawing or forward slash imagine, command V, control V, oil painting. Of course you can make your prompts a little more detailed than that, but that is the entire technique in about 90 seconds most. Thanks for watching.


Good morning everybody, welcome back to another vlog. It is a cloudy rainy day today, which I am so excited about. It's actually supposed to rain for the next week or so, so I feel like a lot of upcoming vlogs you are gonna see are rainy and cozy. I'm sure a lot of you live in a normal climate where rain is maybe not something you look forward to or get excited about, but oh man, I love it. When I lived in Tennessee though, the rain would depress me a lot. Depending on when it was and how long it rained and stuff, it would get kind of depressing and I'd be like, when is this gonna come out again? So I fully get it, but living in a place where it doesn't rain that often, it's exciting. So I'm actually getting ready, as you can see by my hair, I'm fully ready to leave. I'm heading out the door here in just a few minutes because I am getting my nails done. I was actually gonna do it yesterday, which was the last vlog that you all saw when I was out and about. I just pulled my lashes like way too hard with that thing. That was not good, but they couldn't fit me in yesterday. So I am going today, it's like just before 10 a.m. I have no idea what I'm getting done, but all I know is these nails have gone way too long. I usually go like every three weeks, but these are just atrocious. They were really cute and fun while they lasted, like the fun sparkles, but we need to change it up immediately. I have one that's like basically coming off, so yeah, it's time. Maybe we'll look at Pinterest ideas or something like that and get some inspo that's typically where I will look for like nail inspo when I don't really know what to do. So maybe I'll do that. Just throwing on some mascara. I just have some like tinted moisturizer on, a little bit of concealer, bronzer. I actually do really need to wash my hair, which is why I'm gonna wear a hat when I go out today.  So maybe we'll do that here in a little bit. Not sure if that interests any of you, but that's exciting to me. I have been doing some editing this morning. I edited the last vlog that you all just saw and I have some main channel editing to do as well. So I'll do that when I get back, but it's so hard because when it's cloudy outside, all you wanna do is just like lay in bed and do nothing, you know, or like sit on the couch and watch movies, but I will persevere because the content ain't gonna edit itself. This mascara is not doing enough for me, so I need to add some more. I'm gonna add some. I was using the Maybelline Sky High Mascara, which is one of my favorites, but I feel like I need more volume, so I'm gonna add some of this Illia volumizing. I can't use the Illia one by itself though, because it smears like all over my eyes if I do. It's just not good on its own for my particular face. Anyway, I'm blabbing. Okay, let's see what we can do with this hair. There's still so much gel in my hair from yesterday. I have to be very gentle because I have extensions or something in my eye. And this is my hairstyle for the day. I'm gonna throw on some earrings. I'll just pop on some little gold hoops. What is going on here? I've got my little tank top and matching hoodie from Parallel Apparel. I did a main channel video reviewing like YouTuber clothing brands. And it's my first time wearing this one out today and then I just have my airy sweatpants on. These are really comfortable and they shed a lot, but they're cute.  Queen of the long intros here. Hi, welcome. All right, that, I tell you what, as a person with ADHD, going to the nail salon, oh my God. Going to the nail salon is like the largest test in patience. That took an hour and a half. I don't understand, it was just a fill. I'm so confused. It's like a hard gel fill, but the person who did my nails was very meticulous and did a great job, so no complaints here. Went for like a little blue moment, something springy and fun, why not on this just beautiful spring day. I was listening to the Back to the Beach podcast, which is the Laguna Beach rewatch podcast with Kirsten and Steven, loved that. But I actually think I'm gonna save some of those episodes because I have like a 12 hour plane ride coming up in a few weeks. And so I think I might like watch a Laguna Beach episode and then like listen to the podcast while I'm on the plane. That might be something fun to do. So yeah, I am going to maybe stop and get some lunch on the way, cause it's only like 11 40, but I'll probably get hungry in like an hour or so. So I might stop and get myself like a sweet green bowl, although I do have stuff to make that at home. So maybe I'll just do that instead. It's the biggest like freaking flex of control as an adult is knowing that you have food at home, but like wanting to pick up food when you're out. Anyways, okay, let's head home. All right, we are out of the bath. Yes, I did take another bath.  Like honestly, I think I sat in there for like two hours, almost, and I felt like no time at all. It's kind of concerning. But anyways, it's time to make lunch. I think I'm in the mood for, I think I showed this in a recent vlog, but I'm in the mood for like a spicy chicken sandwich, which is funny because I haven't made one since I made that vlog, but whatever. I'm talking like cafeteria style chicken patties. So I got these spicy chicken patties. I don't know if they're good or not. I'm gonna throw one in the air fryer and we're gonna have that for lunch. It just sounds really good. In case you're wondering what moves hyper fixation spot of the week is, it's here. Drew put a chair next to his desk. It was the couch in our bedroom for a while. It was the couch itself in our living room the last couple of weeks. It's sometimes under the covers in our bed, but as of today, he will be here for the foreseeable. And he's done not too. He's opened the closet to get excited about it. Stay in the life of Luke. I'm talking about you. Do you have anything to say? And look who's looking at.  But she's gone free. She did it. Let's go outside. Come on. All right, that's almost done. It has like less than a minute left. So I've already shown you this, but here's what I do. It's basically like a McDonald's McChicken, like a spicy McChicken. And we have this iceberg lettuce that I need to use. So first I'm gonna do a little bit of mayonnaise. You can't do too much. Maybe like a little bit. I mean, is that a lot? And then I actually like dip it in ranch.  We're gonna do a little bit of iceberg lettuce. That was way too much, but whatever. I'm gonna wait for that to come out. And then on the side, I'm gonna do a few baby carrots and some crackers and some bitchin' sauce. I was gonna do chips, but we're out of them. And also I want to use up this stuff. Oh, there it is. We'll do, these are the Simple Mills almond flour crackers. They're pretty good. So I'll do a few of those. And then we will put our patty. She's a beaut. I'm gonna do a little bit of bitchin' sauce. This is kind of a very random launch, but whatever. I'm still a little nervous of like what I've been eating because I did have an IBS flare up yesterday. I don't really talk about that a lot because it's like, you know. But if you have it, you feel me, you understand. So I'm just like, I don't know. For me, it's like sometimes things will be fine and then other times things will be absolutely not fine. So like, for example, I've seen some people say that like vegetables or super fibrous things or whatever will give them a flare up, but for me, it doesn't. And like, I've drank 12 ollie pops in the last few weeks and I've been fine, but now I'm convinced that like ollie pop is gonna, anyways, I don't know, it's a whole thing. But on that note, let's make ourselves an ollie pop. Let's see what we've got left. We have a ginger lemon. We have a tropical punch and a strawberry vanilla, I think. Tropical punch is like one of my favorites. So I think we're gonna go with that. I also love the orange something, orange cream, orange twist. I love the grape, I love them all. So, okay, we will put it in a cute little cup with some pebble ice, of course. Don't mind this jacket sitting on the counter next to me that is out as a reminder that I need to like repolish this or basically I washed it and then I bought some like leather conditioner and I only did one side of it and I need to do the other side. So, okay, we'll get to that. Oh, so satisfying, I love this ice. I'm in a honeymoon phase again with this ice maker, but when it ultimately breaks again, I'll let you did it again. There is our very thrown together lunch that I am going to quite enjoy while I watch some YouTube videos and then we will catch up and style this hair and see how it goes. It's a little while later, my hair is still wet. We're gonna go do it in a second, but I just got a call from Layla's ophthalmology office and her lab results came back and her tumor was benign, yay! So she doesn't have like any kind of cancer that we know of and it's unlikely to spread throughout the rest of her body. So that's amazing, so excited about that. She's cone free and as of really yesterday, she's been cone free and she's healing super nicely and I'm just like, ugh, I feel like I can finally take a breath and just breathe and relax some of the anxiety that I've had over the last week. It has been the most stressful seven days that I have had since probably like the pandemic when she got her leg surgery or maybe when she got her teeth pulled, I'm not sure, but anyways, I'm so happy. So, all right, anyway, just thought I would share that bit of good news. Let's do this hair. I'm determined, okay? All right, I'm determined to do like a cute 90s blowout today. If it's the last thing I do, I'm gonna achieve this look, okay? I've been trying for so long and I saw an Instagram video recently of like a tutorial and I was like, I'm gonna try that. I actually ordered a few products when I got my extensions that were recommended by the stylist. I use the Clarifying Shampoo and Conditioner and I really, really liked it, I'll show you. Not sponsored at all whatsoever but all of these pretty much are by Daveness, I think is how you say it. And so I use the Clarifying Shampoo called Salute. And then the like deep repairing conditioner called Melu. I don't know what these names are but anyways, these were both great, recommend them. And I'm also gonna do the Oy OI All-in-One Milk. And I think it's just like a leave-in conditioner. I think I'm supposed to actually just spray it on my hair. I'm gonna do a little bit of this. Oh, it smells so good. Oh my God. Does feel nice and hydrating. And then what I'm gonna do is use the JVN Complete Blowout Siling Milk and this is what I bought in the last vlog. I saw someone on Instagram use this and it seems really, really good. So you're supposed to apply it on damp hair.  It's been air drying for like, I don't know, the last 30 minutes or so. So I'm gonna do a little bit of that. Use like two pumps. I don't really know how much to use but that looks about right.  This feels very hydrating. So I'm confused as to how this will help with the blowout and like holding it. I feel like I definitely will probably need a mousse. We're gonna try. So let's see. And now we go in with the blow dryer. So I'm gonna blow dry my hair like 90% probably and then we'll go from there. All right, now we've got the rough dry done. I'm going to separate my hair which is gonna be hard because I have extensions and they're weird. I actually don't know if the extension life is for me.  I think I might get these removed pretty soon. It's only been like four weeks but I think I'm over it. I just, it's, it's not my favorite. So okay, we'll pin this up. Cute. And then we'll start with the bottom layer and we're gonna use the bigger of the two like curling bonds and we'll see how this goes. So sorry, this is loud but you take a little bit. Wait, this is so hard to do out of mirror. I'm using the viewfinder. I'm gonna do a little cool shot and then we have it. I'm just gonna repeat this so let's do it. Then you take the rest of the hair down and do the rest of it except the front section. So you like take the front section like this. We're gonna make a cute little bangs bun moment. Adorable, love that. And then do these top sections which I'm gonna need a mirror for so we gotta move this around, hold on. Let me like instinct wise that I should spray this because my hair doesn't hold blow dryer curls very well. It holds curling iron curls for literal days but we'll just try that. This is the Flex hairspray by Living Proof. Says medium hold, so okay. Then supposedly supposed to unclip the bangs and do them separately with the round brush attachment. I think my problem has been curling my bangs too tight so we'll see, I don't know. Okay, you know what? This doesn't look bad.  Just fun to try something different too, you know?  That's what I see people do. Awesome. I mean, this is cute. We'll see how this lasts. I will update you as time goes on but like not a bad, this is as close as I've gotten yet. There's like a couple random pieces that just don't really wanna hold but I don't think that, I mean, it looks pretty good. I'm gonna add some of this oil oil. This is from Daveness. I think this is just kind of like a finishing touch product type of thing and I just wanna keep it nice and like shiny and healthy looking especially these front bits that are like, you know, completely fried but that is pretty dang good. Like that's as good as it's been yet. So I'm happy, round of applause for myself.  Anyway, I think now is the time of night where Drew and I sit on the couch, watch Love Island, relax together, unwind and unplug. So I am going to leave you here. Thanks for hanging out with me today. Let me know how you feel about these vlogs that are kind of like all just in one day like hanging out with me for the day or if you prefer like multiple days in a vlog because I kind of like just hanging out in a day type of thing but let me know what you think. I'll link all of the products that I use down in the description box below to get this too by the way, in case you're curious. I do think a lot of it will have to do with like how my hair gets cut in the future because my hair is kind of like all one length but honestly not bad. Anyway, I'm gonna go. Thank you so much for being here and I'll see you in the next vlog. Bye.


Hi everyone, Sean with jaspyscasebreaks.com here doing 2021 tops chrome baseball 12 box hobby case break pick your team number four where all cards shit So here is our list of customers respect to teams from I can pull in the dimebacks down to Matthew froze in the nationals last spot mojo Andrea Smith Tigers Dodgers Red Sox. Thanks for closing it out And here's our case First part of this break is literally just gonna be me ripping open this case and pack stacking So if you are watching this on replay Feel free to fast forward to once I'm not stacking packs anymore for the good stuff or if you want to just see any super low-numbered cards All the autos and pretty much just the hits Like high like like I said autos and any really low-numbered cards Just click in the description of the break and you'll see a little thing that says recap of the time stamp Hopefully that time stamp works if you click on that and it should take you directly to it But if it doesn't go ahead and just fast forward to the whatever that time stamp says and that should be able to Give you just the nuts and bolts of it If you're watching live, they're stuck Cubs were up six to nothing in the top of the first inning is now the bottom of the third Man on first the White Sox are now tied six Six it has turned all the way around no longer happy times right then Make me a bicycle clown No matter what way around it. There is no fast way to do a hobby box case the amount of packs Packaging overall So hunker down pour yourself your nicest drink Maybe it's milk go grab cookie Andy. How are you? I am good. How are you? Then they do that in jumbo jumbo is already like that. It's a it's a 12 packs to the box Considerably more pat like hard things like 13 cards a pack and it is it is a lot faster The whole going through the cards isn't different. It's just the Packaging is the hard part on hobby Lou Bob up will demand on first and second Lou Bob flies out to shortstop. No error Andrew Vaughn scores Robert now on third Anderson or no Anderson on third Robert at first on an error. I agree Ben Rex sold out nice. Good job on Andrew Vaughn and Tim Anderson not hustling to keep hustling Scored and scored from second third from first Ben's overest Slow mo on his eyes. Just realizing He's dropping the ball. He almost wreaked almost recaught it in the air After a bounce out. Is this is is this 99 already? He's incredible, man. I mean Coming off an MVP season Mentioning something about 100 RBI, but I thought he had already hit it tonight People are booing them like they're like he tried to hit them on purpose. It's like no You're not loading up the bases that pitching coach looks so young Who's the only picture who is that? Who's the cubs of pitching coach? Score two. I was just wanting to find out. I don't think the modern-day Duncanville game is on TV tonight You don't really get any Any break with this lineup? It's just problem after problem after problem over there Three runs to my eight after the remainder is even my favorite card that I've ever pulled It's a really tough question I feel like every week I pull a different card that could be my favorite card that I've pulled I pulled a Mike Trout Super Fracture from last year's Top Scrum. That was really cool I pulled a triple auto of Hank Aaron Mike Trout and Ken Gryffin Jr. That was pretty cool I pulled six or seven logo men now. I'm a Chargers fan So every time I pulled Justin Herbert, which happened way too often. I'm happy about that All the NTRPAs, plus RPAs, macular RPAs, all that stuff Hey Andy, what's your favorite card you've ever pulled? Each Euro auto from 2020 Top's Heritage? Nice Was it one of the Red Ink? Real one? Numbered ones? Or... Either way, that's incredible. I think my best heritage pull personally was a Peter Lanza Real One Rookie Auto out of a 2019 Heritage High Number I'm a big fan of high numbers And did your churro come out of the first release, the regular heritage, or did it come out of Heritage High Number? Two out of five. Oh Andy, was it in Red Ink or was it a was it? Different. Release Blue Ink? Okay. That's very cool. Is that a personal collection thing for you from? Or is that something you would turn over and go for something else? 317 Top's High Number, Jersey Auto, Hand Number, 25 Elendor It's always cool when like you pull something that's great, but it also happens to be your PC Yeah, Dan, that first one's crazy 17, Cisco Elendor, Jersey, Raleigh, and Auto out of 25 Hand Numbered. I think that's what I like about the Heritage 2 is the hand numbering That's why I wish my Peter Lanza was a, I wish it was like the Red Real One Red Ink Auto Because those are hand numbered, I'd like, I think 71 for Peter Lanza was here Remember going to Tempe Diablo Stadium Each hero's rookie year with my dad To try to see him in person and maybe get an autograph. We're Angels fans Since they shared the same facility back then, it wasn't Tempe Diablo at the time We went down there A lot of it was pretty cool. I know that Otani Mania was pretty big, but like I feel like when Yuchiro came over I feel like that was monstrous. I feel like that was just crazy how people were looking forward to that Yeah, yeah, that hand numbering, just that little extra touch Andrew Vaughn, home run? No. Wow, what a catch. I don't think it would have been out anyways, but So since this is Hobby We have three more boxes to rip after this. We'll go through some things we're looking for Hobby, two autos per box, the 12 boxes. Should have 24 autos in here I think the captain's cloth, I know in Jumbo If you hit a captain's cloth auto, it ends up being an extra I'm not sure if it's the same for Hobby or if that replaces an auto in this They're very cool Roberto Clemente cut auto Andy Well now that you, I know that you're looking for Roberto Clemente. I have pulled two Roberto Clemente cut auto one of ones so Up your alley, that's those are probably two of my coolest. I forgot about that Yeah, I pulled two Roberto Clemente cut auto one of one. It never gets old either I was kind of like, I remember the first one. I was just absolutely speechless. I was like, oh Just happened Speaking of it, we've got it in store museum collection.  I Pulled that that Tatis bat barrel signature bat barrel one of one Where it literally has his name. It's not an autograph, but it's his autograph like Engraved in the bat in gold ink or gold. So I pulled that earlier this year. That was unreal Um, I forget what they're called But those ridiculous booklets obviously have the frames which are cool, but the The booklets that have like the the team's stadium in the background like that stuff is Museum collection might be one of my favorite sets from this year. I know diamond icons is like Super high-end. Oh, no And like just unreal but museum collection such great stuff Two boxes left guys. That's it Almost through the labor portion to the point where we get to enjoy The fruits of our labor wisdom has a really sweet mustache right now going 80s 80s cop mustache going right now. It's pretty spectacular Dude wearing a nice Walter Payton jersey in the background of the game. Maybe he's a fan of the Cubs and White socks the Walter Payton nice and neutral Walter Tony the roosa has a pretty Pretty big chain around his neck That's over chain Lou and Diaz shoelace from macula. That's really cool. Yeah, those are I like that. I pulled a From diamond icons. We're just talking about it actually For a customer over on Instagram did a personal box of diamond icons. I pulled a max Scherzer Jumbo cleat and it was like the spike from his cleat the card was the largest card I've ever seen For just being one person like one card It was like that thick. I have to be like that thick the entire card They had to go into like a hundred count card Card box by itself It was super cool Okay, last box to rip guys We did it you have made it through Yeah, it was very cool. Hi Steve I mean As a socks fan. Yeah, but he's still Mario Rivera unanimous Hall of Famer. That's pretty awesome. Cool. Good luck everybody Let's get started Patrick Corbin for the Nationals Dylan Carlson Cardinals Louise Robert White Sox Charlie Morton Braves Jazz Chisholm Marlin and Christian Javier Astros Rod Carew twins Jose or Jorge Alfaro for the Marlins Nick Madrigal White Sox Ryan Mountcastle Orioles Dylan Cease White Sox Blake Snell for the Rays Dane Dunning Rangers Edgar Martinez Marlin Mariners and Jake Cordenworth Padres Garrett Crochet White Sox Patrick Corbin to 399 for the Nationals that is Matthew Fros and Joe Adele for the Angels Daniel Johnson Rookie Otto Indians Emma Warwick Jake Cronin worth refractor Padres Brandon Lau Rays Wilson Contreras Cubs Ryan Mountcastle Orioles no Cinder guard Mets Aaron Judge Yankees Dalton Jeffries A's Otto I capola remember guys all card ship Eduardo Escobar Diamondbacks Kyle Lewis Mariners Devin Williams Brewers or a passata Yankees Clory Cleaver Rangers Xander Bogart Red Sox Dalton Jeffries again for the A's I capola Yasmani Grandal White Sox Ramon Loriano for the A's Wilson Contreras for the Cubs Christian Pache Braves Jose Ramirez Indians and John Carlos Stanton to 3 50 for the Yankees That is Bennett Page Acunia for the Braves Joey Bart for the Giants Willie Castro for the Tigers Alec Bowen for the Phillies Spencer Howard for the Phillies Joe Adele for the Angels Max Muncie for the Dodgers Labor Torres Yankees Roldus Chapman Yankees Peter Lonzo Mets And Luis Vasabe to 499 Rookie Otto for the Giants Lee Cheesman Sam Huff to 299 for the Rangers Jose Arias and Jack Peterson for the Dodgers Alec Bowen Phillies Sean Murphy A's And Ian Anderson Braves Tati's Padres Kebron Hayes Pirates Trent Grisham Padres Will Meyers Padres DJ LeMay Hew Yankees Zach Gallin Diamondbacks Shane McClanahan Ray's Starling Marte to 99 for the Marlins I capola Dylan Carlson Cardinals Gavin Lux Dodgers J. Croneworth Padres Luis Camposano Padres Luis Arias Twins Yoanman Kata White Sox Jackie Bradley Jr. Red Sox Jazz Chisholm Marlins Jodell Angels Luis Gonzalez White Sox I capola Garrett Crochet Christian Javier Astros Alex Redugo Red Sox Reese Hoskins Phillies Brandon Lau Reyes Ryan Mount Castle Orioles Nico Horner Cubs Kyle Seager Mariners Jack Flaherty Cardinals Vlad Guerrero Blue Jays Kiraoui's Dodgers and nice Jake Croneworth to 25 Padres There you go. That is Brian Peeples Aaron Judge Yankees And you get a redemption. It's Keegan Aiken for the Orioles rookie autograph Orioles Ryan Dupuis Jorge Solaire Royals Ryan Mount Castle Orioles and Gio Urchella for the Yankees Very nice Croneworth here Orange out of 25 Brian will be pleased Wish it was the base We've still got another nine boxes for them Rod Karu twins Jean-Carlo Stan Yankees Kevin Newman to 99 Pirates Ryan Dupuis, Casey Byes, Tiger Humberto Mejia, Diamondbacks, I capola Shogo Akiyama for the Reds Christian Pache braves, nice hyper there Edgar Martinez Mariners Dee Dee Gregorius Phillies Kyle Lewis Mariners William Contreras braves Otto J.C. Uba max freed braves Casey Meyes, Tigers Jordan Alvarez Astros Andres Jimenez Mets Brady Singer Royals Jazz Chisholm Marlins Nick Silak Rangers Ramon Laureano A's Jesus Sanchez Marlins Rafael Devers, Red Sox Jared Walsh, Angels Mike Trout, Angels Mike Brousseau Reyes Ryan Mount Castle Orioles, Joshua Bell Pirates Starley Marte Marlins and Kibriane Hayes Pirates Joey Vark Giants, Dylan Cease, White Sox Alec Bohm, Phillies, Kibriane Hayes Pirates, nice refractor Joe Adel, Angels, Christian Yalich Brewers Devin Williams Brewers And Jacob DeGrom, Captain's Cloth Mets, Richard Miller Evan Longoria Giants Andres Jimenez Mets Garrett Cole Yankees Matt Olson A's Ozzy Albys to 399 Braves, J.C. Uba Shoya Otani, Angels Kyle Lewis Mariners Alex Kierloff Twins Joey Gallo Rangers Marcus Simeon A's Fernanna Tatis Padres Matt Chapman A's Andres Jimenez, Indians Ali Sanchez, Otto for the Mets Richard Miller Charlie Morton, Braves Carlos Santana Royals Kettle Bartay, Diamondbacks Jake Cronilworth Padres Kenta Mayeda Twins out for the season apparently Juan Soto Nationals Bummer And Luke Voigt Orange out of the 25 Yankees Bennett Page, Mike Trout, Angels Ahmed Rosario, Mets Sonny Gray Reds Jacob DeGrom, Mets Nick Madrigal, White Sox out of, very nice Icapola Jazz Chisholm, refractor for the Marlins Jose Ramirez, Indians Matt Olson A's Byron Buxton, Twins Joey Bart, Giants Alex Kierloff, Twins Mike Russo, Reyes And Mike Trapp Captain's Cloth Angels, Nick Stover George Springer Astros I get excited every time I see one of those Captain's Cloths because it's turned around Jock Peterson Dodgers only once has it so far Jesus Lizardo A's Garrett Cole Yankees Nolan Aronado Dillon Carlson Cardinals And Alex Vesia 499 for the Marlins Alex Kierloff refractor, Twins Max Scherzer Nationals Jose R. Kitty Luis Arias, Twins And Juan Soto 250 for the Nationals Sixto Sanchez Marlins That Juan Soto Matthew Frozen, Nationals Jazz Chisholm Marlins Jesus Lizardo A's Lance McCullers Astros, Bobby Dahlback Red Sox Isaac Paredes, Tigers And Yon Mancada, White Sox Half-Guys Homestretch John Lester Cubs Luis Garcia Nationals Zach Gallin Diamondbacks Salvador Perez Reyes, sorry, Royals Ryan Mount Castle, Horials Geo Urchella Yankees Vlad Guerrero Blue Jays, Charlie Blackman Rockies And Gold Wave, Ryan Braun to 50 for the Brewers and Brian Queen Red Sox Otto Patrick Weigel for the Braves And J.C. Huber Christian Yellich Variation Brewers D.J. Mayhee Yankees I'm trying to remember which players off the top of my head have J.M.I.J. Variations Garrett Cole Yankees Trevor Story Rockies Jake Cronenworth Padres Gavin Lux Dodgers Nick Madrigal Refractor White Sox Alec Vom Fillies Glaver Torres Yankees Tyler Stevenson Reds Christian Pache Braves Alec Vom Fillies Joey Bart Giants Ollie Sanchez Otto Metz, Richard Villa Alec Vom Fillies and Nolan Aronato Negative for the Rockies Chris Davis A's Max Muncie Dodgers Joe Adel Angels Nico Horner Cubs 6-0 Sanchez Sox are now up 13-6 Remember, they spotted the Cubs 6 runs in the top of the first inning They have now scored 13 unearned runs and are now winning 13-6 Oof Holy shit Cubs It is only the bottom of the fifth as well Andrew McCutcheon Fillies Joe Adel Angels Rhonda Cunha Jr. Braves Jordyn Alvarez Astros Tony Gonslin Dodgers Kyle Schwerber Cubs, Kibriane Hayes Pirates, Yasmine Grandal White Sox Mark Khanna Hayes 9-9 for the Rockies Jonathan Rinaldi Alexander Bogarts Red Sox Alex Vesia Marlins, Ikebola Cody Belanger, Dodgers Joe Adel Angels Hyper Nick Solback, Rangers Miguel Cabrera Tigers Devin Williams to 99 Brewers, Brian Kling Tatis Padres Jake Arietta Fillies Nate Pearson Blue Jays David Ortiz Red Sox Matt Chapman Pete Alonzo Metz Another Orange coming up I think it's an Otto It is nice Alejandro Kirk Rookie Otto For the Blue Jays Ikebola That is 13 out of 25 Nice Orange Otto Christian Pashé Braves Joey Gallo, negative for the Rangers Dalton Varshow Diamondbacks Joey Gallo, Rangers, Jose Arias Joey Bart Giants Michael Conforto Metz Alec Bone-Fillies Cody Belanger, Dodgers This feels like a game for the Cubs that will go to go to positional pitchers Right? Like, they're down 13 to 6 now They were up 6 to nothing They've given up 13 straight runs Anthony Rendon, Angels Bobby Dahlback Red Sox, Christian Pashé Braves That is a That's a Christian Pashé image variation There you go J.C.Uva and the Braves Andres Jimenez, Indians Doesn't that look different than his base pair? Willie Castro, Tigers Very nice image variation Leody Tavares, Rangers Labor Torres Yankees Dillon Carlson, Cardinals Ronald Acuna Jr. Braves Chris Archer, Pirates Juan Soto Nationals Boba Shet, Blue Jays Yoneman Kata, White Sox Anderson Tejeda, Rangers Juan Gonzalez Rangers Will Myles Will Myers Padres I'll show you how it's on, Angels Brandon Belac, Astros That is Icapola Justin Verlander, Astros Ryan Mountcastle, Orioles Brady Singer Royals Jacob Bagram, Metz Clark Schmidt, Yankees And to 1.50 Sorry, to 75 Cubs, Jonathan Arnaldi Brady Singer, Royals Second Auto Blake Taylor Icapola Manny Machado Purple to 2.99 Padres Brian Peoples Bobby Dahlback, Rookie Refractor Red Sox, Andrea Smith Brandon Crawford Giants Tony Gonsolin Dodgers Red Sox Ahmed Rosario, Metz Christian Pache Casey Meyes Tigers Joey Bart Giants Brustal Graderal Dodgers, Alec Bowen-Fillies Buster Posey Giants Jodell Angels Tim Anderson, White Sox Tatis Padres AJ Puck Hayes And Lucas Julito to 1.99 for the White Sox Icapola Kyle Lewis, Mariners Randy Razerayna, Reyes Xander Bogarts, Red Sox Josh Hader, Brewers Alex Kierloff, Twins Kettle Marte, Diamond Becks Yesbondi Grandal, White Sox Mike Trout, Angels Xander Bogarts, Very Nice Red Sox Andreas Smith, Last Spot Mojo That is numbered out of 50 27 out of 50 Xander Bogarts Shirt and Apostle Rangers Alejandro Kirk, Blue Jays Rhys Hoskins, Phillies Ozzy Alves, Braves Caberain Hayes, Pirates Luis Garcia Astros, Icapola Luis Garcia, Nationals Eloy Menez, White Sox Brenda McKay, Reyes Whoa, whoa, whoa Rex A little bit too early for that I know you're not saying anything overtly wrong, but all it takes is a Google search And then Joe's Joe's Fielding Complaints from Concerned Moms You know Do you know what somebody in your chat told my son to look up? Ronald Acuna Jr. Braves Buster Posey Giants Ryan Mountcastle Orioles Luis Robert White Sox And Shirt and Apostle To 150 Otto, Texas Rangers Jose Arias Nice one Albert Pujols Angels Joey Bart Giants Randy Razerena Reyes Lucas Chilito White Sox And nice Joey Bart Awkwit to 199 For the Giants Lee Cheespen, Luis Garcia Nationals Brandon McKay, Reyes Garrett Crochet, White Sox Dylan Carlson, Cardinals Juan Gonzalez, Rangers Tanner Hout Red Sox K. Bryan Hayes, Pirates That's an image variation too Nice Another rookie image variation Pirates, Ryan Dupuis Patrick Weigel Braves, JC Uwe Rookie Otto And Mike Trout, Negative Refractor Angels, Dick Stover Kyle Tucker, Astros Christian Pasche, Braves Marcel Ozuna, Braves Matt Olson A's George Springer Astros Jake Cronenworth, Padres Luis Robert White Sox Shinsu Chu Rangers Marco Gonzalez Mariners Rex that's just going to make them even want to look even more Who doesn't like the the moonwalk things You know Okay one box left We've made it guys You can see the summit We're here Quick recap After this and then it is in the books Cody Bellinger Dodgers Ryan Mount Castle Refractor Orioles Sixto Sanchez, Marlins Broussard Granaral Dodgers Jacob Igram Metz Jazz Chisholm Marlins Max Freed, Braves Boba Shet, Blue Jays Bobby Dahlback, Red Sox Leody Tavares, Rangers Joey Bart, Giants Cody Gonslin Dodgers Paul Goldschmidt Cardinals Dylan Carlson Cardinals Trevor Storey Rockings Half box left Two autos to go Alex Kierloff Twins Jose Altuve Astros Jose Abreu White Sox and Chris Bryant Little Blue Waved 75 Cubbies, Jonathan Renaldi Jacob DeGramm Metz Alex Vesia Marlins Auto Iconic Chris Paddock Padres Dee Dee Gorries Phillies Juan Soto Nationals Tristan McKenzie Indians Nolan and Auto Cardinals Tristan McKenzie Auto to finish it off Indians Emma Warwick Keston Herea Brewers Anthony Rendon Angels and that finishes it off Little Recap then I like Tristan McKenzie's Auto Sure Clearly know exactly you know Alex Vesia is actually pretty clean too Okay, recap time Here is our autos Alex Vesia Marlins Tristan McKenzie Indians Patrick Wagle Braves Shirting Apostle Rangers to 150s Andrew Bogarts to 50 for the Red Sox Luis Garcia Astros Brandon Belock Astros Blake Taylor Astros Alex Vesia Marlins Alejandro Kirk to 25 for the Blue Jays Patrick Weigel Braves Alessanches Metz Nick Madrigal White Sox Alex Vesia Refracted to 499 for the Metz or sort of the Marlins Luke Voigt Orange to 25 for the Yankees Alessanches Metz Humberto Mejia Diamondbacks William Contreras Braves Luis Gonzalez White Sox Iconic Auto Orioles Redemption Dalton Jeffries A's Luis Vesave to 499 Giants Dalton Jeffries A's and Daniel Johnson for the Indians We had two captains claw Mike Trout, Jacob DeGrom Neither one numbered We had an Orange out of 25 Jake Cronenworth for the Padres Not the base but an insert in two image variations both Brookies for the Braves Caberain Hayes for the Pirates So there you go guys That is the break That was 2021 Tops Chrome Baseball 12 Box Hobby Case Break Picker Team Number 4 from jaspyscasebreaks.com I'm Sean, jaspyscasebreaks.com Thanks for hanging out, we'll see you next time


A man who was jury found guilty of aiding in the murder of Bemidji's Rose Downwind has been sentenced to 16 years and nine months in prison. Brandon Rosbach was sentenced in Beltrami County Court today by Judge Paul Benchhoof. In October, jury found the 32-year-old Rosbach guilty of helping Downwind's former boyfriend, Marcello Simerusti, burn and bury her body. If you've enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland Public Television.


Welcome to this course on Transition Metal Organometallics in Catalysis and Biology. We have been discussing olefin polymerization over the last few lectures. In particular, we have been focusing about various topics, various aspects of propylene polymerization or polypropylenes. In this regard, we have noted that in the previous lecture that Ziegler-Narder catalyst can also polymerize propylene. One of the main questions that remained at that time about Ziegler-Narder polymerizing propylene is the fact that the polymers obtained were isotactic in nature and the polymers were connected in a head-to-tail linkages. Let me illustrate this as follows. What is important to note is that propylene were polymerized with aluminum chloride or Ziegler-Narder catalyst to give isotactic polypropylene, which is a polypropylene or IPP. The second thing, which at that time was difficult to understand is this head-to-tail linkages of propylene units. These can be illustrated. This is one unit, this is another unit. These are head-to-tail linkages of this propylene unit. These are the two aspects that needed explanation in trying to understand the Ziegler-Narder polymerization of catalyst. The explanation came in the way of two things that these TiCl3 crystals are supported by MgCl2. The active catalyst actually is chiral in nature, where it has a sigma vacant site adjacent to a transition metal polymer bond. This can be explained as such. Fluoride is supported on a magnesium chloride crystal, where there are two sites. One is the polymer chain, which is bound to titanium. The other is the vacant site. Overall, what is to note is that overall that is chiral site that allows for enantiofacial discrimination of propylene to give isotactic polypropylene. This is the first explanation to the observation that polypropylene is isotactic in nature. This is illustrated by the approach of olefin, which can be either this with the methyl group on this side, or it can be this with the two possibilities of which one possibility is favored. This one is favored, and this approach is not favored, resulting in room for enantiofacial discrimination of propylene to give isotactic polypropylene. The other thing that we had discussed that leads to the formation of head-to-tail linkages is the fact that there is a vacant site present to the polymer titanium-carbon bond. There is a presence of a free coordination site to titanium-carbon bond, and this is what allows for this head-to-tail orientation. Head-to-tail linkages is dictated by that. One thing about Ziegler-Natta polymerization is that the polymerization happens on TICL food supported over MgCl 2 crystals, and hence this is Ziegler-Natta polymerization one attribute it, this is the multisite catalyst. That means that there are many active catalytic centers which are present, which carry out polymerization. As a result of this presence of multisite catalyst, the polymer so obtained become broad molar mass distribution or high in short high Pdi, polydispersity index, so that means that the polymer has a wide range of molecular weight distribution, that is what it means in short. To have more well behaved polymers of uniform property, then the need became for developing a single site catalyst for obtaining Pdi, polydispersity index, single site catalyst were developed for obtaining a narrow distribution, a single site catalyst were developed. That lead to another set of discoveries geared towards developing single site olefin polymerization catalyst. In this context, the Nata system of this titanium dichloride is what provided the first initiation towards this end. The catalyst was titanium with Al2, Et2, AlCl, so this was provided by Nata in 1957 and this is the first single site homogeneous catalyst for ethylene polymerization. This catalyst had low activity for ethylene polymerization and could not match up to the heterogeneous TiCl4 diethylaluminum chloride catalyst, which is the Ziegler Nata original system. It has low activity and second thing is that this also could not polymerize alpha olefins. This thing was like no match up for the Ziegler Nata heterogeneous TiCl4 diethylaluminum chloride catalyst, but nonetheless there are two advantages to this system, which are to be noted here. The first is that this is the single site catalyst, this is the advantage number one, and the advantage number two is that this is also a homogeneous system, so that means that the polymer of low Pdi and much well behaved. So these are the two advantages of this system, despite the fact that it had its own problem like the activity was very low and could not polymerize alpha olefins, these are sort of the drawback for this system. Now then another following Nata's observation, there was another noted contribution was made by Kaminsky in 1980, who reported high activity with MAO or methyl alumina alumino oxane. So at that time the structure of MAO was not known and this MAO was obtained by partial hydrolysis of non-uniform and structurally it was not uniform, non-uniform structure of MAO arises from partial hydrolysis of triethylaluminum. At that time this is what led to enhancement of reactivity for homogeneous catalysis, which is originally reported by Nata. Now following this discovery or MAO applications can be very much engaged from the fact that the corresponding zirconium dimethyl catalyst produced 500 kg of polyethylene mole of zirconium per hour of catalysis. So this is a highly active catalyst with MAO, the zirconium dimethyl thus became highly active catalyst that could produce 500 kg of polyethylene mole of zirconium per hour, that is a huge activity. This was even tremendously exceeded the results under zirconium conditions, conventional conditions in contrast this conventional exist under zirconium nada conditions. So here now we have a which is a heterogeneous system, so here we have a homogeneous system catalysis which could beat the heterogeneous system, so this zirconium MAO dimethyl could beat these conventional zirconium nada conditions under homogeneous system. Now this catalyst was also moderately active for alpha olefins and the product was atactic. The catalyst also moderately active for alpha olefins and produced atactic polymer and this was not surprising given the fact that this is a chiral molecule. The next important discovery was made by Bilsinger as well as even who produced isotactic polymer using chiral resolution one at low temperature and other using chiral derivative. So, that was the first development towards using homogeneous catalysis to produce isotactic polymer as was obtained using heterogeneous zirconium nada system, so isotactic polypropylene was obtained by first even in 1984 in presence of diphenyl titanium myocatalyst at minus 30 degree centigrade, so the low temperature was given, so that more ordered formation could be formed and the second by Bilsinger in 1985 using chiral and zirconium derivative, this is given as polypropylene in toluene 60 degree centigrade and the catalyst is this is a ansa catalyst zirconium is chloride and this gave isotactic polypropylene with the catalyst is to MO 1 is to 300 ratio and MO is given as Al methyl N, so with this we come to conclusion of today's talk where we saw that the development of chiral homogeneous metallocene catalyst that could give isotactic polypropylene under homogeneous condition in presence of this chiral catalyst and MO in large excess of MO about 1 is to 300 ratio and could be used to make this isotactic polypropylene, isotactic polypropylene could also could be obtained using this catalyst under very low temperature as reported by even, so with this we come to the end of today's discussion on the development of catalyst for producing polypropylene, what we had seen that which started off from a simple basic question as to why the heterogeneous zyglarnut and titanium tetrachloride diethylaluminum chloride was producing an isotactic polyethylene to the understanding of which lead to the understanding that it is a multi site catalyst and that a result the polymer obtained were broad and less well we had which lead to the focus on a single site catalyst and the first single site catalyst for ethylene though of low activity was reported by Julio Nart in 1957 using titanium dichloride and ethylaluminum chloride which could polymerize ethylene but could not polymerize any alpha olefin subsequent contribution by Kamensky which who came up with this aluminum oxane reagent by this is a non uniform structure obtained by partial hydrolysis of diethylaluminum lead to high activity reported for ethylene polymerization using zirconium B.C.P. zirconium dimethyl which could even surpass the results obtained from homogeneous heterogeneous zyglarnut conditions and they could also polymerize alpha olefin now subsequent to that further development as reported by even for propylene polymerization at minus 30 degree centigrade or the famous Bridszinger's 1985 chiral and zirconium catalyst which in conjunction with MO in 1 is to 300 ratio could give isotactic polypropylene similar to that with obtained with zyglarnut system so these catalyst is extremely active and could produce about 43000 kilogram of polypropylene per mole of zirconocene per hour per hour and as a result about 50,000 Dalton polymer could be grown in 3.8 seconds so this is a tremendously active catalyst which was producing so huge amount of polypropylene under such conditions so with these we come to an end on today's discussion where we have seen how the evolution of single site catalysts from multi site catalysts to place during a polypropylene polymerization how the focus shifted and how eventually the homogeneous catalyst could make a more well behaved narrow distributed polymer with much more activity higher than that of the heterogeneous conditions using suitable modifications on the metallocene system so more on the catalyst development this will highlight some of the interesting struggles that have been taken up by organometallic chemist in coming up with ideas that could lead to further enhancement of this polypropylene catalysis attributes which will be discussed in the subsequent class so more of these interesting stuff ahead as we go on discussing about the catalyst development in polypropylene polymerization chemistry so with this I once again thank you for being with me in this lecture and I look forward to have some more interesting discussion on propylene polymerization when we meet next till then goodbye and thank you


Welcome to Toffy TV, here is the math reaction. Everton won Manchester City 3 tonight at Gooderson Park, just back from the game. It's frustrating the way the game finished. I don't think Manchester City were a 3-1 better than Everton today, but yes, they controlled large portions of the game. Yes, they're fantastic to watch, they certainly are, but Everton had a good go with it and Edderson's had to make three really good saves at crucial times in the game. That's the tip, the balance, Manchester City's way. Marco Silva made a couple of changes before the game. Theo Walcott coming in, which surprised everybody. Obviously, Bernard was missing through illness. Luca Dean passed a leaf fitness test, he was doubtful as well. Obviously, he went with Brought, Guilffy Sigurdd, Morgan Snidel and back into the side, Dominic Alvert Llewyn. It started up front as well. And obviously, within a minute, we lost Theo Walcott, Raheem Staling's cross hitting him in the side that I had, and he had to go off to hospital. He was replaced by Alex O'Wobee, who came on and didn't quite get into the game. Showed some good moments for a fantastic ball in to Guilffy Sigurdd, and he should have done better just before half-time, but he didn't really impose himself enough on the game, Alex. But City started brilliantly, and should have scored early on. I think it was going the one hitting the ball somehow against the crossbar when it looked easier to score. But then they did take the lead with a wonderful cross from Kevin De Bruyne, an incredible cross. Gabriel has used Steve to head in after about 23-24 minutes, and we were behind. And they had a measure of control about them sitting at times. We couldn't get near them early on in the game, stroking the ball about. But everything did start pushing on a little bit, and occasionally, when we broke out and were able to load men on the edge of their box, we had a little bit of joy. We got level after some brilliant work from O'Wobee, and Seamus Cullman, and a lovely little dink by Cullman. I was going in, don't want to call the living made sure, but when I watched the replay, a half-time on the monitors in front, it looked as though the City defender may have cleared it off the line if Don wasn't there. So we did well following it up, and that's his fourth goal in three games, so it gave him a great boost. And we almost, you know, we could have got in front, like I say, great ball by O'Wobee and Tickets, and instead of trying to just get something on it and help it go, try to control it, I think, and it went behind him, and the opportunity was gone. But you know, we went in at half-time, one-one, I thought we'd done alright. We come out second half, and they got control over the game, but they just didn't really create many chances in that second half. Jordan Pickford relatively untroubled in the game. Raheem Staling was an absolutely brilliant opportunity, put it wide, a great through ball, and he slid it wide, he should have done better with that one. At the other end, we had a Gary Mina header, which Edison done brilliantly to tip over the bar off a free kick. City then got in front, you know, a little bit of a lucky ricochet, he won a free kick, I did a box on Mars, just keiled it in front there into the bottom corner. I hadn't seen it again, but at the time, I thought Pickford should have done better. It was over his side, you know, the wall was one side, and it's gone past them a little bit. The way Christian Eriksons went in, the last game of the season, it spares on a bit the way Ryan Fraser fired it in the other week. I know that hit Delft, but you know, sloppy goal to concede in City. You know, we're back in front, but we had a great chance again, carved out a lovely little move. Got Dominic Alvertley when he made Edison, he should have done better. He should have dinked it over on the way called, and he called the foot of Edison, and it went wide for a corner. We then have another opportunity, Eri Mina, with a header, and another brilliant save by Edison and Dom, couldn't product home. And then City break and Raheem Staling wraps the game up really, smashed it against the underside of the bar, the referees are on buzzers and it was over the line. And that was it really. Man City had a couple of opportunities possibly to extend it. I thought overall, we give a good account to ourselves. I can't make any kind of claim that we deserve to win the game, but to draw possibly would have been a fair result. Just on chances created, obviously City have had 20 shots a goal. They've had obviously 63% of the possession, so it's a weak case I reckon, for a point. I know you see that on other days, but I think much improved from last week's horrible performance against Sheffield United and the week before against Bournemouth. It's a defeat, I'm never happy with the feats. We've lost four of the seven games, which is slightly alarming, but I feel as though this one against the top, top side is a little bit easier to take than the last couple. That doesn't mean that the manager shouldn't be getting questioned. We've lost three games on the run, which to me isn't acceptable at the Premier League level. And we've got a massive game now next week at Burnley. We've got to go out and show the same fight in the termination. A special mention today for Dominic Halbert-Lewin. I thought he did really well. I thought he did well. I believed there's a couple of people saying he was terrible. I don't know what game they were watching. It wasn't the same game I was watching. I thought Seamus Coleman was excellent as well today. We've lost a game 3-1 against, for me, the best football onside in the league. That's it, we've got to dust ourselves down and go again next week at Burnley and roll our sleeves up and try and get a result. Because if we lose at Burnley, five defeats in the opening eight games is a shock and return for a side that has had money spent on it. We shouldn't be losing to Bournemouth, Shringershep United and Burnley, in my opinion. There you go. That's it. That's there my thoughts. Let me know in the comments what you think. Subscribe if you haven't. Give the video a thumbs up. And if you want more videos, get over and join us on page and check out the exclusive Dan Mice interview over there. Thanks for watching. See you later.