Gold Pride is hands down one of the most expensive decks I have ever built in Yu-Gi-Oh! Masterful, with my list costing what was probably around $300 worth of gems. And to make matters worse, the deck isn't even tier one. It is however a lot of fun and really strong when it gets going, which is why in today's video I will once again be taking on to the rank ladder to see how it performs against all sorts of decks and to see if it can get me through Diamond and above. Lose and you'll lose a rank, okay let's see if Roller Baller can get me a win here. Let's see if we get a good opening hit. Oh, we do see the Roller Baller. We also see Emergency Teleport, which is really, really good. I am going to start with the Terror Top though, just in case. I mean, why not, right? Let's see what happens. Let's get the Terror Top out, see if the effect goes off. Draw any Ash Blossoms here. Any, well, can you ask this? Dimension Shifter, that is the worst. Yes, dude. Yes, thank you so much for dimension shifting that. I can't imagine what my life would be like if you didn't. We should still be good. I'm honestly going to Emergency Teleport off of this just to try to get as much possible life points down without touching my graveyard. So who do I want to summon for this? I guess the best possible bet would just be to grab Xiamen and only pop the effect to add. It's going to be very interesting. Dimension Shifter is a little bit of a sad, sad day for me. We're not going to lie. Thankfully, I don't necessarily care about Speedroid or Terror Top actually going to the graveyard. Have I normal summoned yet? I don't think I have, but it's a little crazy for me to do that, huh? Like if I just grabbed Shirakazai, I don't think I regret it here. I really don't. But I don't know if I necessarily want to pop the effect, but I don't know. I guess I grab it. Let me grab it just in case. Let me grab it just in case. And now we get to really do the talking. So what I'm going to do here is I'm just going to boom. We're just going to get that down. We don't necessarily care about these two. So I will just go into Cherry and Carrie. Cherry and Carrie is going to get banned though. Cherry and Carrie is going to get banned, but I think right now what we mainly want to do is build up our board to try to go next on his turn. Let's get this gold pride field spell out here. Bye-bye, bro. Get banned and see you. Oh, poor guy, dude. He never had to do that. Send a card from Deck to graveyard. No, I don't. I don't think we'll be doing that this time. No, no, thank you. Gold pride, better luck next time. In this case, I think we're just going to add a Nitro head, right? Like why would I add anything else? We're just doing this for the special summon. This is going to really hurt though. We're going to take a lot of damage here. 20, 2300. Okay. All right. Now we're just going to get every card on board and pass. We are not trying to do this. We're only going to get the one trap card. Actually, we might get both trap cards. This is why I run the two. I know people are going to say, hey, man, that's not optimal. You don't want to open with the trap card, but you know, but you know, sometimes you don't open with the trap card. And when that happens, I mean, I just find myself having a good day. So Nitro head in defense. We've got three guys on board here. I can even normal summon the Charakas, which do I want to do? I mean, it would be so easy to go into Ryzen Karp, but then I just get gatecapped by the dimension shifter, man. We could have had it all, dude. I could also go into any one of these things. So I think I will pretty much just summon. Let's summon Charakazai just in case, dude. Just in case. Can't really fusion summon anything here, but it's nice to keep the options open. We can also go into a monster effect. Ooh. Ooh, do we want a monster effect negate? Maybe I get a little bit different with it. I don't. Oh, do we just rank these three up into a monster effect negate? I think we do, boys. I really think we do. Let me get a gossip shadow out here. Let me get a gossip shadow out here. I think this is the play. Get a monster effect negate out. Let's see if he can get through this board. Oh, I thought I summoned one too many times. I thought I was getting nipped. Oh my God. All right. Cherry and Kerry is unfortunately going to dimension her shifter. Actually, no, only dimensions that one.  Hopefully we get a hand trap. Oh, Droll and Lockbird moment in gaming. Yes. That is exactly what I want to see. All right. And now on the beginning of his turn, we actually get to show off the effect of Nitrohead. So what this does, it allows us to clog up a part of his board and we can pop this Nitro token at any time to destroy everything in the surrounding areas. So really what we want to do is fusion summon almost as quick as we can, except it will. Yes. Go ahead. Hey, go ahead. Add a card. I can't complain, dude. Wait, does Dimension Sifter stop this? Is that how that works? I don't know if that's how that works. All right. So we don't activate Nitrohead yet. Obviously, there's nothing to pop. Oh my gosh. Okay. So he grabs Rygeki, which is not very good for us. Not very good at all. The Rygeki is pretty rough. Rygeki is pretty rough. I can't even tell a lie, dude. I can't even tell a lie. And I can't activate Droll and Lockbird because of Dimension Sifter. Oh my goodness. Let me just see what we got in the bag. We got nothing, dude. We got literally nothing. That's unfortunate. Unfortunate Rygeki and I can't Droll and Lockbird of either. Oh, life is so sad nowadays. And they all get banished because of Dimension Sifter.   I actually hate Dimension Sifter. Main Phase 2? Are we living? I didn't expect to live here. I mean, I guess you didn't want to play into Gold Pride to start your engines. Even though I don't have any engine. I have no graveyard fodder, dude. Oh, so many of the Gold Prides are banished. Rygeki actually just that. That was about as strong as you'll ever see a Rygeki for real. That was crazy. That Rygeki was another Droll and Lockbird, though. So we actually are able to discard with Foxy Tune now. So I don't, I mean, I guess I don't necessarily mine, but life is getting pretty tough out here. Droll and Lockbird to the graveyard. Do we get stopped? It doesn't look like we do. So we're just going to get Xiamen. And then we're going to have to activate effect, get 600 life points out of here. I guess we just grab Foxy Tune again. And then all we can really do is summon this and beat over him. And I guess that's fine. I mean, I'm not really too sure what the best play in the book here is. They don't, they don't really draw this one up. They don't really draw this one up for you. I guess I'll take the 600 attack. Might as well get that 2900.  Is this still a winnable game? I have no idea. What does this do? Oh, hey, um, I want that. Sure. I mean, 1500 life points isn't going to put us above him. So I guess I'll take it. And then we just enter and hope Droll and Lockbird and Gold Pride start your engines is enough to win here. Very, very, very tough duel. Not a very typical duel. I would say usually we would have already lost by now is how I would go about feeling about this. Still no Gold Prides in the graveyard, which is really, really unfortunate because normally we'd want to grab Leon off the top with start your engines. But in this situation, dude, this is barely a duel. Okay. Okay. Small world. He is struggling right now. Small world. He's got to be struggling. Let's see what he chooses to go for here. He's got unicorn that he's going to ditch and Droll and Lockbird. He's running Droll and Lockbird too. We're all afraid of super heavy samurai out here for an ash blossom. Do I want to draw this? Yeah, I do. Why not? I don't care. Is he going to synchro summon off my nitro token? Is he going to synchro summon off the nitro token? No. He just ends phase. He just... What is going on? What is this? What was that? I don't even understand what happened, but we'll take it. What a first duel. All right. Now we're in a position where we can actually win and get a rank. I will say though, that duel is not usually how duels are going to go. I'm going to keep it real. That was an outlier. Turn one. We're looking okay. I never really want to see Nyanian in my hand though. So that's pretty bad. We do get a Maxi, which is nice. Emergency Teleport can be good enough on its own and we do start with the trap card when... Yeah, I've definitely heard somebody say that that won't happen before. It was me. Let's start with Emergency Teleport just because we do have better luck next time. We might draw out a hand trap here. We might not. Okay. Ziamine hit the board. Talk to him then. Ziamine hits the board. We're going to pay 600 life points, get our life points down, activating the gold pride way. And I think we just take foxy tune here for sure. But we haven't really used our normal summon. We could also just normal summon. But then no, no, we want a foxy tune because I want Nyanian in the graveyard. That's how we're going to think about this. Foxy tune for the Nyanian in the graveyard. Get rid of foxy tune, activate its effect. Ditch. Whoa. Ditch Nyanian. Sorry. That was almost really bad. Ditch Nyanian. Get out. Charaka's eye. Oh yes. And now we just play the game. We're on the line. Hey, I might not be that good of a duelist, but when I practice one line, I can take that one line. Boom. Rising carp in defense mode. He's just here for a good time. Not a long time. Nosey and mean effect. Get him out of here. Tribute this fusion summon card. Now we're going to go into Dear Note. Yes, special summon another. And waggon. Boom. Boom. I'm feeling very confident right now. I'm feeling very confident. Nyanian in the graveyard because why not at this point? Why not bring out Nyanian? Don't forget we can just waggon for our very good punk field spell. I'll take that every day of the week. Punk field spell in effect now. And yeah, I think we just go ahead and bring out Jam Dragon Drive. So we're going to synchro our two punks together. Just get him right here. Yup. Hopefully we can get Shirakaze out as well. That would be really nice. But always activate the graveyard effect first.  Get Shirakaze out here. We need that Jam Dragon Drive. Absolutely activate after that. We can't send Nyanian to the graveyard. So we're just going to, this is literally the rare time where I think, well actually there is, there's some benefit to going Xiamen here because we could keep Shirakaze out on the board. But I think I'm just going to search out the Ghost Ogre. We're going to search out Ghost Ogre. This is a rare time when you can search your hand trap. That's why we run the one Ghost Ogre. And then Jam Extreme Session. Hopefully we draw into another rank three. That'd be really good. Oh, yes, yes, yes. We're getting the best of both worlds here, baby. I'm going to go Gold Luck. Better luck next time just to add a little one. I think I want to add the Nitro Head. I don't think that's necessarily crazy. Let me add the Nitro Head. And let me just, let me try some stuff here. Again, that's 2300 though. I always, I always definitely, I push it. I push it every time. So what we're going to do is Captain Carrie. Captain Carrie hits the board. Boom. That's beautiful. Captain Carrie Effect. That's going to get us our other trap card. Now I'm seeing why I run the double, baby. Look at that. Two of them. You can activate more than one of these a turn, by the way. Oh my goodness. Okay, let's get Nitro Head out here as well. Nitro Head is just very, very good. Or, I don't know, making those sticky plays happen. And then we're just going to go into Captain Carrie for these three here. Going to thin out our deck a little bit. I think this could also technically be wrong. He's going, hey, hey. He knew, hey. Sometimes when you're just playing the game, sometimes your opponent just goes on for 18 minutes. You know, you got to scoop. This is definitely a scoop deck, bro. That is crazy. We win another coin toss. Okay. It's never supposed to go like this. We are winning every coin toss. The luck is on our side today. Okay. Not a ton of hand traps in our hand. In fact, there's no way to lower our life points. So this is actually bad. This is not a very good time. I'm going to be honest with you. This is not a very good time. I wish that we had one card to lower our life points. Then it would be a great time. My opponent must be looking at, my opponent really trying to decide if they're going to shotgun Maxi right now. And honestly, I respect it. A Maxi would have done me in anyway, but there's, there's so little I can do here other than just summon Carrie for the trap card search. If this gets negated, Gigi's well played onto the next one. I had a great time. I'll see you in the next duel. Oh no. Oh no. Oh no, dude. Gigi's well played onto the next duel.  Good game. It's technically not over. We have ghost ogre. Okay. We have one hand trap. So unless my opponent can overcome the absolute strength that is ghost ogre and snow rabbit, then I'll surrender. But until then, we duel on. I've never had a stronger belief in myself that I'm able to win this duel. I can, ghost ogre is like Cariba. I can, I can hear them calling out to me. All right. Well, we're getting cooked. They actually hit us with the planet pathfinder in the current year.  Oh my God, bro. I'm getting done in like Kabasi right now. This is crazy. You know what? I honestly can't show the ghost ogre. I can't let him know I have a ghost ogre. I can't let him know I have no interruption. I'm toggling off. This is a rare play. You wouldn't see me do this very often, but I'm trying to get him to go bigger, go home. I need to see him come out with some big exceeds plays here. You want to play cash tier? You got to make some big exceeds plays. Surely he thinks I have nothing. And I don't have anything, bro. I have nothing. Of course I have nothing. You got me, bro. No response. Nope. No response to this one either. I got to be honest. But secretly, I do have a response. It's ghost ogre, the only chance I have. No, you got it. No response for me. But that's when I'm going to take it over, bro. Oh, you ripped three cards off the top, including a Leon and two foxy tunes. You got me. No response. It's response time, baby. Here we go. Here we go. This is it. This is it. Chengri. Come on, baby. Wait, I can't even do anything to this. I can't even do nothing to that, dude. I guess we just keep ghost ogre for anything else. He's just going to get another card out. Hey, I'll take my life points being lowered, though. I could use that. I need to be humbled. Ow, ow, it hurts. So, okay. So we could roller baller it up right now. Something fierce, something crazy fierce. But honestly, our life points are lowered. There's a whole ton of stuff we could do here. Okay, go ahead. I'm keeping ghost ogre for whatchamacallit, dude. Like, a rise heart? I can't let a rise heart come out, so I need ghost ogre to save me. God, this is actually roller baller's finest hour, by the way. This is roller baller's finest hour if it actually goes off. I'm not even going to lie to you. But first, we'll start with Leon, just in case. Just in case we got to draw anything out here. This could be roller baller's actual finest hour in the flesh. Special summon Leon in defense mode. Leon will activate their effect, and we'll get to summon Captain Kerry from the graveyard. That's going to let us search out that trap card we never got to before. Oh my God, if he banishes, if he banishes pinballer, we are screwed. The only card that we cannot afford him to get is pinballer. Oh, Captain Kerry's also getting eviscerated, which is fine. That's not really the biggest deal, but that does suck.  Please don't ban pinballer, man. Please, please. I can't take it. I can't take it. Don't ban pinballer, please. You can't do it to me. Please, please have no, please have not played against the gold pride deck. Come on, come on. Why would he ban pinballer? He doesn't even know I have roller baller guys. Come on. Come on. Come on. Don't do this. Yes, Star Leon. I'll take it. Just take a Star Leon off the top. He's just getting Leon. He saw Leon. He saw Captain Kerry. He's getting rid of Star Leon. Beautiful. Beautiful. We can't go Stoker that, which is fine. And now I got to know. I got to know. That is so crazy annoying. All right. Well, it's fine. Roller baller out. We can't even use this effect, huh? One, two, three. All right. All we need is three. Roller baller. Roll out, dude. Get the pinballer out here. Get a Captain Kerry. Get a roller baller. Get another Captain Kerry. Three monsters used from my hand. Yeah. You already know what's happening. It's pinballer time, baby. Oh, yeah. You already know pinballers better go crazy. Pinballer effect activate. Um, how many? I can banish three of these to get, what, 500? Uh, 1,500 extra attack. I don't think it's really worth it, so we're not going to do it. Give me this. One, you can sit right there. Yeah. Let me select another card. Give me this. Cash tier. You can go ahead and sit right there. Yeah. Another card. I think I will. You can sit right there. You all can sit right there for me. Battle phase time. Pinballer attack directly. Three cash tier is down. I should have destroyed one of these with Ghost Stoker, but I can't do it anymore. Wait, nine, 10, 11, 12. Do I have a 12? No, I don't. Okay. I guess I'll keep Ghost Stoker and my turn. That's going to trigger Pinballer's secondary effect. Unfortunately, we can't stick around forever. Pinballer is going to hit the grave along with all three of those, but we do get to summon a pinballer from... This is so bad. We get to summon a pinballer. Do I want to bring it out from the deck? I guess I will, huh? We get to bring back a pinballer from the deck, which is unfortunate because we have literally no other cards. All we can do is hope that he's cooked. That's it. All we can do is hope he's cooked. I probably should have destroyed one of these with Ghost Stoker later on. They're both one ofs. I don't know why I didn't. I was waiting for the Arise Hartman. I think we just get... We just get destroyed because of these field spells. We should have got rid of Birthway earlier. I don't even know what to do. I'm gonna be honest. I'm cooked. I think I'm just cooked. This is a very unfortunate moment in history right here. Just unfortunate. I feel like I could have played so much better. Definitely this duel's gonna come down to if I played this Ghost Stoker differently, could I have won? I was so afraid of the Arise Hart that I was blinded. I was blinded. What's he going into though? If he goes into Arise Hart, I'm actually cheering. I'm clapping my feet. No! Dude! Please stop summoning this guy. I should just take you out right now, man. I should just take you out right now. But I can't. If it negated the effect, if Ghost Stoker was also a negate, I would be cheering. Can you even use Ghost Stoker when Arise Hart comes out? Or it'll probably just be banished, huh? So you probably can't even do that. Damn! Oh, what it's like to be bad at the game. He's got the exact same board I took out. He got rid of, he got rid of Pinball in that second time though. He was like, okay, okay, we're not doing that. Unfortunate. I definitely think Ghost Stoker could have been played a lot better this duel. At this point, I'm just holding onto Ghost Stoker for no reason. But yeah, this duel, I guess it's just an example that I'm bad at the game. That's the only reason this duel's included in this video.  That is a shiny card, man. Hey, it's Arise Hart. Hey, at least now I'll be able to test my theory. So what I've come to realize is that this will probably stop Ghost Stoker because it doesn't even work like that. It would be banished. So technically, I probably couldn't even do it. I'm interested in seeing if that's how it works and Ash Blossom. At least let me test my theory, man. Let me learn. No. Okay, so it should still work. Never mind. So at least I'm not that dumb. At least it was kind of a thing I could have done. Hey, I'm still going to get my big moment in the sun, baby. This is what Ghost Stoker was for. This is what I thought would be the best play. Hey, did I just get chain blocked? It's not working. I can't even Ghost Stoker.  What an actually terrible day for rain. So wait, what's different about Ash Blossom then? Oh, it's just that you can discard this card. Why can't Ghost Stoker say that, man? Ghost Stoker is arguably worse. Come on, bro. Oh, I was wrong. I mean, I guess I was right. Technically, Ghost Stoker doesn't work under a rise heart. Damn it. All right, GGs. Well, hey, you got to have a little defeat in every video. To be honest, though, to be honest, I do have to do a side conversation. Why does Quillbow Hedgehog actually look like that? Like that? That is horrifying. Anyway, Speedroy Territop. We've got two of them in the hand. We've also got Crossout Designator, which is very good opening, just in case we see that Maxi. This guy's on win and he gains a rank. So I know he wants to... I know he's looking out for something here. With a hand like this, though, there's really no way to get into the punk engine. So all we can really do is cherry at carry and get our... What is it? Better luck next time? Yeah, better luck next time to start our life point game. So we're going to go ahead, hit the deck, get Takatop out of here. Save that. Hit the gold luck, better luck next time. And now I keep saying gold luck. It's gold pride. All right. So we do have a few decisions to make here because we have Leon and Captain Carry at a card. And this is not the one that lets us ditch, right? All right. So our life points are not lower. So we don't get to ditch. So we get to add one to our hand. Obviously, I'd feel way safer with the Roller Baller, right? Because it's another possible destruction. But Nitrohead is so good. Nitrohead is so good, dude. Nitrohead is so annoying. I guess I should say that. It's not really that good. But Nitrohead would be really great. I don't know if I want to take that much life point damage. The Roller Ballers feeling pretty good. You know what? Let's for the one time let... But if I get a fusion, I should have... You know what? What if I take a chance and just try to pull Roller Baller off? Start your engines. Let's do that. Let's do that. I'm going to take a... This is so greedy. So right now I'm playing for the trap card way, way, way, way, way, way later on, which could be very bad. But let's start with Captain Carry. Captain Carry is going to hit the board. Captain Carry is going to give us our trap card, which is what we want. Trap card's really good. Start your engines. Hopefully we don't draw into the next one. Also going to get a Nitro Head out here. Nitro Head's just also very good. Again, it's going to clog up that board a little bit. And then we're going to also get a Leon out here, even though we can't really do much. And that's... It doesn't get a revive effect, but that's just because it will go into a Synchro. Star Leon. But we ain't even doing all that now. We're going to set this. We're going to set Crossout Designator. And questions, dude. Do I... Do I go for the Speedroy Territop monster effect negate? Like I could just summon this, get a Gossip Shadow out with this and Leon. That's what we would call being crazy. But do I want to be crazy? Because we technically are going to get another carry. I could get a monster effect negate and just try to be him. But is that crazy? It feels crazy. Gossip Shadow's so crazy. Every time I overextend with Gossip Shadow, man, I always overextend. Am I going to overextend this time? Yeah, I am. Why not? Hey, come on. I didn't come all this way to not overextend and embarrass myself. Carry, Territop, Decide, Gossip Shadow, hit the board. Just in case you wanted to try something different on me. You know I got to keep it real. All right, End Phase. Captain Carry is going to... Or Cherry at Carry, sorry. Cherry at Carry hits the deck. Then we're going to get another Captain Carry. We don't get to search again because we've already done that once. But we do get to draw. Hopefully we draw into a hand trap. That's why you run 27 hand traps in the deck, baby. Because you've got to... When you've got to, you've got to. Nitrohead effect is going to activate. And when you're playing Nitrohead, you want to activate the effect where... Oh, wait, what? We do... You know what? We're going to cross out designator that. We're going to cross out designator that. We're going to... We're going to just banish Maxi. That is nuts! Cross out designator. We don't even got to Ash Blossom offensively. What do you have in response to that? No way. Cross out designator. Maxi, banished. Point your sword at him. We don't play with Maxi. That's a childish card. Banished. Nitrohead. Boom. Face up defense. You want to try to block up whatever extra deck thing you're not going to use. So I'm going to try to summon Star Leona to that one. So we're blocking up this one. Oh, he's also playing it, bro. He's also playing it. That is crazy. That's a little nuts. All right. Now we're gonna... Now we're gonna... He's also playing the Gold Prides. Now we're in a little bit of a nut situation. If we pop that, we should honestly be totally fine. Because that's his normal summon right there. If we start your engines, he is cooked. I say we just start our engines here. Why not? Why not? Just start your engines. I believe he's cooked. And if we get Roller Baller, he's double cooked. He just didn't draw the hand traps, man. If you're going in a Gold Pride matchup and you go second, you really... I mean, it's no surprise. You don't want to be doing that. Do I want to send out a carry just in case now? We hope for Roller Baller here. We have to include the Leon because we do need three. Hope for Roller Baller. Roller Baller comes out. It's Gigi. Oh, Leon saved again. But he doesn't get the search. He probably has nothing in his hands. I mean, what could his hands even be? My life points are lower than him. So he's screwed on that measure. We've got a Nitrohead blocking up Foxy Tune. I mean, this is just getting... This is just getting... I mean, we could even just Gossip Shadow this, which we will do. We're just going to Gossip Shadow this. We're going to let him draw. But I think we're totally fine here. We're going to Gossip Shadow this. We're both going to draw one. We have Ash Blossom in hand to be extra, extra, extra, extra annoying. We both get to draw one.  Hopefully he doesn't get anything too crazy. So now he's going to special summon a Punk Monster from the hand, which is fine. Now we're going to go ahead and get it to Star Leon. So we're really trying to outplay him here. He can't... Walgon doesn't even do anything, by the way. And we could also just pop him right here. We could pop and just try to kill him. But my question is why would he not already have a plan for that? Because I know the deck he's playing, Walgon is literally only to search this. He could maybe try to tune into 8, 9, 10. Let me check if I run any 10 synchros. I don't. So 8, 9, 10, that's awkward. We're not even going to... I'm not taking the bait on that one. I'm not taking the bait. Star Leon's going to come out. Star Leon's going to get rid of Walgon if he doesn't do it himself. We're not going to use that effect, no thanks. Does he run a 10-star synchro? You have another card? What do you run? Wait, what is he running? What are punk spell cards? What do you have? Do I shut this down now? I'm confused on what he even has. All right, I'll let it go through. Honestly, now I'm trying to let it go through to see what he's cooking with. He just run...  Why do you run two of those? Draw one card is a little crazy. I don't think we want him doing that. But do we really Ash Blossom that? I will. Draw one card. We're just going to try to shut him out here. We're going to try to shut him out. Called by was a card in hand. Okay, so he's getting the draw. He's going to get the draw. So Ash Blossom never really was a huge effect on this game. I wonder what he got? Because he's already used his normal summon. I'm not sure what else he could special summon. We have Star Leon. We have Nitrohead. This is very interesting. If he outplays me here, this guy is just better than me. Okay, so he's going to get to special summon his other guy. So honestly, I'm going to pop Nitrohead. No, we're just going to let that go through. Okay, now I'm going to go pride Star Leon. Boom, pop this. Okay, so he got another draw off me. Let's destroy that though. I've only got 14 seconds, so I really can't play. Okay, so now I'm just going to Nitrohead pop dude. The pug engine has been cooking me. I'm not going to lie. This guy cooked his way around me like crazy. I actually got outplayed there. I still don't know if it's enough for him to win, but I did get outplayed something fierce. All right, it wasn't, but I did get... Oh God, please! I did get outplayed something fierce.  I'm going to have to just end. I'm going to have to just end. Yes. No, no, no, I know I'm greedy. I'm greedy. I'm greedy. Thank you.  I can't even tell a lie, but now we're just going to go ahead and lower the life points for him. Get another Star, you're... I don't know why I played that turn one, but we should be fine. We're running out of time though. Is there anything that is like obviously a good play here. We could do this. Gold proc. Yeah, I think we just do this. I think we just star Leon our way to victory here I'm not sure how much damage we're gonna have on board, but if we pop this absorb its attack points I mean we should be pretty good captain carry as well. Why not right? I'm sure this is gonna be pretty good captain carry Let me just banish these real quick maxi do I care? I don't think I do care. Let me get that pop real quick Let me get that pop real quick. I think we should have enough damage on board to just win I'm just gonna ban oh wait hold on. I'm gonna banish most of these 3800 and that is enough damage to win out All right, and so that's that's all I'm gonna do. I'm just gonna attack I don't know if this guy has anything that could win here, but let's not let's not overplay ourselves Let's just star Leon and win that was just gold pride going first versus gold pride going second with no hand traps And he's still honestly he did pretty good.  I was getting a little out maneuvered there But we just the advantage was too strong. Let's go into one last one more duel. No way. Oh my god, dude I am the luckiest guy alive I'm the luckiest guy alive But not because of the coin flips because you chose to spend your day with me watching this video and I really appreciate that Okay, sob story out of the way guys. Let's see if we can get one last good duel in We get to go first again, which is kind of crazy And I'm just gonna play the jam extreme session Usually you don't want to open with that and let's get a foxy tune We could just send rollerballer to the graveyard. It actually works out better for us here. We're not gonna do that All right, so the special summit from our deck. We're just gonna go with xia mean xia mean in defense mode It's good to note that this is also going to put our life points low enough to get a leon into rollerballer play Anyway, so even if this doesn't go through, you know, we're still kind Chilling a little bit here. We don't really need our normal summons. So I might I might just normal summon Sharaka's eye to get this going. Let's try it, right? I mean, you know, we don't really need our normal summon We get the jam extreme session for the draw.  Sometimes it's definitely a single player experience But hey, oh we can special summon this. Oh, hold the phone. Yeah Why would I waste my normal summon then just in case I have to what if I want my normal summit for something? So you snifed me dude, this guy this guy had the ghost ogre on deck. Is he playing my deck though? That's the question. We still get the we don't get the special summon.  Anyway, I could be wrong But this is still just going to be a lot of fun rising carp defense mode hit the brakes Uh rising carp here for a good time. Not a long time. Zeeming. Thank you, but you're not needed All right ditch this. We're doing the standard combo here. I've walked us through this a few times Dear note waggon. We don't run two copies of this field spell. Maybe this is why that one guy does I do not let me check. No, I don't I I knew I didn't but I I had to make sure All right, so let's get waggon and dear note and then I mean, we just we just summon this right? I'm not gonna lie jam dragon drive You're supposed to use this to like connect your thing, but I'll be honest Part of me doesn't even want to bring out carry here. All right. Remember graveyard effect first This is specifically to ditch nyanyan. This is going to get our engine up and running jam dragon drive nyanyan We are not adding that to our hand graveyard draca's eye comes out boom Nyanyan comes out boom And now the question on everybody's mind is do I go into chariot carry with leon or with something else? Let's try it. Let's just see what we got right. I mean leon's gonna get us roller baller. No, oh wait.  I thought I synced right All right, that's gonna be good and then we could also bring out nitrohead just for the additional extra Cookening. Yeah, he's gone. He's That board was looking too good So what we would have done there is champion carried with these kept the two Punks for a synchro seven into a like three card bounce. I think I don't know. It would have been a multi card bounce It would have been great that that board was looking a little too strong And um, man, the hard part about this deck is that it's it's hard getting into a board state where people want to play against you Or play it to you because with no hand traps, it's just over but hey, I guess that's why the deck is 300 dollars Hopefully you enjoyed this though. I've been donna doya I kind of want to play this deck again, but let me know. I mean I kind of need to get up to diamond Right. I kind of want to take this deck to master, but I also want to play vanquish. Ah, so many plans. I'll see you in the next video


