Okay, welcome everyone. Thank you for coming out. We're here today to talk about a book we wrote in five days, not really all that long ago. It was about a month ago, a month and a half or two. And, you know, six of us plus Diane Fleming over here wrote this book in, well, realistically we wrote it in, you know, three and a half or four days and we spent another day, day and a half actually editing the thing down in an attempt to have it make some sort of sense. And there was also one more gentleman who was with us at the time, Adam Hyde. He was a facilitator for the book Sprint. This is kind of a methodology that he developed during his time with Floss Manuals. He actually helped found Floss Manuals. And today we're just going to talk about that whole process of writing the book, you know, the kinds of things we went through, the kinds of topics that came up. But I'd like to put a little, a little slight twist on this particular panel. You know, so many times during the process of writing the book we kept asking ourselves, you know, what do people really want to read about? What is it they're interested in? What matters for them day to day? This was really intended to be, you know, the kind of guide that you give to somebody on their, you know, day one of when they're going out to start operating an open-stack cloud, you know. This is becoming, this is a job role, you know, operate this open-stack cloud for me. Where do you start? Well, one of those things could be handing them this book. So that was one of the uses that we envisioned for this book. And without further ado, I'd like to introduce our fine panelist here to start off. We have Anne Gentel. And do you want to kind of take 30 seconds or so and introduce yourself? Sure. So I coordinate the documentation for open-stack and have since Rackspace hired me more than two years ago. So go write docs. Nice. Joe? Joe Topchin. I'm a systems administrator with Savera. And so basically I'm an operator for most of the clouds that we deploy. Where do you operate those clouds? Thank you. From Calgary, Alberta, Canada. Excellent. Thanks. Lauren? So I'm Lauren Hoxstein. I'm the lead architect for cloud services at Nimbus Services. We're a little company in the DC area that does cloud services for engineering applications. And that's sort of like traditional engineering engineering, like mechanical and electrical engineers. And so I sort of wear two hats. I do traditional web software development. And I also administer our little prototype open-stack cloud that we have. The data center out in Ashburn, Virginia. Then my copious spare time, I volunteer on the documentation. Nice. And thank you for that. John? I'm John Prue, systems administrator at the Computer Science and Artificial Intelligence Lab at MIT. We operate about a thousand core cloud internally. My users, it's very much like operating a small public cloud, because I provide the infrastructure as a service and then the research groups consume that through the API. So even though it's an internal cloud, I don't really have much visibility into what my users are doing, which is a bit of a challenge that you're more likely to see in a public cloud than most private cloud deployments. And when you say we, how big is that team? The team that's operating the open-stack cloud, that's about a third of me. So it's the royal way. It's the royal way. There is a larger group that I'm one of the senior members of. We have about a dozen people that operate the infrastructure overall. And one of the things that brought me into writing this book is as documentation for those team members so that they could understand how the cloud works. I had to write our internal docs. You're getting ahead of the game. I'll be quiet then. Hi, I'm Tom Fifield. I'm a cloud architect at Nectar. Nectar is an Australian government project to provide cloud computing to the research sector. So we run a cloud that's this year scaling from about 7,000 cores to 30,000 cores. And we have a whole gamut of the research sector. Everyone from archaeologists to winemakers using our cloud. Yeah, that's really cool. Okay, and I myself, my name is Everett Taves. I'm a developer advocate at Rackspace. Previously, I had run, built, designed, and deployed Cactus OpenStack cloud into production. And that was one of the reasons I was included in this book sprint. My job has changed somewhat since then. Okay, so let's get down to it. I'm going to start with just a few easy questions. I'll first ask, you know, just a couple quick questions to the panelists. And we're also going to start asking some questions of the audience, because, you know, we wrote this book for you, literally, like for you, the people who are actually cared enough to come out to this panel. You know, we want to know what you think as well, the kinds of things like, you know, what what crucial topics did we miss when we wrote the book that matter so much to you, but are completely absent? Or, you know, there's something really important missing from that topic in the book, we want to know that.  We want to hear those questions. Was there anything in the book that made you throw the book across the room, you know, into the drywall? We want to know what the airspeed velocity of that book was. Okay, so panelists, why? Why did you want to help write this book? Starting with John. Well, I'll start because I started answering that earlier. So like I said, I have a team of about a dozen people working on the infrastructure within the computer science lab. And we are looking to move more to OpenStack to provide some of the infrastructural services that we're currently providing on older platforms. In addition to this infrastructure as a service that we're providing as a new service. So I needed to train my internal people and document our procedures. And to the extent that this was generalizable to the larger community, I thought the right place to do that was in the official documentation, rather than replicating that on an internal site, which is kind of hidden away from the rest of the world. Obviously, there's bits that are unique to my site, but I try and keep that to minimum. Be shy. I guess so one of the parts about my job, our cloud is actually quite unique in that it's run by eight completely different organizations using Nova Compute Cells to put it under a single API endpoint. So one of the parts of my job is to get these detailed design documents or architecture documents from these other organizations and review them. And very often they come in and you just really have to either fly to their location and explain exactly how OpenStack networking works or go back and forth for about 20 email exchanges to try and get through to them that maybe you should consider using flat DTP multi-hosts, H.A. instead of this other thing. And that's really an effort saver. So from my point of view, so I'm probably the person with the least system administration experience here since I come from a software development background. And I basically wanted to be, so I like writing documentation. And I realize that's sort of a rare thing, apparently. And I wanted the opportunity to just basically be in a room of people who had done production deployments of OpenStack. And so this was an opportunity to do both those things to generate docs and actually be around people who really knew what they were doing. So by the time we got around to writing the book, I had deployed three different clouds for Cibera. And well, the documentation was was still pretty good. And it got, you know, a cloud up and running, but there was still a lot of day and operational. And this weird thing happened to me. And this is why it happened to me. A lot of those things were missing. And a lot of in-depth troubleshooting procedures were missing as well. And I thought that would be very valuable to have written and given out to the community. And that was my primary motivation. Shall I go too? So I am completely motivated by a very experimental way to write a whole book, 232 pages worth. And I had done a couple of book sprints in the past with other open source projects. So OpenStack seems like a perfect place for us to try this technique. So Everett actually did a great job of helping me recruit these. I didn't know that Everett had worked with Tom and Fudo Australia and helped him set a PIS code. And so this group was just like this amazing, you know, collaborative group where we could try the book sprint method in a safe way where arguing was allowed and not too harsh. And I just felt like this group of collaborators could actually pull it off and they did. So my motivation was like, right place, right time, let's do it. And the foundation gave us 10K to do it. So thank you, foundation. Yeah, and my motivation was, you know, pretty similar to Anne's and Lauren's really, you know, I was curious to see if this would actually work. If this was really possible and to be a part of it, you know, whatever that meant. And also, you know, I knew a number of people already who were applying on being on the team. And I think again, it speaks to I've been a huge community proponent of OpenStack since the very get go. And I just thought this is an extension of that, just the power of the OpenStack community of being able to bring people together to do these kinds of amazing things, developing in this case a book instead of developing code. And then on the technical side of it, you know, coming from development background, I kind of wanted to make sure that the dev was in DevOps here, and, you know, illustrate to people how they can actually extend the functionality of some of the pieces of OpenStack without actually having to change the core code. So many times, operators need the system to do that, that one little special thing in their environment, you know, they've got some weird policy on their network or who knows what. And, you know, being able to show them how to do tweet those things in OpenStack, I thought would be, hopefully, you know, really valuable to them. And I guess we'll see how that plays out. So we talked a bit earlier in another session this week, just yesterday, about, you know, how do we keep going with the book? You know, we want to keep this thing up to date. This is a living document. This isn't just, you know, a book we throw it out there, we throw it over the wall and forget about it. We want to keep this thing up to date. So one of our challenges that we discussed towards the end of the sprint, the end of the book sprint, was how do we get experienced operators to contribute documentation? There's so much knowledge in this community, just an incredible depth of knowledge. But, you know, dragging it out of the minds of some operators is not an easy thing to do. So this is the start of, you know, as much a question to the audience as it is to our panelists. Would anybody like to take a crack at this? Did the questions get too hard too fast? So we actually worked in a system that just did HTML edits. And that was great for the in-person collaboration for that five days. And it gave us a neat pump right out of it. But what we've done since is bring it into the OpenStack documentation workflow. So you have a Garrett review, you have the ability for me to work on a chapter, John works on a chapter, all merges together because it's doing that on Git. So to me, I think that's the way it's a living, breathing document is because of Git and GitHub and our Garrett system. We can merge this stuff together. And I think the output is fabulous. The other thing it enables that's really interesting to me is translations. So we already, I believe, have a Chinese translation of this book done. And that's how it becomes living and breathing. It keeps opening up to more and more groups. And the comment is, I note that there's quite a bit of colloquial language in the book. And whilst there's nothing wrong with colloquial language, if your language is English as a first language, in translation, that could become quite a difficult issue. Something to the effect of a final example is if a user is hammering cloud resources. Now, we all know what hammering something can mean from a network perspective, a disco perspective, and so on and so forth. But when you translate something like that, someone's going to scratch their head. So yeah, apart from that, though, I reckon it's an absolutely amazing job you've done. So I guess as far as the actual contribution process goes. So I didn't actually write anything for OpenStack documentation for the OpenStack documentation team before this book. But afterwards, I've started writing and it's actually quite an easy process. And it's almost a lot easier than subinit code for review for OpenStack. You still have to go through a Garrett review process, but you're just sort of writing words and paragraphs instead of, you know, code structures, and you have to learn a bit of XML. So in terms of barrier to contribute to the book, it's actually quite low once you read through the how to contribute doc. So from someone who is new to it as well, it really wasn't that hard. I think hammering is probably an Australianism from me. Apologies for that. Indeed. Yeah, exactly. Just getting back to the comments about gaining contributions to the book. And I remember when I was standing up my first production OpenStack cloud, at one point, got an email from a colleague of mine, basically saying something along the lines of whoever touches the puppet config again, I'm going to cut your hands off. And yes, it happens. But I think we can really capitalize on this frustration and anger that builds up when you are doing a sysadmin task that or devops task even that is taking a lot of time, especially if it's OpenStack's fault. Even if it's not a bug, even if it's something that is more difficult than it should be, I think we should be encouraging people to vent at the documentation team or just put their vent in a bug report, just type something up so we can take it and not only add it to the book in case the code takes six months to fix, but also use it to improve OpenStack. So I think there's sort of a this is sort of an open problem in documentation is how to get feedback from sysadmins. And how do you get them to even just complain through formal channels so we can take that in and use. So I don't know if there's a plan for it. Does that occur to me? People here actually have a system administration background. How many people have of those people have contributed to documentation and an open source project and any open source project? That's pretty good. Thank you. So let me ask you people. So for those who how many people have contributed to the OpenStack documentation project? That's that's good. Thank you. So let me ask people who've contributed sysadmins have contributed to other projects but not OpenStack.  What's that? I could say the thing that prevented me from being... I just remember getting to like the now it's time to sign the CLA and it's like GPG and I just like my eyes glazed over. I shut down the screen. It was like, seriously, I have stuff to do. But I know that now that's gone. Yeah, I think that's a fair comment. You hit the the Garrett workflow wallow words and it's and especially if you haven't worked with Garrett or Git before it's you just want to get going, right? But now it's just a button. Right. Yeah. So great. It's not that bad. Actually, once you get going, it's not that bad question. So I think one of the things that's possibly missing in this is an appreciation that it's a relatively young project. There probably aren't a lot of people who have the experience. There will be. I think that's that's the number of people around here that are interested already in this. We can see that users are growing. The numbers of users are growing. I think that's great. I think there will be. This is a great start. I think this book is useful. I think it's going to help build this community. So certainly for me anyway, I felt that I was at a point where I could not contribute usefully until now. Thanks a lot. So I have one thing to interject. Tom was mentioning complaining to the documentation team. The acu documentation team is pretty much Tom, Lauren and Ann. The rest of us contribute bits and pieces here and there, but it's a very small set of people. We do have Diane now who's putting serious time into documentation. I want to forget Diane. Even though you are blocked by the table. So we're not looking at hundreds of contributors. So if you have this one little thing that tripped you up and you can even submit a bug saying that you were tripped up by it. If you can make it over that little hurdle and actually enter the five lines that will keep someone else, that's fabulous. But if you can get as far as saying this tripped me up, just in a bug report, there's not a lot of people working on it, but at least then it's on the radar for someone to look into. And I know that a lot of times people don't know the answer a priori. They have to go and research it or post it to the dev list and get an answer for that to put it in the documentation. And for the three of you who do that, I really appreciate it. I also just like to add one other thing. And that's if you're if you're assistant men, don't be shy about filing bugs against any of the OpenStack projects, not even just manuals. I've gone through this cycle between some of the devs that are sort of horrified to find out that assistant men are doing shell script workarounds and poking at the database because the devs don't know about problems that the assistant men are having because there's no feedback coming back that X is too hard or this doesn't make any sense. And there's like a disconnect there. And so if you ever want to, if there's something you don't like about OpenStack, you can file a bug with the ops tag against any of the projects. And they're pretty receptive.  We're not going to change the way we do things. Yeah, if you're if you're gluing stuff together with scripts that, you know, could very well point to a deficiency within the system that the developers want to fix, but don't necessarily understand the use case. Hi, my name is Keith. First, I want to say thank you very much for your work. It's very inspiring, inspiring so much that working with the OpenStack security group, we want to try to do the same thing. So in that vein, how important was the facilitator in making all this come together? And if you guys had to do it again, would there be a facilitator involved? We have not lobbied for the 10k. We're going to try to do this on our own. So give me some feedback, some directions and guidance here on that. Having somebody to shepherd the process is very important. Very important. That's how I had tried to do like maybe one day Doc sprints in the past. And then I went to another one of Adam Hyde's book sprints and lobbied for the funding for Adam Hyde to facilitate. Yeah, it's just I have participated in enough that I knew I couldn't facilitate myself. It's a special skill that you have to practice enough that I mean he he has gone to books prints where he literally gets everybody in the room, but then he gets cornered in the kitchen on day one. And everyone was like, we can't do this and you can't make us. So he had to work his way around like with that and through that and you're going to get the book you want. You don't even know what it is yet that you're going to get but you're going to get the book you need by the end of five days. So I I knew I couldn't do it with Adam. So yeah. And I found you guys an author if you're interested. Yes. Yes. Okay. Good. We'll talk. Yeah because I'm collecting people. Actually, I guess my comment is about the earlier question. I think a lot of artists, admins don't feel like they that they have anything to contribute or that it's good enough. And so there's this fear factor that, you know, well, it's what I'm going to do good enough. And I must admit I'm sort of in this in that I've just I haven't done for almost not yet. I just did for fedora. But skating this habit of, you know, gosh, I've seen this problem. And I know it took me half an hour or two hours, three hours to fix it. I should contribute this. And so one of the things you might do is look at mailing lists. And if somebody writes up a good answer to a question, send them an email saying, Have you thought of it contributing this to the documentation? Suggestion? There's one comment I'd reply to that with, which is the review process. We obviously, when we're going through this book, we kind of broke it up into sections and we'd write a section and then market for review and then one of us would come along and review it. And, you know, sometimes we found syntax errors, sometimes the layout was terrible. Sometimes there was words like hammering in there. But this this same review process actually exists in the normal open stack documentation. So it's possible to just send in a patch and then someone else will have a look at it and kind of mentor you through that. And I found that very helpful when I'm writing code for open stack. I mean, documentation is something that you can, if you know what you're talking about, just, I don't know, more Australianism to smash out fairly quickly. Whereas code, you have to think of all the test case and this kind of saying having this review process, I think really helps. And just being aware that the people are there to help rather than actually put a big red minus two on it and say this is wrong and this and that and the other. I think that's something where we can improve the time of our views. But it's something that might assist. So I guess another comment on that on on fear of contributing.  And that's it's understandable. And but it's something that people really shouldn't be afraid of. This was the first open stack operations manual. So in a way, all of us were putting out these problems that we had. And there was, you know, there was obviously a chance where it's like, well, everything you guys did was completely wrong. But it didn't turn out like that at all. It turned out where a lot of the things, everything that we documented was incredibly well received. And a lot of the goofy mistakes that are documented in the book have been like shared across, you know, all sorts of different, like there was, there was an IRC chat log that Lauren pointed me to where someone came in and said, I'm having an issue where my instance just randomly locks up. And if I log back in, then everything's fine. And someone goes, Oh, check page number, whatever, of the open stack manual. And it's it's the VLAN on VLAN issue. And that was incredible.  But I'm really glad that other people have now seen the solution to that. So there really shouldn't be a fear of saying, Hey, I ran into this issue. It's yet to share whatever you have. And it's going to make a great knowledge base of of issues and solutions. I got to attend a presentation pretty recently. And the speaker was talking about contributing to open source communities, whether it's documentation or code or what have you. And he himself said, you know, one of the things and this is going to get a little touchy feely. But I mean to effectively sometimes to effectively contribute to an open source project, you need to be vulnerable, because you're really putting yourself out there for peer review, right? And all of the things that goes with it. And it's intimidating. I personally find it, you know, pretty intimidating.  And if you can distance yourself from your code or from your doc and say, it's not you that's being reviewed, but it's your documentation that's being reviewed, it's your code that's being reviewed. It's, it can be actually quite liberating. And I think you become a more defect, more, more effective developer or documentary. What a Freudian slip that was. Okay, moving on. Did we have any other questions or should I ask another one? Great. Just sort of humdrum question. What's the release cycle going to be? That was my question. That's not a humdrum question. It's, I think, an undecided question. We did have a session yesterday discussing, you know, what is the life cycle of this book? How, how do we contribute to it? How do we, how do we release it? I don't know if there was a decision. What there were opinions. Yeah, so I mean, this is the perfect question for the audience. I mean, like one of the things that came up in that session was, Oh, there's, there's a handful of groups doing continuous integration, continuous delivery. So, you know, the, the doc, the book just has to be updated constantly, simply not realistic. And in addition to that, not everyone is doing continuous integration and continuous delivery. Most people only have the resources to upgrade every six months or what have you. So what would be useful to you? You know, when, when do you upgrade your open stack clouds? And, you know, that might be presuming a bit much that everyone, or even most people here have a open stack cloud right now to answer that. Or that they've upgraded it. Or that they've upgraded it. Yeah. No, and, and intentionally so that wasn't one of the objectives of the book. But once you get past that point and you want to learn how to operate that new version, let's have an answer. So keeping in mind, if you look at things like the O'Reilly texts and that may or may not be a good example in the context of what we're trying to achieve here, but, and given there's only three core people actually on the team who are actively writing this stuff, I would suggest maybe a yearly update cycle would be possible. I think that would be maybe realistic to say that maybe every year the group should get together and, and, you know, pen, pen and update. Because within the space of a year, you've got those two sets of release gaps. And maybe that's worth it at that point in degrading. But yeah, beyond that, to say every six months, I think is too much to say any more than that is too much. So when you see, like the open stack operators fall some guide and now that Grizzlies out, does that actually put people off from reading the book knowing that it's, it's, you know, as the word say, it's a release behind. But even though a lot of the information is still very relevant, so that you don't find a problem with that at all. Do you think that tagging the book with the false and release is a good idea or it should just be left out completely? Maybe additions of the book are important. But I don't think you need to say it's false and release. It's a grizzly release and so on and so forth. But additions in a year number or something is probably appropriate. Maybe others have other opinions. I think that it's important in the book to say which release it covers. But you shouldn't have the book saying this is a grizzly release. A slightly different question. Grizzlies just come out. And if I'm not mistaken, the documentation is still fulsome. And so if you want to go see grizzly documentation, do you need to go to the Get Repository and check it out? So we always publish continuously to docs.opensack.org slash trunk. And I mean, we might even merge like five times a day some days. Tom's pretty prolific there in Australia some days. So you can always just substitute slash trunk for slash fulsome. But one of the things we talked about yesterday was we need to release the grizzly docs, but they're not done because the installation isn't tested. So as a doc team, we decided last week, let's release after the summit, after the install guide at least is tested. After that, we'll collect bugs just like our timed released code does. Be useful on the main page to say this is fulsome. And if you want to see the grizzly documentation that's in progress and not tested, go to this. OK, yeah, there might be useful for you guys to talk about how you chose the reference architecture, like how you made those decisions because that was a big part of the process. Oh, do you and I want me to mention that? Sorry. I was going to say example architecture. Yeah, example architecture. Reference is just such a loaded term, but but that was actually, I mean, that's that's a part of the discussion as well. John, do you want to hear? Yeah, so there's been a lot of talk of reference architectures in this room today. I don't know how many people have experienced that, but obviously we need something to talk about. You can't talk about it in a vacuum and you can't talk about all the different ways you could possibly permute all the different pieces together. So we kind of took a target of what we operate and what we've seen people operating in in mailing lists as sort of the best covered cases and the most popular pieces in use. So we use KVM as the hypervisor because that's what a lot of people seem to be using. Mostly made our choices with with that idea in mind. With the user survey, I guess we get to take a look at that and see if we were right. But that that's mostly, I think, how the discussion progressed. What did you think, Lauren? Yeah, I don't know if I have that much to add there. I mean, we had to write based on what we knew, right? So that's one of the reasons you don't see quantum in there. And so you have to and then this is a general problem with documentation, right? I mean, we, you know, if we haven't installed it ourselves, we can't. It's harder for us to write that documentation so we don't know if it's going to break somewhere. And so we this was like a subset of everyone's knowledge or maybe a super set of the example architecture was a super set of what everyone had a direct experience with. So they could actually write what they knew. I think you made a good set of choices. And I think you were also pretty clear that you had made these choices and that they weren't the right choice. They weren't the right choices. They were the choices you made. Yeah, that's good to hear. I have a general question actually. Do you plan to also incorporate questions or discussions that happen on other online public forums like like ask.openstack.org or other places where people ask questions and there are others who give them answers. I just had an example of this where I had a problem with some swift configuration. I asked the question and eventually I was able to debug it. I put the solution in there and I just later found out that one of the engineers who was active on OpenStack actually took that and put it into the documentation. This apparently has happened in the last one week. I didn't even think about actually adding to the documentation. But he already did that. But I'm sure there are many such, I guess, bits of information or maybe even longer discussions that are already there on other public forums that could make it into the ops guide and make it into the book and that will be useful for people. So I guess I can comment on this because this is something that I try and do. I read the mailing list every morning and if there's something in there that crops up as something that is a common case that people encounter or something that's a bug, try and add that to the documentation. The problem is there just aren't enough people to actually do things like go through all of our Start OpenStack.org or even the old Launchpad answers site and take all of the caveats and pointers and corral them into a document. If you'd like to start doing that, that would be fantastic. But yes, we do try and do that. It's just basically limited resources, which means that we haven't managed to get all of the community's knowledge together in one easy to replace. Yeah, I mean, I would say I like agree entirely. So I do something similar.  I try to do that with blog posts. So if anyone there's like plan at that OpenStack.org, which aggregates a bunch of different blogs that are out there, there's often a lot of good content on there. If I see some, if I have the time and I see something that's really good on there, we try to contact, we have to contact the author. We can't just copy and paste it in. Almost everyone, I know it's ever said no. I mean, sometimes people don't respond to me, but typically if they respond, they say yes. And then we slurp it into the docs and you get a lot from the mailing list. But it's really just a matter of resources. So we do it when we can, but there's just much more content out there than there are people who can make the edits and put it in the docs. OK, so it's six o'clock, I believe. That's our wind up time. Did anyone have any closing comments they'd like to throw out there? Besides pull requests accepted to the docs and standard open source throw it. I also want to thank Rackspace for donating these books. They actually purchased the print copies to give to all you. So I do have to send a shout out to Rackspace as well. They hosted in Austin, Texas. We brought in Yummy Tex Mix and then they turned around and bought books for all you guys. So thank you, Rackspace. Thank you, everyone.


