Acid plus carbonate reactions are another example of a neutralization reaction, and that's because one of the products is water. Again, as we did with the previous examples, we will look at a general equation and then a specific example of that general case, and then we'll split things up into ionic equations to see what's happening for these types of neutralization reactions. So when we look at the reaction between an acid and a carbonate, we have a salt and water, which are the same two products that we got from our acid plus base reaction. But in addition, this time we also produce carbon dioxide gas. So when this reaction occurs, you will see bubbling or effervescence, and that's an indication of the presence of a gas. Of course, we can then test for the presence of that, for the actual identity of that gas using the lime water test, which will tell us that the gas that's being produced is actually carbon dioxide. So let's look at a specific example. Again, we'll choose hydrochloric acid, and this time sodium carbonate. So when we do this example, HCl in solution with sodium carbonate in solution is going to produce water, H2O liquid. Plus carbon dioxide, which is actually going to be a gas. And then the salt as previously will work out. Again, we've got the cation, which is coming from the base. I'm going to shock it here. There we go. There's green. Beautiful. There's the cation that's coming from the base or the carbonate in this case, and the anion, which is coming from the acid. The chlorine in this case. So as with our previous one, NaCl is our salt. This equation isn't balanced. So we just need to make sure that it is, and we put a 2 there and a 2 there and we'll be good. And of course, as previously, if you can work out whether your salts are soluble or not, then it means you can make sure you're putting the right subscripts in when you're writing these equations. So you see this equation looks very, very similar to our previous one where we looked at an acid plus base specific example of hydrochloric and sodium hydroxide. But now the presence of the carbonate and iron has resulted in the release or the production of carbon dioxide gas. So what does this look like in an ionic form? Because again, we've got some ions that are acting as spectators here, so we may be able to remove them. So we'll start again this time. We'll look at the ones that we've produced. I'll just leave the ions without the subscripts for now just because it's a little quicker as we're going through this exercise. So there's the acid hydrochloric acid. We have sodium and the carbonate ion. Now water is a liquid, so we don't separate it out. And carbon dioxide is a gas, so we don't separate it out. But we do put down the sodium ions and the chloride ions. So as we've done previously, we then look at our spectator ions and you can see we have two chloride ions here and two chloride ions here. And we have two sodium ions here and two sodium ions here. Which means that our net ionic equation this time, slightly different to the last one, is 2H+, in solution with a CO3 2- in solution produces water and carbon dioxide. Very important equation, that one. I'm going to come back and have a look at later on. As with our previous neutralization reaction, you can see that this production of water, which is a really important characteristic of neutralization reactions, hasn't occurred on its own this time. It's also occurred with the accompanying production of carbon dioxide gas.


