Improving cognitive performance with aromatherapy in young healthy volunteers is one thing. But how about where it really matters? This group of Japanese researchers had this pie-in-the-sky notion that maybe certain smells could lead to nerve rebirth in Alzheimer's patients. 20 years ago, to even raise such a possibility as a hypothetical was heretical. Everybody knew that the loss of neurons is irreversible. In other words, dead nerve cells are not replaced. An important factor in neurodegenerative diseases. That's what I was taught, that's what everyone was taught, until 1998. Nerve cells with advanced cancer volunteered to be injected with a special dye that's incorporated into the DNA of new cells.  And there they were, new nerve cells in the brain that didn't exist just days or months before, demonstrating that cell genesis occurs in human brains and the human brain retains the potential for self-renewal throughout life, something we can take comfort in. Still doesn't mean smells can help, but an aromatherapy regimen of rosemary, lemon, lavender, and orange was attempted for a month. Here's the trajectory of their ability to form abstract ideas. And their cognitive function, starting six weeks before the treatment, showing a rather steady decline until they reversed after the aromatherapy. The researchers conclude aromatherapy may be efficacious and have some potential for improving cognitive function, all of course without any apparent side effects. What about severe dementia? We always hear about the cognitive deficits, but more than half of patients with dementia experience behavioral or psychiatric symptoms. Thorazine-type anti-psychotic drugs are often prescribed, even though they appear to be particularly dangerous in the elderly, but hey, it's easier to just prescribe a drug than offer non-pharmacological alternatives, such as aromatherapy, rubbing a lemon balm-infused lotion on their arms and face twice daily compared to a lotion without the scent. Everybody got rubbed, but in the lemon balm group, significant improvements in agitation, shouting, screaming, and physical aggression, and improved quality of life indicators, less socially withdrawn, more engagement in constructive activities. That's important, because when you give the anti-psychotics, patients become more withdrawn, less engaged. It's like a chemical restraint. Yeah, the drugs can reduce agitation too, but that may just be because you're effectively knocking the person out. So, aromatherapy with lemon balm is safe, well tolerated, highly efficacious, with additional benefits on key quality of life parameters. These findings clearly indicate the need for longer-term, multi-center trials, but we never had any, until never. We still don't have any. The study was back in 2002 and still nothing, but is that a surprise? Who's gonna fund such a study? Big Balm?


While you're asleep and dreaming Your brother and your sister will always be a reflection of what's in your mind your brother Your sister Shows you the contents of your consciousness and that's important Because if you don't want to be a victim you have to start to see The judgment or attack thought in your own mind If you don't want to feel at the mercy of a world that's external You have to start to realize that Everyone that you meet or even think of is simply a pictorial representation of what You believe you are so We need Reflections to help us Be aware of what it is that we're holding on to in consciousness


What injuries did, oh my god, one suffered? Well, during my career, a few things. I broke my collarbone in go-karts and I broke my little finger. The pinky finger is here and then obviously the big crash in Bahrain in 2020. I got burn on both hands. Second degree, second degree superficial on the right hand. So nothing apart from a little bit of discoloration here. My left hand is the one that obviously got hurt more. I've had surgery, I've had skin graft. It's working well. It's a question that I have all the time. Actually today is a bit painful. Today the skin is a bit dry so it doesn't work as properly as it should. It is painful all the day, all days. It is painful all the time. It's more discomfort than a pain. You get used to live with it. There's no special treatment that I need to do anymore. I can be out there at the beach on the sun. I do cycle with gloves on just to avoid too much contact with the sun but the humidity and the heat of the Florida weather actually makes my hand feel pretty good. I guess it was a good thing that we moved in.


One of the challenges which customers are facing right now is that data is everywhere. In the organization, they have multiple islands of data and customers are trying to solve this problem. What we're doing is we are actually leveraging the operator framework, which is from my opinion because I'm an engineer, it is the go-to tool for scale, for seamless management. An operator will help you to deploy an application from scratch. It will provide you a life-cycle management. It doesn't matter which application you're talking about. It could be a normal, you know, a WordPress application. It could be MySQL. It could be databases. And even it could be analytics applications. So the operator framework which Radhat is a very book contributor to, they are trying to automate this entire tool chaining into OpenShift and Kubernetes. And the other thing is data because AI needs data and data needs storage. So RookSef is basically an operator framework component which will deploy Sef on top of Kubernetes and OpenShift and then it will be tightly coupled with the application and it will help customers to think about hybrid cloud and multi-TN workloads isolation things. So customer will end up having a common layer backed by Kubernetes, control plane, Kubernetes infrastructure that they could, you know, have best of woodwalls, hybrid cloud and their on-premise cloud.


Okay, so it was quick introductions to position the QBAI and now I will let Guillaume to go a little more in depth in terms of technical. So, today we're going to talk about a function pack for AI called FPAI Sensing 1. So there are several function packs available here at ST to get you started building application. It could be like an IoT cloud function pack, one for predictive maintenance or for allura. But we'll be focusing on today's function pack called FPAI Sensing 1. This function pack has two example neural network implementation in it. The first one will be the acoustic scene classification where it will listen to ambient noise and tell you if that noise is an indoor noise, outdoor noise, or in vehicle noise. The second one is the human activity recognition. So it will look at accelerometer data and tell you which type of activity you're doing, whether you're running, walking, or jogging, and so on. So it's supported on several of our boards. So you can use the Nucleo platform with the shields for the sensors. You can use the sensor tile or the newly announced sensor tile.box or the IoT board that we'll be using today. So the sensor tile is good for form factor implementation with battery powered devices. And the IoT board is great for a single board development with the embedded ST-link programmer and the UART connection. The sensors, they're all tied, the ST sensor are all tied to the hardware using ST libraries and third party libraries. We have a dedicated ST AI library for neural networks, audio pre-processing, and then on top of that sits the user application to tie everything together. Other features implemented in this function pack are the BLE connectivity. This is just to configure your hardware to send the output communication to the screen and view the results of the neural network. We have a low power implementation using free RTOS and the STM32 advanced stop modes. We have a photo feature for firmware updates and neural network updates. And then the form factor implementation shown here. So we have the neural network will be running on the STM32-04 microcontroller connected either to the microphone for the audio input or the accelerometer for the human activity recognition. For the human activity recognition, so this was done using an internally collected dataset that we collected using a sensor tile stored on the SD card. We then use that data and train a neural network model on a powerful computer and then use the tools like QBAI to map it to an STM32 microcontroller. There's also some embedded pre-processing running to remove, for example, the gravity of the sensors. Then the other demo is the audio scene classification. So we also recorded some data internally and then it can listen to the audio and tell you whether you're indoor, outdoor, or in the equal. The pre-processing that we'll be using for this is the log mail spectrogram. So this is just an FFT followed by the mail filter bank application so that the signal looks more similar to what your ear can hear. If you were doing keyword spotting or trigger word detection, you would be using something like MFCC. Other demos we have is the handwriting character recognition. So this one is shown outside where you can just write with your finger on this LCD touchscreen letters or uppercase letters or digits from 0 to 9. And this one has a very small footprint of only 26 kilobyte of RAM, for example. But then we can see a more resource-hungry application such as the food recognition. So this is a computer vision AI application. There's a camera that's able to look at a dish and recognize up to 18 different classes of food. The difference with this one is that it has been implemented in fixed point numbers. So instead of using 32-bit float numbers like we were using before, it will be using 8-bit integer numbers for the calculation. So this will reduce your memory footprint by 4. And it's also faster for your inference time.


I am Dr. Olyth Selvan, Consentant Hepatologist and Chairman Division of Liver Transplantation in Manipal Hospital. Liver cancer is diagnosed based on a blood test called alpha-fetaprotein and radiological imaging of the abdomen either by ultrasound or CT scan. Symptoms of liver cancer which occurs are pretty late in the disease process. So if someone presents with symptoms related to liver cancer, it is usually an advanced disease. So if you talk about the early symptoms of liver cancer, they're either not there or pretty non-specific. So unless you look out for liver cancer, it is very difficult to diagnose liver cancer early.


wealth is created by combination of many things, but one of them is catching new trends early. And you were talking about how humans aren't free thinkers. So and what happens is what it really comes down to. It wasn't till recently that a scientist actually came up with this term of risk averse humans are risk averse. That's in our DNA. It's like humans 1000 years ago, if they took too much risk, they fell off a cliff or they didn't have glasses, they didn't have antibiotics, you didn't have all the things we have now. So taking risk was very dangerous. So new trends like Elon Musk caught EV cars when they were kind of doubted that they'd be a real thing or Jeff Bezos build a website in 1994. So all these wealthy people for the most part are catching trends early. And I'm not on the level of a Elon Musk or whatever, but just catching that little YouTube ad. There was no competition.


