Hi friends, welcome back to my channel and welcome back to another collab. I am really excited to be participating in this collab because it is all Thanksgiving. We are going to put together an entire Thanksgiving dinner for you that is WW friendly. So if you are wanting to stay on track on Thanksgiving, we have you covered. So I am making a delicious sweet potato casserole as my portion of the Thanksgiving dinner. Once you watch all of the videos in the collab, you'll have an entire dinner that is WW friendly. So you can't beat that. Thank you to Paige at Turning the Page. I'll put it here on the screen for you, here on YouTube for hosting this collab. What a fabulous idea. So if you wanna see my sweet potato casserole that I have for Thanksgiving, just stay tuned. For my Thanksgiving recipe, I'm going to be making a healthy sweet potato casserole. You guys, those sweet potato casseroles are loaded with points, but not this one. This one is the perfect pairing for your Thanksgiving table. So let me show you what is in our sweet potato casserole. You're going to need some sugar or sugar alternative. So I'm gonna be using the Loconto monk fruit sweetener, light butter, unsweetened applesauce, salt. The recipe called for nutmeg, but I'm gonna go ahead and sub in my favorite pumpkin pie spice only because this has nutmeg in it along with so many other amazing pumpkin Thanksgiving spicy flavors. This is from Dax. Dax seasonings are all no salt, which is amazing before weigh-in. Or if you're watching your salt, they are all natural, no MSG. They have very, very good ingredients, very minimal ingredients. So it makes this a fantastic choice. This particular one, cinnamon, spices, and honey. That is it. This you guys is to die for. This is the best pumpkin spice seasoning ever. I love it. Dax has over 20 different seasonings. My code here on the screen will get you 10% off and free shipping. So head over to Dax, check them out. Again, amazing, amazing products, no salt. So perfect for WW. So I'm gonna be using a pinch of this in place of the nutmeg. You will need one cup of chopped pecans or pecan pieces, some cinnamon, and sweet potatoes. Now I took the easy route and bought these precut, pre-pilled, pre-everything, Trader Joe's sweet potatoes. This is the ticket to quick, easy sweet potato, anything. So you'll need two pounds and this is a two pound container. So let's get started on this sweet potato casserole. So our first step is we're gonna put our sweet potatoes on some boil and we're just going to roll them up. They are going to go in a 450 degree oven until they are cooked through. Now the recipe, of course, wants you to use whole sweet potatoes. So they're asking for an hour to an hour and a half to cook through, but because these are precut pieces, I'm betting it's probably going to be about a half of an hour. So I'm gonna go ahead and get these into the oven and I'll be back when they are nice and soft. So I just pulled my sweet potatoes out of the oven. They actually took just about a half an hour when they're precut up like this, so huge time saver. So what we're going to do is transfer our sweet potatoes into our blender and we're gonna add in a couple more good ingredients and then we're gonna get this all blended up and make it into a puree. So I have my sweet potatoes here in my blender. To that, I'm going to add one cup of unsweetened applesauce and I'm going to blend these two things together and then we're gonna add in a few more of our ingredients, but we do ultimately wanna get our sweet potatoes and applesauce blended up first. So we're gonna do that. So we have the sweet potatoes applesauce mixed together. Next step is we are going to add in three tablespoons of melted butter. You can also use coconut oil or ghee, but we're gonna stick with the lowest point option, which was the I can't believe it's not butter. To that, we are also going to add in some ground cinnamon and again, I would just do this to kind of your liking and then it did call for that dash of nutmeg. So I'm gonna do just a dash of the pumpkin pie spice from Dax and then lastly, we are going to put in a little bit of salt and then we're going to give this another big blend and get this nice and blended together and then we will be ready to put this into our pan. So now we're gonna go ahead and take that blended up sweet potato mixture. Oh, you guys, doesn't that look delicious? And we're gonna add it to a nine by nine baking dish. I greased mine, although the recipe did not call for it to be greased, I would rather be safe than sorry. Oh my, this smells so delicious. It smells sweet, spicy, buttery. Oh my gosh, you guys, yum. So we're gonna get this spread evenly in the bottom of our dish or as even as we possibly can. And then we're gonna put together the topping with the pecans and all of that cinnamon, sugary goodness. So I have these sweet potato casserole in the bottom of my pan. This looks and smells so good, I cannot wait for this recipe. So I have that in there in my bowl here. I have one quarter of a cup of the monk fruit sweetener. To that, I'm gonna go ahead and add some of my Dax pumpkin pie spice and I'm basically going to make a cinnamon sugar or a pumpkin pie spice sugar mix to add to the top of my casserole. And that will just caramelize really nicely with those pecans and just add that caramelized, sugary, crystaly, gooeyness to the top of my sweet potato casserole. So just get that nice and mixed together. And then with my spoon, I'm just going to sprinkle it right over the top of the sweet potato mix. Get it nice and even and then we'll top it with our pecans. Next, I have my one cup of pecan pieces. So I use both of those small bags, oven's ready, those small bags of the pecan pieces. And I'm going to sprinkle those over the top. And again, once this cooks down, that caramel-y consistency will come from the cinnamon and sugar mixture that we added. Oh, I'm so excited for this. Sweet potato casserole is my favorite part of Thanksgiving. My mom makes honestly the best sweet potato casserole, but it is not anywhere near. I mean, as far from WW friendly as you can be, it is loaded with a butter and heavy cream and sugar and marshmallows. But it is absolutely to die for. And it is the one thing I look forward to everything's giving. I even have her make it for Christmas. So I'm excited for that, but I am more excited for this WW friendly version of sweet potato casserole. So doesn't this look outstanding? So I'm going to get my oven warmed up, which you heard it beep, so it is good to go. I'm gonna put this in my oven at 375 degrees, just until everything starts to crisp up and caramelize on top, probably about 15, 20 minutes. And that's going to depend on your oven. And then we'll pull this out and we'll let this cool. And we'll be ready to give you the smart points and serve this up, yum. The sweet potato casserole is out of the oven. Doesn't this look so good? My house smells all things fall. So you're going to cut this into 10 servings and each serving is going to be six smart points. So really not bad for sweet potato casserole. And you have to remember that we have pecans and butter in this as well. So you can't beat it. So one 10th of the sweet potato casserole is six smart points. I will show you what a serving looks like next. Staying me on this Thanksgiving collab and thank you again to Paige over at Turning the Page for hosting. Make sure you check out all of the other channels participating down in the description box. Also, you will find the recipe for this healthy sweet potato casserole, so good.  So definitely something you could take to Thanksgiving and nobody would even know that it was made using Weight Watcher ingredients. So definitely check out everyone else participating so you have a complete Thanksgiving dinner in your arsenal. Thank you so much for watching. If you are coming over from someone else's channel, welcome, make sure that you subscribe. Hit that little bell so you're notified whenever I upload a new video. If you head over to one of the other channels from mine, please let them know that I sent you. And also thumbs up this video and comment down below. Let me know if you're going to be adding this to your Thanksgiving dinner table. And I'll see you guys all in my next video. Happy Thanksgiving. Bye.