Hi, today I will explain to you how you can find streaming videos and DVDs. Notice I'm on the library home page, library.rit.edu. You'll notice in the middle of the page there's a search bar. I will click on the catalog tab. You can type in your keywords here or in the search bar or click on the orange search icon. Now I'm on the library catalog search page. I'm interested in finding information about ASL poetry. Notice I put an asterisk after the word poet. You might be wondering why. I want to find variations in the spelling of that word, like poets, poems, poetry, etc. So I have results from my search and I will look at this list to find a video I want. I can organize the search by date or time. I'm interested in the first or no the second title. Evolution of a Deaf Poet. So I'll click on that title. The record gives you the title of the performer, the name of the person, the title of the video, where it was published. It was published here in Rochester. Actually during a conference we had here in 1987. You'll notice there are two links. The top link is the YouTube video page. And the second one is called the library's digital collections. You can click on either one to find the video. For my example, I will show you the first link. It's really nice because you can see this video with close captions. And you can also turn that off if you want. If you need the transcript, you can click on the three dots in the corner, right here, the three dots, and click on open transcript. And then you can see the transcript too. So that's how you find one kind of streaming videos. We also have videos you can find in databases. I will show you how to find that. You can narrow your results to videos only. I will change my search terms to deaf poetry. I see something I'm interested in, deaf jam. You'll notice that this video is in our database, canopy. So I will click on the database link. You can see the page come up. This is an example of what it looks like. Also, when you click on more, you can open up the transcript. It also explains how to cite the video. You can set your transcript and caption settings. You can choose the font, color, etc. Now I'm going to go back to the library home page. Now I want to find a DVD. It looks like there's one I'm interested in here. It's called Flying Words Project by Peter Cook and Kenny Lerner. It tells you where you can find the DVD, the first floor, and the deaf media collections. It also has the call number. You will need to write it down or send it to your cell phone. You can check it out for three weeks with your ID card. So that sums up my presentation about finding DVDs and streaming videos.