Our next speaker is the art director of information graphics at Scientific American where she started as an assistant director back in 1996. And then she joined the staff at National Geographic Magazine before coming back to Scientific American. She studied geology and studio art at Smith College and received a graduate degree in natural science illustration from the University of California. Please welcome Jen Christensen. So as the program promises, I'm about to walk you through the process of developing data visualizations for Scientific American. But rather than focus on the tools used to create them, I'll be addressing things from the art director's point of view. I have the distinct pleasure of hiring designers on a project by project basis. So I can rely on the talent and the constantly evolving skills of freelance visualizers. So my job lies in helping to match the right artist with the right data set and then nudging things along, always with an eye to the ultimate audience. In our case, it's a science savvy but non-specialist reader. Before I talk about specific projects like this, I'd like to step back a little and provide some context. The collaborations that I'll be speaking about are entirely driven by the ultimate context. And by that, I don't just mean final medium such as ink on paper or pixels on screens, but also the meta context, including Scientific American's international editions, our legacy and the realities of our workflow. Scientific American is the oldest continuously published magazine in the United States. It was founded in 1845 as a four-page weekly devoted primarily to inventions. In 1921, the scope officially broadened. It shifted from a weekly inventor's paper to a monthly periodical of popular science. Several redesigns occurred during the decades that followed, but the next watershed moment occurred in 1948. When the magazine expanded coverage beyond advances in industry and embraced the broader world of applied and theoretical science, the magazine would communicate science in a clear language to the interested layperson. The English language website was launched in 1996. This is how it appears now. It's followed by the next major magazine redesign in 2001. And our most recent redesign of both the magazine and the website occurred in 2010. Our tablet edition for the iPad was launched in 2012. And we have 14 international partners who have access to our original content, but also develop articles specifically for their own audiences. So it's not a page-for-page direct translation. We're also now working on a multilingual web content, which should be challenging for interactives. We'll get there when we get there. Meticulous illustrations of inventions and mechanical properties were a trademark of the early issues. And although many of those diagrams were based on exact measurements, I think this diagram on inertia, momentum, and projection can be considered the first proper data-based chart in the magazine. Perhaps it's a little generous. It portrays an impression of the values a little bit more than an exact representation of the values. But the fact remains that it exists specifically to communicate a concept based on measures. This example is pulled from an issue after the 1948 redesign I mentioned earlier. This is the era that resonates the most with me. It's classic science communication in which a scientist, a journalist, and an artist collaborate to reach a non-specialist audience. The style continued for several decades. As an announcement leading up to the 1948 redesign stated, the Scientific American will employ pictures to communicate the science precisely and plainly, just as this 1975 chart pair on cancer. But in a few more decades, plain would be a little out of vogue. The graphics in the 2001 redesign issue mark a distinct departure. The charts are broken into smaller, more digestible nuggets. And the introduction of non-content varying details, such as a third dimension and drop shadows, they suggest that the goal of the graphics is no longer simply to convey the information as clearly as possible. They are also being used as devices to activate the page and entice readers. But rather than dismiss the 3D pie charts as misguided, what can we learn from this conscious choice to shift from plain and precise to self-consciously dynamic? After all, illustrative details at the expense of a clear read of the data is nothing new. So what do these two eras, 1921 and 2001, what do they have in common? Well, in both cases, the magazine was actively trying to engage a broader audience. It's an honorary and necessary goal, which leads me to today's philosophy towards data visualization in the magazine. My goal is to help produce graphics that honor the data, but also entice the reader. That means embracing new forms when appropriate and never underestimating the power of a welcoming gesture, such as the B illustrations here. So another bit of key context, workflow. At Scientific American, we officially launched the visuals for each issue with a day of preliminary art meetings. They're half-hour brainstorming sessions based on the first draft of the text for the article and notes from the article editors. Our article text editors have subject matter beats, whereas our art department is a more generalist team who have media beats. I do information graphics, we have a photo editor, a layout editor, etc. By the end of the day, we're usually able to rough out a basic plan for the whole issue. I focus specifically on the graphics needs. Here's a basic production schedule. It's not quite this linear as Matt Bostock's earlier talk touched upon, especially that first two weeks. I should probably change this graphic. There are usually five articles with graphics needs each month, and two issues are always solidly overlapping. So let's move on to the graphics. I'll start with two examples pulled from the same issue. First, the flavor network. This was a print-first project that would accompany a somewhat playful introduction to our full single topic issue on food. The graphic would be based on results published in a peer-reviewed journal. You may recognize this figure from the original paper and scientific reports published back in 2011. It connects food items that share chemical compounds. They then went on to cross-check those connections against recipe databases to see if there was a relationship between off-impaired ingredients and their chemical compound overlap. As it turns out, western cuisine does tend to pair strongly related ingredients, but classic recipes from East Asia do not. Our goal was to create an image that would bring some of the researchers' conclusions to a new audience and perhaps reveal the patterns in a more intuitive and engaging way, although this was a pretty darn good figure for an original scientific publication, I must admit. The paper was open. I could download the initial dataset right away to review, and it was a signal that the authors would likely be open and excited about collaborating, which they were. YYON and Sebastian Anert were really helpful in suggesting a filtering method and reviewing sketches. With the data in hand right away, I could go ahead and carve out a space for the graphic in layout, and I reached out to freelancer Yann Willem Tulp to see if he was interested in the project. Now a reminder, I'll be speaking about these projects from the art director's point of view, not the artists. When possible, I'll also direct you towards some resources that will help flesh out the story. In this case, check out Yann Willem Tulp's presentation from the Visualize conference in New York. I don't believe the video is live yet, but here's a link for when it does become available. There's a landing page with just no content available yet, kind of teaser there. For this project, my directive to Yann Willem was fairly open-ended. Take the dataset behind the original flavor network diagram, and develop a one-page variation on it for our print magazine. If interest builds and if an interactive made sense, then we negotiate a web companion item. So this is the first sketch that Yann Willem sent to me. You'll see from his Visualize presentation that it was definitely not his first attempt. Like Mike spoke about earlier, kind of the wild exploration stage happened before it got to me. And at this point, we're starting to now kind of polish as we're headed towards some very real print deadlines. I tried to get concept sketches into layout as soon as possible. It became clear that I'd need more than one page for the graphic and to set it up with some text. So coordinating with the whole article team as soon as possible would increase my odds of being able to take on a little bit more real estate and spill over the gutter for an introduction and annotations. So back to the sketch. Yann Willem's motivation? Well, the original flavor network already did a great job of highlighting the topology. He could improve on it by sorting or grouping to make it easier to read the information. He sorted the ingredients into columns by category. Each black dot is an ingredient. The size of the dot corresponds to how often that ingredient appeared in a recipe database. The blue circle paired with each black dot represents the total number of links with other ingredients. Gray lines connect ingredients with shared chemical compounds within the same category or food type. Orange lines connected ingredients with shared chemical compounds across categories. The vertical position of the dot is based on the ingredients mean shared compound value for all of the links that an ingredient has. So this was the sticking point. In some ways, it's a logical metric to sort by. Ingredients with lots of strong relationships would rise to the top. But it's kind of a complicated measure. It takes a few mental leaps to figure out what it's showing. The overall structure and plan for the graphic felt right, but the metric behind the vertical position of each dot wasn't very intuitive. So I asked for variations. Yann Willem sent lots of options. I notated his screenshots with a description on the right to solidify the logic in my own mind and so I could more efficiently communicate with others on the article team. I won't get into the details on all of these sketches, but thought you might like to see some of the options that followed. This one was my favorite. Vertical position is based on the total number of connections to other ingredients, not the strength of those links. The blue outline circles that originally held that information were no longer necessary. Once the structure settled in, we turned to fine-tuning the aesthetics, informed by the color palette and style that was emerging for the full special issue. Here's the final article. You'll note that we added annotations to bring attention to a few points that we found interesting. But perhaps most critically, we included a really large how to read this graphic panel in which we walk the reader through the symbols used in the graphic in a very conversational way. This approach emerged really organically from the verbal explanation I had to provide to a colleague whenever I showed them the graphic for the first time. And it was more inviting than a small key or legend kind of hidden in the corner. This is also the first thing you would see for the interactive version. While I was fine-tuning labels working through the fact-check questions and presenting a print version for press, Jan Willem turned attention to developing the interactive version for the website because folks at the magazine were definitely interested after having seen what he had done with it thus far. The best option based simply on our budget and deadline schedule would be to start with the print version and then allow readers to select and view by-ingredient. This would allow them to see all of the connections by selectively removing many of the lines. Now selecting by-ingredient did seem logical, but a drop down list for over 300 ingredients was unwieldy and a complete list on screen was not legible. Fish eye distortion as you can see being experimented with here was still too dense to efficiently navigate. So what about simply clicking on the blue ingredient dots? Well it turned out that many of the selections only showed a very sparse network. Of 381 ingredients, 148 had no links outside of their category, so they would only have the gray lines, not the pink or orange ones. And 150 just had one link outside their category. So only 83 ingredients would have two or more pink connector lines. Randomly clicking on ingredients might not yield a very satisfying experience for the user. So after exploring a few other ideas as well, Jan Wellum suggested that rather than selecting by individual dot, why not select by a row? The reader would be less likely to accidentally stumble across a really boring ingredient time over time over time, and this approach would also still filter out many lines so that an individual connection, you could still follow it. Here's the final page in its entirety. Now originally I had hoped to simply embed the interactive version in our iPad app, but we're using our app using Adobe DPS, and we ran it to some bugs. Without the time or resources to properly sort through the problems, I had to simply reformat the print version to work on a tablet screen, and we linked out to the full interactive that resided on the Scientific American server. Here's a look at how things were rebuilt for the iPad. Slide out instructions on how to read the graphic, and an annotation overlay. Now circling back to the other food-related item. In this case, the assignment was much more open-ended and pretty much out of our comfort zone. It would be a digital-first reader-directed exploration tool, drawing from a large data set but without pre-analyzed conclusions. I asked the Office for Creative Research for food-related suggestions. Jared Thorpe and Ben Rubin pitched several ideas. The magazine team was most interested in data about produce shipments into the U.S. based on daily reports from the U.S. Department of Agriculture. Here are some preliminary explorations of the data over space and time. And this is how the final data ended up being displayed. Readers could choose the produce item by a drop-down menu and customize the time period by sliding date tabs at the bottom. Three produce items could also be compared against one another on the same screen. And total import volume over time could be explored on an interactive map. A few details still needed to be sorted out with the interactive item, but the reality of the press schedule meant that we needed to turn attention to the print item. An early concept sketch contains some really neat ideas, but it was overly ambitious for a single static page. I see this a lot when folks move from the web to the print page. They want to get all of the ideas that they developed for something that doesn't have space limitations onto a single print page as well. So we tried deleting some of the sides of stories and clicked the maps into a small multiples grid. Here's the final page as it appeared in the magazine. And this turned out to be a bit of an informal experiment. Two interactives launched at the same time, both on the topic of food. One was fairly contained and based on a single study. The other was much more robust and open-ended. The flavor connection did really well for us. It had lots of unique views and was picked up quite a bit from other media outlets. The produce finder didn't land with as big of a splash. There are lots of variables that I haven't accounted for. Each item was promoted differently on social media and even our own homepage. But my instinct is that folks liked a contained item with a clear punchline and a scientific backbone. The produce finder might have been just too open-ended. We didn't give readers a clear directive or a reason to explore. Or maybe it was because the flavor network highlighted beer and cheese and the produce finder highlighted kale and broccoli. But regardless, I think there's value in both genres and we're keen to keep experimenting on both fronts. So far I've talked about a print-first project and a digital-first project. But sometimes the needs of print and web are so different that it makes sense to approach the same data set differently for each medium. For our annual State of the World Science special report, I hired artist Arno Gelfi for the print spread specifically for his bold and dynamic style. For the web, however, I can embrace a quieter aesthetic as evidenced by the interactive from Yanwell and Tulp. Here's a closer look at the print spread. The center spiral of bubbles represent the top 25 countries in science as measured by an index based on research paper output. The bottom left list shows rankings for a few other measures including a number of patents granted. Yes, we could have made this spread work harder in terms of density of information, but in this case, it all came down to the context. The full section was really text heavy. The central graphic spread not only needed to show the data, it also needed to act as a welcoming entry point into the whole section. Yes, data visualizations should honor the data, but they also need to be mindful of their context. On the web, the graphic would be presented as its own module. The context was very different. Here we could focus on presenting more information. We start with country rankings, but the reader could also see absolute numbers. And sometimes no matter how much it pains me, an interactive web version of a static graphic might not be the best use of limited resources. Although Moritz Steffener would have been supremely capable of creating an interactive companion to this print graphic, I had to be a bit realistic about things. The page is based on a neat nugget of a project in which scientists Laurel Burkle and her team compared their bee and flower interaction data with a similar study from the same site conducted over 100 years ago. It was a perfect candidate for a static one-page standalone graphic on the topic, but the scope might have been a little narrow for a full interactive. We ended up doing a static version of this kind of reformatted for the screen in the iPad instead of doing kind of a variation on it. The text editor and I were initially captivated by the study when doing research for a different, broader article on native bees. We set aside this figure from the original paper to revisit later. I couldn't help but wonder how someone like Moritz might reimagine this dataset. He wrote about this graphic on his blog, so check out the link above for a great process post which also speaks to some of the tools that he used. But I won't attempt to rehash that now. Instead, I'll pick things up after he reached this point. After many concept sketches, he settled into basing the structure on the bees themselves. Here, each pale yellow circle represents a bee species, active in Carlinville, Illinois in both the late 1800s and 2010. Pink circles represent bee species that were active in 1800 but are now locally extinct. Each tab position within those circles represents one of 26 species of plants that are pollinated by that group of bees. The color and size of that tab holds information to how that interaction has changed over time. I was sold on the basic concept, but there was still work to be done. Moritz tried grouping species by genus, but this preliminary sketch did not include all of the species, and although it's intriguing from a visual standpoint, there wasn't a strong editorial reason to group them by genus. So I took the original pattern and built out a version that included the correct number of circles. Once we sorted out that the graphic would actually fit on one page, Moritz started refining things. Rather than have the extinct bees pop out in a strong pink or red color, he let the circles fade back, helping to reinforce the idea of disappearing bees. And to help reinforce the hunting home pattern, Gillian Walters illustrated three bees in a vintage style as a subtle nod to the project's start in the 1800s. Since this is an unusual graphic form, we needed to really craft the annotations and labels. Once again, we led in with a conversational style, rather than just featuring a stripped-down key or legend. So let's revisit the legacy of Scientific American. Most of my decisions are rooted in the tradition of precise and plain visual explanations of scientific discoveries. But I also need to be cognizant of the need to be accessible and inviting to broader audiences. In my opinion, those goals are not mutually exclusive. But in certain contexts, even within the same magazine, it may make sense to shift a little bit in one direction or the other. I may skew towards a more playful and lighter solution when the graphic itself also needs to function as an invitation to dive into a larger text-driven package. I try not to underestimate the value of a welcoming gesture, such as illustrative details, and maybe a clearly stated and upfront invitation to read the graphic provides a little leeway to feature a more complicated or unfamiliar visualization form. Thanks.