Where do you go then? Where do you go?


December 22, 2021. A day that will live in infamy. Mark your calendar as the official day that the Matrix franchise died. After years of crickets, one of the Wachowskis comes back out of the shadows to make a movie so insultingly bad. I would argue it's one of the worst follow-up films ever created ever! And no, I'm not being hyperbolic. While, yes, there are plenty of films truly atrocious and worse than this, the fact that it's a follow-up to such a beloved set of films. The first film being incredibly iconic, amazingly quotable, a truly touchstone moment in not only people's lives, but in cinema itself as it would shape the way action films are produced going forward.  It's been too long. People have moved on, done other things. Some of them are completely different people. I got my buddies together, rounded them up, the same dudes I sat in line for hours to watch the other Matrix movies in theaters day of fun, and we went to this one. And not a single one of the four of us had anything nice to say about the picture, and I saw nothing but a sea of disappointed faces.  So I red-pilled up, watched this thing on Max to see if it was as atrocious as I recall, and guess what, fam? It's actually worse! It somehow managed to be worse on a second viewing. Today, for the next 20 minutes or so, depending on how frisky I feel like being, I'm gonna be going over this movie from top to bottom, front to back, and everything in between, roasting the living hell out of the Matrix resurrections, the Matrix rebooted, the Matrix rebranded, the Matrix ruined! And maybe you'll agree with some of the things or all of the things I have to say, and if you like this film, that's fine, you might not want to settle in, because it's gonna be a rough ride for you. But here we go! Let's enter the Matrix. Resurrections.   At Patreon.com slash Adam Does Movies, where he gets access to hundreds of exclusive videos, including several monthly V-Logs, what a time to be alive. But what a true treat this is. So that's a possibility for you as well. Otherwise, you can just subscribe. That's free of charge. It doesn't cost you a dime. And you can hear me talk honestly about all sorts of movies every single week on the channel. Alright, let's begin. We start out on a positive. The first scene of the movie looks like the Matrix without the greens, the hues are gone, but that's kind of fair. I'll give them a pass on that. Because at the end of the Matrix revolutions, they did reset the system. It rebooted again, and the sun was made a little bit brighter. Everything was a little less Huey in the news. Everything was a little less Huey Lewis in the news. They got rid of the greens. So that actually is canon. It makes sense. But it doesn't really make this mesh visually with the other movies. It's already on its own, the ugly stepchild. What isn't so forgivable is how this movie is shot. There is a cheapness to it. A digital look to this one that the other ones don't possess. The older films look cinematic. They look like they're shot on film. They probably were. This one has that garbagey kind of stage play vibe to it that I just can't stand. So the movie fires up with a small amount of potential. There's some intrigue here. We are revisiting a scene from the first film. The intro to the first film, as a matter of fact, where Trinity is in a room up in a hotel. The cops are down below. They turn into agents. Your men are already dead. Get set. It's iconic. It's phenomenal.  But this version is a bit different. We have a new character. Meh. What's up, Doc? Says Bugs, our new kind of protagonist for some of the movie. Kind of the first whole half. And then she mysteriously disappears for a while, comes back later. But she's pretty much forgotten about, which is fine because she's not that exciting or interesting. She does have blue hair, though, and that's kind of cool. That's something that's everything, really, about her character. Anywho, she is checking out this sequence as it's playing out. And she says to her buddy, I don't know his name. It doesn't matter. No one else matters in this movie. Jack's plug-and-play dildo vibrator. I don't know what his name is. But she says to him, hey, there's old code mixed with new code.  This isn't the same Trinity, and it's not. It's not Carrie Ann Moss. It's a different actress playing the part.  And it's not even great. Bugs is running around on the rooftops. She's in pursuit of Trinity, who's fleeing from the agents. We have some sound effects akin to the old films, but none of the bullet time. In fact, there is zero bullet time, at least in the traditional sense, in this movie. We have poor man's bullet time, Kmart bullet time. The agents start now going after Bugs once they realize she's there. She jumps out the window, which, coincidentally, I wanted to do as well. Lands on a car. This is the best shot in the entire film. And it is a pale cosplay of what we had in the previous movies. She enters a keymaker's shop, which actually turns out to be Thomas Anderson's old stomping grounds. This is where he did his coding. This is where he started following the rabbit down the hole. But who do we have here? Morpheus. That's right. Well, Lawrence Fish. My fish is back. Lawrence Fish burns in this film. No. He did not come back.  That's cool. That's different. Why? What? This Morpheus is code put into an agent or something. I'm already at a loss as to what's happening in this film.  As an aside, and there's going to be several of them during this rant slash roast thing that I'm doing, I was invited onto the Rod and Tomatoes YouTube channel. That's apparently a thing that exists to debate some guy as to whether or not the Matrix 4 is good or not. They informed me off camera that several people wanted to debate the movie, but couldn't because they didn't want to lose their presser.  That is something that a person admitted to me. They did not want to talk crap about the Matrix because they didn't want to fall out of favor with Warner Brothers. I don't have any qualms about it. I jumped into that debate. I feel like I destroyed the guy. I went in hot, I left angrier, and he at one point had the audacity, and I've heard this from several people on different outlets. He had the cojones to say that the reason this movie is special was because Lana Wachowski wrote it in order to heal from a loss of a parent. Bravo. So brave. So stunning. My response to this statement was swift. It was simple. It was to the point. I merely said, listen, I lost a father at a very young age, but I didn't turn around and write a shitty screenplay to get over it. Okay, that is not an excuse. I certainly didn't write a crappy screenplay to a beloved movie franchise to bury the thing. All right, bury the parent, not your movie property. Anyway, we're back with Mr. Anderson. He's now a video game designer in this new version of the Matrix, and he's actually the most prominent, most well-respected video game designer on the planet, because you know what he made? The Matrix. What? How meta? How profound? They had him become the creator of the Matrix within the Matrix. This was actually an idea a lot of fans had way back during the original run, especially when Reloaded came out. There were a lot of theories saying maybe Zion is actually a Matrix inside of the Matrix.  But that was the idea. This is, I guess, kind of a way, a workaround to that concept, but done in the worst possible way you could imagine. Now, upon first inspection, Keanu Reeves still looks great in this movie, but he doesn't look like Neo. He looks like John Wick, because he's currently part of that much more relevant franchise, John Wick. Unlike the third or fourth at the time, has the longer hair, didn't bother cutting it for this movie, didn't bother cutting it for the majority of the film. He goes to the coffee shop with his buddy and in comes Karen, AKA Carrie Ann Moss, AKA Trinity. She has been relegated to a soccer mom character in this movie, going to get coffee with the kids. Her husband's literal name is Chad, and her actual name in the movie is Tiffany. Tiffany! Hate myself for watching this again. Neo, needless to say, is into her, but he's afraid to go spark up a conversation. We're now jumping back to the office where Neo is getting berated by his boss, who is actually the new Agent Smith, new and improved, played by a different actor.  That's right, two Chads in this for the price of dumb.  She's cashing a paycheck, she's getting in and out, maybe burn the whole place down behind her. And listen, we're going to go on a second side tangent now because it has to be addressed.    I'm just trying to respect everyone as best I can.  I don't care. I will say the Wachowski brothers have a pretty good track record with movies. The Wachowski sisters, not so much, haven't made a good film. Come on ladies, give me something to work with again. During this office conversation, the movie does clip show callbacks to the previous three entries. Just straight up footage from those movies put into this one like a glorified clip show. And I guess it would be fine if it was a quick little nod or a look back in time, but this happens throughout the entire movie. Several minutes of callbacks dedicated to the old footage.  This is where the movie goes full blown meta, as new agent Smith informs Neo, who's just Thomas Anderson at the time, that Warner Brothers, who is the company they work for in the movie, it's so meta.  Yet it's so surface level with the commentary at the same time. Warner Brothers wants them to make a Matrix 4, as in the video game Matrix 4, but also the movie, see the, wow, the parallels are striking.  And so they have to push forward either with Neo's help, Mr. Anderson, or without. They'll find a way. And Anderson even says like, I thought you couldn't do that without me. And Smith's like, well, we'll find a way. We'll find a way. And so he has to, his hands are tied. Either he makes this movie terrible, or he gives it to the studio to make terrible. What? Do you see how flawed this logic is? There were people online saying how brilliant and how sharp this film is, because Warner was able to burn down her own house and not let someone else do it for her.  Oh, all right.  Congratulations. I can't honestly imagine Warner Brothers making a worse version. They could have hired a competent writer and director to make something actually good. But instead you came back and had to put Wachowski on this thing and just ruin it all. That's not brilliant. That's not sharp. That's just shitty. And there were a lot of people like myself who freaking love the original trilogy. Yes, I love all three of them at this point.  Three is definitely rough as hell, but I can get through it. I can get through it. This, though, is just a whole other level of terrible. The scene ends, but the commentary is far from over. We're now at a team huddle and Narici is, for some reason, present for this one time only. She seriously has 30 seconds of screen time. She's in and out, cup of coffee. Gone.  They're talking about the games within the film and what they represent. The rich story, the lore, what it all means, what it's a social commentary on. This is essentially a Reddit forum come to life. During this miserable montage, Thomas Anderson's popping blue pills constantly, trying to keep himself from waking up. Back at the coffee shop, Thomas takes the leap and asks Trish for a cup of coffee. They sit down together. They have a boring-ass chat about the good old days in the video game. Tiff has this theory that Trinity's based off her because she just has a feeling about it. Maybe it's some suppressed emotions, some brain activity from a past life coming back to Hunter. Thomas Anderson's like, yeah, maybe. Maybe. I don't know.  I don't have anything to do. It's time to go into side tangent number three. In this version of the Matrix, apparently video game graphics are so life-like, they are one-to-one. Thomas Anderson's developing the Matrix video game. This is the fourth game. The other three games are the other three movies that we've seen.  But it's supposed to be video game clips. They're the same thing. It's ridiculous. Why not just make him a director in the Matrix? Then showing movie clips from the past ones makes more sense. It makes more sense that way, having him be a director. And then it just really is a true one-to-one comparison. I don't know why they went the video game route at all. Since Lana was hell-bent on pouring gasoline on her own franchise, what she should have done since Neo in this is a computer programmer or whatever, a game designer, she should have used clips from the crappy Matrix games that the Wachowskis helped oversee. There was Enter the Matrix. There was the Matrix online video game RPG thing. They should have gone and used... They should have used the clips from the games. It would have been hilariously bad. And it would have fit right in with this. Back at the office. Neo gets attacks from Morpheus himself, who's hanging out in the bathroom. That's the appropriate place you want to meet your hero. Hey, haven't seen Morpheus for a long time. How are we going to introduce this character again? Let's do a brilliantly crafted, timeless, ageless shot of the floor where you see the foot step down and we're just going to do a nice pan up till you see the stoke shot of him get revealed coming out of a bathroom stall. Morpheus tries to convince Mr. Anderson that he is in fact in the Matrix. The mirror starts to ripple. He tries to red pill him up.  We get another action scene. This one's far worse than the first, which is an impressive thing to already say, but it's true. Anderson's boss shows up coming to the realization that it's actually Agent Smith.  I just, I was fuming watching this movie. I was steaming, man. Let's go on to side tangent number four. When I saw this film, I guess we'll call it in theaters with my friends and we left and I was just a shell of a man who was already a shell of a man before going in, so I was like a shell of a shell, two matrixes deep, inception style. I came home and it was late. The next morning, my kids woke up like Christmas running down the stairs, ready to open their presents, but nothing was under the tree and it wasn't Christmas time. Well, actually it was Christmas time. Hey, regardless, nothing was under the tree. Instead, the present I was supposed to give to them was whether or not this film was good, because I had spent time with each child of my two going through the matrix movies with them. My daughter I started with, we watched all three of them back to back to back three days in a row. We grabbed takeout, we grabbed food from Chipotle, we had a fantastic time watching them over lunch. Two years later, I did the same thing with my son and it was an awesome experience both times. So this movie coming out lined up so well, because my kids had both just gone through and watched these movies and they were super pumped for the next one and I was super excited to share my thoughts. So when I came down the stairs and they saw me and they're like, Papa, how was the movie Papa? This is how they talked to me. My vision, which was looking down at the floorboards barely came up to meet their eye level. I couldn't look at them directly in the face into the eyeballs and I just shook my head. I just shook my head disapprovingly and that was all I had to do. And their reactions were honestly heartbreaking. They both just went, oh, okay.  I really didn't like this movie, but I am not going to stop you from watching. It's already available on HBO Max. You are welcome to sit through and watch this film for yourself.  Just, I can't even talk about this movie. I get so pissed. When Smith shows up and he grabs his gun off the ground and he's kind of coming to the realization that he's back in a new shell, it also dawns on him that he used to be a different character. And so again we get clip show of Hugo Weaving, the awesome Agent Smith, one of the best villains of all time. Not hyperbole. I believe that in my bones. You have Hans Gruber, Dr. Evil, Agent Smith. Those are my like top 10. The scene inexplicably ends with Smith shooting Neo, I think. And now he's on the couch with his psychiatrist, played by Neil Patrick Harris. NPH, we will find out is not just a psychiatrist. He's in fact this new branded architect known as an Analyst. I mean Analyst. It pains me to see my boy NPH in this role because this character sucks and he deserves better, but this is what we have to work with. Up on the rooftop, Neo attempts to jump to his death. I envy him. But Bugs saves the day. She's like... What's up doc? My name's Bugs because Bugs in a computer but also Warner Bros. owns the Looney Tunes and we're trying to bring the Bugs Bunny stuff back. Acme vs... Oh, that got canceled. Come with me through this door.  As one does. In this version, you don't have to go through good old fashioned untraceable landlines. You can just hit hot spots. You can point to destinations like mirrors and whatever. It doesn't matter. It doesn't matter. The way they get around is mobile. It's more mobilized.  But they're supposed to be video game shots. Up gigantic on a wall behind them we see greatest hits, montages from the flicks. What is... I hate this movie so much. After more exposition, which this entire movie is, they head back to the train and another action scene takes place. This one arguably the worst of the bunch so far. Still no bullet time.  Close up fight scenes. Very little choreography. Very little coolness to any of it. The iconic black leather. The glasses. It's all missing. Replaced with really generic NPC characters. We do get an introduction to one new thing. Swarms. Swarms are when the machines take over an entire group of people, essentially zombifying them so that they can go after a target. Not a bad concept, but ultimately doesn't serve much of a purpose in the film. Finally, Neo takes the plunge through a mirror, red pills up, and he's reborn again in his fluid sack. Since this whole movie is a trip down memory lane, we're now in a white background again.  Re-explaining everything in a lot less exciting fashion. Then we get the Dojo fight again. Finally, a cool hand-to-hand martial arts action sequence. No! Absolutely no! Nothing of value is taken here, but we are going to get a glimpse at Neo's one attack that he's going to use for the majority of the rest of the film, and that's this force push Hadouken blast that he does. But keep in mind Keanu Reeves looks like he would rather be doing literally anything else than acting in this film. He's putting in zero effort at all, and really all he's going to do from this point on is just go ugh and kind of block things with his hands and wander to and fro meandering from scene to scene, bringing almost nothing to the table. I've now hit the one hour mark of an almost two and a half hour movie.  One of the sentinels saves him. It's a good sentinel. There's good robots in this one. There's good machines. This one's name is Psy-Babe? Or Cry-Baby?   It's a pet that they can give commands to. It's a friend. It's merchandise that maybe Warner Brothers could put in a package on a shelf at Target and your dumb kid will buy, but no one's doing that. Nobody liked this movie. Take Neo to the new human machine hybrid city known as Ayo. And it's led by Jada- Keep my wife's name! Smith.  She was like, Neo, remember back in my day with you? I didn't believe you were the one.  I hated you then.  Not happy they brought you back. Blue hair, girl. You're fired. You're demoted.  I believe there's a hero in all of us. That's right, we got her. We got Jada. Now you'll be back, baby. And it's been a while since I've really celebrated this type of character, but what we have in our midst is a strong female lead. And for the Matrix franchise, it's about time.  But we got Naiobi now. And Naiobi doesn't play, fam. Naiobi tells you how it is.  How things really work now. That they've kind of joined up with some of the machines. They're working in harmony. They grow gardens. They had forest fields and stuff. And she even gives us a chance to pour one out for fish. We see a statue of the old Morpheus Lawrence fish burn. We have our fish up there, standing proud, standing tall. But ultimately, it was pride that killed the beast. He didn't believe that machines and humans could work together. He believed in the one. He wanted to stay behind at Zion or something. And they keep it kind of vague as to what actually happened to him. You have to play the video game to find that out or something. Who cares? Naiobi doesn't have answers for everything though. She is unclear. She's a little cloudy with a chance of meatballs as to why Trinity's being kept alive. Because her body was actually right by Neo's up in the pods. And keeping her alive, that's a bit of a flex. Because last time we saw her, she was impaled with about 13 tons of rebar. Metal going through all of her. And that was like the third time she died in that movie. Not a good weekend for Trinity.  It took years of repairs, putting the flesh together, reconstructing the brain materials and whatnot. And this was all at the behest of the new Analyst, I mean Analyst. And that's going to take us to the plot for the rest of the movie, which is to save Trish. Free her mind in Vogue style. Free your mind! Neo and his crew roll out but they quickly come into contact with an old friend, the Frenchman, who's now homeless. And a hobo. Everyone in this movie's kind of a hobo. Neo, the Frenchman, the Frenchman's goons, those vampire guys, they're back for some reason. Even Nairobi looks decrepit, wearing some old garbs. We are on fight number four. This is the worst fight yet, if you can believe that. Very little choreography to be found. They're fighting on top of wood structures. Things are breaking. People are going through walls. They get that subway section again from the first film. Done horribly bad this time around because just like everything else, it's worse. Agent Smith talks about how he's a free agent, if you will, able to kind of go wherever he wants, be his own man sort of thing. He's not at the behest or the control of whatever the machines are doing, which is nice. It is unclear as to why he has to kill Neo. If it's a grudge or whatever else, it's just really not clear at all. And later on, I will just fall to the wayside completely. But for now, they're going to fight for a little bit of waste time until inevitably we get to the scene that matters, which is the meetup with Patrish. They can finally connect and be together again. But before it happens, NPH interferes, snaps his finger, and bullet time kicks in. It's back, but it's not.   NPH just moving around and is like, oh, it's bullet time. I figured it out. I used your idea against you. Ha, ha, ha, ha, ha, ha. Free your mind in that depicted. He then goes on an explanation bender talking about how Neo and Trinity needed to be close, but never connected because it makes the energy or the battery life or the machines or some of the matrix even more strong. It makes it even more secure. It makes it so that their powers can keep the real sheep away from the truce. Or something.  What doesn't kill you? Makes you stronger. Stand a little taller.  Their mutinous behavior cannot stand. She looks at Boggs and says, Beep, beep, beep, beep, beep, beep. That's all, folks.  That's right.  For some reason, NPH let Neo leave. I don't, I don't know why, but he goes and talks to the new Oracle, which is the little girl grown up from the matrix revolutions. Full disclosure, it is at this point, I am now scrubbing through the rest of the movie. I'm hitting fast forward through chunks of it. I can't do it anymore.  It's pure torture for me to sit through and listen to this dreck.  Legit, hate it. I hate that people like it. I don't hate them for liking it, but I'm like, I'm just upset. I'm upset about it. I hate that it has a fresh rotten tomato score. Barely, but it's in the 60s and that's fresh. The movie is just so unimaginably awful. The freaking awesome slick action's gone. The memorable character is replaced by generic garbage. That high octane music nowhere to be found. Memorable sequences like the lobby shootout, the burly brawl, the highway chase escape, there's so many freaking awesome scenes. Nothing in this movie compares to you. Nothing compares to you. The trilogy was an event in time and space itself. The first movie touched greatness on its cheek. It kissed it.  It's a slap in the face. It's a handy without the finish, which is maybe the most despicable thing anyone can do to anyone else. Pressing on. Neal makes his way to Frankenstein's trinity and grabs hold of her. They touch. You got the touch. You got the p- And she wakes up fresh as a daisy. But now she has to make the ultimate choice. Does she choose Neal? Does she choose love?  Well, seeing as we never saw Chad and we barely saw her kids in that connection, there isn't much of a sacrifice there. We didn't get to know her as a person, this new version of trinity, so we don't really understand the sacrifice she's making at all.  But before he can get the job done, Mr. Anderson, Agent Smith shows up. He thwarts NPH, Neal, and trinity get away by doing some force pushing on the back of a motorcycle.  Trinity's doing cool stuff, driving around. Neal's just going, just kind of playing patty cake with the air. Eh, I don't like it. You know, ain't bullets. I don't want you here.  Super punch, super push. After failing to get hit by several cars, I came back inside to finish this movie. The Matrix is literally throwing bodies at these guys as people are jumping out of windows, smashing into the ground.  It all looks pretty terrible. At no point in time in this movie does Neal do anything remotely cool. He doesn't fly yet. It's gonna happen. It's gonna happen. He does try and fails embarrassingly, so, but we're at the end of the movie now. Thankfully, mercifully, we're coming to a close. Our two lovebirds are up on the roof. The sun is rising. It's beautiful. Spiritual. It's emotional. And they take a leap together. Leap of faith. A leap of love. But then the helicopter that's holding them up by an invisible rope that they took out digitally carries them up to freedom and safety as they're awkwardly suspended in the air clearly held in place by a helicopter. As Trinity hangs on to Neal because she learned to fly before he did.  She's great. She was always great. She's just even better now because she's actually the one. Well, she's actually the two. Two become one. Spice Girls taught me that. That's right. It turns out there's two ones the whole time. How dramatic.   They swing by NPH's house in suburbia. He's just chilling out on the porch, having a tea or something. And he's like, what are you planning on doing? Rebuilding the matrix as you see fit and doing whatever you want. I don't care, blah, blah, blah. And Trinity goes, no. I mean, yes, we are, but we also wanted to thank you for giving us another chance. Okay.  The machines could eventually kill them. What's the end game here? What are we even saying at the end of the day with this movie? What was the point of any of it? Well, nothing. That was established in the script when they said this was a heartless reboot, a heartless sequel, whatever it is, a reequal. And fittingly enough, the final shot is our heroes flying towards the camera just like in the original movie. But this time, Wake Up isn't played by Rage Against the Machine. It's played by a girl band. Because of course it is. Because of course it is. So brave, so unique, so different, yet so much the same. Now, final side note. I heard that the original Matrix trilogy and this movie, of course, was always a trans allegory. That's what Lana said. This was a trans allegory the entire time. All the movies were. Okay. Bullshit. But if you say so, I don't really care. That was the fun of the Matrix, was talking to people about it, sharing ideas behind it, sharing the messages, the symbolism. All that stuff is fun to talk about.  I need the thing to look and work right functionally on its face and this falls on it. I want to thank Brian Davis at patreon.com slash adamdasmovies once again for making me relive this horror-filled nightmare that I had to endure for two and a half hours plus write down notes, film, edit. It's a journey that I never thought I would have to do again. But here we are. Thank you for watching or listening or whatever you did with this rant, roast, thingy-ma-bobber. If you want to hear more, I have a whole playlist of roasts and rants on the channel. I do movie reviews every week. I do live streams every week. It's an awesome time. I talk movies 24-7 over here. Well, no. I mean, it's a matter of speaking. So I would love to have you stick around. Let me know your thoughts on the Matrix Retired in the comments below. Unless you liked it, then I just don't want to hear anything from you. I'm joking. Whatever you want to say, it's fine. Please like the video. Subscribe again. I implore you to subscribe to the channel. Become a Patreon. If you really liked what I'm doing, there's a super thanks icon somewhere under the video. You can hit that and say, hey, Adam, I love this video. Thank you for saying everything I thought. Here's five bucks. Here's 20 bucks. Whatever you want to give, I appreciate. And hopefully, I see you next time. Take care. Bye.