We were able to make our like pop stars so sexy, but like can I have trouble like making Hyundai sexy? Of course the battery is important panoramic roof But the most important is that I can turn it into a KTV Can these Asian car brands actually compete with Tesla for the future of the EV market? Well, the internet seems to think so and maybe I do too Andrew Tesla is always in the news Elan's always in the news But this time it's because the future of its EV market dominance may be called in a question due to that You know German manufacturers, but mostly because of Asian car manufacturers. We're talking about South Korea, Japan China Vietnam is in there coming for the throne Wow. Alright, so let's get into it We're gonna cover the main competitors guys. We are not car experts. Okay, we understand that However, we are Asian guys and Asian guys love cars and Asian cars have dominated the market at least on a certain level for the past 20-30 years, you know, so guys let's talk about it David Who's the number one competitor in the game? That's going heads up with the Model 3 on the affordable EVs All right now. They're a competitor. We are talking about South Korea with Hyundai and Kia We're talking about iconic our Ionic 5 6 7 future models that are yet to come out Andrew They are swinging for the fences these cars look super futuristic. They're taking a lot of risks on the design They kind of look like mini Porsches mini like Audis, but even more futuristic Andrew. They're coming for it Yeah, I mean they're jam-packed with features obviously all in all a lot of people would say that they are a better value now Better value does not always equal sexier or what people want Of course as we know with kind of like Android phones like the Samsung series like those are great phones And they have a lot of features that you know iPhones don't I think it's clear that a fold for from Samsung has more features Andrew than iPhone right but a lot of people still want to go for the iPhone because you know for a number of reasons But anyways, like do you ever think Koreans are like? Oh, we were able to make our like pop stars so sexy But like kind of trouble like making Hyundai sexy So if we can just make the BTS of cars would be good for sure I mean they're right there. It's the most competitive out of all the Asia brands You think it'd be Japan, but we're gonna get to that later But Andrew there was a little bit of a blow recently because Biden is going to tax all foreign imports next year soon And give the discount only on American EVs Tesla is an American company and South Korea Andrew. They felt betrayed. Yeah I mean President Biden like we sent you BTS So why can't you give us a break on the TAX for the KIA number two Andrew? We're gonna move on to Japan. This has been the most dominant like car producer for the past 30 years globally And Andrew guess what they do not embrace the electric vehicle They only have like two EVs out of like a hundred models that they make You know what's really interesting? Japan is always one of those cases where they still all their products are still really high quality And they led the future for many decades, but now that same attitude of just betting on themselves might be holding them back Why are they only in the hydrogen game and not the EV game? Well, they do a little bit of a lot of like EV battery hybrids with combustion engines and a lot of hydrogen But it's because Andrew they themselves don't have the electrical grid to support EV charging and sort of like to structure their cities There's no space for EV stations and enter their island country. They have a lot of hydrogen So that's why they're betting on hydrogen. Here's the thing the rest of the world is not betting on hydrogen I will bet on Japan and hydrogen vehicles Whether this bet works out or not. I know that I did it my way Do you think they're making a huge mistake or do you understand the I guess the Situations and the constraints and sort of the mindset behind going with hydrogen I mean if you read a lot of articles guys, and I'm not an expert I'm not a scientist, but I heard hydrogen if you can do it is better than electric actually for a number of reasons So I guess they're hoping maybe that the whole EV thing like maybe blows over and then They'll be ready with the hydrogen vehicles at the end of the day or you know, maybe that's the only thing that they can do I don't know. I'm not really sure Godzilla emerged from the waters and the methane Extract to make hydrogen also will come from the depths of the ocean We will die on our sword like a samurai Regardless of the future Yeah, it's kind of like Japan was leading like J-pop and a lot of pop culture for a while And they were so innovative and then they've kind of been stagnant maybe the past like ten years You know what's really interesting Andrew? Japan will often develop the very best version of an older school technology like physical currency But it works so well They don't really feel the need to like hop into digital currencies or even like credit cards as much Andrew moving on to number three Andrew we're talking about the biggest EV market in the world the biggest car market in the world period We are talking about China David China has neo. Okay. That is like one of the best EV companies and then also they have BYD They have Lee Otto. They even have X-Ping man. All right. So I would say this So China is a huge car market a lot of EVs But I guess there's always questions about Chinese products even though everybody knows that they're affordable And they're a good value, right? You're going to wonder about the quality of the vehicle You're also going to wonder. Uh, did they just steal designs? I don't know if you really care about that and then number three as far as coming to America given the geopolitical technology cold war that we're in Obviously, like I could see a US not letting a lot of Chinese vehicles in for a number of security reasons, right? Yeah, possibly safety crash test history chronicles and things like that I mean uh long story short. I would not bet Andrew on the Gonghe six coming to the US shores anytime soon However, there are a lot of other markets globally that China can export a ton of EVs to right the affordable EVs I mean, these are the biggest car markets in the world by uh size China US Japan India Germany brazil south korea russia And it goes on and on. I mean think about it There is a lot of places that need cars So I guess at the end of the day if your car brand isn't dominating America America's not the only market sure America would be considered the top market, but uh, there's so many other countries out there that need cars You know one thing that I Thought was interesting when I was researching Chinese EVs Andrew is they really focus on in-car entertainment Like a lot of people got karaoke systems Even tesla had to put a karaoke system with tesla microphones in it to like be competitive with everybody else You know when I am shopping for a EV of course the battery is important panoramic roof But the most important is that I can turn it Into a ktv Number four guys, I'm losing my voice I know I know and we're talking about a country that people might not Expect to see on this this vietnam coming through with vin fast david you are so passionate about this Thank you for sacrificing your voice for this guys vin fast We'll get your vietnamese friend excited because they're actually Producing some pretty cool EVs out there guys If you look at it, they even have stores in america where you can check out the cars Yeah, we designed it in italy, but we made it in hyphen man Yeah, and they're trying to move their manufacturing to north carolina soon So they got big plans because they the big man because they're like vin fast, man You know like you got a you don't have to pay in cash, but you know you get to vin fast Man, I thought vin fast was vinh ph ast man Amen Are you telling me at the showroom they're gonna get some of the san jose abg So i mean vin fast h8 h9 guys the next country that is a huge car market and now a huge ev market Is india and india has some of its own car brands actually a number of them But the number one that we're going to be talking about is tata. That's probably the biggest one Uh, they're also known for making very affordable cars, but they got some new evs That are looking pretty slick the new tata curves man. It looks like as good as anything out there, man You know, I mean we got it all we got everything from tata nano down for like cheaper consumer All the way to curve I'm telling you man if we can get rishi sunak in a tata curve, man It would set it would break the internet Yes, uh, but uh jokes aside I actually think the south asian market is so gigantic that uh, india probably doesn't need to have their cars In the american market to be honest because they there's so many countries around there that need cars So yeah Andrew Let's just get into it andrew do any of these brands or collectively have the chance to challenge tesla's global market Dominance i'll tell you this There's a chance, but it'll probably always be a little bit like an iphone android type situation the androids always got crazier designs You know the tesla designs. They look very classical.  It's very minimalistic sort of like the iphone's minimalistic But people kind of they kind of trust it right and they kind of rock with it I mean to be honest. Yeah, if it's a good american brand I feel like americans are going to lean towards that especially given that like, you know They'd rather do that than like support other foreign brands. I mean low-key. That's always a feeling that people have Um, but I think that these other ev companies can produce better values than tesla I really think so and I think that as far as the model 3 goes which msrp is at about 45 46 thousand dollars I mean if you bring an ionic 6 at 40 000 dollars, I think it's gonna compete with the model 3 I don't know if it's like the x is gonna has any competitors or anything But definitely on the affordable end. I think it's possible. Yeah, I agree with you I think the majority of the competition where like tesla's gonna feel that crunch is gonna be on the lower end Probably sub 75 000 car. Yeah, but but for example for hunday, which is the main competitor It is gonna be hard to shake that hunday branding where like people still see it as like just a cheap car Like oh, I don't want to pay 70 000 for a hunday. Are you kidding me? You know, that's why they have genesis So I guess I'm surprised they didn't make a genesis the new like make the top ev in the genesis They do have ev genesis though, but interestingly enough the ev genesis don't look like ev cars.  Hey, man. Who knows japan just does the hydrogen car so well Everybody just wants the hydrogen cars. I don't know if there's any country that could do it It would be japan andrew. Um, I'm rooting for all the asian car manufacturers Even though we're like tesla stockholders. I will say this nobody gives you anything in this game though you got to come through With some great designs some great customer service and some great values consistently to break this market when it comes to the value game, you can never count asians out man You know, i'm i can't say for sure. They're gonna beat out tesla and all the other brands But on the affordable value level. Yes. Yes. And very much competitive thing andrew the market consumer market is more fragmented than ever Different people looking for different things. You know, some people care that tesla got creaky doors. Some people don't care All right, everybody. That's it. Uh, again, we are not car experts if you guys have some insight Please let us know in the comments down below. Hopefully you like this video Let us know if you really think these car brands can compete with tesla tesla being the big dog having the coolest branding Leading the way right now, but uh, yeah, let's know in the comments down below We're the hot pop boys. We're talking about everything from asian food to asian cars. Let's get it until next time. We out. Peace


What's going on everybody? My name is John Hammond. Another Pico CTF video. This challenge is called Practice Run 1 for 50 points in the binary exploitation category. I don't know how much of this is actually binary exploitation. You'll see. You're going to need to know how to run programs if you're going to get out of here. Navigate to this location on the shell server and run this program to get a flag. Easy enough, right? Okay. So let's actually just go ahead to this directory. Again, we're going to be on the shell server. So we simply need to grab that link. If we haven't had it before and SSH with our account as our username, let's actually make a directory for this. I'm sorry. Got to get that good practice in practice. Run 1. Let's hop over there and let's SSH to that account. YouTube at shell.com. Great. Enter your platform password. And now we are in there. What I'm going to do is I'm actually going to try and set the stage to do this automated in the simple one liner. But let's just jump over there to grab that flag quickly so you guys can get what you came for. And if you want to see that sprinkle sauce at the end, we'll tackle that. This program is called run this. All you simply have to do is dot slash run that program and it will pump a flag out for you. That's the challenge. Just running the program. That's it. So we could go ahead and copy and paste that move that in there and get our points. And that's fine and dandy, but we'd like to be able to make this a simple get flag dot SSH and flag dot text that we can encapsulate and work with and maybe save for some later use. I don't know. Again, good practice to just document our solutions. So what I'm actually going to do is go ahead and create a little private key for me to be able to get into the server fast and easily. So I'm going to use SSH key gen on my local computer. You can see I've just started a new shell down there. I'll go ahead and put this in my current directory, which is home John Pico. It'll go ahead and creates. I don't want you to actually overwrite the directory. My bad. Let's do home John Pico ID RSA. So it has a full file name in there. No passphrase. And now we simply have an ID RSA, which is my private key and ID RSA dot pub, which is our public key. So we can take this and go ahead and put that in the authorized keys directory of our account on the shell server. So let's make directory dot SSH move in there. And let's just add a little authorized keys file. So authorized underscore keys, cats, cats, authorized keys, paste that in. And now we should be able to simply disconnect from here, create a new session connection. If I were to use SSH tack I, and in my parent directory, I have my private key, which we'll just use to authenticate. And now we're immediately logged in with that command. We can stage this just a little bit further, because SSH will let us run commands as another argument once we're connected to the server. So if I had practice run dot one, all we have to do is just take this actual path here. And we know the binary is called practice, or run underscore this. So that will just pump out the flag after it connects to the server. So that's nice and easy. Now we can run our save flag alias, which should go ahead and create that as a get flag script, create a little flag dot text for us. And we are done. Everything that we've wanted to automate put together is simply there. We can run finish and now we've got that automatically set to complete. And that is that simple, just a little bit extra fluff for a crazy trivial challenges run this binary. But I hope that was good and fun and worthwhile. If you like some of that stuff, please keep watching. Please do like the video, comment and subscribe. Love to see you guys on discord server. There is a link in the description. Love to see you on Patreon, love to see you on PayPal, love to see you on Instagram, love to see you on Twitter, love to see you on Facebook, love to see you on LinkedIn.