He he he wow you too team keep it clean.  What is going on? It's engraving here with another video and in this video We're here to talk about the news that literally just dropped minutes ago Between the chiefs and the Redskins the end of two errors the end of the era of the QB in Washington And the end of the era of the QB in Kansas City So if you haven't heard if you haven't heard if you haven't heard Then this will be this is my office pyro. It's not a baby room if you haven't heard This will be the new Jersey that Alex Smith will be wearing The Redskins agreed to trade to get QB Alex Smith To get QB Alex Smith So I believe the trade won't be able to be official until the offseason begins, but they have made the agreement So now Kirk Cousins is set to be a free agent Before we get into this That's wild man before we get into this. Let me introduce myself me. I'm engraving vision This is my YouTube channel engraving vision. I'm a Ravens fan Now even though I'm a Ravens fan on this YouTube channel We talk Ravens all the time, but we also talk Redskins. We talk chiefs.  What's going on everybody that came through? I appreciate y'all being here, man Thank you. You could also follow on to the Instagram and snapchat, but anyway Hmm the end of an era feel like we're making a WWE promo or something, but that is wild That is wild There had been talk about See, I'm more surprised on the On the Redskins part than the chiefs part because Redskins they've been doing a franchise tag thing with a he said it's such a DC movie Yeah, that's true. They they love doing the wild stuff And they they've been kind of slacking over the past couple years and doing the wild stuff But this is Redskins right here like Clinton Porter's for Chan Bailey back then Who Albert Haynes worth Redskins usually do the they do the wild they do the unexpected the dynamic lab trade Um, who else did they get the Deshaun Jackson signing? Redskins have done No, wait a minute Deshaun Jackson wait, whatever Redskins have done their thing They have they do the wild stuff and this was very unexpected. I did not see this coming Because I felt like He said but will it help the Ravens?  I felt like he was gonna be their guy I felt like he was going to be it I know they had been doing the franchise thing the franchise tag with him for a while Slapping a franchise tag on him, but now that is no more. He is out of there, man He is out of there. That's crazy, too. That's crazy Kirk Cousins man the dude who been on the honor with the Redskins since he was a rookie him in him in RG3 He lasted longer than RG3 both with the Redskins and been health-wise and then now it's looking like NFL wise, too Think RG3 was the number two overall pick and Kirk Cousins was like a third or fourth round pick I think fourth round from where Michigan State don't quote me on that. I don't remember but Kirk Cousins is free to go wherever he wants to now Unless the Redskins No, he if he signed the franchise tag and that means it's a one-year deal So they're gonna let him walk now, but Alex cut Alex. I'm gonna say Alex cousin. I'm over here mixing them up Oh, it was MSU. Okay. Appreciate that. Now Alex Smith on the other hand He we all knew this was coming with Alex Smith. This is not a surprise with Alex Smith that he got traded It's not a surprise at all. It's not a shock or anything like that. We knew he was gonna get traded We knew he was even gonna get traded a release. We knew he wasn't gonna be with the chiefs anymore. The writing was on the wall When they drafted a QB in the first row, you don't draft a QB in the first round to have him just sit there forever You don't do that maybe if they had like an all-star QB if they had a if they had a QB that um That was just a monster day in and day out and Alex Smith is nice Don't get me wrong, but he What I said before I feel like Alex Smith is limited and he for a lot of games this year He did shut me up, but they also just Proved me right Alex Smith. He's hit his ceiling with the chiefs He'd hit he's hit his ceiling with the chiefs and I guess they feel like He can't get any higher He can't get any higher But yeah, it's like father in a rise he's father in a row was different because with Brad Farve you had a Hall of Fame quarterback You had somebody that you knew could get it done and you drafted a rod You knew he was gonna be a future, but you had him learning behind one of the most historic QBs of all time but with Alex Smith and Patrick Mahomes Alex Smith, he does his thing or whatever, but um He's not one of the most historic QBs of all time I mean he has a low turnover percentage or whatever, but oh and this is it's a second round draft pick two. Oh plus more, okay But yeah, Alex Smith is not a Hall of Fame or anything like that, but I mean he gets the job done but like I said his His ceiling has already been reached He's already hit his peak He's done the best that he can do he took this team as far as he can take him and the chiefs I guess they knew that. Hey, you know what Alex Smith? We loved you. We loved everything. We did for you I mean we loved everything you did for us, but It's time to get you on up out of here boss It's time to get you on up out of here So we'll see you we'll see you when we see you So now it is officially Patrick Mahomes time Yeah, there has been some rumors that uh that Kirk Cousins could end up going to Denver because you know they got their whole QB Situation over there. They had Brock Lesnar Osweiler.  Kirk Cousins is going to be paid He is going to appreciate that feeling for life. He is going to be paid Kirk Cousins is going to be paid. Yeah, this I just saw that extension thing pop up on my phone, too That's crazy, man. Rescue is just I'm not I don't want to say they're throwing it away They just don't know they don't everything for Alex Smith, man. They don't know that before your extension like let's let the guy I Don't know man rescue is just yeah, like like Mark Hill said earlier He said it's such a DC move because that's exactly what it is, man Redskins they they going all in giving them a four-year extension and like I don't get that man. I With the with with you trading for Alex Smith. Okay. I'm like I'm kind of neutral on the move Alex Smith and Kirk Cousins are very similar to me They're very similar to me I think Alex Smith if I had to go with one over the other will probably go with Alex Smith It's close though. I will go to I will go with Alex Smith over Kirk Cousins though, but not by much not by much But It's like, okay, you trading for him. Let him show you what he's got You're gonna give this dude of a four-year deal before your extension really like that That's wild man That's crazy.  You got rid of Kirk. Good Don't get Alex too late man too late Scrubs he just throw too many pics. We'd be expecting it every time you kiss me Outbound mall city idiots Make sure y'all leave a like on the video to click the thumbs up button click that thumbs up button There's 80 people in here, but we only got 40 lights y'all make sure y'all click the thumbs up button Um, but okay extreme challenge.  It's time for him to take over the reins and do his thing Where is Kirk Cousins gonna go to now though, where's he gonna go some people saying Brown some people saying Broncos I saw somebody put Vikings Vikings. They just got a situation over there QB. I don't know what's gonna happen with them He he's definitely gonna have options. Okay clutch time with the Vikings fan. He said Vikings What do you think is gonna have clutch time? What do you think is gonna happen? And I don't know if quality control is still in here. We all think it's gonna happen with a case Kingdom And Sam Brassford and Teddy Bridgewater Jacksonville. I see some of y'all saying Jacksonville too But um, I know they said they want Blake bottles to still be that guy, but but but Even though they said they want Blake bottles to be their guy Stuff changes stuff can change like that stuff can change like that and NFL People's word means nothing and Even contracts don't even mean nothing you could sign a 10-year deal and they can cut you tomorrow Yeah, they'll deal with the salary cap problems and whatever but I'll see the Browns and chiefs with talking about Alex Smith earlier. Okay a lot of news coming in I love when when news drops when when an official deal drops and then you get all the news that That happened in the background to all the ifs and what ifs and the butts and oh this could have happened But so the Browns were trying to do their thing for Alex Smith, too. So obviously didn't work out Obviously didn't work out Yes, the Jets need a quarterback who they have the last year. They have the guy who used to be on the Browns the Ravens killer Josh McCown so Extreme say Kirk should go to the Giants I You know what I think they're gonna keep Eli some reason I think they're gonna keep Eli I think it it should be time for them to go ahead and move on But I think they're gonna stick with Eli because I feel like it's more so a Homer thing of not that I don't want to say a family thing But he did win your two Super Bowls. So I feel like I feel like that is keeping him there I feel like that's keeping him there. That's keeping Eli in New York. I know recently. They haven't done anything They haven't done anything. I know last year. They had a boatload of injuries. So They what did they go 3 and 13 or 2 and 14 or whatever it was? They're there their record was bad So, I mean that was that So, yeah, okay, Kyle said Eli isn't leaving until his contracts up.  So but anyway, it's another story for another day Whoa, and that is some gas for tonight. Anyway But yeah, man, that was that feel good said he should go to Arizona DJ is coming back. They still got Larry Fitz and a good defense and not bad teeny just got some injuries That's true. That is true Kirk cousins go to Arizona. That's an immediate upgrade. That is an immediate upgrade immediate upgrade Because Carson Palmer he retired and he was always getting hurt. They had yo Gabba Gabba so he He's a backup at most So yeah, you can even you can either go draft or you could go for Kirk So Kirk is gonna have options. We already know that he is going to have options He is going to have options. He is going to have options so Now Alex Smith, who are his weapons in DC? He got Josh Dotson Terrell prior only signed a one-year deal and he won't be back They had they weren't feeling they weren't feeling to real pride this year I don't even know how that roster is looking but obviously the roster's gonna change a lot because They have between now and the whole offseason and yeah, so we got a long way to go before roster's are set We didn't even get past the Super Bowl yet. So We'll see May go to the Ravens Landry. Hey, I hope so man, but I doubt it. Let Kirk go to the Ravens so they can have a good QB Jamison Crowder. Yeah, the little guy he's small receiver But yeah, and I think he's a partner China too the caps low for Landry Yeah, we Ravens ain't got enough money for that do most likely it goes to when Super Bowl said Anthony. We'll see man We'll see we'll see I am um, I'm hoping they win But we'll see man Kirk to the Dolphin. Oh, I don't think that's gonna happen But hey again, it's NFL. So you never know They got Ryan Tannehill he's a hundred million dollar quarterback They had Jake the snake Cutler. He is a 13 million dollar one-year quarterback and now that deal is over So he'll be a free agent if he decides to retire again We'll see what happens with that. I don't think he goes to the the dolphins though I think dolphins would probably be ruled out of that But again, you never know Jaguars. I see a pyro said Jaguars to again for Kirk cuz I just I don't like I said They said they said they want to stick with With Blake Bortles but Let's see because this is obviously a new opportunity presenting presenting itself now, you know us as Ravens fans We know how people can go back on their word. They can change their mind Gary Kubi exit Hey, um, I'm I'm gonna stay with it when he was our offensive coordinator We went to the divisional round offense play great defense came up short shout out to Dean Pete's and it's not much defense But anyway, um, Gary Kubi exit. I'm gonna stay with the Ravens.  What did he do left went to Denver to go become the head coach So he went back on his word Also Dean peas speaking of Dean peas in his non-clutch self. What's up, Lizzie? Yes, this is very true Speaking of Dean peas is in his non-clutch self. He said he was gonna retire this year He retired and then four weeks later.  I'm gonna under retire I'm gonna go be a defensive coordinator for the Titans. So what that means is Hey, no problem. There's a shout out to you man. I appreciate you so what that means is that People go back on their word and things change so with with With the Jacksonville Jaguar saying that Blake bottles is going to be their guy They could go back on their word and change switch it up Just like that and then end up going for Kirk Cousins. So hey, we'll see man We'll see we'll see we'll see how it goes. But yeah, I appreciate y'all man Appreciate y'all coming through here. Make sure y'all subscribe if you haven't already if you knew here We do these streams all the time Any football news mostly Ravens news, but any football news that drops we stream about it We talk about it and this is one of the only places where you can give your Reaction how you feel about whatever Live and we can all talk about it in the stream together. So I appreciate y'all see we got 78 people in here right now 70 likes Let's make sure we get that get the numbers across the board even So 78 people in here. Let's make sure let's get to 70. Let's get to just let's get to 80 likes Because I know it's 79 people in here and those are some people that was in here already might have came back somebody Might want to go get dinner or whatever But I appreciate y'all for real for real I mean like I say you can follow on Twitter Instagram and snapchat or three or three or engraving viz Just like the YouTube channel. I am g r a v e and vid s. What's up, Gerald? What's up, Gerald? See that's what it's about and this is team keep it clean. So There's no cursing all comments got to be kept a hundred percent clean We don't talk down to anybody else. We keep it clean man. We chill We do we do that. Oh Oh, oh, yeah, Raskin. There you go. There's your hell to the Ravens, right? Hey, I appreciate that Jetson Yankees nation Thank you. What's up, Julius? Buffalo Bills get Kirk Cousins. Ooh, that is a Forgot about them because the bills appreciate that as any day la Cruz because the bills They tie right tail is gonna be gone. He's gonna be gone He's gonna be gone So yeah, he's that that would be a good move for them Broncos the Jets for me for Cousins. Yeah Bingo sick, it's funny. Hey, what's up, DJ swag? Dude, I'm telling the Jaguars are getting cousins Joshua Gutierrez is sure about that. We gonna see man. We're gonna see what to the be back here I'm not sure who to do is a cowboy x-factor. You're right now They said it was for a second round picking some other stuff to win So we're gonna see AJ McCarran get Josh Norman out of Smith.  There's another shock of a cousin's going. Yeah, cousin's out of there. He's gonna be out of there. That's It's crazy. I'm not and no no king trick. I don't think Tyra will be back at all at all Okay, right there's gonna make the playoffs. I mean, it's too early to tell me It's way too early to tell for all the teams right now It's way too early to tell because this we ain't even get to the off-season yet free. We still got free agency We still got the draft. We still got preseason. We still unfortunately got injuries. We got all of that stuff Yeah, we talking about playoffs for next season. Yeah, we we didn't even get to the Super Bowl yet You're right. We didn't even get to the Super Bowl yet, but it's there man That's true quality control. We said think about how many players are gonna be coming back from injuries next year That's true. But then the bad part about it is think about how many players will get injured next year And we don't even know who that'll be yet So that sucks again like I always say worst part about football is injuries worst part worst part Worst part Chris Richards. I'm not sure who Chris Richards is sounds like it's probably a player from college But I don't watch college football. So I'm not sure who that is Cousins going to want to go to the Giants. Oh to sort of get revenge and say hey y'all left me hanging like that What's up Robbie G? So y'all left me hanging like that and y'all didn't want to pay me Y'all didn't want to give me the long-term deal y'all just wanted to franchise tag me end up going to the Giants and giving payback Because all the other the NFC East teams are already set that quarterback that press got What's the cost it went Or Eli Manning is we'll see about that. We'll see about him Like I said, I feel like the Super Bowls the other only reason that they keep an Eli Manning Pedro said rescue should draft the quarterback because Smith is 33. Oh, he's four-year extension for 33-year quarterback who You just traded for so he's new to your team. It'll be a new system for him. I don't know. We'll see me We'll see me The Eli Manning area is over. I don't know man Like I said, I think the only reason he's still there is because of the Super Bowls Now if they got rid of him, it will be surprising but not surprising at the same time, man It'll be it'll be strange. What I think about the Saints Saints offense Continues to do a thing way the defense they Just they were one play away from moving on and that was Who that I know that was a heartbreaker for Saints things me that was tough the way that they got eliminated from the playoffs that was tough, man That was tough That was tough But it's all good man It's all good cousin to the starter so I don't see any way he wants to sit behind Eli for any amount of time That's true Eli to the Broncos. You think two brothers gonna play for the same team I don't know what Eli would do if he got cut up. I just I don't see anybody at safe instance No, well, Nizi if we get ready skin news, then sure But if Eli Manning were to get cut I just I can't see you if besides if it was the Jags I just couldn't see anybody like Jumping for my oh, yeah, let's get Eli. Let's get Eli. Let's get Eli I couldn't see anybody getting excited to bring Eli to their team I couldn't see anybody getting hyped to bring Eli Manning to their team I just I just couldn't see that maybe if it was a Jaguars, but that's it That's that's it Cuz Tom Cawthon is there and he knows Eli, but other than that, he said all y'all keeping to real slugs We'll see man. We'll see We'll see See it, we'll see how it goes man, but Yeah, Cowboys not gonna get Kirk cuz they they got that press cut. He ain't doing that Nizi said if Gino Smith can start over Eli then so can Kirk I think that was more so been McAdoo saying, you know what Giants? I hate y'all I know y'all gonna fire me that's kind of when somebody like they have a job and they just they're absolutely 1000% sure they're gonna get fired So they're just showing up to work and literally doing whatever That's what I think that move was by been McAdoo to start Gino Smith over Eli Manning That was wild man. And um, that's that's that's what I think that uh That's what I think he was doing when he did that I think he was just like, you know what forget you Giants I know y'all gonna get me up out of here. So you know what?  So how about that? so anyway, um That was that so There you have it He said buddy give Kurt that hundred twenty meal lay fist to the packers. I don't know Yeah, Julia step Gino Smith start that's what I think it was he knew that um, oh here it goes The chiefs got a third round pick for Alex Smith And there's also a player going to the chiefs too. Oh, we're gonna see who that is man We're gonna see who that is we're gonna see who that is real soon I'm sure that is going to come out real soon probably within the next 10 minutes Where will Larry Fitz go? I don't know if he goes anywhere. I think Arizona's too loyal to him Or unless they send him to a a playoff contender, you know how they do get Josh Norman out of Smith We'll see Let's see. Oh low key one in Smith. Hey, y'all almost had him apparently y'all almost had him almost Cleveland finest Browns they said that Browns tried Browns tried it, but They didn't succeed won't know actual picking Tim watch speculate They said it's a third round pick they said it's a third round pick just now man But they also say this it's a player involved too. So it's a chiefs player involved besides, uh, I mean, we're gonna see who it is man. We're gonna see who it is. So Waiting on that we wait on that no one wants to go to the Browns Well, that that QB then that college QB does was it Baker may feel to a different one Who was talking about he should be the first over out first overall draft pick to the Browns And he said he's a winner and that he could bring a winning attitude to the Browns and stuff like that I forgot. Oh, was it was it Josh Allen? I thought it was the other guy Sam Dono. Okay, some people saying Josh Allen Okay, most people saying Josh Allen. All right. That's Josh Allen for the one So I'm gonna go with Josh Allen, but I'm not sure man Yeah, I would like to see Manziel come back to Just put him in a different team a different atmosphere because Browns have shown that they They're not the best runner organization in the world So they I Just want to see him somewhere else. I want to see him somewhere else XFL, um, I mean, we'll see it's gonna be different. It's gonna be more football So we'll see how it goes. Let's see how it goes Can veils make superbowl with Kirk Cousins? Yes or no, I don't know. I just don't feel like Kirk Cousins Anybody can get hot, but I don't feel like Kirk Cousins is really a superbowl quarterback You never know man. You never know never know never know so That's that. Oh jb's move you caught that one too appreciate that Antoine your reaction to the trade. Um, I just thought This is something that the Redskins have been known for. Um That's that this this is the Redskins all day. This is what they do.  That's what the Redskins do so That was that so cousins. Yeah, you could go to arizona too. You gotta listen to teams that uh That can get his services So hey, that's it quality control there goes man You don't have to learn those players man. I'm gonna try. We'll see how it goes man. A couple years though Got a couple years. There's been no commitment with Kurt at all I know he wasn't gonna be around but to get out of Smith is a plus Yeah, because I like I said, I will give Alex Smith the edge over Kurt cousin. I'll give him the edge Um So yeah, that was that man. So anyway appreciate all y'all up in here right now. Thank you uh for coming through Um, again, like I said earlier, make sure you subscribe if you haven't already Uh turning notifications on if you haven't already and leave a like on the video click the thumbs up button And you can also follow on twitter instagram and snapchat All three are engraving feeds all three of them, man. Do you think Smith is a top five quarterback? It depends on what the categories of the what the what categories you're talking about If you are saying a quarterback a top five quarterback in committing The least amount of turnovers Yes Definitely Um, if you say a top five quarterback just overall No, um Do you have confidence in Alex Smith arm strength? Yeah Alex Smith got a strong enough on the throw the deep pass Um, it ain't the strongest in the world, but he got enough to get it done, man Um, Eric said Smith is a bus driver. Kurt cousin would be a better quarterback on a good team Hey, we'll see man. Well, baby a retire after winning the Super Bowl Okay, the alburton kid said patriots won already and left that he ain't going with eagles He ain't thinking eagles are gonna win at all So shout out to alburton kid. I don't think he would retire though Yeah, I remember he hate me macabre. I remember he hate me. He was at running back. I think it was number 30 Um, I don't remember the team though, but I remember him. What if Vic never retired? Oh, man I love Michael Vic. He was in a real deal, man Um, oh, we're not feeling this news. He said no, no, no, no, no, no Um, I definitely see him as more mature and less reckless quarterback. Good trade Yeah, well there it goes He mean good trade On reskins end They should get a chiefs of first and the fifth row For alex Smith. No No Yes, I do one thousand subscribers with no videos. I sure do um Johnny football, I mean, hey Johnny football I would hope he would get another shot, but I don't see it happen Vic should have went to minnesota. Oh, that could have been something. Who knows but yeah, if you Some of y'all younger some of y'all older Some of y'all might just know michael vic from mutt but Vic was if you ever got to see him like live if you ever not live But if you ever got to see him play when he was in the nfl when he was on the falcons Not the eagles. I mean eagles. He did his thing after the first year, but not eagles not when he was on the jets Um, not when he was on the stealers But if you ever got to see michael vic when he was on the falcons if you actually got to see it And not even just highlights. It was like when michael vic He made football so exciting because any given play any given play he he could take off And or he could just throw a deep he any given play anything could happen just like that just like that so He was a he was a monster man Oh, they said the play will be named tomorrow. All right, we'll see man We'll see if you think puff buying the jets now. I wish you would buy the pandas. Oh, so but That'd be cool if you bought somebody. I would like to see that I would like to see that kirk is better than you than alice in this at dominique garland I don't know. He said vicki madden. Oh five was nasty really madden. Oh four because that's when he was on the cover of it But yeah, vic was crazy. You know how um Every once in a while like if you were playing street football Maybe if you even play regular football at your school college, whatever um There's always those quarterbacks who you try to uh play like And I remember when I was growing up. It was vic michael vic was the guy michael vic was the guy you wanted to play like vic I even would try to uh to I would try to run around if I was playing quarterback when you're playing like street football Try to run around and I would try to throw in my left hand, but he was that dude, man michael vic was that dude um So, yeah, we'll see We talking about basketball. We talking about is this trade a cheaper option? well, I probably yeah, probably yeah, because um Because Kirk Cousins gonna command a lot of money. Alex Smith. They they said they're gonna uh, they gave him a four year extension but um We'll see. I don't it's not gonna be as much as Kirk Cousins will be getting paid uh in in march once free agency starts so Lee johnson chiefs going to the super bowl with patrick mahones. All right, we'll see man. We'll see Do you think we'll see possibly see a jags pittsburgh a lc championship game next year? No. Oh, do I like basketball? Not really Not really Uh, jay lorenzi mad 19 cover. You might just be right, man You might just be right So Let's see We could end up being a hundred percent right on that one But anyway, I'ma go ahead and get off of here now Appreciate all y'all coming through seriously. I really appreciate all y'all coming through like I said if y'all are new here Um, thank you. Thank you. Make sure you subscribe and turn your notifications on so you don't miss anything I know I said that like 50 times, but I just I just got to make sure I'll make it clear because I don't want any y'all missing any videos I don't want any y'all missing any videos. So thank you Thank you for coming through all the new people or the old people whether you've been here before Whether whatever you every everybody. Thank you for coming through man. Appreciate y'all. I love y'all make again subscribe Turn your notifications on leave a like on the video And you can follow on twitter instagram and snapchat All three are in great events. It's ing rav and vids All one word just like the youtube channel. So thank you. Thank you. Thank you um I love y'all appreciate everything y'all do for this channel because y'all make this channel exactly what it is, man Whether you've been here for a long time or you've just been here for the past 30 minutes and this was your first time So thank you and I will see y'all in the next stream. I'm going man. We out