World Cities Day this year is happening the same day the world leaders are gathering in the United Kingdom and Italy for the Climate Change Conference and it's not surprising that the theme is adapting cities for climate resilience. Plus TV Africa's Ngoziko HSE went to find out how cities can grow sustainably. More than half of the world population live in urban areas and cities have progressively become hopes of innovation. Sometimes to the detriment of the environment. Ocone Afar, a suburb of Lagos is facing an erosion which is threatening to wipe out the community. Residents have consistently tried to engage with the government in order to find a way to protect the community. Just like Ocone Afar, cities and their suburbs worldwide are increasingly suffering from the effect of climate-related disasters. Desmond Majekodumi, an environmentalist and a chairman of the Lagos State Urban Forest and Animal Shelter Initiative, tells me that a concert effort to protect the environment is the only way to cope disaster in the state. It's very simple science. When you apply heat to water, the water expands. So the oceans are expanding. At the same time, when you apply heat to the ice caps, the ice caps are melting and they're putting far more water into the ocean. So we need to prepare for that by building barriers of protection along our coastal area. Barriers of protection along the coastal area and also far more effective drainage systems. Mr. Majekodumi believes in the idea of a harmonious relation between cities with nature and says Nigerians have a role to play in being part of the solution. We need to really, really ramp up with our environmental positive attitude. We need to go green. We need to just, you know, ensure particularly our mangrove areas where we're developing now. We need to really, really slow down that process very, very much. Like in the lekkie area and in Badagri area, mangrove, mangrove is one of the most effective natural ways of sequestering the CO2. As we observe this year's World Cities Day, experts want residents to know they can work with governments to ensure the sustainability of our planet. For Plus TV Africa, Ingozika or HSE. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Bridges are dramatic especially when they're lit up at night But they're not the only water problem that the Romans have to solve here in Augusta emerita They also had to figure out how to get water to them. So I'm gonna look at bridges and aqueducts today now I Thought I was gonna be all smart and ride out to this little bridge over the alcantarilla Um, it's near the Guadiana.  I'm like, dang There's a lot of Roman ruins when you have something of Roman origin and It doesn't even have a sign telling you what it is and I oh, yeah, I Thought I was smart and you know I was recording on Strava and I was like, oh, yeah I got out here and I kept going I went out into the country and I enjoyed that and then I decided to come back into town And I click and on my ride though. I wasn't back to the hotel and I stopped in front of a Roman bridge that I didn't take a picture of Because there are that many Roman ruins that nothing is mentioned. I then of course proceeded to ride back over anyway So these two bridges are small but the showstopper is this one over the Guadiana it's More than half a mile long. I think it rates it seven-tenths of a kilometer. So it's pretty decent size bridge and The whole thing isn't Roman But it was initially constructed by the Roman in this part here definitely is and If you go out into the island in the middle of the river you can see That the arches look pretty good and in fact when you get up close to it I tried to stick my thumb into the joints to show you just how tight they were and it's really well fitted even after all these years and all of the Being near the elements because you know rivers flood anyway The Romans knew how to build a bridge They also liked a good water feature in town even if this one's kind of gross This was in front of the temple of the Nerva and it's really nasty and stagnant but it underlines a fact that people have to have water and They did just that the Romans brought it in when they couldn't go underground Which they definitely did they brought it in aqueducts As you can see they didn't necessarily survive time, but this one is called aqueduct with De Los Milagros It's not in great shape this one over here it's called the aqueduct of San Lathro and it's in considerably better shape It also has a bike trail in front of it. Can you guess how I found out about the bike trail anyway? So this water would be brought from various sources either Springs bubbling up or they dam up something I believe aqueduct De Los Milagros was fed by Dammed up reservoirs and Aqueduct of San Lathro San Lathro was fed by Springs bubbling up anyway They would be brought into town and this is just outside of where the walls to the city would have been and I'll give you a little help seeing the course of the aqueduct Would have been brought in and Here's some more With some more help from your imagination they would have brought it in and put it into sedimentation or catchment Cisterns where basically they take all the nasty sediment out Because who wants to drink all the nasty stuff and water you've got to treat it somehow and the Romans actually did that which is Pretty advanced So that's kind of all I've got for you today. It feels kind of perfunctory to me. So Add a comment and tell me how I so dearly messed to this up that does seem to be the thing the classics community loves to do um drop me a like if you want to let the algorithm know what to do and Subscribe if you feel like I'm saying things that are useful next week Definitely not going to be more of Spain though. I do have a little more to share till next time