Bride's first dance is ruined when she notices this. If there's a memorable event in our lives, then it's definitely the wedding day.  But since nuptial events are so special, we all have high expectations. Everything has to be perfect, and everything is overpriced. This leads us to those terrible weddings where everything seemed to be all right until someone punches the bride's father. While the bride from our story didn't witness a fight at her own wedding, she would soon realize that her perfect night was a disaster. There are some things you simply cannot control, but not in this case. Maybe it's just us, but rehearsing a wedding is so unnecessary. It's not a movie, a play or TV show. It's an event from real life and people are not there for a show. We're all going to a wedding to celebrate the couple that gets married. And while we did say we're not there for a show, sometimes the wedding becomes a show, especially when things get out of control. You'd think speeches are to celebrate the bride and groom. Well, in most cases that's what happens.  One single cringe-worthy event impacts the entire day, and you cannot simply forget that moment when those wedding crashers showed up to ruin your perfect and pricey wedding. Let's take for instance Melissa's wedding. The wedding is indeed one of the biggest days in our lives, and it must be perfect. After months of planning, every bride tries to make her dream wedding come true, and hopes everything would be perfect. The dress must be right, the cake, the music, the venue, and all the little details should be flawless. But things don't always go according to plan. There are some crazy stories out there, with brides fighting their sisters, or in-laws exactly on the wedding day. Thankfully, Melissa was marrying into a very loving family, and they were all supporting her. What she didn't know was that Brad held a secret from her. She felt something wasn't right though. As the wedding got closer, her premonitions would soon take shape. However, she never thought that could happen to her. Melissa and Brad were a very happy couple, and nobody was expecting to see their wedding fail. You'd think nothing could go wrong, but then some things cannot be controlled. Take for instance the free bar or the music. Emotional guests would indulge themselves with too much alcohol before the party starts and get so drunk they may crash your wedding by holding long speeches or running towards the stage to karaoke with the band. Melissa and Brad's wedding was soon going to have a problem as the music stopped. A few weeks before the wedding, Brad started to be secretive about his whereabouts, noticed one of the maids of honor. The best man was her boyfriend, and he was also keeping it all secret. What was she going to do about it? Tell Melissa? Her boyfriend was a bit cryptic on the phone when talking to Brad, so the maid of honor couldn't bear it anymore. She had to know for sure, so she approached Melissa. Melissa was so busy with planning and taking care of the wedding she didn't notice Brad was talking more on the phone and running too many errands. When approached by one of her best friends, she realized something was wrong. She knew Brad was being faithful, but what was he hiding from her? She brushed all her worries aside and focused on the big day, not knowing that the mystery will be solved right on their wedding day. The week before the wedding is very stressful, and as Melissa and her family was taking care of the last details, Brad was indeed meeting someone else. Soon enough, Melissa would find out. She had no idea that it would be right during their dance. This was the worst day in her life, she thought as the music suddenly stopped. The cameras were rolling and their video went viral overnight. Here's how their story begins. Mr. and Mrs. Brad Hewitt had just tied the knot, and while they had no issues during the first hours of the reception, things would completely change as their first dance began. Just when the bride thought everything was going according to the plan, she saw how her perfect wedding began crumbling into pieces. We all know that many weddings have something that goes wrong, but this time it went viral. It was spring when Melissa and Brad planned to get married. What she would experience was a small mistake at the wedding. Or so she thought. After the ceremony at the venue, the time for the traditional dance came. It was their first dance as a husband and wife, so it had to be memorable. Someone at her wedding was up to something, and the confused bride had no idea what was about to happen. How could she have been so clueless? Before Melissa got married, her name was Melissa Baker. She came from Akron, Ohio, and when she was little, she always dreamt of becoming a gymnast. She became a model at 17 years old and posed for different companies until her big breakthrough. Then, she met her other half. Melissa posed for the Sports Illustrated magazine, and she's quite popular. But she had something else on her mind. The model said that what was more important for her was family and home life, and when she later met the man of her dreams, it was time to tie the knot. The whole family was getting ready for the wedding day. In the photos above, Melissa shared on social media how busy they were with the wedding preparations. She was taking care of the centerpieces, without knowing that soon she would be shocked by what she'd witnessed at the wedding. And she wasn't the only one left speechless that day. Everything was as planned. The ceremony ended, and Melissa was getting ready for her first dance with her husband. Little did she know what was about to happen. It indeed was a perfect wedding, considering the beautiful bride would soon have to witness this. Now the special moment was about to come as Melissa and Brad were about to have their first dance. Everything was perfect, thought Melissa. However, Melissa had no idea that a surprise would make their wedding unforgettable. The cameras were rolling, ready to capture those moments. In the video posted on YouTube after the wedding, you can hear the DJ announcing that the newlyweds were about to have their dance. He then says that they have chosen a very special song for this dance, because it is from one of their favorite artists. The first seconds of the song can be heard. You can hear the song like there's no yesterday. What's interesting about their song is that it wasn't even released as a single. Mark Willis, the country singer, had a few number one hits, but like there's no yesterday was not part of them. This was a special song for the bride and groom. Then, things go sideways. For Melissa and Brad, this song had a special meaning, and it was perfect for their dance at the wedding. The night was just getting better, thought the guests. Then, they realize something is wrong. You can see the two newlyweds dancing on the dance floor to their song, slowly shuffling when suddenly the music cuts off and Melissa looks at Brad in confusion. The two stop and look at each other, and Melissa tries to keep her cool, waiting for the song to continue after the problem is fixed. She's wondering what could have possibly happened. Then, the DJ can be heard again, saying something about the music not working anymore. How was that even possible? What was happening? Then, the DJ says, well, we do have a keyboard, so we're gonna do a live version. Although visibly upset, Melissa agrees that it's better than not having their song at all. But she'll soon realize what's happening. A man joins the stage with a guitar and Melissa, and Brad continue to sway as the music carries on, but Brad slowly positions his bride so that she sees who is on the stage. That's when she finally gets it. She then realizes what was really happening and begins crying tears of joy. The newlywed spin around, and now Melissa finally sees what was the problem with the music. It was all a setup and she was actually dancing to the live version of the song, performed by none other than Mark Wills. The bride's reaction is indeed priceless. In the video, you can see Melissa screaming and running away from Brad to join the crowd. Then she comes back and does her best to continue the dance as Brad holds her in his arms. The two continue to dance, both crying and smiling at the same time. You can even see Melissa exclaiming, oh my god. She couldn't believe her favorite singer was out there, on the stage, performing that song for them. When the song is over, the bride goes towards the stage. Unfortunately, the song is now over, and Melissa lets go of Brad and runs to thank Wills for coming, and the groom just has to wait a few seconds. Then, the newlyweds become famous overnight. Here's what happens next. The video of the first dance became viral on YouTube, gathering over 26 million views. And their beautiful story carries on, Melissa sharing the latest great news with her friends on Instagram. Thankfully, Melissa's wedding was not a fail as other unlucky brides weddings were. What did she say about her reaction in the video? When the music stopped, she imagined they'd have to carry on with the reception, and have no music, which was a real fail since the night was just starting. On her social media, Melissa shared parts of the popular video, in which Mark Wills crashed their wedding and said that she will never forget the moment I turned around and saw Mark Wills. Here's what is the couple doing now. It means the absolute world to me. I can't thank them enough for going out of their way to make this happen for me. It's a feeling I will never forget, recalled Melissa on Instagram. Brad took a lot of time to plan this perfect moment, just to make the love of his life happy. And she thought he'd hide something bad from her, when he actually prepared a huge surprise. Three years passed since Brad and Melissa got married, and every year she shares a photo of her dancing with Brad, recalling their perfect wedding moment. A few months after the wedding, the happy couple had more great news. Months passed, and the Hewitts celebrated the arrival of a new family member, a little baby boy. This fall, their boy turns three years old, and their family photos are too adorable not to be checked out. We're so happy for this loving family, and if you want to learn more about their life as a married couple head over to Melissa's Instagram. Let's have a toast for the young family that has made it through their wedding with no fights, dropped cakes and other drama.