The women in general were kind of silenced, they were not silent but they were silenced because they were not at the table and that's the achievement of this campaign to bring the voices of the women here. Women collected 500,000 signatures demanding that their human rights would be recognized. We are facing unfortunately some setbacks. This very, very important idea that every person has rights from being born and has rights and is equal is questioned again. Luckily the women are not stopping because they haven't achieved everything yet. They are far from having achieved everything and now the danger is that it will be taken away from them but they will not let that happen. What inspires us are all the women and girls in the world that fight for their rights and often in very difficult situations. Be courageous, we need a lot of women human rights defenders.


Hi Dag, how are you? I'm good, how are you? It's the beer mug for me. Yes, of course, I have to have it everywhere man. Let me ask you. I know you're so close to Mamito and just working close to her. What are you expecting today? Oh, it's going to be a good show. It's going to be chaos, laughter. People better be energized because it's going to be very energetic. Yes. All the performers there are killers. So it's really going to be a good show. I mean even for her just to organize this. It's quite a big deal. Please tell her something. Yes, congrats Mamito. That's a big step, you know. You're taking the bull by the horns. That's the way it's done. Yeah, that's the way it's done. I'm proud of Mamito man. Amazing Dag. Thank you so much. All right, thank you. All right. Award the winner. Hey ma'am, how are you feeling? I'm good. Yes. Let me ask you. Has life changed over the past one week? Well, more work. Because this entire week I normally work three, four days a week. Yes. This week I've worked six days. Wait, nika zimpia manini. No, niki na bado. Okay. But nilu kwa kwa call sheet from Monday to Saturday. Then I'm like, where? You can't complain.  I mean professional. Chas to match up as well. Yes. Thank you ma'am. But I'm so excited to see you. Najwa Mamito is one of your close friends. What are you expecting today? To laugh. As loud as I can. Yes. Please tell Mamito something because even just doing this today is quite a big deal. Please tell her something. Congratulations! Mamito, all your friends are here. Yes. Amazing mama. Thank you so much. And I hope you enjoy. Yesawa. Alright guys, I'm hanging out with one of Mamito's friends as well. Chasa mama. Hi. Chasa? Uko powa? Habisha? Awesome. Ume pendeza sana. Thank you. Nika ma tulembot, very red. I have seen so many people with red today. Hey. Baby is part of the theme. Kuliza, let me ask you. Mamito is doing Mamito and Friends today. Ukiangalei kitwenya nafanya big e-vileo na takaku muambia ni ni? Neza muambia kitwenya nafanya she's opening a very big path kwa yoku encourage female entertainers in Kenya sababu kuna vile kido gopale female entertainers emela liwa maskiyo. Sana, sana. So, she's doing a very motivational thing and I'm so proud of her. Yes. No, you also bina. I want to watch a Vivo. You've been a female entertainer as well. What are some of the challenges in Yoneza Semanya? Kwanza especially doing comedy Ume pitiya? To be honest, personally, Sijapitiya challenges mingi sana so I'm not going to touch about that. Learn about Mamito and her success and her progress and how she's pushing herself. Yeah. Yeah. Learn about yae na yae pekiyake. Sure. I mean, wajapia wukiwa deyem na kama kusapot dey mwenzako. Nakunam tu labda na kuo chpale ana takaku kwa you know where you guys are today. Maybe you guys are going to encourage kumakuna challenger na pitiya it's not going to last. Eh, kama wuna pitiya hard time mwenendela tuku jitu maata saenyo jitrash tata saenyo na feelu ko down Arasa enya content na kula two views badu na jituma just una make sure pia umekama uti place kama hi you meet other entertainers unas you interact with them wana kwa mbiya nishidagani wana pitiya so from that you know where you stand in the industry. For sure. Sababa wuna eza kwa na masida but tu jui watwengi wana go through the same thing badu wana jituma. So uki kosaku uki lala kwa nyumba kila kitu kwa simu Auta achive cho cho se Yes. So my dear. Thank you so much. Wacha tukwachili, a window watch show. Thank you. Alright, nice to see you.