All right, I'm Destiny or DB Babjack and I run the Osfo office for United Health Group, which is the fifth largest company in the United States, which should mean that I have all the money I will ever need to support all open source efforts, but we already have giggles. So, as you probably can guess, this is not where that talk is headed. We are going to have a little bit of an interactive component for those of us in the room as well as those of us online, so I'm going to invite you to take those devices that you're glued to and go to menti.com and enter the code on the screen, which is 2615-5878, and this is actually going to capture responses from you, so just to kick us off with a super easy one, I'm just going to ask you how many open source contributions you made in the past year. We are all home, so we should have made more contributions than any other year. Sure, that's the stats of my office are showing as well, and I'm actually running it from my phone, so you're not actually going to see it pop up on the screen, but you will see it pop up on your phone. Let's just make sure that's a true statement. So as I'm waiting for you all to log in, I'm going to preface our talk. So we're here to talk about open source corporate sustainability. Why are we here? I think I prefaced it a little bit by saying usually in a corporate setting, we face more challenges than nonprofits because you work in a place where you're trying to balance two things, which is bottom line profit against changing the world and making it a better place through code. So I think we've seen a lot of the models that have been tried. We're going to talk about that, see how successful they have been, but the big problem, the reason we're actually here in this room talking about this today is that code is not a great seller of itself. It's not charismatic, it's not sexy to everybody. It's probably sexy to the people in this room and maybe at this conference, but it's not as sexy as in Roads and Bridges, a Kickstarter campaign, or helping for the code. Yes, it is 2615-5878. So it seems almost unfair that the open source code has sparked this revolution, that we're moving in a place where we can work collaboratively together across the world to do big things, but funding it, supporting it, especially at the places where they have the means to do so is still a very difficult thing to do. So that's what we're going to talk about. So why does sustainability matter? I'm still seeing your responses come in, by the way. So so far, 100 contributions. Somebody made 100 contributions I'm hiring, so just email me, none, 10, 7. So why does it matter? Community dependence. The people at this conference, the people who are contributing to the Linux Foundation, open source projects around the world, communities depend on contribution. And contribution is supported through OSPOS, even corporate OSPOS. I understand that's almost a dirty word, right? Second reason it matters. Our corporate organizations now run primarily on open source software. The majority of installs in our organization is open source, and in almost every organization, that shift is well underway. So the failure to contribute, the failure of offices to support our developers, the failure to sustain efforts, results and breaks for our operations. So we do care as OSPOS, as corporate OSPOS. Thirdly, we, most OSPOS job, one job is to create a polished technological eminence in the community, right? To showcase our top developers, our top talent, to get them out there and create this pervasive influence, this halo, if you will. Well when the majority of your efforts through your OSPO are abandoned, or poor quality, then your reputation suffers. And finally, innovation progress. So we all know as working together in an open source community, we can gain more progress than by working siloed within our own four walls or siloed within our area, but by collaborating openly, our innovation progress moves exponentially. The corporate OSPO supports a large portion of the developer community. So without that office, this type of progress will stall and slow. Okay. So moving to question two, there was a good mix here. It ranged from none to 100, I'd say the meaner median is somewhere around 10. And then if we go to question two, here we go. I think if I touch the button here, it'll move. Let's see. Nope. I touched it too many times. Give me one second. Oh, dear. And it stopped working for me.  This will be the developer's only question. We'll see if we can get that up there and working or it might have technical difficulties. The screen's really small on a phone. One more. One more. I'm afraid to tap it again. Give me one second. Oh, dear. Goodness gracious. Okay. So we'll come back to this. Trust me when I tell you, if I can get this up and running, we can do it and it'll be fun, that when I'm interacting with my developers or my team of developers, there is hesitancy. Anybody in the room ever hesitant to start a new open source endeavor? Okay. Yeah. There's two nods. Three nods. Why are you hesitant? You have masks on, nobody will ever know what you're talking. Yeah. Okay. There you go. So those are two big ones. Two. Right? And that's the failure of your OSPO. I'll take that one. That's my failure as an OSPO leader. I made it hard for you to do your work. It might not succeed. Anybody afraid that it will? Yeah. Okay. So that's where, let's talk about this. I'm new to open source. I took this office in June. This is my first time at the Linux conference. I was really surprised by this thing that I learned. It's a phenomenon I've observed at United Health Group. It's a phenomenon I've talked and discussed with other OSPO leaders about.  Developers like to do fun hacks, right? My developers at least, they like, they're great developers. They do a lot of open source work. I'm fully dependent on them and I admire each of them. But there is a tendency to want to get in there, do something cool and get out. Right? That's the kind of mindset that comes from our classically trained developers to this point. I would say we're on the verge right now of a new type of developer that I'm going to talk about. But I will say that my developers cringe when I ask them to think about what they're building in terms of those two things that I just put on the screen. I want you to tell me about this repo that you want to open. This community that you want to support. Tell me, because I make corporate OSPO office, how that fits into my, wait for it, product roadmap. How does it fit into the product roadmap of your engineering team or your human resources team or the security team? Is it something we need? Is it something we can sell? Is it something that will sustain itself over time through some type of ROI return? Or is this literally a donation? And we'll talk about what I mean by a donation here in a second. So how do we get developers, offices run for and buy developers to adopt this horrific, in their opinion, business strategic mentality? Right? I often hear, hey, I'm not a business guy, I'm a coder. I'm here to code. I want to hold up in code for 24 hours, go play some video games and rinse and repeat. But I need them to document, talk, become a product owner, circulate, and make sure and get buy in for what they're building. So here's my quick formula. First adjust your own expectations. Understand the beast that you're dealing with, right? You're talking about people who may not want to do what you need as a corporate OSPO. The second you do is adjust the expectations of the people on your team and the people that you're about to hire. And we're going to say no longer is it okay to just be a great developer and a great coder and a great engineer. That may have been true in the last generation, but it isn't now. I need you to now be a unicorn. Most people in most fields are familiar with the concept of a unicorn, right? And I need you to be a good engineer. I would prefer a good engineer who is a great documenter, a great communicator, and a good strategic thinker over a great coder. Because the latter skills are the skills that you need to work in a community. They're the skills that you need to sell a product. They're the skills that, and I sell, I mean, get acceptance of, right? Building a great piece of code isn't great when it's drawered. Sitting in a drawer on the desk. In the desk. It's not great when it's put up in a GitHub repo with the worst read me you've ever seen, right? Because nobody touches it.  Can an average engineer understand what is being built and done with each of your products or projects? Support your developers. So mentioned was it's hard to start up a new project. Your job is to make starting a new project a simple, easy thing. A new developer should have an idea and be able to sit down and start contributing to an open repo or build their own in 30 minutes or less. If that is not where your Ospo is at, your foundational work is still in front of you. Lift with your back. My husband always says knees. But I see him lift with his back all the time, and what I mean by this is go in and do the hard work. Sometimes you can't do it the easy way, which means go in there and actually build your system to work for your developers and still code. Somebody said none. I don't do coding anymore. This creates a divide between those who are actually in the trenches developing in the open source community and those who are making the decisions in the Ospo. Do you have to do 100 contributions in a year? Absolutely not. I never could. That would just mean I would never sleep. And I really believe in healthy sleep for myself. But can I contribute once a quarter? Absolutely. So do it. So now we're going to talk about that evil thing I just mentioned. One of the reasons that projects and products and offices fail, don't make it as long as they would like or never level up, is because we are thinking about code and products is two different things. Code and products need to be one thing. The closer you can align these two things, open source for open source, the more sustainability you would get.  It's a great discussion. If I ask a product owner the same question and say what is this product that you want to build, I get a five-year roadmap with the key features and the key connections across the organization and a reasonable budget and a CBA. Those are two very differently prepared approaches to beginning work. And the latter is what is actually going to help you plan appropriately to make sure that what you're building is what you want it to be. So once upon a time I admitted to a professor of mine, sorry, a mentor and a professor of mine that I didn't study for the test and didn't do well, right? And he looked at me and said, I like you.  You don't owe me an apology. You know that you get out what you put in, right? So if you're looking at your Ospo today and you say, look, it's not the quality that I want it to be. The onus is on you. You have to look very systemically at what you're building. Look at each product, product line, project. I'm using the word product on purpose instead of project because I don't think we should have projects, at least in a corporate Ospo.  In service of my Ospo, I will work on products, healthcare technology products specifically for my company. But look at the quality of the bricks that you're putting in. Assess the strength of every product, the fit of your Ospo vision, the roadmaps as they align to other elements of your organization, the lottery factor, which I think sometimes is referred to as the truck factor. I don't like to put that out there in the world. And then the scope. There is a sweet spot for scope, which we'll talk about when I hit moderating factors. A product is larger than a project, and it's not so large that it's a platform every time, right? It's a, that's the size that you should be hoping for. And thinking about these as equivalently sized bricks is a kind of good way to think about it. If you, let's imagine that you go, once somebody wants to start to build a new project and it's going to be a healthcare data platform. But it's eight times the size of any other product on your portfolio. You can throw that on top of your pillar, but it is going to knock it over. So you have to think about, can I sustain that? Is it too big for me? Do I have to shut something else down in order to take that on? And then the last one which we're gonna touch on for a little bit is the ROI. Does it have one? Is always the big question. So I challenge each of you and anybody running an Ospo to go home tonight and say, I'm gonna design the blueprint for my office. How many pillars do I need to hold up my roof? Do I have four? Do I have 40? How will I build it? Who will be my business partner? Who are my contractors? And then the one that I think is really difficult for us is, who and what will you say yes to? And who and what will you say no to? And I struggle with this because an eager engineer comes and says, I want to contribute to this community and they're really powerful. And I think it's a good bet, but it's just that. It's a good bet on that investment dollar. So I'm going to say that a very unpopular thing. We're gonna skip this because I can't get it to work in a second. But I want you to think of these three as the potential outputs of your office. Just think about it for a second. If you think about all the different things that your office puts together, does it look like a pile of spaghetti?  Or does it look like, I think this is a sandcast, but we're gonna call this a palace, right? A very well-designed palace with a great view of the organization and a great view of the open source landscape. Where do you want to work? You might want to work in the pile of spaghetti, because you can do absolutely anything you want. That's an option. But if you want your products to live and have impact, you probably want to go for the castle. Because that office will know how to get that done. Your meatballs can get lost in the spaghetti, right? In a poorly, let's say, designed roadmap portfolio. All right, I'm going to address the elephant in the room. Corporations save tens of millions of dollars in software cost by using open source technology. So why aren't they using that and just giving it back to our open source, our OSPOS, to fund the work one in, one out? Well, every corporation is using open source to support their organization, which means it's a competitive savings. So that actually disappears, because your competitors also switched to open source. So those savings are no longer real, right? It's just a shift in the ecosystem of how you do business. The second, another dilemma that is difficult for us is that open sources, open source offices as they grow have greater demands. Projects get larger, communities get larger. The size of the vision gets larger, it expands. Even products themselves go through the same type of cycle. It's easy to start it up, and in the growth period it takes quite a bit. As you get mature, things eventually start to get on the decline in terms of effort. But your maintainers need to still be there in that decline period, right? For every new product or you go out to build, you have now made a permanent investment in human capital. Those people will always be on those products. Okay, so how do we get it done? I'm gonna talk about a few ways that we can organize strategy around developers and organization contributions, and then we're gonna talk about ROI a little bit. So I think most people are familiar with this first concept. It's called the open 20%, open source Friday is an example of that. Another is incentivized allocation, where the more you contribute, the more time you get. This sometimes looks like a sabbatical. This can look like a rotation in the open source office. This can be six weeks off, right? To do whatever it is that you want to do. Bench strength, if you as an organization can reward your auspice by putting more people on the bench. Typically one to five engineers should be allocated per 1,000 engineers. I have 33,000 engineers, I do not have over 150 employees, right? Adoptions and donation, maybe you can't become an adopter and an official sponsor and contribute to absolutely every open source project that you're engaged in. Maybe you can award the top two that your developers are passionate about. So for us, that's CNCF, right, and retain. You can use your marketing dollars to advertise for external contribution, right? So you can use the power of the community to come back and do the work. I'm gonna speed up because we are running out of time. But you should be familiar with all of these models. They have been tried in open source before, the freemium pyramid. This is an ROI generating model where you offer some elements of your code for free and then charge for additional sometimes seats or licenses or expanded versions. You can give away your code and software for free but offer only support and services. This will bring in some dollars or you can even host the entire application end to end as a service. Or you can do open core where the base code is free, but you do charge for the software wrapper. In your organization, this is the one I really wanna spend some time on, you can consider three things. One is foundation partnership. So this is partnering with places like the Linux Foundation to use the power of the people that are here and making sure your roadmap is aligned with theirs. That's a win-win for everybody. So if I bring my healthcare technology roadmap over to Linux Foundation, a lot of the work will be shared. It's a great way to get things done without necessarily having to volunteer thousands of my own people's man hours. Sponsorship. So usually you can get sponsorship through a few different types of organizations.  And then the last one which is my absolute favorite way to ensure sustainability of your office is to embed yourself into other organizations. It's no surprise that when funding gets tight, auspose can suffer. But the more integrated you are with the following, the easier it is to sustain your own roadmap and agenda. So the Human Resources Office is a great partner for talent. Whether that's talent acquisition, talent retention, or even your talent halo in the community, what people think about you. The security teams, if you have one, are usually concerned with a lot of things that you are as well. And they will take up those open source efforts on your behalf. The Social Responsibility Office is a great partner for doing open source in a way that affects world change. So in our example, we are hosting a maternal health data hackathon, and starting to build free maternal health data sets. And that's something that the Social Responsibility Office is funding, because it meets their agenda. You should align to the inner source community because I would say there's probably about a 60% overlap in roadmaps with your inner source community from a getting the work done perspective. And it can make it easy, like I was talking before, the zero to 30 minute climb to getting work done, that can be achieved through direct collaboration with your inner source office. And then we have invention, product teams, engineering, ML, AI, and comms. I want to stop while we still have a little bit of time. If you want to know more about that, you can hit me up at dbabjack on Twitter. And then my slide decks are available. So all of these are actually moderators of sustainability. So you can have a look at them. But having them in play and solid will usually help sustain your office better. We have one minute for questions. Yes. It's a good question. We have, yeah, we have dedicated attorneys in our Ospo as well as a direct relationship and partnership. So I'm actually giving a talk with our invention team at our open source Friday about how invention and open source are two sides of the same maturity coin for a product. So we like to believe that all products have various elements and all elements are either invention or open source or both. So if you use the Apache two license, for example, you can still go for a patent if it is something that is patentable. Good question. Anything else? I think it's a great talk. In future iterations, you might want to try and work that around that. Yeah. Yeah, I think that's very interesting. And I think it's still spot on. Coming out of the corporate culture, we do want to create products. But the community wants to contribute and can only contribute to projects usually. So finding that middle ground and kind of facilitating the transfer between the two would be a good step in the right direction. And that takes you back to business models. Yep. Thank you. All right. Thanks.