We explain why clean energy is a reliable energy source, or is it? Clean energy is energy that is produced through methods that do not release greenhouse gases or any other pollutants The main sources of clean energy are wind energy, solar power and hydroelectric power In addition, energy that comes from geothermal power, biomass, biofuels and nuclear power are also deemed by some as quite clean in comparison to energy derived from fossil fuels However, let's focus on the cleanest of these energy sources Energy that can be generated from renewable sources like solar power, air currents and water Clean energy is reliable because it will always be available. The sun will always shine, the wind will always blow and water will always blow It will not run out like non-renewable sources of energy like natural gas, coal and oil But it will still depend on fluctuating weather conditions Let's consider how reliable each one is Solar power devices can only supply maximum power when exposed to full sunlight Which makes them unreliable at night time in cloudy conditions and in parts of the world where it is dark for long periods in the winter Solar panels are an easy addition to any rooftop or field But solar power is difficult to store because it requires a lot of battery storage The good news is is that this is something scientists are working on all the time Wind power is more reliable in many areas than solar power as turbines can easily be erected offshore However, they can only operate when the wind is blowing above a certain speed Hydroelectric power is created when dams use the natural flow of water to generate energy This method is extremely reliable on a large scale and reliable even in small rivers and streams in wet areas A combination of renewable and non renewable resources is currently being used to meet our needs However, the time will come when fossil fuels run out and renewable energy sources will have to take their place So how reliable is clean energy? While the wind may not consistently blow everywhere. It's almost always blowing somewhere We can apply the same rules to the Sun's rays Clean energy sources will help fight global warming and air pollution more wind farms, solar farms and hydropower plants will help build the infrastructure we need Technology will improve the efficiency of battery storage, solar panels and wind turbines in the future As technology continues to improve, harvesting and storing of power from clean energy sources will increasingly improve too to provide clean and reliable sources of energy