Okay. So just one second. Yeah. So the first agenda for today, the demo we had, the first thing I wanted to tell is that I have raised the PR for the blog post. I'd like you guys to review it and as soon as we can publish it. So apart from that, from the demo, what I'd like to discuss is Oleg's comments. He was talking about about the scope of our benchmarking strategy. And he was, he was, he gave a suggestion that we should also consider the depend, as far as I could understand him, the dependencies upon which the Git plugin works like the credentials API, we should also consider them by we're benchmarking the plugin. So I'd like to discuss that because I think this meeting, we can use it to plan what we want to do for the next phase. And yeah, so first, let's just discuss what Oleg was saying, Mark. I'm actually not, I haven't explored the dependencies of Git plugin. So this much I could understand, but could you please explain more how we could use a suggestion in our plugin in our project? Yeah, I think, I think so audio check first, can you hear me okay? I'm not sure if my internet's well behaved. Okay, great. So the I believe his concept was that there's a higher level or no, there's already in Jenkins, a layer at which things operate, for instance, in a job, and you see them when you run a job. The output is there where it does a Git version command and that it does a Git config something and it does something else. And I think what he was expressing is, could we benchmark the aggregate of all those things together and get useful information with the intent of looking for things we could stop doing or do differently. As an example, in the checkout process when you watch the commands that are being being reported, one of them is it's doing a Git config. So it's actually calling command line Git and doing a Git config. That is an obvious target for a JGit transition so that we don't have to fork a process. Java is great at opening files, writing content to files. And so that's one of those places where, but it's not clear to me, would that actually help at all? And I think that's what he was looking to explore is, okay, is there an interesting difference if we were to put a benchmark at the level of something above in a pipeline step? So a checkout SCM, if we did a benchmark of checkout SCM in a pipeline and said, hey, let's compare checkout SCM for CLI Git and checkout SCM for JGit. For me though, the number of variables there explodes. It's even harder now to decode which are the significant variables and which are the insignificant variables. I think as far as I've learned about, I've researched about micro benchmarking, the general advice is to micro benchmarking exactly means to isolate to a single point in your operation and then try to test it because if we are trying to benchmark the whole operation, the amount of variables we'll have, the unknown variables, that's something which for that, I considered that as well to time the whole process as well because I discussed it at one of the meetings about the scope of the benchmark, a big benchmarking strategy that maybe we could also write something, write some kind of benchmarks for the plugin, Git plugin as well because that information might be more useful for the users because the benchmark setting in the Git client plugin would be benchmarking the same operations and there might not be too much change in the operation, the way Git fetch is working, so benchmarking the same, the benchmarks just serve the purpose for once that we benchmark them and we gain insights and then we use those results. But if we have some benchmarks at the level of the Git plugin operations, which would involve, like the SEM check product involves a combination of Git operations, so if you're able to benchmark that at each build any developer creates with the master branch, that would be very useful for that person if they're changing anything and the performance is increasing or decreasing or if it's being affected by that. But then at that meeting or what you, the mentors, we decided that that would be, for the current scope, it would be, it could be something we could do once we achieve what we want to right now, but right now that would, that isn't something we're looking for. So if it's something we want to consider, maybe we can, right now I think the current issues we have, it's first, for an example, first I need to, the benchmarks I do for a single operation, I need to be more confident that I am able to get good results and we're able to actually use those results in the plugin. Once we, maybe we exhaust those avenues of exploring single operations and we're not able to find any useful insight to improve the performance, maybe we can move up. Would that be a good strategy? That suits me just fine. I'm still, I think, I think you got it. Oleg's, what I took from Oleg's suggestion was if we had completed the other objectives that we had set, we could go to a higher level. I don't think that we've completed those other objectives yet. And I think there's much to be learned still in the, in the, at the level that had been defined. So not, not to discount, it's very dangerous for me to ever discount that genius that I work with. He is, he is a delight. Oleg is absolutely brilliant. But it's, it's also, I think we had a good plan. Let's continue that plan. And as we learn more, we may then broaden it to say, Oh, yes, he's got the right suggestion. Let's go higher level. Okay. Okay, that sounds good. Okay, so the second thing is the bottom of the demo, we, so we, the PR for the fix for the redundant fetch issue was merged, but there was also Mark requested an opt opt out global switch, which would be helpful for some of the users if, if our logic is not correct. So, so with that, before discussing the issue, I would also like to ask, should we, should we add any issue track, should we start tracking our issues with Jira? Why I say this is because when we were discussing this issue, I, I thought by mistake that when we're talking about the global search, we're talking about the switch, which we will implement in the performance improvements once we have the performance improvement. So I was, I was actually not aware that at the time when you asked by merging after the merging the PR that we need an opt out switch for this fix as well, I was not aware, I forgot and I did not track it. So I was thinking and also, also one more thing with this issue is that sometimes we discuss what we're going to do, I raise a PR, but it's maybe not everyone is involved with the PR. So for for everyone here to follow what is happening with the issue and the sub tasks and if we have people can go and update it, I can track maybe track things better. So it might be a good idea to, to now for from the second phase, try the issues via here. But if there's, if there's any issue with it, if there's something we'd like to discuss about it, please. Yeah, if if if JIRA, I love that you've suggested using JIRA, that's great. And if you think it will help you in any way, you have my wholehearted support. That's I flinch, because Git plugin is the number three highest owner of Git is of open issues in JIRA. It's second only to Jenkins core and the Maven plugin and Blue Ocean. So so it's, it you're not you're not helping my warm fuzzy heart feeling that says, Oh, I'm improving the plugins improving. But you're doing it, you're proposing a really good way to track our work. So that that I no problem, let's use JIRA. Absolutely. Okay, okay, Mark. So I and with the so with the issue with the opt out switch I was talking about. So I implemented it and I raised a PR for it, Mark has seen it. But with the implementation, there is a one problem. And the problem is that it's not persisting for each build of one build, I configure it and I, and I, and I start the build, it works, the switches working as it should. But once the build is complete, I again go back to Jenkins configure page, it's the checkbox should be checked in. If it's checked in for the first time, but that's not happening. So I did not get a lot of time to actually look at what do you do you have any pointers for it, Mark? Do you do you? Oh, okay, is it something in the code? Do I have to add anything else? Yeah, I think, I think if you were to do a side by side comparison between the pull requests that I just merged from Bart Deverent, yes, your pull request, you'll see a very simple difference in terms of the API naming convention. And that API naming convention is all all the crucial thing here because it breaks the coupling between the user interface, and the getters and setters. And and it tragically, it's absolutely silent that the connection is broken. It just it doesn't show you Oh, I tried to set something in Java ignored me completely. Oh, that's I think it's the fault. Yes. Yes. You think something. That's it. So I think the mistake is that I was confused with using redundant fetch or the second fetch. Because if we are giving an option to the users, I feel that this we should not call it a redundant fetch, because we it is not redundant for them. So it should be called second fetch, but we were using redundant fetch for a long time. So I think I I redundant fetches. So there's a confusion there in the code. I like I'll change it. I look it up. Okay. Yeah, well, and and but your your attention to Hey, we don't rename things just casually is actually quite important. We haven't yet released the redundant fetch removal. So we can still freely rename things. Once we've released something a public symbol in Jenkins becomes tragically and unforgivably part of the public API, even if you didn't want it to be. So your naming mistakes, my naming sins from four years ago are still very much in the in the code. And they have to be otherwise we break compatibility. So so we this is a great time for us to choose a good name like allow a second fetch and get rid of bad names. Don't be shy. Once we release, we don't get that forgiveness anymore. We're stuck. I understand that. Okay. Okay, so I'm going to do that now. Okay, so after that, I was thinking to plan what we want to do for phase two. And and also with the planning, I think what I wanted to discuss was what we did right in the phase one, what we did wrong, according to you guys, and what we like to continue and what we'd like to drop. So something in that format. So let's start with what we I think I'm not sure what we like. Let's let's start with that. According to you guys, because I think your review is more important for me to move forward. Then I can give my review and that's important. Yeah, Mark. So I was delighted with your progress and with your engagement. Really thrilled and excited to watch the progress excited to see the engagement. Very positive. Love it. And that was done by code requests, pull requests by looking at code and by and that you were willing to do interactive testing at the places where interactive testing actually was more effective. I like that it's, it's uncommon for a student to realize that interactive testing is actually sometimes the most valuable thing you can do at certain points in a project. That's oh, but I want to write code. No, no, sometimes we test. Well done. Well, that's an important thing. I one of the important things I learned that just writing a fix is not important. Compatibility is a is a very essential. I would say thing to remember while you're writing anything for for a report for a plugin or for a utility which is being used by so many users. Well, it's a good it's a fair point that in different environments, the compatibility requirements are different. Right? If if you join an employer that's writing Linux kernel work, they care much, much more about compatibility than we even dream of. If you're doing brand new blue sky code, compatibility is not relevant. Go as fast as you can. Okay. Justin. Yeah, I mean, I would echo Mark. You're very enthusiastic. You seem to take take a task. We say take a bull by the horns. If you know the idea. So it's good to see that, you know, you take take stuff on you do some research on on stuff present some options, which is nice. It's good for us to hear. I think in any like software development project, it's good for if you're working on a task, you're showing the other people on your team the options. It's always helpful because they may come up with other things, but they may they also have a head start in thinking about the different options because you've you've given some of those. So that's nice. Did a great job on the presentation. Yeah, I'm trying sextant. Okay. Omkar, would you like to say? Yes, so yes, I jumped in pretty late for that thing. But yes, it is true. Yeah. Yep. So till the time like last four weeks, those have been amazing. Like your work, it's pretty pretty, like, more than pretty great. And the yesterday's presentation was amazing. And the best part of you that I felt was like, you're able to go with the approach. And if you find anything wrong, you're like, open enough to expose that fault in the approach. That's the best thing that I've found till now. Yep. Okay, and I look forward to get engaged more with you with the phase two. And yes, and it's definitely it's exciting. Yeah. Okay. So let's let's go for the issues that we the problems with you think you guys think that I should address. That's that's that's the most important, but I why I don't know why I orchestrated this thing like this. I actually want to know what were my mistakes. Then I was during phase one, which I should look into in the phase to some things like maybe the speed or the speed with which I'm taking tasks, or maybe the documentation part, the way I'm taking that any, any, in any sense, you guys feel so one of my worries was that if we were as mentors, redirecting you a little too comfortably that we were, Hey, let's go off plan a little bit, a little bit, because we think this other idea looks interesting and attractive. And and I wonder if as mentors, this is not not your fault, this is really a mentor choice where sometimes I am, it's very easy for me to get interested in the most recent shiny thing. And and go after the interesting recent shiny thing when when the plan we assembled was probably better than anything recent shiny. So so I think it's a point for us to be careful with each other to be sure. Hey, don't let recent things be received undue focus compared to to the big picture of where we were going. Okay. Okay, man, that's a great feedback. Okay. Just in home car. Anything? Yeah, I would agree. Like, I think I've probably given some suggestions that may have like taken you. I don't think you, I think you justifiably were like, took the suggestion and maybe I think we stayed on schedule. So I think we were good. I guess I don't went too far. Yeah, I think the only thing I can think of is probably also schedule related. And I'm not sure that this is necessarily something on you. But I guess we're have we have we done a check up on like where we are on schedule. And if we need to readjust any of the dates or anything like that or the projects, maybe that would be worthwhile doing periodically. Yes, I think that that's an important thing to do. It is it is and we haven't seen that I should I open the proposal where I actually propose the goals we had or the way we are going to do and then compare it with what we have done. So I generally keep on following that particular thing like I follow up the agendas for meeting and I also check on the proposal. So I think we are definitely on the track, but I'm not sure of the timeline, like what, what timeline exactly we need, what milestone we need to achieve with what time exactly, but we are definitely on the track, correct track here. So, yeah, I guess I'd say that's only really like, if someone is tracking it, if that was already you, like, that's already good. And I have it also say like, Yeah, but just we need to check if the time time stamps are currently like, we're not running too much behind the schedule, we need to check that. And it's a software project too. So I mean, software projects, you're not going to be 100% accurate with what you thought a month ago, or maybe even a week ago, sometimes with how long it actually takes. So that's just a reality. So sometimes you just need to readjust. So that's kind of where that cadence of maybe, are we in the right spot? Or do we need to readjust? It seems like we're moving pretty well. Okay, okay, yes. So, yes, ma'am. I like the idea of looking at the timeline, I tend to ignore timelines. So we may want to make a systematic thing in these maybe one one of the sessions in a week, where we remind ourselves the timeline was this, are we okay with deviating from the timeline or not? Because I've I've been totally oblivious to timeline, thinking instead about task and photo, you know, what we want what what I think we should get done. But timeline, you put effort into thinking about the timeline. And we would honor that effort, I think by looking at it and deciding, shall we accept this as a deviation from timeline?  So according to me, what my expectation for phase one was that I would to fix the redundant fetch fix because that was something for the for that I attempted to fix even before the GSOC, the community bonding phase started. So I was so what I thought was that I would write the benchmarks, I had one benchmark, I would write more benchmarks, and I would possibly try to discover more issues, just performance related issues, and side by side try to find a solution on how to implement those in the plugin. But I think where I've lagged is that I've spent too much time on benchmarks. And I think my, my goal was to find a difference. Even if there isn't, my goal was to find a difference. And I'm not sure if that's how much that's helpful. Maybe it's helpful to a point. But if you overdo it, then you maybe you'll, you know, I'll try to see results where I where they're not they're not existing. So that's one, one concern I have with myself. And I think I'm going to change that when I'm doing the benchmarking thing. And also, I think I need to maybe I need to put a stop at where I go with with the results I have. And parallely, try to focus on the fact that we need what's more important is that the existing results we have, we have a system to add them inside the plugin. And that's going to be that's going to take a lot of time because when I was planning the timeline, I was not aware of how much time it would take. I thought that it's going to coding a certain task would not take too much time. I was not aware how much time after the coding process would take that is the testing of it and then taking it to production. That whole process I was not aware of while I was writing the timeline. And with the git fetch issue, what I've seen is that it would take considerable time in this case in this plugin for this repository. So so so I think there has to be a fine balance between how much I research because I feel that this project is not 50% but it's somewhere around the research we're doing exploring and 50% it's using that to code things. So so it's really important that I balance both of them. I think I could not balance this time for this phase coding was less and research or finger figuring out ways to consolidate the results I have profiling and then looking into how the operation is working also. So I do explore the code I do try to understand as much code as I can. It's not like I'm not reading code. But I believe that I did not I should have find found a way to the heuristics. I was thinking that at least I would have a prototype by the end of phase one, which I could not because I think that I spend too much time on benchmarks. Because I feel even after spending too much time, what clear observations we have is with the benchmark results of git fetch is that J get the size of positive and the J get thing we have. And with LSD more it's it's it's not much of a difference. But I think that I, I've spent much more time to find more things. So if that's a good thing, I think to a limit it's good, but not at the cost of not providing a solution, which is actually what we want ultimately for this project. So I think that's one of the biggest concerns I have. And I would so with tracking what I want to do is that I think that would help me more to stay within the line and hold as much as I research for the benchmarks. So yes, that's I that's what I feel for the phase one. And yeah, I mean, I think some of the beginning of this is like some of what you said is the nature of you're teeing everything up your bootstrapping all of this stuff to gain advantages later too. So I yeah, it's probably a lot of nature of the beast kind of thing. And yeah, you don't know what you don't know. So yes, that's true. Maybe all of the experiences I've gained through this phase one, it'll be easy for me to in this phase two when I'm exploring benchmarks or I'm coding stuff. Yeah, I like I'm I'm very interested in and like the idea of that sizing heuristic being a good coding task and a good coding task to include in phase two. I think that that has real potential. It's real code. It's something you can do while we're making progress on other things. So yeah, I like that a lot. Balancing that which probably has very specific concrete things with exploration of are there any other operations besides fetch where J get is substantially slower or substantially faster than CLI get because right now we've we've you've benchmarked two or three and one of the benchmarks says yes, clear difference. The other one says no, not a clear difference. The question is that all right, which or should we continue writing more benchmarks or rather is put you focus fully on have you you choose to focus fully on the heuristics and using what we've learned from that one benchmark and I I don't I don't have a good answer on do both or do one. I think I'm open to either either process whichever you prefer. Ideally I'd like to do both because if we don't explore then then I'm not sure how much we like we would we could cover at the end of the project. So I would not like to stop the researching into the different areas of this plugin but but then again focus on the coding task as much. So the last question I have is so now I'm going to write ideally either I'm going to add the size estimator part of the code to the get sm telescope or I could create a new class that's I work on that more first. I have to give more time to that thought but I wanted to ask since I would have to design a class and what would be good design principles I should maybe read about or if you guys could give me some advice on how I should design such a class where I'm I have heuristics and I want to I'm not very sure of the thing I'm delivering but I have some kind of an estimate. So this is a very new type of I would say a functionality for me to get so I just like if there's some possible advice or maybe things you would like me to explore before I write this class because I think if I have some if I read some good principle and then I try to code them it'll be easier for us to then review it and the process will be faster. I think that's the right way to do it. So yeah. I wish I could say I'm a good designer Rishabh. I'm not. I'm hoping that Justin and Omkar are because my my my usual technique is do something very badly and iterate on it until it becomes somewhat less bad. That's what I was thinking about but I thought maybe if if there's something which is essential when we're trying to create a class like this or something like this. Get SCM telescope for me feels like a great pattern and a great place for you to explore it. I think that is exactly the concept and if you if you read the SCM API documentation as written by Stephen. He has a page called consumers for consumers of the SCM API. You can read more about his strategy and why he did get SCM telescope. What his concept was so that consumer documentation on SCM API is a really really good read and therefore you're reading from somebody who actually is a good designer as opposed to listening to me who is we know not a good designer. I'm I'm I'm pretty solid at maintenance programming and pretty solid at testing. I'm not really great at designing new code. Super good gem. Like I think what you hit on is is kind of what I was going to say too. I think different code bases kind of sometimes tend towards different practices and stuff like that too. Java's generally has good practices and there's like books you can read on on this and stuff like that. But I think I'd agree with Mark that take a look at what you have for this. Take a look at other classes that have been designed in here that might do something somewhat similar and you'll be able to potentially snip some of those things from there but also combine that with iteration because you're not going to I don't know. I think as many times as I've tried to design classes like I usually find something or another thing when I'm testing it or writing unit tests or something like that that I might change some stuff up anyway. So okay yeah that sounds okay. I'll start with exploring the data SCM class. I'll be focusing on it first. The SCM telescope and reading the consumer. Then maybe come up with a prototype and then we can discuss the design. Maybe it's not the right time to ask the question. I wish it were. I wish I had the answer but the answer I have anything I give I would be making it up and I'm sure what I would be making up is much much less quality than what Steven has already described. Okay but I think it's great that we already have a class which is doing similar. It's designed for the similar purpose so I think I should look at that first and then yeah common. Okay so okay just one last thing before ending the meeting. I was always planning to document the process we've gone through for the benchmarking. I never did it. I could not do it but now what I was thinking was to create a document which basically acts as a repository of the results we have and as a public I would say document which would have the results and the observations or the process we've gone through for each of the operations because I would say that even if we implement some of the features using those observations it's important for us to see where those observations came from so that if there's an issue in future we actually know how we got to that point. So yeah that's also one big I would consider it's a very essential task. Contributing.adoc is your destination. Yes. Yes Mark. Great. Okay thank you guys thank you for giving your time. Just just just a second so are we planning to include that OS level testing like environmental testing that Mark mentioned yesterday in phase two? Yes I would say benchmarking with benchmarking as I've already mentioned in the presentation we would widen the scope. Okay I haven't discussed the benchmarking I think we can discuss it in the next meeting as well. With benchmarking I want to focus on the repository structure that is the commit history number of branches and other parameters in the size keeping the size constant if that's possible. Then the second thing would be different platforms. I haven't focus enough on how different the operations are working on windows versus linux. I would like to focus on that and then once I have observations from that experiment I would move on to the suggestion given by Mark to run it on different platforms on the infrastructure. Can you give me the .io? So yes yes Mark. Aren't we going to get that we're already running the the jmh benchmarks that you've created on different platforms on ci.jankens.io now? We can't see the results nearly as conveniently as what you've what you've what you've shown in your environment. We don't have the jmh plug-in we don't have that benefit but but they are running and so I yeah I think I think it's not it we've already made progress on it and and yes we can make more progress. So the the progress I would have to make is just to analyze them. I did not take both of those side by side and analyze them. That's something I missed. Yes so I would do that but Mark with that okay I'll I'll discuss in the gated channel. I think the time is over. It's it's a small thing. I'll discuss it in the gated channel. Thank you guys. Thank you so much. All right thanks everybody.