Hi, UXD team. You ready? OK. OK. Welcome, everybody. Today we're going to be talking about the expectation of open source user experiences and how the competitive landscape has influenced teams to being more proactive as far as user experience design goes. We're going to talk a bit about open source, open source UIs, as well as proactive and reactive design methodologies. And we're going to use Red Hat as a case to show examples of each and talk about how our UXD team has changed over the last five to six years. So my name is Serena Nichols. I'm the DevTools UX Lead at Red Hat. I'm Colleen Hart. I'm the OpenShift UX Lead at Red Hat. So before we get into talking about the expectations of open source UX, let's try to understand why open source is getting so popular in general. I'm sure this is a crowd would agree, but technology thrives in the open. And it's a proven way to collaborate in the software space because people are sharing and being collaborative and just building on top of others' work. So in a panel earlier this morning, I think Sarah did a great job of kind of summarizing this where you're building something, but you can only reach some certain limit without help from others. So you're just kind of continuing to build on others' work by providing feedback or accepting feedback in some cases. So it's kind of this continual cycle where everyone's being more transparent, but the end product is benefits from that. So with people wanting more awareness, everyone's kind of pushed into this open source atmosphere and everything's in the open. So with design in the open, how can we think about the user experience design process in open source? And it's the same principle. So it's about being transparent with your designs and your processes. So it's allowing others to contribute new designs maybe or provide feedback on existing designs or ways to actually improve. So maybe it's giving avenue for others in a community to provide comments or propose changes and kind of lead that discussion in an open platform. OK, so now we're going to talk about open source UIs. In the past, providing reactive design was kind of perceived as just doing enough to make products more usable. And if you look back to 2013 and before, enterprise software was really considered hard to use and cumbersome. And then 2014 and 15, what you saw happening was companies like Salesforce and Google started investing a lot of money into user experience. And they were really starting to be referred to as the pioneers of Enterprise UX and kind of pushed the UX movement across Enterprise UIs where there was a lot more focus on usability. So today, companies are heavily investing in UX. And they're really utilizing more proactive design methodologies. They have a lot more investment in UX, meaning they have a larger UX department. They have more resources. And they're really able to kind of go through that process of research and design and collaboration before development and throughout development. So now we're going to examine the progression of UX in Red Hat itself. So if we look back at Red Hat in 2013, our UX team was centralized. And we had about 10 people by the end of the year. Here's an example of, I think, six of our interfaces where, as you can see, they're very disparate user interfaces that felt super disconnected as a whole. They varied in behaviors. And each dev team spent time and energy to develop all the user interfaces separately. There was nothing in common between the two. So if you kind of fast forward about three years, our UX team had then grown to about 50 people. Not only were we comprised of interaction designers and visual designers, but we also expanded to include both researchers as well as front-end development. And our team really started to take off. We had defined a set of common user experience standards, which we called pattern fly at that point, which had implementation in both Angular and React. And our product designers and our developers were really able to utilize pattern fly to make those products look like a single product portfolio. And as well as, since they use common components, they had some level of consistency between them. So as you can see, this set of six products looks way more consistent and really feels like a single portfolio versus three or four years before. So now in 2019, clearly Red Hat has really invested into the user experience in usability. Our UXD team now has 106 people. And pattern fly has now evolved to be our open source design system. It's called now pattern fly four. It's been revamped to provide modular, accessible, and responsive components. And it's really driving our new UIs. Here you see a few screens of our newer products that are really using pattern fly four. And the expectations of open source software really continues to increase. So Red Hat's clearly, like I mentioned, continuing to invest in UX and designers and bring a more proactive user experience design into our projects. Yeah, so thinking about proactive design, this gets us into this topic of what is proactive design versus reactive design. So proactive design is really when you get a lot of information upfront because you're going through an entire UX process of gathering information, research, observing users to get that information. Because you're driving that process, you have more influence. So you're working to funnel down to a design to affect the whole user experience and the whole flow of a user versus on the reactive side, you have less influence because it's really driven by the product. So what exists in the product? You're making some minor tweaks, but you're not driving based on this information gathering. It's kind of here's the problem, let's react. So there's a little more concern and a scramble to make some minor improvements along the way. So taking a deep dive into proactive to start. So proactive is a holistic approach. Like I was saying, you'd have, in this case, you have, as a designer, more influence. So over that entire, thinking about that entire flow, you're solving a greater challenge, a user challenge, something that users are stumbling across. So thinking about exploring with usability testing or even just observing users. Sarah, one of our researchers was talking today about just observing and understanding what problems users are going through by just asking them questions or even just watching how they use a product can be really helpful. So suggesting alternatives based on these observations takes time and that's kind of the downside of this proactive design. You have to invest in it upfront. So Serena talked about the trend is moving in that direction, but it's definitely not easy. It takes time and planning, results are worth it. So looking at some of the quotes we found that resonated with us on the proactive design side where proactive designs are informed by actual user needs, not by guesses about how people might use a product. And designers are empowered to promote what an ideal experience could be. So it's really, in a proactive design case, you're providing even more guidance because of that research you've done upfront. So without it, you're only fixing part of the problem because you're fixing a problem based on something that already exists in a product. So maybe it's caused by decisions that were made ahead of time into the product versus understanding users' needs and solving the problem upfront. So looking at an ideal flow, creating journey maps for user flows upfront, you're dictating what that flow should be rather than backtracking in a proactive design case. So the ideal process is probably something, some version of this, we've probably all seen, it's really the design thinking process or I'm sure there's various buzzwords for it, but it's really taking into account some process where on the UX side, you're thinking about the discovery phase, which is really important in the proactive side. So running usability tests, competitive analysis, interviews, really digging into the personas to understand who you're designing for upfront before you're jumping into actually creating journey maps and kind of conceptual designs, then getting into wireframing, prototyping and kind of some iteration there before actually some implementation. And even after implementation, we'd like to be able to test and retest and kind of iterate a bit there on some of the design. So the proactive design process is really kind of what we think about as our ideal approach if we have the time and the resources. Okay, so now we're gonna take a case study for proactive design, which is OpenShift Topology. So the topology view is something that we wanted to be able to visualize application topology of an OpenShift project. And so we started this effort in late 2017 and as part of our discovery phase, one of our customer conferences, one of our designers held an activity where they asked our participants to kind of roughly draw out a diagram of their architecture on pieces of paper and explain and discuss how those parts interacted between each other. And these are a few examples of those. So these were trying to really understand how people's products, how people were working with OpenShift and what their architecture was like so that we could help figure out how to visualize these in our product. So as part of the create phase, mockups are created and we did the typical sharing with internal and external stakeholders for feedback and this was a super iterative process.  So we had quite a lot of time to do different iterations and get feedback from customers. So based on some of the feedback that we did get from customers, you see a new set of designs were created, relationships are different, what you're seeing visually is different, the information that you're seeing is different. And this came to be like from a product perspective, what we really wanted to try to achieve. So based on mockups, what we decided to do was POC it. So based on the API support that was currently existing in the product, we tried to have somebody develop POC and see how much we could achieve. Some of the data wasn't available so we had to cut some functionality out. And the other thing that we figured out was like some of the interactions that we wanted to achieve really weren't as possible as we thought they were. So again, we went back through and did another iteration on the design. And then we had our team started to implement that early this year. And this is kind of going through a usability test that we held at Red Hat Summit which is our customer conference in May this year and got additional feedback. And so since then we've tweaked it a little bit and what you're going to see here is kind of a preview of our final product and half of you are from the UX team team so you know that but we're also running a usability test on the topology view in the cafeteria area if anybody's interested in doing it tomorrow or Saturday. But this is going to be part of OpenShift 4.2. But this is a really good example of being able to go from having a long time period to having a long time period, just about two years from start to finish where we were able to do user research, competitive analysis, multiple iterations of design, collaborating with development as well and being able to produce something in time for a release. Yeah and just looking at another use case not quite the two year lead time but similarly still a proactive design use case for sure we had maybe just under six months, at least three to six months for this feature we were working on. Same product we were looking to create a service catalog and it started with a bunch of research up front. So we did a number, we went through a number of interviews and conversations with stakeholders and looked at four or five competitors and did some extra reviews of strengths, weaknesses, kind of what these products that were already out there were doing and what we could kind of learn from the existing competition. So that first phase was super important for the service catalog design as well and then we jumped into kind of following that at least month or so in the research phase. We jumped into the concepts and started thinking about how we wanted to structure this thing and how a user might flow through the various pages or areas of this catalog. So we kind of had a team, a couple of us were working on the early concepts and then came together and picked what we liked and didn't like of the various concepts to pick basically to create our ideal scenario and move forward from there. So still on the creation side but moving, you'll notice it started to move more towards a higher fidelity mockup. So we, on the far left, still we're in balsamic, lower fidelity, but as you get towards the bottom we started working with the visual design team within our group to get that high resolution to be ready for development. So as we passed it on and started working with the development team, we got some prototypes and implemented that we could tweak a bit and test a bit at Red Hat Summit, get some initial user feedback based on those prototypes and kind of go back, like we said in that process, go back and iterate on some of these designs to tweak them a bit, make some improvements where we could, kind of based on a couple of the things that we noticed. So one key being, you know, not everyone, depending on their environment, not everyone would see those highlighted items at the top. So that whole blue area might go away, you know, what can we do to make this catalog a little bit more interesting, maybe pop a bit more and what can we do to make the categories stand out a bit more. So, you know, once we saw it and watched users interact with it, we kind of realized, okay, we need to make some adjustments. Let's add some search capabilities in here. Let's add a tour so users know how to use this new product. So kind of that revamp, and then it went through another round of implementation with those updated designs. So definitely another example where we followed that longer lead time proactive design cycle. Okay, so now we're gonna dive into a reactive design. So by a show of hands, how many of you guys think that reactive design is a bad thing? Okay, cool. So reactive design is not design driven, right? It emphasizes that UX is an afterthought, which for sometimes for a designer, it's not like what we like to hear, right? Cause we want, a lot of times we wanna hear that. That development's gonna listen to us. So here's a quote about reactive design. It's just what it sounds like, reacting to a problem in the moment. So oftentimes we're asked how we can fix something, help users are complaining and these things are too hard, so what can we do? So reactive design really results in fixing problems based on decisions that have already been made or implemented. So is it a good thing to do reactive design? It definitely is, right? I mean, sometimes people think about applying a Band-Aid or putting lipstick on a pig, adding visual improvements, syntax changes. UX is being an afterthought, but really it's not impacting the end-to-end user experience but it's still improving usability as a whole. And it's better than nothing. So I think one of the questions we have here is like how many companies have enough designers that are able to provide thoughtful designs for every feature that we create? That doesn't happen. So in actuality, developers are gonna have to develop things when they don't necessarily have a design and then use reactive design as a tool to make things better. So yeah, I think a positive use case for reactive design, this will be very familiar to you, but basically we had a case where a feature was upcoming in our product pretty recently and the development team had a cool idea to expose this API Explorer into our product and it's an interesting concept that we hadn't chatted about on the design side at all and we kind of got brought in after this initial POC was created. So on the UX side, we're thinking, okay, we're in the reactive state, we wanna get this into an upcoming release. How can we make some improvements to start? But it's already created and seemingly going in the product as is. So one thing we did was just take a step back a bit and try to think about, can we validate some of the assumptions and use cases that this is solving? What are the, what's driving this requirement and need in the product to help us understand how we can then improve it in the product? Like I said, of course there's minor tweaks we can make but we really wanted to make it a usable feature that will succeed in the product. So when development is asking us for help on something already implemented, we can still do some of that like gut check of what is this requirement? What is it fulfilling this feature? So looking at our reactive designs, I have a couple of examples but a few of the things we looked at were can we just make it a bit more usable by adding some filter capabilities, some search capabilities, sorting, some basic things. You'll notice we kept the basic structure of there's a page somewhere in the navigation that has this list view of things and when you actually dive into one of the objects, you're getting more information about what metadata is available for that resource. So it was still a list view and a detail page but just adjusting kind of how some of that information might show up and how users might flow through the pages. I think we got some improvement from these designs. So just simple things like adding tabs or adding some hierarchy to the page. We got some improvements there and just a couple other screens from the design side. We were thinking about this, maybe it's not the V1 version of this feature but maybe it's something we can implement moving forward and make it even better by adding this throughout the product. So this feature in particular is allowing you to explore various resource types in one exploration area but what if we provided that help in context? So when you're looking at a specific resource like a pod, you could access this exploration help in that context. Maybe using a side panel was the recommendation in that screenshot on the left and part of the reason for that is that was an existing design convention or pattern that we're already using in other places in the product. So it was kind of one of those in a reactive design state, you're trying to make use of things that already exist. Do you have enough lead time to introduce completely new patterns? Probably not but maybe you could think about that for a forward-looking feature and in the meantime make use of some existing patterns that you have to improve the feature. So that's kind of what we love to do in creating even just like some of the tabs, some of the side panel designs that you see on these pages. And then when we got back to the updated implementation, just searching through for some of these screenshots in GitHub, there were 17 or 18 pull requests related to this feature. So the key was definitely collaboration. So we had a lot of collaboration back and forth between design and development and there were a lot of these minor changes, let's implement sort. Another PR, let's look at filtering. So it was definitely a success in my mind because of that collaboration. So a couple things, it built trust for sure going back and forth with design and development working hand in hand. But it also, we definitely both learned something from each other. So I think on our side, on the design side, we learned by seeing their initial POC what was possible and what this feature could do for the product, what was kind of available via the APIs and maybe what limitations we had today. It was a little bit more clear to see versus if you don't have anything upfront to work from, it can take a long time to gain that product knowledge and do that upfront research work. Sometimes two years, hopefully not always, but that's kind of why in some cases this can speed up the design process and I think it did for us creating this feature. So building trust, collaborating, it was a positive result. So I would consider reactive design as being something that can work if both groups are kind of on board. Yeah, so I'm going to talk about a couple more examples of reactive design, not specific examples, but just general. But I do want to kind of reiterate what Colleen said and what I said previously as well is in open source companies, collaboration is key, right? It's one of the biggest premises that we have. And I think that is what really makes reactive design work better. Being previously, to Red Hat, I worked in a company that was not open source and the collaboration was not the same. So I think, at least here at Red Hat, reactive design to me is much more successful. So another example where reactive design can be useful is like if you discover usability issue during beta testing, right? And it needs to be addressed before GA. So in this case, you're up against a time crunch. You need to kind of research what the problem is and determine how to best solve it. And you probably have to collaborate with your stakeholders, product management as well as developers to identify how much can you fix, how much, based on the time that you have. This could include addressing the problem completely. Or if you can't, like maybe you can still improve it by providing contextual help or adding some documentation to explain the problem or how to fix it. And then you can also be sure to plan for a better solution that can be implemented in the next release. And another example where reactive design is productive is if a design attached to the developer, in a work in progress PR, for example, and they're looking for somebody to collaborate with. In this case, you probably have more time since the developer has asked for your help. And you want to work with them to understand what the issue is and take advantage of your design system. So like Colleen said, look and see if there's any patterns or design conventions that you can apply to the problem to help fix it or at least provide some consistency. And again, if there's not enough time to fix it the right way, just suggest a stop gap and see if you can implement that and follow up with the plan for a better solution that can be implemented in the next release. So now we're just gonna go over a few of best practices or lesson learned. So when proactive design works well, it's a great tool to take advantage of when you have the resources. So if it's a new product, if it's a new feature of a product and you have a considerable amount of time available to work on the design, when can it go wrong when you don't have very much time to market, right? So there's a couple of examples. One, if you just need to get something out in a release very quickly. Another example where proactive design doesn't work well is in open source when we're using new technologies and we might be designing with an alpha version of something and APIs are gonna change really quickly. Sometimes you just have to, in that case you're gonna have to use reactive because whatever design you produce is probably gonna get changed when the software goes from alpha to beta and the APIs change. So there's definitely situations when proactive does not work well as well when the time to market is limited. Yeah, I think some of the lessons learned. So when one can reactive work well, it's a couple of things we just discussed in the last use case, but really for one in the open source like Serena said, in collaborative environments that definitely helps so you can have that, like that Explorer feature I was talking about, you can have that back and forth conversation. You definitely I think need that in the reactive state and then when teams are agile and ready for features or pages to change quickly. So you're making incremental changes. You can make some iteration, some changes in version one and then iterate on them in the next release or in the next cycle. And as long as everyone's kind of on board, yeah, we're gonna revisit this page maybe again and again, that's okay. That's kind of part of this reactive side when you're making these small improvements to get something out the door that's usable enough at times. So if everyone's kind of on board on the same page, then reactive can work. Also to improve product cohesiveness. So we kind of joked about it just sticking a bandaid on it, but it's actually, it's important. So look and feel does matter and we try to be just looking at some of those screenshots in the beginning of our products. Way back when in 2013, I think they were from the portfolio didn't look cohesive and that's something that at Red Hat we've been trying to focus on to make it look like one cohesive unit. So yeah, some minor tweaks you can make being reactive could be some visual changes, look and feel things. They're important and they do make a difference at the end for the full user experience and user flows. And then similarly the syntax. So keeping it consistent, whether it's conceptual help, contextual help, excuse me, or it's field labels or tool tips, simple things that can be reactive. Like, oh, let's try and make these changes before at least goes out the door. Those are things to look for where reactive can be okay. Do we want to only think about the content strategy from a reactive standpoint? Definitely not, but it's ways to sneak in some of that work as a quote unquote afterthought to sneak some of it in. But yeah, we should do all of this on a proactive base as well. So I guess, yeah, I was gonna say, I think there's one other thing that like, we're coming at it from, because we're working on web applications too, right? So if you want to think about things like if you have a SaaS offering or websites, I think reactive comes more into play as well because you have a shorter development cycle. But we're definitely looking at it from the point of view where we have at least a three or six month cycle. Relief cycle, yeah. Yeah, when you can make more media changes, it's definitely easier, yeah, for sure. So yeah, in summary, we mentioned this a number of times, the collaboration, but the key to success with design is to be collaborative and iterative at every stage. So there's really a place for both proactive and reactive design for, you know, in every case, I think. So you can use both depending on your lead time and what scenario you have. But yeah, in today's landscape, you need both. So curious if anyone, that's all we got. I understand what you're saying about the strength of the proactive approach. And from what I'm seeing here, it looks like it's always attached to a product, or that kicking off the cycle. Is there any room for doing that on its own as kind of like just pushing out the boundaries of UX and then applying those lessons learned when a product comes up, or do you always attach it to a product? That's a much better product. I think I understand. So you're saying is there room to, like before there is a product to do some proactive research to understand, like what even? Yeah, yeah, I think, you know, where I come from, like everything's product driven. We're doing all of our UX work to serve as a product. And it's never really any time to just kind of, do we throw on our own and then apply it to a future product. So I'm wondering if you get a chance to do that. I didn't hear the total end there, but I think, I guess from my perspective, yeah, we are thinking about it in terms of, you know, adding specific features to the product, but I'm trying to think. I can see from a research perspective, I mean, I think there's always room for proactive design. Like if there's researchers in the room, it probably agree that talking to users, you know, anytime you have a large amount of lead time talking to users, you kind of can't go wrong. Like it's hard to argue with data. So whenever we're struggling with some of our design decisions, we often turn to the research team and ask to run usability tests. Even if it's, you know, we've gotten anecdotal feedback here and there on random features. Like we often turn to the research team and ask to take a step back and just ask them to just go talk to users, whether it's they give a certain direction or in some cases they don't. Like they'll run a really open ended research activity to try to get feedback from users that like those users are actually thinking about rather than us dictating, like tell me about this specific product or feature or page. Kind of like what do you do today to use, you know, what do you use today? How do you go about your everyday? What can we learn from them to bring that data back? But I don't know if that like answers your question. I think the other thing too is like at Red Hat, we have product managers that set the direction of the product, right?  So they kind of have like that future vision of where we want to go. So oftentimes by the time we start working on something, like there's already an epic that says, okay, this is what we want to do in the next set of, in the next release, here's what we want to focus on because they've already done their research based on competitive analysis as well as talking to customers and how they're using the products today. So our level of research and interaction with customers is different. It's like, it's more usability than it is understanding the products at a higher level. So that helps. Thank you. So user experience is far more than user interface. And I know Red Hat as a, you know, old school geek company, health and suspenders, Linux world, a lot of old deckies came from a very command line, even pre-web focus. And you see that in a lot of the products. I think that's what you were dealing with with a lot of those early interfaces. But the risk on going the whole UI ways end up with where Microsoft was in, which is that you can only do certain use cases through the UI. And I was wondering if in your team, you're getting an emphasis on being able to span the whole realm of user experience, not just web UI, but from new user being exposed to a system at both the, ideally web UI is a wonderful way to bring them in there. But to be able to think in the terms of bringing them from new user through to power user, or to be able to say, okay, eventually they need to be able to take the workflows that they're doing here as a one-off on the web into our automation tool chain and getting it into Ansible or something like that. And so there is a whole workflow there. Is that part of the language that we use when we talk about the round trip of user experience design? I think we're getting there. I can give the example. So for OpenShift in 4.2, we're gonna have a developer perspective or developer console, right? And they have an associated CLI called ODEO. And so what we're talking about is making sure any improvements that we're doing in the user experience. We also kind of match in the CLI to provide consistency between the two. Is the developer gonna be able to do that? Like, I just did this in the UI. I wanna see the ODL command to do the same thing from the command line. Is the developer, I'm sorry, are they gonna be able to? So not just us be able to, us as Red Hat and the wisdom of the world, to be able to put that power in the hands of the developer to say, okay, I just clicked through. How would I do that from the command line? To be able to teach them that? So oddly enough, there has been some discussion about that in the last couple of weeks, whether or not it will happen in the next six months. I don't know. But that is how you talk about it. But there has been some increased discussion around that. Yeah, I mean, I'll give you the examples with K-Native and Serverless and how that's gonna, how those all come together in the developer console and there was a face-to-face a couple of weeks ago and some of that stuff started. We started talking about those, but in my experience, that's brand new, hearing those conversations. I have not heard them very frequently before. So hopefully that's where we're going. And I don't know. Like, I don't know if you guys on the OpenShift side with OC, do you have any interaction with? No, we don't. But we've started to hear a lot more from, like when we've talked to users, we're hearing a lot that they're using the UI or coming to the UI to learn, new users often are trying to learn, what's, how do I kind of get started? What are these different resources? What are these different workloads? And they're kind of there to learn. And once, like you said, they're progressing into maybe a more power user. Maybe they're only using the command line at some point. But we ended up talking to a lot of users that because they're using it to learn, a lot of these features are coming up where we want to help teach them through the UI, whether it's contextual help or kind of pointing to different sections. One of the things we've talked about is adding some hints of, okay, you can only take this flow so far in the UI.  So providing some hints or tips of either how you do the equivalent task through the command line or how you can expand on a flow to do more complex or more advanced tasks through the command line, like providing that in the UI in context so that people can learn and eventually get to a place where they are doing those advanced things, maybe without the UI. We've started to talk about that for sure. This is a lag. So the other question is, I know how the Red Hat product cycle works and it's built on the idea of taking a successful open source product and locking it at a certain compatibility level and back porting fixes and changes to that. So REL7, there's a certain expectation if something works on REL7, it will work through the entire REL7 life cycle. And then when we go from REL7 to REL8, we can make big changes and break things. And we have the same thing with OpenShift going from three to four. And I think we've seen that OpenShift four is gonna break a few workflows because there's some really, really different assumptions in there. And so when a customer, and my customers are banks, so they're fairly risk adverse, when they're going to make a change like that, it's a huge impact and they'll probably put that off for a long time. Putting on your Red Hats, what requirements are put on you for user experience and user ID, UI changes within a single product line versus some kind of reactive versus proactive? Like what can you do between OpenShift 4.2 and 4.3? And what would you have to wait for OpenShift 5 to be able to do for changes? What are the guidelines that you're given that way? I don't know. I don't think, I mean, that's a good question. Yeah. So we started work calling and I started working on OpenShift at the same time and that was on 3.7, right? Yeah. So I'm trying to think of what was the big change between 3.7 and 4.0. Really is the UI is that 4.0 is tectonic. It's based off of the tectonic CoreOS acquisition, right? That's the only major release we've been brought to. So I don't really know the difference between a major release. The difference between minor dot releases is more time-based as far as I've seen. So it's not like you can only do a certain thing. It's really just how much can you get in in a three month or six month cycle? I'll give you an example that might frame what I'm trying to ask. So in IPA, in IDM, we have a tab on the top and I know this intimately because I worked on and this was a sticking point where it's called network services and underneath there's DNS and there's auto mount. And if you take it from a UX perspective, DNS is a dominant use case. I might deploy IPA solely to get DNS there. The number of people who know how to do auto mount that would do it through the UI is probably zero. So we've taken a really important UI element and hid it behind this idea of network services. And this is something that should be, and I filed the bug and the bug was overturned because the UI developer didn't talk to customers and didn't see it the same way. It was like functional fitness and this. But I could see his point, which is changing something like this breaks things because there's an expectation that it's gonna be there. And so he actually had a really good point, which is you shouldn't break that expectation except, and I'm trying to figure out where is there, are there guidelines like that? So it's like a regression then. Essentially, if you did that, you would no longer be able to satisfy that use case in the UI if you removed it. It might be tagged as a regression. I mean, the UI's not automated, so it's gonna be a human looking at that so they could still do it, right? If there was a DNS tab now at the top, they wouldn't break them that perspective. And this is a human judgment, obviously. Whereas if you thought, oh, you're DNS, I need to go into network services and then see DNS there and it's not there, then that would break them. And thinking, okay, we have to do something with auto mount. If we buried auto mount, that would break it. But to just change this here would not be a, from a automation perspective, it wouldn't be a non-backwards compatible change. So do we think in these terms, do we have restrictions or requirements along these terms? We talk about dealing with UI changes from minor version or major version? I know it's a hard question. I don't know that I'm framing it that well. I'm not sure. I think it's more because we just don't have as much experience going through the major versions. I don't, within the same product. So for example, going from three X to four, right? So not only did we do the, we went to Tectonic, but in addition to that, a lot of the developer workflows are no longer available in 4.0 or 4.1. So perfect reason to have it a major bump. And then in 4.2, that's why we're starting to introduce the developer console. I don't particularly know if there's anything written about that though. Interesting question. Thanks. Thank you. Thanks everybody.