Hello, this is Laptop Media, and today, we will show you how to open the MSI Modern 15 and what's inside of it. To take this laptop apart, you have to undo 11 Philips head screws. After that, pry the bottom panel and lift it away from the chassis. Please remember, it would be of great help to us if you just hit the like button and subscribe to our channel. That would motivate us to make even more and better videos for you. We got the smaller of two battery options, which has a capacity of 39.3 watt hours. It lasts more than 7 hours of web browsing, or above 5 hours of video playback. To take it out, unplug the battery connector from the motherboard, and undo all 4 Philips head screws keeping it in place. Here it the memory is soldered to the motherboard. You can configure the laptop with up to 16GB of RAM. Storage wise, there is 1 M.2 PCI EX4 slot, which supports Gen 3 drives. However, the cooling looks quite decent. There are two heat pipes, as well as a heat spreader over the VRMs. A single fan then blows the heat away. If you'd like to see more disassembly videos of the latest notebooks we would highly appreciate if you hit the like button and subscribe to the channel.


What's up everybody? Jason here with Jazby's casebreak.com 2018 Peenie Donner's Optic Football 20 box blaster casebreak Grand team number one just sold out and this is a early bird free spot giveaway. So First 16 spots purchased in this break get entered into winning a free early bird spot giveaway So we randomize the customer names Before the break number one at the end of the randomize it gets a free spot and chase Lamar Jackson Hollows Baker Darnold Allen bark again much more Last Lamar Jackson PSA 10 hollow so for $1200 plus remember no veteran common ship and it's a full 20 box blaster case So the randomizer here dice roll is going to be for their early bird customers of teams and the names So good luck Let's roll the dice And it's five and a two seven times just for the other bird customers number one gets a free spot one two three four five Six and Boom chat you are the early bird winner. Congratulations free spot. Now. Let's go seven times now on the customer names and teams And I'm sure we'll have another one of these guys one two three four five six and seven Nicholas Nicholas seven times here one two three four five six seven seven times total seven lines down to the Green Bay Packers Niggas with the lines Matthew the Seahawks Brian with the Panthers Allison with the Eagles Brian crowd you have the Bengals chat free spot Texans Matthew the Steelers niggas with the Ravens Jeremy the Raiders Chad with the bills Brian you have the Cardinals Adam with the Browns Jeffrey with the Titans Adam with the Patriots Chris with the Chargers Adam with the cheese Brian crop of the Broncos Nicholas with the Vikings Mark with the Falcons Karen you have the jet giant niggas with the Dolphins and Jets Steve with the Jaguars Bucks Jeffrey with the Cowboys Marissa with the Saints Mark and with the 49ers Oliver you have the Bears Spencer with the rounds Mark B With the Colts Mark and within the Redskins and Nicholas last one with your Packers There you go alphabetize it maybe as a quick trade window In the meantime while you guys are trying to trade I'm gonna open up this case and start Rip and open some of these packs We've got a little bit of trade activity in one trade proposal I'm assuming Allison wants to trade the Eagles for the Browns So Adam Cupperman if you're here, let me know if you want to accept that trade Mark saying Redskins and 49ers available Raiders for trade so there's a lot of teams available for trade Let's just make a trade offer now guys So that way we can See we're gonna close this or continue to open up the trade window All right, is anybody gonna accept the trade or we're just gonna close. I'm gonna close right now like in 15 seconds Brian says no, thanks Jeffrey Nick trying to get to one of the two bigger teams So I don't know if Cleveland's available or Buffalo's available. I know Cleveland has been tried out a couple times bills Chad if you're here Let me know if not I'm closing it right now Think everybody wants the first like best five teams, so I get it though Always at least try right? There you go. He says he's good. Thanks. We're closing it thing guys trade window close. I guess trade window close It's a print out this list and let's rip. All right, so here you go. I ripped open five blaster boxes There you go. Again, these actually blasters are very popular on our Jackie's Alcon website. I don't think we have any more left, but we've done at least a couple cases worth of this stuff Pretty good value guys, especially if you get the right hollows Packers win a Nicholas Caloletta and Braxton Barrett for the Patriots pink rated Ricky Sam Darnold created rookie For the Jets that one Garoppolo hollow Royce Freeman I Don't work Tremaine Edmunds stud for the bills Vonte Maddox for my Eagles, nice Lamar Jackson, little base Raider Rookie, and Jaden Scott, another one there for the Baltimore Ravens, another one man, this is a Ravens hotbox, look at that, this is a Ravens hotbox, all Ravens here, nice Josh Allen, Bill's Bonachad, Alex Magoo, Kiki Kuti, Justin Watson, nice Royce Freeman for the Broncos, DJ Char, Luck, Kiseki, and Boston Scott, look at that, you got a little Boston Scott, and he was a saint on the practice squad before he got signed to the Eagles practice squad, and became a stud for the Eagles, he's definitely going to be our backup running back to Miles Sanders, there you go, little Boston Scott, it is Nick, and that's how the price has gone up just a little bit, but this is still very underrated, I think, I think optics out of prism doesn't give as much love, it has gone up just a little bit, Nick, I'm glad I'm able to hit you fire, oh really, Raider Rookie, there it's found okay so that's even, that's that's helpful right, just power it before you do it, because then I can just like make him out of it, Jason Hamilton for the Broncos, Jordan Lazzly, Howard, James Washington, David Williams, next one, Portland Sutton, I do too Ryan to be honest, fans of the game, but I usually don't watch them like you guys, because since I'm breaking my wife and I like to watch them together, so I don't watch them until I get home late at night, yes I'm excited for these two episodes here that are coming out, like I said I knew Jordan when I was a kid, didn't get to see him so much, but I did watch him as a kid, and it's like last year or two of Bulls, and of course Wizards, but didn't really get the whole background story of it since I was a kid in the 90s, so in 98 I would have been like six years old I think, and my sister was really really into basketball at the time, so I don't always watch basketball a lot too, and a nice Josh Allen Pink, Bill's with Alan Chadby, Jordan Thomas, you know I thought he'd come out a little bit more, but maybe he still will, you know, because there's still a couple episodes, if he doesn't come out this week, but I mean yeah, I think Kobe, I think everybody knows that you know, Kobe basically wanted to be Jordan, he studied him, he just wanted to be like him, you know what I mean, just in his own way though, you know with that mom of mentality in a way, so you know yeah everything you kind of see in Kobe you see in Jordan, so yeah like he said it's true right, there's no Jordan, there wouldn't be no rings for me, so I remember when I was a kid, you know obviously Kobe was big, because growing up here in LA too, my sister, my sister before Kobe came to the league, you know she liked Penny Hardaway, was her big one right, with Shaq, Penny and the Magic, and then when Kobe got drafted that was like her favorite, so you know I got to see and hear about Kobe all the time as a kid, but I'm not gonna lie though, I mean I feel like I rooted against the Lakers in Kobe only just because I wanted to like get my sister mad, but yeah how Ryan's saying like Iverson though man in the early 2000s was like damn that dude was so good, you know he seemed to handily like beat the Lakers in like game one right, he's one of the like one of the greatest players for him to not have a ring kind of like Shaq right, he was just like a one-man show, and when we heard that news about Kobe it was just literally our day after our grand opening, I just remember waking up to like the news here in in Southern California and like hearing oh you know there's a helicopter crash and we don't know who it is yet but we'll keep you guys updated and I'm like oh damn it's a helicopter crash but then knowing that it was like Kobe's helicopter it was him in there I was like wow that's crazy, Luke Falls, no I'm good, Ido Smith for the Falcons, Sean Watson second here, Richie James, we got one Lamar Jackson Pink, Raider rookie in the center, he looks beautiful, very nice, there you go, there goes with the Ravens, Durham Smith, Mike Giseke, Mike White, Nick Chubb, Ray Ray McLeod, Jordan Lazly, and nice another Lamar Jackson base, they're on pain, all right you guys last five boxes, so we're getting to the finish line, we'll be like maybe five minutes behind or so but we'll be on time for everything else I think, all right last five last boxes and again I'm sure we'll have another one of these posted either today or tomorrow, I see we have a have another one up there so maybe we'll use it for another cake break, nice did it awesome, we'll add that to the break schedule once I go through it, DJ Chark, Sean Lee, Christopher Hart, Herodon, Sonya Michelle, Mike Hughes, DJ Moore, Dalton Schultz, Socombe Barclay, Karen Steele of the Giants, Calvin Ridley, Dolbyn Bonamark, Sam Darnold, Jets, and Devonte Boyd, Shaquine Griffin for the Seahawks, Nick Chubb, Justin Jackson, and there you go guys that is the break, the 20 box blaster in the books, again not really known for the autos and the blasters but a lot of pinks, raider rookies and base raider rookie tharts with some hollows all being top loaded, some of the bigger ones here, Lamar Jackson, Pink Lamar, Josh Allen, Lamar Jackson, you got to get three Lamar Jacksons there for the Ravens, appreciate it guys, jazbyzcasebreaks.com