Against the Houston Texans in week one Ravens got a lot of penalties called against them There was a lot of sloppy play But they were still able to score 25 points and take care of business against the Cincinnati Bengals in week two There was still some tic-tac-y penalties There was a little bit of sloppy play but a lot less than week one But they were going against a very tough Bengals team the Ravens were depleted with injuries But they were still able to overcome that but in week three Going against a coach team that had low expectations a lot of people considered it a trap game But I was feeling like oh no Ravens gonna take care of business in a major way They were just not able to overcome it. They had so many chances They had so many different opportunities to and yeah They have a long list of injuries right now even Raven Nation live pointed them all out and listed them all out for us JK Dobbins, Justice Hill, Gus Edwards, Keith Mitchell, O'Dell Beckham, Junior Rashad, Bateman, Tyler Wallace, Tyler Lindbom, Andrew Voorhees, Ronnie Stanley, Nick Moore, Marlon Humphrey, Damarian Williams, Trayvon, Mullen Marcus, Williams Ardarius, Washington, Adolfi away David Ajabo, Malik Ham, Tyus Bowser. Wow. That is a lot of people hurt, but That was not an excuse for Yesterday's game. You could blame it on the refs if you want to and yes There was some weird calls and toward the very end of the game the refs miss two big obvious calls One was a face mask on Zay flowers That would clear as day and that would have been a penalty that would have offset the Ravens penalty because they got called for an Illegal blocking it back and that brought them back But that the penalties would offset they would have been able to replay the down So that was a missed call and then at the very end when Ravens went for it on fourth down There was a missed pass interference called on Zay flowers again that they didn't call So you could blame it on that but that's not an excuse either The Baltimore Ravens has so many different chances to close this thing out, but they just simply failed They were their biggest enemy yesterday and that's not taking anything away from the coach because coach they took care of business They did their thing but the Ravens they just could not get it done and they had the chances Let's start off with Lamar Jackson Lamar Jackson had a very weird game yesterday Because if you look at the numbers you look at the stats Lamar Jackson went 22 for 31 202 yards No, no touchdowns with no picks but and you could look at that Oh, that's solid and then he had a hundred yards on the ground 14 carries for 101 yards to touchdowns So it's like all right, he scored two touchdowns on the ground I contributed what not but the fumbles the fumbles are still an issue and they got to get that cleaned up the fumbles have been happening every game every game and That's a big big problem. We got to get that taken care of with Lamar Jackson yesterday The fumbles obviously an issue But then there was some bad passes to and not to say that Lamar Jackson's every pass is gonna be perfect Cuz it's not not every pass is perfect from every single quarterback, but yesterday. There were some missed opportunities big time Some of the ones that stood out to me the most there was that it was late in the game I don't remember if it was fourth quarter or overtime a lot of yesterday's game was a blur But where it was a pass where it was a corner back lined up they flowers in a slot I believe and there was a corner back lined up on him But that corner back blitz so I guess they was the hot read and Lamar threw it to him But he threw it behind them now. I don't know if it was just a bad pass So I don't know if Lamar anticipated they flowers just Get sitting on that first down I'm not sure what it was, but it just he missed them. He admit it was a missed opportunity So it was it was bad and then with Lamar Jackson, too It yesterday was a game where it brought out some bad habits And one of those bad habits were just holding on to the ball too long Especially in clutch and crunch time. There was an opportunity where the Baltimore Ravens They were in pretty good field position and then Lamar took such a bad sack I want to say it was an overtime, but it might have been at the very end of the fourth quarter I don't remember but he took a really really bad sack It was that play where he got sacked and then try to throw the ball away at the last lap after the last second But his knee had already hit the ground and it was just it was too late And that was one of them plays where it's like man Lamar We gotta live to play another down because it's not like it was fourth down anything like that Ain't no a with the pressure. It was coming in a lot yesterday But still that's a play that Lamar you guys to throw it away So that was tough and again, he did make some good plays made some good throws But it was a lot that was left out there on the field too and it just it was tough When we talk about Todd Monkham with Todd Monkham Yesterday was again not not his best game either Because the Blitz was coming in a lot and the Ravens just could not get it going and what the coach did a phenomenal job of They were like Ravens ain't getting no deep passes on us We saw it against the Bengals and like no we ain't letting it happen And even a little bit against the the Texans But the coach were like now Ravens ain't doing this and they did not allow any deep passes There were a couple shots or whatnot, but they they took him away And I really thought that uh with this game I'm like and and I've been saying it like it's nice how the Ravens they loaded up this team Because you got if your top guy goes out or one of your top guys goes out like Odell Beckham, Jr. Was out yesterday. Okay, cool. He's out Ravens still got to taking care of because they still got all those weapons and whatnot But those weapons were just They weren't there. They weren't used they they weren't a factor Ravens could never just they could never get it going Top monkey in this game. I'm surprised that we didn't see more screens We saw I remember one of them, but I'm surprised we didn't see more Because the offensive line they they did definitely struggle in the game yesterday big time Sam Mustapha, he had he had a low snap that resulted in a fumble It just contributed to to the fumbles Lamar had his fumbles already didn't a low snap that didn't help But the offensive line they they were just struggling yesterday So that obviously wasn't good The running game. Oh boy the running game It was weird because Gus that was early on he was looking solid as normal But then they stopped using them and it was like, huh? And then he came back a little bit and then he ended up going out with a concussion It's like man Ravens just cannot catch a break for nothing Melvin Gordon, he was in there and he did okay. Can Drake. Oh can Drake that was a Big momentum shifted right there. I know there were a lot of people blaming Ken Drake for the Ravens actually losing the game No, it was just it was not his fault alone. There were so many contributing factors But can Drake did catch that pass got a lot of nice. Yeah, it was looking good It's like all right jizzy and then boom that ball got knocked out and the Colts recovered it I said, oh man and at that point I was thinking oh, yeah, Ken That's a wrap for Ken Drake and we talked about how we expected the Ravens to release him because especially with him being on a Practice squad, but then they gave him more chances and whatnot and he did not necessarily redeem himself But he did do better didn't fumble anymore at all But steel with the injury to Gus Edwards the concussion and who knows how long it could be because with Anthony Richardson from the Colts He got concussed last week and didn't play in this week's game So with Gus Edwards, he got concussed this week So we'll see if he plays in next week's game. It's still to be determined just but just another injury on the Ravens long list of injuries and Again, we this is such a long list and it just it doesn't make any sense to me How they continue to get injury after injury after injury after injury after injury. I don't know what it is I don't know what's going on, but it's it's sloppy. I mean, it's not sloppy. It's just it's weird It's weird the game yesterday was sloppy some moments from the game The the kick the kick after the after Gardner men's shoe stepped out of bounds and the safety I'm thinking like oh, yeah, yeah Ravens got this in the bag, baby. It wasn't over, but I'm thinking Oh, yeah, yeah Raven's gonna take your business and about to be over Hardball said that there was a miscommunication. He said that initially when they when the Colts were doing a free kick that They told they flowers a just fair catch it because it was after the two-minute warning but then how boss said oh, then they added some time to the clock and It was before the two-minute warning, but he said they didn't have enough time to communicate that was a flowers Because I was wondering when he caught doing did a fair catch and I'm like why didn't he just run out those last couple of seconds? I want to take it to the two-minute warning But right there that's a lot of people saying oh rookie mistake rookie mistake. That's on Hubble that that that part right there That's on John Hardball because there was a time in the game where they did have good situational awareness Where it was when the Colts Was I think was late in the county remember when in the game it was exactly but the Colts they lined up to kick a field goal and when they lined up to kick a field goal It was on a fourth down obviously they line up to kick a field goal But then they did this mass Substitution where they brought the offense on the field and they were they were looking like they were gonna go for it I was like no, no, no We're not ready for this I'm calling the time out because we just want to prepare for that. It's like okay How ball good job calling the time out in that situation because you wanted to make sure you were prepared and you were ready So then the very next play they came out like they were gonna run a field goal And they did the exact same thing again They did this mass substitution But Ravens also did a substitution and then the Colts got a delay of game And that forced him to kick a field goal and that kicker I think Matt gay But he that boy was the baller yesterday that dude was kicking him Think he had four field goals over 50 yards something like this crazy man He did a phenomenal job yesterday But anyway, how about had great situation or awareness on that play but in the play was a flower It's like hey if if you need to communicate something to say that's going to be game-changing Call the time out call the time out it was at the very end of this very close to the end of Regulation and you're in control your team just went up three points And he about to get the ball back because they just got a safety call a time out and get it under control So he knows exactly what to do because those three seconds those were precious three seconds That could have made such a big difference a huge difference when it came to the time and the clock management and whatnot So that right there was on John Hubba But again, this was a collective effort. It was a collective effort of a loss by everybody Likely Isaiah likely. Oh, man, it reminded me of Anquan Bolton in the playoff game against the Steelers and I want to say 2010 I think was 2010 but anyway, I don't remember what year was I know y'all remember what year was when Flacco he threw the Anquan but he threw a touchdown anquan bolder now This wasn't a touchdown Isaiah likely, but it was a perfect pass hit him right in the chest and Anquan Bolton just dropped it. I was oh man, and it also reminded me of that that same game with a TJ Hoosman Zata Where it was the fourth and I think fourth and 11 very into the game Flacco hit TJ Hoosman Zata right in the chest and he dropped it but anyway This play to Isaiah likely reminded me of that because Lamar hit him and it was for a first down He's a big first down And he hit him and Isaiah likely just dropped it. He dropped it and I said, oh man. Oh It hurt bad. It really hurt bad With Zay flowers in yesterday's game He he was making a lot of smart play Can we talk about past catching now Zay flowers was making a lot of smart plays because something that I know From him throughout the entire game, which was a big positive he would catch the ball and there will be two defenders around them and Instead of trying to go around the defender and possibly lose yards trying to make them miss He would go forward. He would make sure he always went forward instead of losing yards And I guess he realized like man, this is a tough game We is a struggle for yards right now So let me do everything that I can possibly do to get positive yards whenever I got the ball in my hands And I really appreciated that from Zay flowers because those were some though. Those were some good moves Zay flowers had eight catches for 48 yards Nelson Aguilar he had four catches for 39 yards. He has a nice tough tough tough catches And he was out there trying man. He was out there trying so I give it to a mark Andrews I thought that he was gonna have a louder game today or yesterday, but he only had four catches for 35 yards They they took care of business against him. They took care of business against really everybody Melvin Gordon, he had a couple of catches Drake had a couple catches Isaiah likely he did have that one big catch But yeah that drop now Rashad Bateman Shaw Bateman extremely quiet game. I hadn't even I don't even remember when he got that one catch for six yards I don't even remember but Rashad Bateman. He they said he had a hamstring injury after the game and that's unfortunate because Hopefully it's nothing Rashad Bateman.  So hopefully he will be healthy moving forward, but he was very quiet very quiet I even try I joked around like during the game during the last year I said hey, they better get Rashad Bateman involved. Well, he's gonna request a trade man But Rashad Bateman was really quiet in the game for the This is just a sloppy game sloppy sloppy game for the offense as a whole for coaching It was it was sloppy, but defense see with defense they they they shared in the the wealth of Sloppiness a little bit like giving up a hundred twenty-two yards to Zach most they said they had a problem setting the edge all game long Big problem the runs up the middle They were holding that down for the most part But it was those runs to the outside where they just they couldn't do it they could not do it They could not contain them and that's where Zach Moss was getting most of his big breaks But even still even with that and Zach Moss, he did most Patrick Queen, too So that play was like oh, he caught him nasty They didn't they had got pressure on garden issue on that play too but garden issue did a good job and threw it up and that was that but even with all that being said I just I Can't put this on the defense. I can't I cannot put this on the defense yet They did have their mistakes obviously they did have their hiccups But I cannot put this loss on them because they continue to hold it down Time after time after time after time after time again They really did and they were doing overall a good job. Yeah, they were giving up some stuff here and there But they were they did enough for the Baltimore Ravens to win Even in overtime they gave the offense a chance to win. They gave them opportunities to win Offense just didn't take it off. It's just had the defense keep coming back out there over and over again And we hate to see that you hate to see that especially a game with Kyle Hamilton It's like a defensive player the year type of game The man had the three sacks had some tackles for a loss had a bunch of tackles had a force fumble had past deflection Kyle that was a defensive player the year type of game, but it all goes not necessarily for nothing But it's a loss it is a loss and that's got to be deflated in you could see I remember the point in the overtime when you could just see that the Ravens were just deflated especially on defense They were they were deflated and I think especially after that The fourth down where they went for it and they didn't call the pass and if they they were done They were done and you a hope that they could get a stop and then they did end up getting the stop But then it was a long field goal, but it was a field goal that was in a range of gay And he is making those all day Justin Tucker Justin Tucker's just no in the conditions were a little ugly But Justin Tucker he was off too It was off off. So again, everybody contributed me though Those are some long field but it was the ugly Justin Tucker because we got these high expectations for JT Super high expectations for Justin Tucker, but he he was he's missing so and again the conditions were the what the conditions were But it's still Justin Tucker. So he like, oh, yeah, but gay was making them But Tucker just he couldn't get that long but he did make he didn't make one of the longest But um, it was just an off game for the Ravens just everywhere Everywhere Brandon Stevens Just thinking about him there were he did make some plays that there was one play where I loved it because He had stripped the ball out of there stripped the ball out of there on a deep pass that got him in shoot through up But then there was another play toward the end of the game where he same thing He tried to strip the ball out of there. He was in position But he just could not make the play Michael Pittman, Jr. Caught it over him. So it was a struggle game man This game definitely made me miss Marlon Humphrey a lot more than we already had This man made you miss everybody Because while I did say earlier the the injuries were not an excuse for the Baltimore Ravens with this game They were not they weren't at all. They were not an excuse But with the end with if you got some of those guys healthy like they could have made a difference That they they could have made a significant difference here and there But the Ravens they just they got to be better man And I mean that's so easy to say but they they have to be much much better They all contributed to this loss They cannot continue to give games away like this They cannot continue to be sloppy one thing that I will say it is much better that this something like this is happening now Early on in the season because you don't want it to be happening late in the season They got to get the turnovers cleaned up though They they cannot continue to just give the ball away. They cannot continue to donate the ball with these fumbles They got to get it cleaned up and that's Lamar Jackson. He got to get the fumbles cleaned up for sure Past protection past protection. We know that we're working with backups two of these guys are not starters and last week's game Last week's game was great against the Cincinnati Bengals. They did an amazing job There was still some time where they let some pressure in but overall they did an amazing job, but this game They just they couldn't hold it. They couldn't hold up like they did last game so that will contributed to the loss to and just Raven's not taking advantage of opportunities miss communications and This stuff has no choice but to improve as the season goes on and has no choice But to get better as the season goes on But it's going to take them just doing a little extra a little extra than whatever they doing now It's gonna take them doing that much more work than whatever it is They're doing now, but the Raven should be able to take care of business I do not think that are all of a sudden. Oh, well this team. They're not a suitable team since they lost to the coast No, losses happen upsets happen They they they happen all the time To different teams to some of the top teams some of the love it is what it is any given Sunday But Ravens certainly they know what they need to clean up We know a lot of what they need to clean up and it's important that they take Aggressive action and getting it done because this game was not that