He will be feeling a touch of nervous. I'm sure he will be. He's got the backing of this stadium. He's off the inside, Maxine Drabbing, lots of support for him as well. The football world under-21 champion, Wildcard tonight. Sanrio, live back from Sweden, is off gate 3 in the White Helmet. Niels Christian Eversen of Denmark, going off gate 4 in yellow. All eyes on Woffenden, raiding champion, three times world champion. He's come back earlier than many expected. Here he goes, in heat number 2. Woffenden wants a top 8 finish this year now. That's his target, doesn't want to rely on a thing. The way they go from the start start, he's going to make it. Woffenden now allows the drop of the inside for Drabbing to challenge him. And Eversen around the outside, it's very tight down that back straight. And Eversen, lovely run from Niels Christian Eversen. Drabbing is in second place right now. Woffenden is trying the outside run of his home side. Drabbing up the inside, low from the youngster, charging hard. But Eversen made their Drabbing a superb move up the inside early doors to get the better of Eversen. Now Woffenden's running on. Just running out of a little bit of attraction. Drabbing, who was so quick and free-practice yesterday, leaves the door open for the inside move. Eversen coming back to the world champion, Fabrines Schreis in heat number 2. The Wildcard, the former under-21 world champion, leaves the world champion. Yeah, Drabbing's on his way to victory. A dream star for him. Woffenden is going to hold the inside line for second spot here. To Brotswijk 1-2 and Eversen third after leading the race there. This stadium is erupted, erupted into a sea of noise. That was great speedway to tell the heat number 2. Proper speedway in heat number 2. Action burst into life for two home riders. Drabbing has been in terrific form of late with superb yesterday. Certainly looked so very comfortable in practice the Wildcard. We'll see it again. He makes a good fist of it initially, but elects to run wide in the first corner. Not quite sure, finds himself in a little bit of no man's land. Drabbing then decides that he just wants to hut that inside line. Eversen there initially has hit the front. But this inside line works well for Drabbing. And that quite clearly was some local knowledge. There's no doubt about that. Talking to Max Frick's crew, they did say. First four races quite possibly they will hug the inside. Woffendon then electing to do something very similar and comes through into second place. Actually has to get off the gas at one point because nearly ran in the back of his team mate. But this is one hell of a speedway race and I've got to say that the action is burst. Burst into full view at this very early stage of the Grand Prix. Super stuff.