Do you also get bored with the same three options that we get in Elementor's Post Widget? Not much room to be creative there. And then you might be like me and try using other Elementor add-ons for their blog post widgets. That way you could add more style and do more as far as how you're gonna show your blog post grids and sliders on your website. Problem is, no matter what widget we use, we're always stuck with whatever options they give us.  Even your WooCommerce product grids and sliders, you could build them any way that you want. You could structure them, you could, anyway, any way you could imagine, you could build it. Well, you can. And I'm gonna show you how to do that inside this video with Jet Engine and using their listings. This is gonna be so easy and I guarantee you, once you see how to do it and how easy this is and what the possibilities that you have with it, you're not gonna go back to any add-on or even use the default post widget because now we could build our blog post the way that we like.  And that is because I choose not to rely on add-ons. I wanna keep my websites fast and clean. But still, using Elementor, one of the benefits are there are some really great add-ons to use. Jet Engine by far is the most used add-on that I use whenever building Elementor websites. So if there was a must-have add-on to get, I definitely would go with Jet Engine or even the whole Croco Block Suite. So if you already got Jet Engine and you already got Elementor, well, you're ready to go. And if you don't yet, there are links inside the description. All right, let's go ahead and get started and have some fun. And this is a website we're gonna add our blog post grid on. So if we go down here on the bottom, we got our latest post section down here, let's add our grid.  And just for reference, let's go ahead and add in Elementor's default post grid. So I'm gonna go here to my widgets, put in post. And we're gonna see here, here is our post widget. Now by default, we have this layout right here, which is our classic skin. We also have the cards. And then we have the full content. Full content is basically unusable. So I feel like really there's only two options. And here are the limitations right here. So here we can style it up and make it look cool. But we can't really change things. For example, we have the terms up here. We got our categories and that's pretty cool. But if we wanted to use the classic, we don't have that option right there. And let's say you wanna put the date on the top and you want the title down here. Well, you can't rearrange that.  So we are gonna build our own and structure it the way that we want. If we want the date on the top, we could put the date on the top. However we want it, we're gonna be able to build it. So let's do that now. All right, I'm going to delete this and let's go back to our dashboard. And here I already have JetEngine installed. After you've installed it, you're gonna see these options here. We're gonna do this in listings. So select on listings. And from here, click on add new. And we have a few options here. We're gonna leave it on post because we are pulling post queries. And then here we have the post type. Since we're gonna be doing one for our blog post, just leave it on post. Now, when we do do one for our products in WooCommerce, then we would select on products. And there's a whole lot of different options. We could also use custom post types. That's getting into more advanced and that would be a whole longer tutorial. We're gonna stick to just making a blog post grid for this tutorial and a WooCommerce product grid. The R timestamps down inside the description so you could jump around or come back to find the sections that you need. All right, let's go ahead now and give it a name. I'm gonna call this post grid one. And then we could choose, we could do this either on Elementor or Gutenberg. We're gonna leave it on Elementor because we are building our site on Elementor. What we are gonna do here is we're gonna create just one grid item. That's all just one. And with the listing widget does, it's going to repeat that item for us, making it a grid or a slider. So let's go ahead and get started. I'm gonna first start with an image here and let me use a dynamic tag and I'm gonna put post featured image. Let me go ahead and style this up a bit really quick. I'm gonna make this 300 pixels height and I'll leave it at the max width and I'm gonna set this to cover. Next up, let me go ahead and add our post title right here. I'm gonna use a heading tag and then I'm gonna click on the dynamic tag and select post title. I'll style it up really quick. Let me go back to the column over here and remove the spacing because I'm going to do a few things here. Next, I wanted to add the date above the title. That was one of the things I couldn't do on the Elementor post widget. So let me do that. I'm gonna click in terms right here. I'm gonna move this post info. I'm gonna put it above my title and this is just me playing around right now. I'm just showing the possibilities of what could be done. All right, let me go ahead and set this up. I don't want any icon on it. Let me fix my text, give it a color. I'll go ahead and give it orange. Let's just now, let's make it blue and give it our settings here. Let me add some spacing underneath the image. All right, and now I'm just gonna add a read more button right here. So let me put a button and then here as well, I could go ahead and click on dynamic for the link and we're gonna do post URL. And let me put read more. Let me add some spacing here. All right, let me style this up a bit so it looks kind of cool. And now I wanna add the category tag. I wanna put that up over here above the image. I think it looks cool showing the categories. Let me go ahead and do that by typing in post and we're gonna use the post info widget. I wanna put this above the image. Let me click off these three. I'm gonna go here and I'm going to select terms. And then I am going to choose categories. And let's remove this icon and style it up. All right, I want this to stand out a bit. So let me go ahead and use my global styles. I'm gonna go here to my width, put it in line right here, add some padding on it. Let's do four and then maybe 20 and 20 on the right and left. And now let's add some background color on this. Gonna give it that dark blue so it stands out. And I'm just doing this quickly to show how this all could be done. Let me do a negative margin on the bottom to pull it down. All right, it's hiding behind there. So we wanna go over to Z-index and put it on top. Let me just go ahead and put out one. If one doesn't put yours on top, then move up to 10 to 100 in order to put that element on top. And now we already have something built that we just could not do with Elementor. And again, we could do this any way that you want. You could structure it, build it. You are essentially building your post grid here. Now, let me show you how this all works. Let's update this. We're gonna go over to our Elementor page and our homepage right here. I'm gonna refresh it. Let me go back down to where we're gonna add our blogs. Now, go down here to your listing elements and we're gonna use the listing grid. This is where the magic happens. What this listing grid does, it takes what we built here inside our listing and it repeats it. So if we're using blog posts, it's gonna repeat the style through all the blog posts. If we're using WooCommerce products, it'll repeat it through the products. There's much more. We can use custom post types, listing websites, real estate websites, all kinds of things. Now, we're gonna keep it simple on blogs and WooCommerce products right now. All right, so go back to the homepage. And in our listing grid, we wanna go here to our listing, type it in the name and we wanna select that name. And you see, our blog posts now have been generated here. And then we have full control down here on how do we wanna display it? Do we want four? Do we want three? We can set it up for mobile. We can go through. We have all these options right here, equal height. We could go ahead and set this to be equal. We got the load more. We could do it by infinite scroll. We could do it by click. So we have all those options we will find inside like a post widget normally, but we also have a lot more in here, especially when it comes to the post query and the terms query. Now, that's a whole other tutorial. There's a lot to unpack in there. We're gonna keep this one easy, something that anybody creating a post grid could use right now. Now, one of the thing I would like to show you is the slider. Now, we could also turn this into a slider as well. All right, and let me show you again, just a little bit more on how this works. If we go back to our post grid, let's say we don't even want something in the blog post. We could put anything in here. And let me just show you what I mean by anything. Let me put in another text widget here. We can add anything and it will loop. Let's go ahead and update that. And if we go down here, now whatever we put in here is gonna automatically repeat and loop. But as long as we put a query in here, like a post query or product query or even custom post type, it's gonna pull that data and that's how we get these right here. And one thing I like to do as well is I like to make my changes and updates right here inside the list. Like, let's say I want to change this text right here. It's a bit light. Let me go here and change it to something more thick, update it, and then you're gonna see the live changes happening right here inside your grid. With this method here, we could do whatever we want. There are so many possibilities. You could create a sidebar list. You could create something that's vertical and stacked. You could create a big image with the title on top of the image. There's so much that you could do. So it's just like building out an Elementor page except you are now building out a section for your blog post grid, one individual item, and then you're gonna repeat it using JetEngines listing grid widget. All right, now let's go ahead and check out WooCommerce products really quick and see how that works. We're gonna go back to our listing items. I'm gonna add a new one. We're still gonna leave the listing source at post, but for the post type, we are gonna go down here to products. And let's add this WooGrid. We're gonna leave it on Elementor, but again, we could do Elementor or Gutenberg with this, which is super dope. All right, let's create the listing and let's build our product grid. So I'm gonna do a section right here. I'm gonna start off like I did with the other one. I wanna make this small just for the visual. I'm going to add an image up over here. I'm gonna go over here to the dynamic tag and down here, I'm gonna go to WooCommerce and choose product image. Now I can style it up. I'm gonna change the height to 300. Let me make sure the width is at 100% and then I'm gonna change this to cover. Now let me go ahead and add the product title right here. Now you could do this with the heading widget and just use a dynamic tag. You could go here, let me scroll down to our WooCommerce section and we could put in the product title. And let me style this one up really quick. I'm gonna change text color just so that way it looks decent right here. Now I wanna go ahead and add the price. Again, I'm gonna use the heading widget here. Also make sure to change the HTML tag so that way they're right. I would use a div right over here. On the product title, I would use an H2, that's all good. Right here though, let's go back to where we're gonna put our price and we're gonna use the dynamic tag again. Scroll down to the WooCommerce section, put product price right here. Now let's style this one up also and I'm going to, let me see, give it that color right there. I'm going to fix my widget spacing here in my columns so I have more control over it and I could go to my image and let me adjust the padding on the bottom of my image. Same thing on my title. All right and let me go ahead and add a buy now button. So we'll scroll down here to our WooCommerce section and now we could add the add to cart button. We're gonna put that right down over here and let's style this up a bit right here. Let me add my button text right here. Let me change the text color. I'm gonna put white in the background color. I'm gonna give it this navy blue. My border radius was cleaned that up right there. Let me add padding down here. Let's go ahead and click on update and put this in our front end and now I'm gonna do the same.  Underneath listings, it was WooGrid. All right, select that. And now we got our products. I only got two products that I put on this demo site right here but all your products will generate. And the same thing, whatever you add in here you could add in, let's see here on the top. Let's add a category tag right here. Go back down to WooCommerce, product terms. Click on product terms and we're gonna use product categories right here. Let me go to advance, remove this B4 text right here. I'm gonna change this right here to an H4. I'm gonna fix a color on it. Let me put an orange. Let's use some tiny text. Let's use some padding right here. I'm gonna make this inline. Let me give it a background and then I'm gonna use a negative margin on the bottom to pull this over the image. And let's make sure to give it a higher index. And there we go. We got our own grids that we built for WooCommerce. Same thing, we can make this into a slider as well. That's it. Now the freedom is yours. You could create your product grids, your post grids, any way that you like without having to write any code. And if you think this was cool, well wait until I show you how we do this with Bricks Builder coming up next. Now I do have a tutorial coming out this week showing how to do this with Bricks Builder with the query loop builder, which is the same functionality that is just built into Bricks with no add-ons needed. And I know a lot of us Elementor users are praying for Elementor to build this into Elementor where we won't need Jet Engine in order to do it. So I am gonna have that coming out this week. I'm also wanna do a comparison between the two for the Elementor users that are also experimenting with Bricks. So if you like this, then make sure to subscribe, like, drop your questions aside of the comments, I get back to everyone, and I'll be back again soon. Thank you.