Hello, everybody. Hooded Cobra Commander 788 here. We are in Cobra Convergence 7. We've got more Cobra Convergence 7. And today, we are talking to Talking Joe. We are talking to Talking Joe. We have Mark and Tim here. So Mark and Tim, please introduce yourselves. Tell everybody who you are, what you do, and where to find you. Hey, so I am Mark. And I guess I'm the half, that's gonna say. I'm the guy who comes up with a lot of the driving direction for Talking Joe, lining up things. Tim joins me and adds brain and thoughts to the conversations that would otherwise be brainless and thoughtless. So I've been doing this for a few years. Originally Talking Joe was originally started by a guy called Chief with his buddy Ben. And their mission really was, at the time, was to start with a G.I. Joe real American hero, issue one from 1982. Read that, record what they thought about it afterwards, and try and get all the way through to the end of 155. And they accomplished and kept on going. And along the way, Chief Broke had replaced a number of his co-predenters. And somewhere along the way, I was at the replacement. And when Chief ran out to batteries, I just picked up the baton and kept on going. So we've been reading issue by issue through all of the IDW Hammer Run, all the way through to issue 300. In tandem, we've started on the Devil's Jew era. And we're sort of just made our way up to the beginning of the Joe Casey run at the moment. And along the way, dipping into all sorts of other things. Besides, we've spoken to Larry Hammer and Jim Shooter and Ron Ruddatz and all manner of artists and creators along the way. So we typically will drop a weekly episode and you can find out all of the details over at TalkingJoe.co.uk, which is the website which has links to YouTube's, podcasts, social media, all of that stuff. Tim, I think I've used up all the things that you would have had to say. Mark is the producer, creative director and editor of Talking Joe. And Mark knows and loves GI Joe comics very well and I show up and talk, but I have made comics, taught comics, I own a brick and mortar comic book store so I sell comics. And so we are interested in analyzing is such a strong word, but examining the ups and downs of art and color and story and storytelling and lettering and along the way, Mark has lined up some wonderful guests most of whom are directly related to the issues that we are reading. And in the case of someone like Jim Shooter or Rod Wiggum or Ron Ruddatz, someone who historically is important to GI Joe and since we just got through the 40th anniversary, it made sense to line up a bunch of those guests. That is awesome. And I think it's fantastic that you're looking at the legacy of GI Joe and the people who helped create it. So Mark, it sounds like you kind of inherited Talking Joe and Tim, it sounds like you have a significant amount of comic book knowledge. So that's a great foundation. That's a fantastic foundation. How long have you, the two of you been working this show together? How long have you been doing that together? I think it started just before, just in the before times, right Tim? So it was, I think it was like towards the beginning of 2020, I want to say. Just, did we start just before lockdown? And then... I have a planner right here. I think, who did it cover commander? What happened was Mark did an interview with me where Mark was the only host because for many years I had been researching and writing a history book on GI Joe. So before Talking Joe, my presence at GI Joe conventions or online was linked to a real American book, which is the title of my book and also my website if you added.com at the end. And so I was a guest on the show and I talked for so long. Mark broke it into two episodes. Did we, was that interview December? I feel like that was December, 2020. Okay, I'm probably getting my years mixed up then. So... I think we've been doing this for two and a half years. And then very soon after, because Mark, you had just reviewed issue 275 and done the big Robert Atkins interview. So very soon after, Mark said, hey, you like to talk about GI Joe? Would you like to talk about GI Joe every week or sometimes five out of six weeks? And this was now, this was now everyone was stuck at home now. And I thought, that might be good for me. Awesome. Yeah, real American book is a fantastic resource. I hope everyone will check that out. I will make sure that there are links in the description of this video. Please check out those links. Fantastic resources and a great show. So thank you guys for all the work you do. You've done a tremendous amount of work and it's a great asset to the community. So thank you for that. Thank you very much. Let's talk about, let's go back to the early days. So I think it's fair to say both of you are GI Joe fans. How did you first get into GI Joe? Like way back when, what was your first experience with it? Did I go first Tim? Okay. So you might have detected that I'm a Brit. So my first encounter was with Action Force. So that was being published in the pages of a comic called Battle Action Force, which was initially, you know, focusing on all of the Palatoy toys. So the Red Shadows and Zed Force and all of those guys. And so you'd see that in like in the news agents being released weekly. And yeah, I was bought that by my dad a couple of times and I was like, whoa, this is the stuff. Then I saw some of the toys in the shops and like, yeah, Mind Blown, these are amazing. And so yeah, that combination of comic and toy together sort of, you know, really cemented it. So I followed Battle Action Force until it's demise. It was terribly, and demise of, you know, Palatoy Action Force and it was terribly, terribly disappointed and sad and, you know, that lovely thing that I love so much has gone. And then randomly sort of just, you know, without sort of knowing that it was coming to sort of happened upon sort of the newly relaunched version of Action Force under Hasbro and Marvel UK. And yeah, kept on going from there really. So yeah, collected all of the weekly Action Force Marvel UK issues, which I think there was like if the issues, I wanna say, which, which, you know, had these original stories, but also the Larry Hammer reprints, then over time as well sort of got to track down all of, all of that material and filling all of the holes in that, that collection sort of sporadically. And, and yeah, kept on going really. Didn't, didn't stop too much apart from the dark times when I had kids and thought, yeah, let's just sell all of those toys because I'm an adult now. I'm not gonna ever play with those again. So that was the, that was the only blip.  My brother asked for the Sky Striker and my parents said no. We had a lot of Lego and Matchbox and Hot Wheels. And he said, no, no, no, it's not, I'm not gonna get into a new toy. It's just cause it's a jet cause my brother was big into planes. And so was my dad. And I don't remember catching the first mini series on TV, but I remember catching the second mini series on TV and my first figure was Blowtorch. So I got in in 84 and my brother and I got really big into the toys. We had, we had Transformers, we had Playmobil, we had Lego, we had these other things, but G.I. Joe was the best. And it was supported by this amazing show, which had superior artwork and superior writing and it was on five days a week. And then in 89, I was at a bookstore at the mall and I saw issue 90 on a spinner rack. And the show was over, the show was in reruns, right? I didn't know that geek episodes were coming. And I had this need for more G.I. Joe stories and on the cover was Road Pig. And Road Pig had never been on the show and I've looked through that issue and I saw all sorts of things that I would not see in the show and specifically characters who had not made it to the show. And it was only a dollar, which was one third the price of a figure. And I said to my brother, look, he'd actually read a few issues at his friend's house and he and I had sort of bought an issue or two before that but it sort of didn't know what it was. And he said, a dollar, don't buy that. And he was doing the math. What he was actually saying is, right, that's one third of another figure. So save that dollar. And a dollar wasn't actually that much. And I read that comic so many times and in it was an ad for a mail order company, East Coast Comics in New Jersey and they had many cheap back issues. And so that was the beginning. And that got me into all comics. I think this sort of line is pretty standard where a kid in the 80s starts reading the Marvel comic either cause they've seen the TV ads or cause it's somehow in front of them and then they sort of remember the TV ads. Oh, I've been told to buy this for the last five years and then we got into sort of what's the book that's most like it, right? The Punisher or the Nam. And then X-Men and Wolverine cause someone at school kept talking about Wolverine and then Ninja Turtles cause that's in the air. And then that summer is the Tim Burton Batman movie. And so the world of comics opens from G.I. Joe. Yeah, I think you're exactly right. A lot of people got their introduction to comics in general through G.I. Joe and a couple of people that I've talked to in these interviews have said the same thing. That G.I. Joe comic book series I think may have inspired a lot more comic book artists and writer careers and other involvement in comic books in general than maybe acknowledged that a lot of people started right there. And Mark, I'm glad you mentioned Action Force because I'm enjoying seeing a lot of people outside of the UK now discovering Action Force and really loving it, especially like the toys, a lot of which were just a little different from what we got in North America, but different in some really fascinating ways. So I'm really delighted that people are discovering that now and it's like a whole new world that has opened up. So Mark, you said that you didn't take too much of a break before kind of returning to G.I. Joe. Was there anything that kind of inspired you to come back in and pick it back up again? Yeah, so I've never taken a break from the comics. I've taken more of a break from I guess the community and from collecting everything with the toys and stuff. So yeah, there's I guess a few triggers I guess. So probably the biggest one was talking Joe because I'd been buying the comics but being sort of allowing them to sort of stack up and just not read them. Because the first few issues from Hammer on 155 and beyond, well not the first few issues, let's say, didn't necessarily sort of inspire me too much. It wasn't the best start to the run, I think it's fair to say. And so that sort of slightly soured me on that relaunch. And so I kind of, yeah, out of loyalty and out of knowing that I love this stuff, I continued to buy it but just wasn't inspired enough to read it. So the real thing that did it for me was Chief who was a good friend of mine, starting up the podcast and getting me to sort of read it along with the episodes as he was doing it. So before episode one, we were kind of talking about the podcast and how it would work and what we'd do and so yeah, that sort of gave the inspiration of not just hearing him do the Talking Joe podcast but also discussing it with him directly as a friend. So that got me kind of actively back into the swing of regularly reading the comics and sort of interacting with the community and things like that. And then probably the other sort of dimension to it is probably just like the launch of classified and having kids at the right age. So I've got an 11 year old now who is really into GI Joe and well, the GI Joe toys more and specifically the classified line. So he's sort of loving that and sort of buying that for him as a toy for him to actually enjoy and play with as a toy is a wild idea is just a lovely thing to see and sort of my passion for the kind of the GI Joe is a as a holistic thing, being able to sort of enjoy that as a thing with him is sort of brings a whole different dimension to it. So that's been a lovely thing. All right, Tim, did you ever take a break from it? And if so, what brought you back? I only took a break when GI Joe took a break from all of us. It did. That's not strictly true, Tim. That was you? Well, I was buying all the extreme toys and I watched season one when it aired and I got season two. I interned at Sunbow Productions, which by then was called Sunbow Entertainment when I was in college and I dubbed all of season two of Extreme for Myself. Yeah, I mean, in Mark, in 97, 98, there were those Toys R Us exclusive real American hero figures, but there was no GI Joe content otherwise. And then 98 and 99, but then the toy sort of came back properly and then Devils Do launched. I remember reading the announcement, I was sitting at my laptop in college and I saw the announcement somehow, maybe it wasn't online, maybe I was just holding an issue of the Paper Transformers Fan Club newsletter with the announcement that Bench Press Comics was going to make new GI Joe and new Transformers. I was really excited. No, my break is more that in high school and college, in high school, I transitioned from being a GI Joe toy buyer and player to being a GI Joe toy collector. And there were, it's like eighth grade, ninth grade, 10th grade where I was buying and playing with some toys, but also buying some toys and keeping them man sealed and then buying a few older ones. And the prices back then were so reasonable. And a few years after college, I sort of stopped buying the toys because I had run out of space and I was also buying Transformers. I'm a big Transformers fan, not enough to do a weekly podcast. But in some of those linear years, like in 2000, 2001, 2002, I was on a Transformers discussion board every day when I was at work. Should have been working because, you know, Beast Wars and Beast Machines and also the annual convention BotCon. And then a couple of years where there was a second convention, OT, TFCC, the official Transformers collectors convention. And my friend and I were making this hilarious Transformers fan fiction comic book called the Trans Spoof. And but whenever GI Joe comics were going to come back, whenever GI Joe comics were gonna come back, I was ready. And when there was that issue of Wizard Magazine with those pinups for like potential 80s books and then Devil's Do showed up and the cover of the issue one from Devil's Do is so great. And I, talking Joe listeners will know, did not like the first arc, didn't like the first issue, didn't like the first arc. And I bailed on that series around issue 10. So actually, I guess this is a long way of answering your question. But I was buying some of those toys then because there were those cool three packs with the figures and then later some two packs, three packs with comics and then later two packs with comics with the 25th anniversary bodies. So, but the thing I really want the cartoon to come back and there's no way that, you know, I mean, the 80s, 90s comic gets continued. There's no way that the 80s cartoon gets continued. You know, Disney Plus is sort of making a sequel to the 1992 Fox X-Men cartoon. And it's called X-Men 97.   And so I'm not a toy buyer these days because I also switched in the last 15 years from buying cool things where there are many, many of them, like 10,000 or 100,000 units to original art or artifacts from animation cells or, you know, original artwork from Hasbro, partly because I wanted it and partly because then it can go in my book. Awesome. Yeah, that's, and again, it's a great resource. Please check out the website. The link will be in the description. Anybody who hasn't seen it yet really should. And Tim, you talked about being into Transformers and kind of being in that community. Mark, is there anything outside of G.I. Joe that inspires you? Anything beyond our Joeverse that you are also interested in? Yeah. So I'd say sort of like generally the world of comics is sort of my sort of a parallel passion to G.I. Joe. So I'm sitting in front of my library and these aren't just G.I. Joe comics there. You've got some other non-G.I. Joe things in there. So I think part of what I bring to Talking Joe when I'm reading the Talking Joe comics and discussing Tim is a kind of broader awareness and knowledge of comics outside of G.I. Joe. And what we try and do is sort of look at them sort of slightly objectively and rather than saying, this comic's cool because it's got my favorite G.I. Joe character in it.  So Ron said, we don't like something. We'll try and explain maybe what is it about the story or what is it about the arts that particularly connects or sort of disconnects with us. And one of the joys has been coming back to the devil's due comics and doing a read-read through of those and coming to, you know, for me one of the joys have been that I read them 20 years ago and passage of time has meant that it's entirely blurred in my memory and I can't remember any of the specifics. So it's fun to kind of rediscover the comics. And for Tim, someone who was originally not a fan and let me know if I did my best Tim Finn impression and be like, these aren't written by Larry Hammer. I don't like them. So 20 years later, coming back to them from a slightly different place and reading them with a slightly different eye of that, you know, at the time it's like, these are the only GI Joe comics that are coming out. Take it or leave it. If you don't like them, tough because you're not getting any other GI Joe comics. Now they've been out for 20 years and it's like there's plenty of choice and what you can be spending your time and energies focusing on. So it's that passage of time, I think sort of softened things and allowed Tim to come out of place of coming at them slightly objectively and getting some level of enjoyment out of the process of looking it together even when maybe the substance of the comic itself isn't always necessarily to exact taste. Tim, I'm talking for you. So if you can... No, that's... In your own words. So I think of myself as a historian and I've done a lot of interviews for my book and I read history, read history books on comics and animation. I don't read novels. I watch some streaming shows that everyone watches. I watch the Star Wars shows. I watch the Marvel shows. But because I have for many years wanted my students to see a continuum in the history of animation in America and in the world. I taught a comics class for many years and it was not a history of comics class but for a week or two I would do a lecture and there are threads and there are connections and I don't mean something like, Snake Eyes' origin is in 26 and 27 but then you also have to read 144. That's at the surface level. So what I'm interested in and what Mark is also interested in and game for are sort of threads and context. So for example, as we're reading an issue either Mark has found interviews with the person who drew that issue or the person who wrote that issue and sends me the link and says, oh, we can talk about this also because this answers some questions we have. Why didn't this person draw the whole issue or what have you? But also what is happening elsewhere at Marvel or at Devil's Do in the 80s and 90s or in the 2000s? What's happening in the comics market? What is happening in larger pop culture? What's happening in to some extent geopolitical the geopolitical arena? If you were reading the Battle of Benjean in Marvel issues 112 to 117, you would of course say to yourself, oh, this is Larry Hama's analog for the actual Gulf War. It's not Iraq and Kuwait and also Cobra's involved. And so you can do a little or a lot of that with G.I. Joe comics and it might be something like, oh, well what was the best selling comic that month or that year? Oh, it's this Batman event. It's this X-Men event. It's the Spider-Man event. How might that affect Devil's Do? Or now how might that be affecting IDW in the last 12 years? So in addition to the nuts and bolts of, I like what this character is doing or I don't like what this character is doing. It's why might the writer be making this decision beyond a creative decision? Why might the publisher be making this decision beyond sort of we've got 22 or 20 pages to fill? And some of that we can get from people who were there and some of that we can get from reading around it and reading up on it and some of it we can get just from sort of looking really carefully on the page and putting our heads together. And I think there are, one of the reasons why I'm so pleased to have joined Talking Joe is that there are a lot of places online in text and in video or in audio where someone will talk about a G.I. Joe toy and I think I was waiting for someone to talk about G.I. Joe comics the way that I wanted to talk about G.I. Joe comics and it turns out Mark and I can talk about G.I. Joe comics. I can talk about comics the way I want to talk about comics. I mean, that's why I'm writing my book, right? I thought 23 years ago, why isn't someone writing this coffee table history art book of real American hero? Well, thank you. Thank you for you guys for what you're doing. We are about at time, but before we wrap up, what I would like to do is just kind of turn the floor over to you guys for any final words to our audience and remind everybody that Talking Joe is in Cobra Convergence 7. Again, there will be links in the description of this video. At the time you see this, their presentation should be out now. So go right away and check that out. Subscribe if you haven't already and check out the rest of their catalog. They've got a very deep and rich catalog of material and content that you will definitely want to check out. But to wrap it up guys, I will turn the floor over to you for any final comments to our audience. Yeah, I mean, just to echo what you said really, I mean, your theme this year sort of gave a good springboard for something that I wanted to talk about anyway. So yeah, tune into today's episode to find out what we think, because I don't know what we think yet because we haven't recorded it yet, but it's the mysteries of time. But so that's been a great prompt to look at something that we were meaning to and hadn't got to yet. So that will be a lot of fun to do as an experience for just me and Tim and hopefully for the, yeah, sort of a rare little golden nuggets that maybe sort of G.I. Joe Comics fans aren't familiar with. But beyond that, yeah, we sort of put out a weekly podcast most weeks. We started at issue one. We've worked our way through to issue 300. So you can join in the experience, read along, go all the way back and start at the beginning or just delve into some of those more recent ones where pretty much for the last run of IDW month by month as those issues were coming out, we would be talking to the creators involved because when they moved into those kind of untold tales type arcs, it was a new artist each week, each month. So it meant that we could be very regularly talking to the creative team and meant that we talked to an awful lot of people about G.I. Joe how much G.I. Joe meant to them or not and their sort of creative process for sort of putting all of those issues together. You can also delve into the devil's due eras with a read along on that and explore the back catalog to hear from various luminaries such as one of my favorite artists, Rod Wiggum that we had the great privilege of speaking to not so long ago. So that in a nutshell, is it like and subscribe, he says. I've talked for a long time. I have nothing to add. Mark, that was great. All right. And thank you. And thank you, Hooded Commander. Oh, and also best jingles in the business. Absolutely. Oh, thank you guys. I really am grateful that you're involved this year. Thank you again. Thank you for all you do. Thank you for being such a great asset to the community and providing so much information that is useful. So thank you, my sincere thanks to you. And I guess that's it for now. Thank you guys. Once again, everyone, links are in the description. Go right now, check out what they're doing and make sure you subscribe and check out everything they have done over the last few years. You will not be disappointed. There's a lot to see there. So thanks, everyone. Thank you, guys, and we'll see everybody soon. Thank you so much. And thanks for all you do as well at bringing us across the community together. Thank you, Hooded Commander. Thank you, guys.