Welcome to your last session of the day. Apologies for standing between you and beer. We'll try to keep this high energy and fun, and send you off to the reception in high spirits. First, hello. My name is Christine. I'm the CEO and co-founder of Honeycomb. I care a lot about observability, but a lot of the techniques that I'll talk about in this talk can apply to whatever tool you happen to be using. Software in 2023 feels more like magic than it ever really has before. We are all here at this conference to explore what new magical capabilities we can add to our applications and user experiences. And for better or for worse, it feels like every CEO and CTO out there now turning to their teams, asking how LLMs can be incorporated into the core product. Lots to be excited about here. It's fun to be squarely in the middle of a phase change in progress. Everything is new to everyone together, but there's also a reality check. There being a lot more demand for AI functionality than the people who have expertise to build it, and that means software engineering teams are often the ones who are picking up the task to just figure it out and build it. And to be clear, from my perspective, this is something that's okay. As a generalist, software engineer, the fewer silos we can build, the better, the more we can transfer existing skills, the better. So this is my bias coming into this talk and about why we're trying to pull in existing techniques to leverage in this new space. Because on one hand, using and building on top of LLMs, it's a lot like using any other black box that you interact with via API. Lots of consistent expectations we can set about how we make sense of them. And in essence, we've learned how to develop against these black boxes and turn them into testable and mockable and reliable parts of our systems. But there's one key difference between having your application behavior rely on an LLM versus like a payments provider. How predictable the behavior of that black box is. And that difference, that lack of predictability breaks apart all of the different techniques we've built up along the years for making sense of our complex software systems. We have all these techniques to ensure correctness of the software that we put out in the world. But where with a normal set of APIs, you can fairly tightly constrain the inputs. You can reason about what inputs are valid and invalid when we build on LLMs. We are often literally inviting free form, open user input in whatever language and words they want to use. Reproducibility becomes a lot more challenging. Regressions are going to happen, especially if you have a model team or public API that is actively improving the model that your application is depending on. And with a tightly constrained black box API, again, you can reason about it in a way where I have a bank account. I'm gonna debit $5 from it. That bank account should have five fewer dollars in it. It's much easier to reason about and debug than a thing that is literally meant to simulate the full flexibility of human expression. So ensuring correctness is a lot harder. And I have heard that the right way to solve these problems is to build an evaluation system, to evaluate the effectiveness of the models in your prompt, which is absolutely a thing that you can do if you have an ML team to do it. But most of us aren't ML engineers. And the promise of an LLM exposed via API is that we shouldn't have to be an ML engineer to incorporate this technology. Rag pipelines make this even more complicated when we're adding additional context to our applications to help LLMs return better results. And it's just more work that your application does and introduces even more unpredictability into how these applications behave. So this turning upside down of our worldview is happening on a literal software engineering systems, systems engineering level, because these black boxes aren't testable or debuggable in a traditional sense anymore and there's no solid sense of correct behavior that we can fall back to. It's also true from a meta level. There is no environment where we can conduct our tests and feel confident in graduating that to production. Even normal product development practices have to be turned inside out. You can't just be like, oh, I have this early access group and I like how they're using the product and now I can release it to the wild and that will be a fair simulation. When the possible range of inputs is anything a human can dream up, all you're doing by limiting the folks who are able to use this feature is by constraining the set of inevitable failures you will encounter when an uncontrolled and unprompted group start to do things in your product that you never expected them to do. So should we give up on everything we've learned about building and operating software systems and embrace the rights of the prompt engineers, as the specialist skill said. If you have been paying attention to the title of this talk, the answer's obviously no. Because we already have a model for how to measure and debug and move the needle on unpredictable and qualitative experiences. Observerability. And bear with me a little bit. This term has become so commonplace. It's kind of fallen out of fashion to redefine it. Someone who's been talking about it for a while, hear me, I think it'll help some pieces fall into place. The term originally comes from control theory. It's about inputs and outputs. And it can often feel overly formal when we're talking about software systems, which it still emphatically applies to. But it pretty literally feels applicable to a system that can't be monitored or simulated with traditional techniques. Less formally, I think of it as a way to compare expected behavior against actual behavior but in live systems. And to ground this in things we may be familiar with, for a standard web app that you might be using, whether this is your bank website or something else, we can capture what is happening inside the software by looking at the arguments we're sending it, the parameters we're sending it, some metadata about how the app was running, and what was returned. And this lets us reason about the behavior that we expected for a given set of parameters in order for the engineers to debug and reproduce the issue that the actual behavior, when the actual behavior deviates from that expectation. And the thing about black boxes, these external APIs that we can use, is that even if something, it depends on something that's outside of our control, we can extend that technique, look at the inputs and outputs, and reason about what's happening and why and how what we're feeding it influences this behavior. The approach becomes the same for LLMs, unpredictable and non-deterministic as they are. It is a blanket statement that in complex systems, software patterns become unpredictable and change over time. With LLMs, that assertion becomes a guarantee. If you use LLMs, your data sets are going to be unpredictable and will change over time. And key to operating sanely on that magical foundation is having a way to gather, aggregate, and explore that data in a way that captures as accurately what that user actually experienced. But accurately, I mean expressively, right? And things that reflect what your application is trying to do. That's what lets you reason and build and ensure a quality user experience on top of LLMs. The ability to understand from the outside why your user got a certain response and how to prevent hallucination and what your application can do to ensure as high quality experience as possible. Because observability ultimately is here to create feedback loops that let you learn from what's really happening in the code. The same way that we've learned how to work iteratively with tests, observability lets us all ship sooner, observe those results in the wild and wrap those observations back in the development process as quickly as possible. So a little bit of a reality check. Why are we listening to me? Besides, I'm on stage and you have to and we don't have beer yet. Well, Honeycomb is a SaaS tool and we happened to release our query assistant, small feature built on top of LLMs in May 2023. I'm gonna say small. I think the customer impact was quite high but only took us about six weeks of development. And we dedicated about eight weeks afterwards to iterate on the experience. And I really like calling out this last piece because what we were able to do was really lean into watching real users in the wild use the feature and improve it live with that feedback. A quick overview on what this did. Our product has a visual query interface that lets folks interact with their telemetry. We believe that point and click. It's always easier for someone to learn than an open text box. But even so, there's a learning curve to use any UI. We're really excited about using LLMs as a translation layer from the human intent into what the GUI actually needed. And because we wanted to preserve a lot of the interactivity and explorability, we wanted folks to, of course, be able to tweak and iterate on their output. You can see, okay, you type in the thing, we do the translation, you can keep iterating. Because of this, there is no, and I think this is true of a lot of features, functionality built on LLMs, there's no concrete or qualitative result that it rely on that says, great, this feature is good, it did its job. It's a very qualitative sort of ask, hey, user, did this help you? Was this result helpful? Did it move you along in your investigation? And using this philosophy of observability, really gathering feedback and thinking about things from the user perspective, we were able to capture qualitative feedback and use that to posit some higher level product goals, like, will this help retain new users? Will this smooth the learning curve and measure those results and feed that back into our iteration? Spoiler alert, we hit these goals, we were really thrilled by how this was received. And yet, we still meet a lot of teams who are still in the early stages that they're exploring with LLMs, who were not as confident as we were to ship something live and see how people used it. And I think that this is rooted in the fact that when you're comfortable with this approach to observing a system from the outside, measuring results and expecting to pull them back in quickly, you can have a level of confidence in what you put out there that flexes really well to the uncertainty of this new world. As we were building our future, these are some of the things that we learned. Imagine for anyone who's been building on their own, these things are not new. Your users will do things that are unpredictable. You will have something that you're improving over here that breaks something over there. And they all reinforce this idea that what we've been doing all along to ship high quality correct software doesn't quite apply. And down here, there's a blog post that goes into this in much greater detail. So what do we do? What can we do about this? Well, step one, sort of the underlying piece of observability is leaving a paper trail for yourself. How and why your code behaves a certain way. I think of instrumentation as just like documentation and testing. It's another way for your code to explain itself back to you. And in this case, again, it means capturing as much logic, things that are unique to your application, your product, your domain, what users might struggle with as possible in order to validate or invalidate hypotheses for why is my code not behaving the way I expect? Why is this feature hallucinating? In a normal software system, this can let you do things as simple as, you know, figure out why latency is going up, figure out why one individual user is associated with unexpected behavior. It can let you do as things as complicated as figure out which implementation of an MP complete problem gated behind a feature flag behaves the best under real user workloads. So it's all about testing your hypotheses on production data. Brought into the LLM world, the same principles apply. If you capture as much as you can about what your users are doing in their system in a format that lets you look at overarching performance and then also debug into individual detailed transactions, you can do this sort of zooming in, zooming out high level trends individual debugging that we need to iterate quickly with unpredictable systems. Here you can see there's a whole range of things that you can capture about the interaction with any given feature. Capturing this sort of data lets you ask high level questions about the end user experience, score the quality of the response, aggregate on that, track progress over time. You can ask and answer high level questions about trends and the latency of those LLMs, what it's actually like to hit that API, whether the problem is on your side or theirs. You can then group metrics that you're capturing on fine-grained characteristics of each request, which then let us draw conclusions about certain user segments who are abusing the feature or using it in new and unexpected ways, or how context that we're pushing through the application impacts LLM performance. The more free form you are also, not having strict definitions for things like errors lets you capture that unexpected behavior in a not everything marked as an error because this is necessarily an error kind of way. When you're iterating fast and you're working with an API that might hallucinate, sometimes it's not an error, sometimes it's just behavior that you need to handle differently. A general philosophy, I have a thing against exceptions. Not every exception is exceptional, not everything exceptional is captured as an exception. It's just the way it is. When you use something like traces to tie all these pieces together, these complex pipelines, this rolling up of context, you can see how all these pieces contribute to a certain user experience. Likely you cannot read this from where you're sitting, but the tiny blue line at the bottom, that finally is the actual call that our service made to open AI. Everything before that point is building up the context to send an ideal prompt over. And all this context is what we need if we have any hope of figuring out why things went wrong, why our users got a terrible suggestion and how to iterate towards a better future. I think the thing that I'm most excited about here is that, again, this isn't a whole new skill set. A lot of this shift in how we build software is already underway. We already have some of the muscles built we need. As a baby software engineer, I used to take a lot of pride into shipping really fast. And I wrote tests along the way because, of course, this is just the way that things were and this is just a part of shipping good code. But in the last decade or so, maybe a decade or more, depending, we've already seen a shift in this conversation. It's not just write a lot of code and maybe write a lot of tests. We're already starting to see phrases like service ownership and putting developers on call and testing and production enter the lexicon of what does it mean to be part of a software engineering team. The developer's scope is starting to include production and what real users are experiencing in the wild. If we take that behavior shift, we've built up over the years, we do some tweaking. The things that developers have taken into ourselves, driven by a test of in development, can really be neatly applied to production maybe under a different name. If we identify the things that we should, the logical branches that we should test for in a test case, well, we can translate that to instrumenting our code with intention so we can capture that paper trail and debug. With tests, you're constantly comparing expected versus actual and why these deviate in production, whether built on the hell ones or not, you can watch for deviations. You can see what happens when your change goes live and see whether that's, again, what you expect. And with TDD, we're expecting to act on the output of these feedback loops, fail fast, expect to iterate. That happens with production too. These are guardrails that we have generalized already for building complex software systems that can be applied to LLMs to greater effect for all the reasons we've gone through already so far. Test driven development was all about the practice of helping software engineers build the habit of checking our mental models while we wrote code. Observability is all about the practice of software engineers, SREs, DevOps, et cetera, having a backstop to our mental models when we ship code. That's the ability to sanity check the LLMs. Necessary when we're never going to be able to have a mental model that is accurate enough to rely on, if like it or not, in this new gen AI world, nothing is predictable, except that there will be chaos taking a photo. I'll have a thing at the end where you all can download the slides if you need. So I wanna highlight one very specific technique that is a little bit adjacent to, but a little bit different from observability, which is a concept popularized through the rise of SRE commonly associated with existing software systems and ensuring consistent behavior. Just in case folks in the audience may not be familiar with this, I think of it as a way to force product and service owners to align on a definition what it means to provide great service to users. Often it can manifest in statements like these, and often they're used to set a baseline and measure degradation over time. You hear them a lot associated with uptime and performance in SRE metrics. But in our world, in the world of building on LLMs, when the LLM landscape is moving so quickly and best practices are emerging, it's almost like the emphasis there shifts. Instead of expecting degradation to be an uncommon case to watch out for, instead, SLOs can, you can flip them and have them help you watch out for, react to, improve on something that you know is going to happen. Having the landscape around you change and having your feature behave differently than what you expect. I'll show you an example. When we released our feature, I mentioned six weeks in development, we gave ourselves eight weeks to iterate. This is a thing that we posited worked and weren't really sure. What we did is instead of setting a baseline and then freaking out if it went down, we set a fairly low baseline. Usually SLOs are measured in terms of nines. Here, we set it at 70 something. We chose to set our SLO to baseline and actually use it to track improvement, saying, hey, this is what we're releasing, we wanna make it better, we wanna make the user experience better, we want people, this would be more useful over time. And we used, again, all those tooling around SLOs to help us identify the highest impact things we could do to move that line upward. This sort of telemetry that we captured, the expressiveness that we were able to rely on to map it back to our application logic is what allows the team to iterate fast, iterate confidently and work around this unpredictable and inherently hard to model API. And by choosing to measure from the outside in, it enabled a level of debugability that you don't get if you think, oh, I'm just going to instrument the LLM or I'm going to build my own model. It allows for this decoupling and moving faster. But you don't have to take my word for it. Two of our customers came to the same conclusion, actually independently. They were already using Honeycomb for parts of their application. Duolingo, language learning app, being a mobile app, they cared a lot about latency. And so when they released their LLM-backed features, beautiful use case, of course, for large language models, helping you learn another language, they made sure that they were able to instrument everything. Both the applications interactions with open API. Open AI, and also everything along the user path that might influence latency along the way. How services talk to each other. Different types of language, which language experience they were in. Intercom, another example here where they are a B2B messaging app. You might go to a website and have the chat bubble pop up, might be backed by Intercom. They similarly were rapidly trying to incorporate LLMs into their features, but they have a really heterogeneous set of customers, really broad surface area to their product. And so what they cared about was user experience while they were changing out some of their plumbing, and being able to track as many possible parameters at a given time so that they could isolate which set of parameters impacted that ultimate user experience while introducing LLMs.  But this is what lets them ship confidently attach cause to effect and really understand how engineering work impacts what the user sees on the other side. So in the end, LLMs break so many of the existing practices that we rely on to ensure a great software experience. But existing, there are ways to take existing software engineering and SRE techniques to make building on top of LLMs make sense. If you're able to capture all the metadata and use it to understand what's happening in your application, you can build great experiences, magical experiences for your users, as long as we embrace that unpredictability and measure from the outside in rather than really trying to expect an LLM to behave like a normal API. If you're curious for more, I am, of course, from Honeycomb. You can go out there, find out more, a little bit more about what we do and how we've helped our customers. If you want a copy of these slides, there's a QR code. It will lead you to not only these slides, but also a list of the links and blog posts and resources that I drew from in order to pull this together. Thank you for your time. I think I've got a few minutes for questions. Or again, don't let me keep you from beers. Thanks, everyone. Any questions? Inform the ability. Users, well, I'm not trying to think about anybody, personally, of course, but users very often skip giving feedback. Or, you know, like, how do you, what do you do in the context of how the app is developed or what you're expecting, what you said, expectations-wise in the UI that help raise the participation rate of users. That is, there are many design answers I can give to that, which would be a bit of a stretch because I am not a designer. I think what I would do if, you know, let's say, like you're saying, I look at the number of people that gave us that feedback and it's only like 3% of the people who actually use the feature. I would look at other signals for what would they do next that indicated it was helpful? They're running queries in our tool. If they are able to move on to their next query, maybe it was helpful, if it was different. If they just re-ran the same query again or what they started with, maybe not helpful. I think GitHub Co-Pilot last year actually released a really interesting study here where they similarly didn't want to rely on subjective feedback. They wanted to look at other signals for was, how do we measure success of this feature? And it's really interesting paper because they initially theorized that I think it was, they were like, oh, if people accept our suggestion and Co-Pilot and move on, then it was helpful. But what they found through a mixture of quantitative and qualitative feedback is people, the real measure of success is whether they accepted but then iterated on it. They like tweaked it. And so it's something that's going to be very dependent on how you are trying to help the user and what you're trying to unblock. I would much rather spend time there than why is this thing hallucinating in the first place. Any other questions? Yeah? You mentioned about the... Absolutely. This is like demo data, but a thousand percent, what you are capturing as that paper trail should, as your feature evolves, the telemetry you're capturing should probably evolve, the same way that tests and documentation evolve. The information and the metadata that you need to understand what's actually happening is necessarily going to be tied to what you're actually doing in the application. If you have a feature flag in the future, you probably want to know if the feature flag is turned on or off at the logic branches. I think that there is... I've met some teams where they're like, oh, well, we have our set of metrics, and it should never change, and these are the blessed set of metrics that we use to understand our application. I feel like that is just trying to build software with one hand behind your back or a foot stuck in the ground, because you're not going to be able to adapt. Certainly, there are some... It's possible to go too far to an extreme, as a team. I want to identify some conventions for which fields mean what and how to have canonical, like this is a customer ID, this is a user ID. But I think modern observability tooling allows for that flexibility and allows for, oh, I want to add this new field because I've added this new path through my application. Does that answer your question? I have lots of feelings about what people should not be able to do with data, mostly what they should be able to do, and some tools make that harder than others, but we can have that conversation while I'm not on stage trying to be vendor neutral. Yes. Is there some tooling? Probably. I mean, there's an infinite number of cool things coming out these days. My challenge with... If I was presented a tool that told me, it would help me figure out why my feature was hallucinating. I would say, cool! How do you know what hallucinating looks like in my application? How do you know what matters in my application? Are you going to let me shove... If I'm an e-commerce site, are you going to let me shove in the merchant and the inventory item and all the things that let me debug it in my systems, as well as all of the standard working with a model functionality? I think in a time of great change, my approach is always, how do we empower the people who are creating the change and the people who are building the software rather than putting too much faith in a tool to solve my problems for me? Again, it's a question of where you draw the line, but I really like seeing what teams can do and we say, here's the data that you need to investigate and really own, from the beginning to the end, what you want to build and whether it delivered that value. Any other questions? I'm going to take off the mic.  Thank you all for your attention today.