Okay, so like I was saying last week, we were talking about something like this, reaction progress or reaction coordinate diagrams, right? And we were talking about, effectively, one step reactions where we were going from a reactant to a product, like our reaction was A to B, right? And we had a one hump, right? With the activation energy, we were calling this EA or delta G double dagger, right? And then we were calling this delta G here. Sometimes you'll see this delta GRXN or delta GR, things like that. That just means the delta G is a reaction, right? This is an exothermic reaction. Why? Because it's delta G is negative, right? So heat is being given off. So the reactants are at a higher level than the process, okay? So we're going to talk about, so this is a one step reaction. So now we're going to extend this to two step reactions. You can come for you lemons. Two step reactions, okay? So in a one step reaction, of course, that one step is the rate determining step because there's no other steps, okay? So it's like, you know, I don't know. Anything that you do in one step, right? You can imagine a lot of things. Okay, so let's erase this and compare this to a two step reaction. We'll do a two step exothermic reaction. So instead of going directly from A to B now, it's going to go from A and in between there, there was a transition state, remember? But now it's going to go A to an intermediate to B. And in between that intermediate and B is going to be another transition state. And remember, transition states are always at the top of that energy diagram, okay? Remember? So we did put TS formally up on that one. But if you go look back at those other videos, we were, okay? So let's do this type of reaction, exothermic, okay? So how many steps? One, two. That's how I know, okay? So this is a two step reaction. So from A to intermediate to B. So we could draw it. So up here, in fact, in this case, we would call this transition state one. We would call this transition state two, just to say one comes before two. The transition state one would be up here. That would be the point at when A is converting to intermediate, which is down next. And then transition state two is going to be up there. And that's going to be the point at intermediate converting to B. Is everybody okay with that? Okay? So is everybody okay with saying, this is a two step reaction, right? By looking at this diagram, how can you tell that? Two humps, yeah, okay? So it's just like the one hump camel and the two hump camel. Remember what we were talking about, okay? So remember the same, all the same notation applies though, okay? So if I say this difference from reactants to products, what's that going to be? Delta G, right? And since it's going down, it's going to be what? Negative. Okay? So remember what we called from the starting material of the reactants to the transition state up there? What do we call that? Activation. The activation energy, okay? Or EA, right? So or delta G double dagger, okay? So in this case, we would call this EA one, okay? Is that okay with everybody? So EA two, hopefully everybody could pick this out on their own, but it's going to be from this point up to this transition state because this is like another reaction happening, okay? So in fact, a two step reaction is actually what it is. One reaction occurred, then another reaction occurred, okay? It's like when we were walking across a river, right? We had to go on one rock and then go on the next one, okay? That's two steps, okay? So you can kind of put them into two little categories, okay? So this step also has an activation energy or delta G double dagger two. And in this case, right, we actually have, we can say, well, there's two steps. So one of them must have taken longer than the other one, okay? One of them takes a longer time than the other one, okay? So remember, it's just like pushing a boulder up the hill, right? This is going to take energy to push this boulder up the hill. But once I push it up to here and then I push it off, what's going to happen? It's going to go down there and it's going to slow down when it gets here, but it's going to just keep going, right? It's going to have so much energy going across, okay? So this step here takes very little time relative to this step. Does that make sense? Okay? So we call this one, in fact, the whole thing, right, not just the side of it, the rate of determining step, okay? So from A to I, step one is the rate of determining step, okay? It's not this actual point from the perfect step. Is everybody okay with that? So again, with a one-step reaction, that's the rate of determining step, because there's only one step. Is everybody okay with that? Are there any questions on this? Which part makes the bang? The bang? Yeah. So it's going to be the one that gives off the most energy, right? So it's actually the whole thing, right? So honestly, once you get up here, you're giving off the most energy, but the difference in energy is from here to here, you know? So you're inputting a little bit more energy. That activation energy is just a little bit, but it's this that gives off the bang, if you will.