Mwanshwa kipingi ituwae in the morning, you just in time for the next conversation of the day. My name is Ram Magukko, this is all about health today. We are talking about drug and substance abuse. Have you ever interacted with someone who does that, drug abuse? What are the reasons as to why they indulge into it? Do you know some of the preventive measures? What do we need to do as youths to cover ourselves to jilinde? For us to be able to protect each other and take care of one another. This is all about creating awareness on drug abuse, especially among the youth. And even as a parent, how can you tell?  Because some parents end up knowing way later when it has escalated to the point of addiction. This morning I'm joined by Anthony Njaga, he is a counselling psychologist, he is a mentor, he is a public speaker. He is a killer kid. Karebusana Baba. Santi Sana Bro. Na Shkoro. Mwana api mwa kikimendikuwa? Encouraged to inspire. Encouraged to inspire. It's an initiative whereby I go to schools, sanasana universities, colleges, high school. Kungalese issues, like this month nafanya, drug abuse, alcohol and masturbation, which we challenge kubu sanasana, sanasana for the young people. Miki na waju ikusu zivi tu. Tunainda tu wuko tunawangelesha because now when you wait for counsellors, na umtu aku jesession kuako aku kungeleshe, ita utangoja sana. Ita utangoja sana. But now that's what we are doing this now today. We have brought the counsellor Mwanawe to your living room. Tunainda kungeleshe, aku pashe kama di pukupu. Atu apashe. Tunainda tu faktu bilezi. Tunainda tu na accept this things as a human. Tunainda tu faktu bilezi. Tunainda tu faktu bilezi. Tunainda tu faktu bilezi. Engage with us. The hashtag is one in the morning at Ram Maguko. Tag him also. You're on Instagram and Facebook. Yes, official Antonin Jenga on Instagram. Facebook Antonin Jenga. Yes. Official Antonin Jenga. Yes. Umpatia api vi IG, Facebook. Tag him, comment. At Y2Five channel. Remember we are also live on our website. www.kbc.co.ke 4 slash Y254. Participate with us and we shall sample your feedback as we continue with this one conversation. So, Bon Antonin. Yes. You have an initiative. First of all, let's start based. What is this initiative all about? Ulianza Lini and what is it that pushed you towards going for this? And why? Why? Why this? Nikianza encourage to inspire. Actually, it's a long process but let me try and bring it to you guys. Encourage to inspire Ulianza way back. The idea came to me way back in 2020 around, let's say, August. Uko June. Agatikovidili kwe mi shikavizuru lastia. So, the idea came to me and I thought issues ni mingi, young people are going through a lot. Nakumboka lastia, a lot of issues are going on. Mingi sana, psychological, wato li kwa na face a lot. With the pandemic. Yes, with the pandemic. And with the increase of violence now that people are at home, isolation. Exactly. So, like I kujia that now, that now, if you kachinu nga jemtro, kachinu nga jemtro kujia kungaleshe amakua kwambishi dazaki, it will take time. So, why don't I now go to these people now, the young people mo sokozi, generation yasemi wambi ama young people. If you watch me right now in your young person, and your young person is between the age of 15 years to 35 years. And if you in that age bracket and you watch me right now. Encourage to inspire is here to tell you things that you didn't know. Kubitu huku na jua about nendele. As we go by life in nendele and time in nendele, generation nga change things and new people nakuja new things. So, I am here now to tell you as a young counselor because I am only 23 years as a young counselor. 23? Yes. Oh my God. Imagine. I am so young son raga kukurilit na mayut. Yes. So, feel free. And you see, this is so rare. This is so rare. And I was, you know, watching what you do because I've seen some of the things you do on YouTube. Yes. You have clips that are there. Yes. And you're doing a very fantastic job. Thank you so much. I don't know how is the reception on the ground so far? The reception is good. One thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing, one thing one thing, you see these ще many kids. And the reality in life nyesiko, so many are here, drugs, how attacking. So certainly. Yes like it in dbd too because now only $pohambi wants them. So I wanna encourage inst Picka Kujo tPart, and I came last year and until now I've got it but to school, a launch sheet last year KMTC check 38 in the, Mastabation to alcohol. Mastabation kunza ui story ni. Na fakhutafutahukuu ngele na mba'ya. Mastabation. Yes. Iba nitaa kwa Drugs. And drug abuse. It can start from any age. Yes. One thing that many people don't know is it can start from any age. From your dealings with people on the ground. Umuwa na waliwa dogo sana, wana zfika enjigani apivi, kwa miki dogo, enyo naza kutimiya drugs? Onajiwa skwezi funny thing, unaza pata mtoto, actually that's it. Ui ni mtoto na jafkisha 18. A 14-year old, 13-year old ana tumiya drugs. Mtoto na chanamu woka, ui mtoto na wutabangi, ui mtoto na jinvovna heroin, kokei, nani mtogo. Na waza zia wajuizu vitu? Waza zia wajuizu, wana fiki rei umtutuango ni very innocent. Kumbi mtoto na mkukitumiya bangia, mkukitumiya heroin, nani kokei, nani jini amaji. You know drugs, drug abuse, drugs in substance abuse, nili you overusing something. Na jo kama ni down, na jo izin medications na piyango ahosi. Izo ni drugs, right? Lakin if you overuse it, kukitumiya excess, now you're abusing the drugs. Pia iyo nid, one of drug abuse na pia izima drug abuse, kama bangi, kokei, heroin, mirai and stuff like that. Okitumiya excessively you are abusing the drugs. And you know one thing that we need to highlight also is, sometimes a parent doesn't know. And I don't know if there is a parent that is watching us today. You have a child, that child is 12, 13. Then maybe abusing drugs and you have no clue.   So one thing I'd like to tell the parents, if you're watching me right now, one thing I'd like to, kwa ambia, ibit a young parent, bit an elder parent. Okiyona, let's say for example, definitely hata kwa ambia na tumizi drugs, na kufichi amibi na kwa gupa yo so strict on the kid and everything. Na kini? Na kwa uliza taka taha. Taka taha. Asa, unadjo amtu toa kwa definitely ataka mani na 13, 14, anana zangana tuvi tufishi-fishi kama manbi esti ako nao. Okiyona zaka kwa amtu toa kwa nafika, umu mambia time ya kufika kwa kunyumba ni 6, umu tu na na fika 7. Ataka mani 1 hour late, juliza na fika. Anani, alafu akifika kwenyumba, haende sitin room, anana direct to the bedroom. Bedroom direct? Bedroom direct. You should be careful with people who go direct to the bedroom. Kuna kituana ficha. Lazi na kuna kituana ficha. Anana kujana na bedroom na kuna chwinga ma metyu. Umu muliza muna utemi. Hata kia kwa table room na kula apo, ako tuna chwinga muna wu situa ma betwinga ma amini kutusawa. Alafu anana cheka cheka. Kuna zeli tu ma sense na nana wu mitu wa yuko sawa. Anana zaka kuka ni kama kudizi-dizi, afil-fiti. Those are some of the signs. Someone who's chewing. Chwinga ma. Usidani tu ni bolgamia. Ni bolgamia kawida. Inaza kwa na ondoa harufia bangi. Chwinga ma skweziwa na tumi anana kwa na ondoa harufia bangi. Kufita white. Anana chitu.  Ngayi wo muna wu na fukiria kwa sawa. Kumbe ni anana traiki fitu ya yu smell between Asi usidibdi Udrive L. Asa muna pata yu chewinga matahitaw. Anana dananda wu huli, muna umalizi chewinga, asubu ya mi yamki, muna umalizi chewinga, mibiata asubu ya lukua mebeba pafikido, waka na loo, kasmoga kachuko air freshena, kachuko spray, mibiata unai fenya kwanyumba na weini na wajuwi, wa zazi yawajuwi. So wana fukiria... jola yag kiza na kwa zini ya, aamiye ajam tu toa ke ensef hands Kuma tu toa ke na tumiya this drugs to this thing is so sad, ni maia sana biki mafia people are learning nowadays Nowadays, V2, genera neneh change wana to one we have any other things that we want to talk about china maji that youths are doing that are actually associated with drug abuse una pata wana jua as i was telling you before the show ndi ka wana me cheka wana juqasu drugs kwa na una yekanga kwa different things. Una jwa ni meski hauji kuna kwa naka naka kitu ni to weed kuki. If you're a parent, watch me. Watch it me right now. Mtu tuwa kiki kujaka nyumba mbe ba cookies. Don't take that ni kama cookies a kawa ida. Naka kwa naka weed content. Kuna weed naza kwa kukis, naza kwa ugali. Una naka bati de party. Mtu tuwa kuna bati de party na bestia. Yaki mbe bia family friend. Kuma family friend na shikanishana yo drugs. Ame na kapika ugali. Kafiki re ugali tu ni ni. Just for... Ugarli piya unna. Mtu tuwa mbe kula ugali a mbe shiba na jeveli ugali na shibishanga. Mtu tuwa mbe naza kucheka. Iza ma effects bangi kucheka. Too much laughter. Una kula excess. Pia mtu tuwa bidewek yo naka nyumba na kula ugali. Ame kwa kikula ugali portion kido kwa ma cha patin bili ya ma moja. Ya maza kula ja patitana. Bangi. Bangi na lita. Ina ampati ya so many other types. To something that... So bangi na zaba ya mda kule kama kitu gini. Bangi ni mba. Mi nambiyangawa sayi. I remember nili ya chaku wuta bangi like four years ago. You used to do drugs? Yes, I used to do drugs four or five years ago. Dika wacha I used to do bang. This one I'm doing it. I know maybe my parent hajuwi, but I used to do. Mam, kama nani watch. Polisana I didn't tell you this, but now we are on air. We had to do this. Mi metoma kama mba yamba. You're not confessions. Confessions, but anyway it's true. How come you were able to hide it paroko a na Jo yu mam na when you... we werebery doing it in a camp motoruming place. I was on an issue in Nairobi. We were doing boardings. As forئa chaku 2 weushi umi nani na gindaal, na widuz, agini ya ja at this time onwards. I remember activ Particularly moko Mkeli kili ya kumisa took a look on years ahead. nm'ilu u kumesa, granmous there, hungos there canvas may be family meetings sasawa oku za nga kusia mandi wa iiu iiu yu anakula mira anakula vidu zambuzi weu iu did was so embarrassing wa inilio feel too vibhaya ii remember, aki ni mi... iious to really use bank for some time nili kwenakunya di pomba vibhaya sana nili kwenakuu ya di home late and people used to think, some of my hongos used to notice mazei since then mazei mi na shkuru iiit's not anizu, nikiwa jisha mtu Anatumiya drugs and everything, not only bang, maybe anatumiya cocaine, heroine, maybe ochi mi right now you're young person, wukuna challenger kunduka from, amaku jitoa from, heroine usage, cocaine usage, bang piya, other type of drugs, it is not an easy journey, but trust you me, what I can tell you is this, take time, usi, usi, usi, usi, appreciate your small winnings, asin wukuna leo, wukuna kunditu miya heroine, cocaine, bang for, kilasiko, kilasiko, wume on at least for today, nkesho, wume tu miya for a period, kido agot warakama wume, wume tu miya rogama. You just mean the mice, if it was number 20, 10, 5. Trust you me bro, kwa chaisi bitu si rahisi, see once, if it is addiction, inakwa wanga very challenge kutakum se kwa yo stuff, addiction is very very bad, okwa addicted into something. What made you stop? What made you change? I used to, ok piya wana jwa, I'm a first born, wana jwa piya kuhu let kuhu, illa first born mentality and now I have siblings waka nyumayangu wana ni watch. Being a mentor, wana bongaza. Another thing I did change in myself, principle yango, I decided now this thing hita nipelakama, it will just drown me. Imagine I'm 23 years and I don't do that, I stopped doing it, niki, nikiwa nikiwa high school, sana. And when did you start? At around what age then? Nili kwa 14, 14, 14, 15, 16, between 14, 15, 16 hapwa. Wow, and you can imagine those who are watching from home, if it can happen to someone like Jega, it can happen to you and even at a tender age you are even younger than 14. So myself, I was in ajam, I was in ajuchu, Ugali, Japati, Japati wana kulekses everything. You checked excessively for yourself? I checked it. You checked? You only aimlessly for yourself? That's why sometimes I don't like people who just love you. When I came in, they said it was a joke. I checked you, I checked it. Maybe you checked that you are mudabang. Hahaha, something we can say. We just finished in... I would look at some reasons to make people want... do drugs because apparently outside they realize that they are doing drugs That is so涼iv, and in this context the reason is as well that leads or push towards drug and substance abuse One thing I will say is peer pressure Peer pressure is the main thing The company, the group of people, miwa maybe I'll say Show me your friends and I'll tell you who you are If you choose the brand and buy it So if one of the friends in your company in your group uses these drugs Trust them They will influence you Definitely So peer pressure is one of the major reasons kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa kwa k Ntia mnye sk tieson na skey mbika na sifa, yile sifa yi konayo So, yami enda mnske ni kisha dya, ame wuta Pusa ame kisha, dya nazafany na msiyafil fiti Aki hainda policingine Piya kustiza, what you hear from people Yole yole, yole yod story a drugs ime kwa ni kama ikona film fullanim People are talking about it even yana yana makehai and everything And then people, you end up thinking that it's actually a good thing because you can talk about it a lot which is not You feel like, hey I'd like to try it Yes, yi kona say defects nbain I think that is social pressure. Yes, social pressure. What to? I want us to look at it in terms of, also in terms of the self-esteem of an individual. Does it have an effect on someone's self-esteem? The drugs? Yeah, the drugs. Can having low self-esteem also push someone towards that? Yes. Kama ni mutumunye a kuwangi interactive na wa say hawezi stepa, pa ezi kuwana that confidence, an a kuwanga tokiwi ake na ogopa. Actually, that can make that person because one thing, being idle in a causing drugs a lot, drug and substance abuse. When you idle most of the time, auna company, auna ma besti wu konawa nye munaiz at least, mwende mw semi munainda kufanya sport fulani. You're always idle, you're always free. You know there are these people we call, is it melancholic or introverts? Hawe ni watu biniwa na. You know introverts, ya watu apendi ku interact, they're not extroverts, they're not outgoing. Ya, you know they're just people who just love themselves, company ake kevi ake. So hapun eza pia, hana self-esteem ya ake, ata awezi approach mwama bie, e mi na feel ni kama ni kuna pressure kutumi ezi staff. Is it right or wrong auliza? Ata auliza kwa zana shindwa ni tanzaanza haji. So self-esteem ya ake na kwa demoralize aku ineyo self-confidence and end up kutumi ezi drugs. Na salsa wewe, there's one thing that pushed you toward starting it. Yes. From that time, must have been in high school. Yes, in high school. Biniwa ni ilu kusku masasa wewe maniawe, because at the end of the day, bia mtu anashanga, mtu mani ako shule, Anomal afrikana parent will say nili kupela kashule wusome. Wusome. Unafanya ni ni. Unafanya ni ni. Kazi ni kwenakutumi e ma dawa. Bale mi teli, I'd like to tell parents pia, awa ni wa toto. Definitely. Laki ni, they're human like just you. Naki lam tu wana kwa nga na pressure kivi ake. But don't usi tangi usi isolate usi neglect mtu towa ake. Ako atika sababa wana tumia these things. Najiwa, inaza kwa ni hakwa na jwa. Najiwa hakwa na ila, hakwa na idea what these things are. Naka kwa introduced na friends ukushu. Laka ma mimi nili kwa introduced tuma base. Wabu base tuli kwa ni introduced nwenda. Outa na sama. Sushika hi nifegi. Shika hi nifegi. Najiwa fei gina effect. Mi na cha pangwa. Ina cha pavibasa ana. I remember, by the way, I sita sama sana. One shout, I used to use seven in a day. What? Rolls saba. Ina day? Ina day. Please mama. Ina choma hape playo yo take. Najiwa mula siku. I think I also, I almost got into that. One day ata wima mangwa jwi. We were in school primary. Primary. And then there is a particular toilet. I think they like going to the washroom. Washroom, exactly. Ina kwa nga place fula ni wanaeza medited. Siji wana. Siji wana washrooms harufuna. Washrooms wana wedi na nga nga adi. Di wana. Di wana. These people who use a lot of bangi wana kwa nga. They are not clean. They are not clean people. They are not clean. Because they are in a way. It's a drug and substance abuse. It's a mental health illness. I kwa nge tukitu akawida. Someone will just wake up in the morning. Amu ata anza. Ina kwa nga ina anza nga from Samuia. Young people, let's say for example, university and campus. Ina colleges e. Una patamtua me toka shule ana expectata pata job. Wana sayi kuna COVID-19 jobs ni nga muku pata sayi. Honestly speaking, sayi things are, life is so hard, so difficult. So your pressure na fanyam pra? Pressure. Ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, Anu feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel, ana feel po kwa kn Cabinet inankata souhi, anda feel Benin La Pe dialoga near thik majedegi stocksa kio k động pidaw inakati kf too 60, We are in tough times I felt that people go through issues when they are at school Yes I was afraid of Let me speak to the young people If you are young person watching你 na shindwa bangi, what is this you are talking about? Bangi bangi bangi zmarujuana wana itanganguwai, kivela, marijuana, kishada. So kiskezi majina, iyo tini bank. Na iyo kitu inakwangana effects, not when you're well-typassive, muntua kivuta for the first time, sivilem tu miniyata ipassive, kuna mba kivuta for the first time atachizi. Na kuna mba kivuta for the first time ata enjoy na ikwe. So you might think it's a sweet thing to have, you might think it's a sweet thing to enjoy doing, lakini trust tu mi, ii kitu ina zakwana effect, baya sana. Antoni? Yes. Time is not on our side. Takan, we say, story, inena biosana. Inena biosana. I want to give you just 30 seconds. Yes. Wrap it all up, have a final word about drug and substance abuse to be used there. And also you can just mention just one or two things that we should do to prevent such things. Okay, 30 seconds, right? Yes. Hama, one minute. Anyway, what I'd like to say is this, if you're watching me right now and you're a young person and you use these things, You don't blam or asemeti. You are not a human.  These things have effects. N Bandha, ita kwa effect of the bias. I tell the young people if you don't usi pojenga se, you know we are the future generations. So if you spoil your time right now, oki jia ribusahi, trust me, in fichita kwa very difficult. Now you can prevent. Take your time, Poli poli poli poli. Kamu me tu onoka kitu mia heroin 4 times in a day. At least 2 times in a day. Poli poli poli poli. Kamu me kwa kiki fanyanga. The drugs, every weekend, every weekend, every weekend. Try to say me he weekend sita tumia. Yes. And my social media accounts on Instagram is at official Antonin Jenga. On Facebook Antonin Jenga. And you guys go support and encourage to inspire initiative.  Nkwa na shule. You want us to come. Halami on my Instagram DM. Nambangu kwa po. Now we will be interacting. Zanda Zanda. At Y254 channel. The hashtag is one in the morning at Ram Agukko. Engage with us. That business to the end of this conversation. Antonin. Yes. We cannot touch on everything. Like kini, it has been a pleasure. Thank you so much. Zanda Zanda. Uda apakonza kongelereyo story amastabesion. Plana de unite. Wait wait. Thank you so much. Thank you my brother. Okay. That business to the end of this conversation. We are taking a short play. Could be back in a bit. This is why in the morning.