It's too early for this. Stop, stop, stop, stop. I'm so jealous of you. It's gonna be a good day. Dolly sets up. Hi guys, welcome back to my channel. If you guys are new here, my name is Kinsey. I'm a 24 year old lifestyle vlogger living in Dallas, Texas. I decided after reading the Miracle Morning Routine book that I wanted to try the Miracle Morning Routine for a week, I recorded three of my mornings. If you guys aren't familiar, it's a book and they go by the acronym SABERS. So S is silence, A is affirmation, V is visualization, E is exercise, R is reading, S is scribe. So writing. I used to wake up at five in college all the time and like this, for some reason, I can do six, but five is just a lot for me. Be sure to subscribe if you guys haven't already. Without further ado, let's get into the video. Oh wow. Time to get up. I think I'm gonna do part of this stuff from bed.  I'm gonna try all of the things, besides obviously exercise from my bed this morning and see how I feel with no coffee.  Okay, if you guys post it. This is actually my first time really giving head space. I'm going to try to get like a beginner's one. You might somehow get rid of all the negative thoughts Okay, I already feel calmer. I did a 10 minute medication, a 10 minute meditation. Next is A for affirmation. So you are not making my morning peaceful yoga. I never do affirmations and I don't really wanna just sit there and say them like I know that's probably what you're supposed to do. I'm more of a journaler. So I'm gonna write my affirmations. I also like don't have affirmations. So I'm going to make my own. I know people who like have their own. So I'm working on that this week. I feel like I'm just not so sweet doing this all on my bed but we're trying different things this week. The next thing is visualization. And yes, I have like a vision board but it's on my like Canva. So I don't like that I'm getting on my phone. And do I just sit there and stare at it? You know, this is the one that I really don't really get, but I get the importance of it. I totally see it. So that's what we're doing. I just know that I'm visualizing of things. Okay, I'm visualizing. So since I am exercising last, I have reading and scribing left, which is just writing. So reading and writing in the morning, I'm gonna be reading a nonfiction book. I'm actually reading a Scouts book, The Emotional Entrepreneur. I'm trying to read this very slowly so I can really get as much out of it as possible. This is what I'm reading this morning and then I'm gonna write. Guys, I just wanna say I feel amazing. So now I'm gonna go take the dogs on a walk and then do 12, 30, 30 and then we're done. The routine definitely seems to be a little bit overwhelming. Like there's a lot to do, but it doesn't feel that way literally at all. I'm gonna try it this week in different places in my house and combining different things. Like I wanna take a walking meditation as I walk the dogs. Like we'll see what happens here. This, do you wanna go to walk? Do you wanna go to walk? Are you guys ready? Do you wanna go to the I? I just checked my phone. I went on socials for like two minutes. Haven't been on them all morning and I wish I wouldn't have even done that. It was a full hour or something before I even checked my phone, which I wanna get to the point where I check it after I even work out or if I want to look on the trouble and I don't think I'm that boy. Here we are, the dogs are staring at me so I'm gonna go. Bye guys. Bye bye. I'll see you later. We're going to work out. All right, and we're done. All right guys, I officially finished my morning routine. I liked meditating a lot more than I thought I would. I would like to try a walking meditation cause people talk about that a lot. Maybe wait even longer to get on my phone. Oh and not do it for my bed. I wanna see if I like doing it from downstairs more.  So anyways, I'll see you guys in the morning. Bye. I guess that must be nice. I'm so jealous of you. I don't like waking up this early. All right, so here's my idea for today. I wanted to try combining the E with the S. So silence and exercise. I wanna do a walking meditation with the dogs. For some reason I've been in this like midday workout thing. Like this week I've not really wanted to do super early like crazy workouts. So I'm gonna like work out, work out later but I do wanna get in movement. So I'll do like a walk but I wanna try a walking meditation cause I've been seeing those everywhere but we've talked about them. I will say I did like meditating the other day. I just had socks with my hair last night. Downstairs we go people. It's very dark here. It's gonna be a walking meditation, okay? Coco, you were really ruining my zen. Oh my God, I can't handle that. I'm not getting on social media guys. Okay, I'm back from my walk. Thoughts on a walking meditation. So like probably not something you would do with dogs. If I was gonna do it by myself when I eat coffee in the morning, I'm into it. And also I think I'd rather just listen to a podcast and do the meditation alone but I'd definitely see the benefits of meditating. Time for some coffee and then we'll keep going with this routine. Clean Dolly. It's gonna be a good day. Dolly sets up.  The pods are stuck. Too early for this. Do you guys ever have weeks where it's like really used to wake up early? And then weeks where it's just not? Stop, stop, stop. I don't even know what to do. Whoa. Why is this happening to me? Here I am. I am gonna be including this in the vlog because I did get requests. I posted this on my Instagram stories that I got the nut pods and pumpkin spice. Um. Look at the spoon that I have right now. Like. Wow. So I'm going to visualize, do affirmations, read and write I think. Are those, yeah those are really the four. So that's what I'm doing this morning. I actually think that I have an even better setup for tomorrow that you guys will see and I think that's gonna be the one that I stick to. By the way, I did get a new nonfiction book because I do wanna read a nonfiction books in the morning. But I'm gonna start with my visualization. So affirmations, comment below how you guys do your affirmations. I write them as a rest your day. One chapter of this book which I'm actually really excited about. Now we are going to journal and then I am off with my day. Vince, I don't wanna hear it, dude. No, I'm so sorry. Oh no, now you can't. Oh no, no, no, you already did it.  Comment below if you were watching when I got Vince. Day two of my morning routine that I'm trying out, a little five a.m. morning routine. I liked this one, but I think I prefer yesterday's over this one. I really do notice, I know I've only done this for two days, but I really do notice quite a difference in me mentally, emotionally, and even just the motivation and discipline that I have throughout the rest of the day. And guys, you know what we always say here? What do we say? We say, I remember, confidence is built by making promises to yourself and keeping them. I learned that from Adnanilah and I think it is so true. Where I stroll into that. This is the best ice roller ever, practices. And I do visualization in this one. I've been doing this more, I just only filmed these three days. So I do affirmations, visualization, reading and writing. And then after that, I'm gonna work out. My journal practices. Last on the list is exercise. So I'm gonna take the dogs on a really long walk and then I'm gonna do 12, 3, 30. Life hack, if you're dreading your workout and you don't really know why because I actually like core power, just switch it up. Finishing my coffee, we're going on a little morning walk. Also, I just wanna say, Scout's book, The Emotional Entrepreneur is so good. We're done with the workout. I just walked for almost an hour and then we did 12, 3, 30. We're out, I'm gonna get ready. Good morning everyone. Cheers. Okay. So I did the morning routine. I tried it out and I will say a few things. One, the 5 a.m. hour doesn't work for me anymore. It worked in college and right now for some reason it just doesn't work for me. I just get really, really tired later on in the day and yes, I get a lot of stuff done in the morning but I just kind of lose my like midday and night which I feel like as a 24 year old, it's kind of vital. Like I don't wanna lose my nights and feel like I just feel really anxious that I feel like I need to go to bed at 8 p.m. to wake up super early. I definitely can do 6, I can do 6.30 just on average and that makes me feel good. I already love going to like a 6 a.m. or a 7 a.m. workout class and then leaving and feeling on top of the world. Third day that you guys saw was definitely like my preferred routine and I definitely did like the challenge. I liked trying something new. I think that the things I would change, one is I'd like a bit 6. Two is I would keep changing my workouts because for some reason I just haven't been into like what I've been doing lately so I would keep changing that and honestly probably either start working out at home again or actually join like equinox or something. I like the journaling exercises. I liked meditating. I'm still not like sold on it. Like I know that as time goes on I'll get more into it but I definitely notice a difference. Yeah, I liked it but I just, I can't do the 5 a.m. because then I'm so tired later and I have no life and I really value my life as a 24 year old so. I definitely did like it though because it makes me feel like I can run for president and that I'm like really productive and so love that about it. Anyways, I hope you guys enjoyed today's video. I'll have the book linked down below in case you guys wanna check it out. I definitely have loved the routine. Maybe if I did it more I wouldn't feel like I needed to go to bed at 5 p.m. Be sure to subscribe because you're here. Love you guys so much and I'll talk to you soon. Bye. Have my most energy in the mornings which is when we do the toast and that's when I'm required to have energy. By the time I get home it's like work from bed the rest of the day.


Are you a man or woman in sobriety and you don't want anybody to know about it? You might feel embarrassed or ashamed and you want to keep it on the down low. Well, I actually used to be that way too. So in this video, I'm going to show a little bit about my story about how I had some closet sobriety and I want to give you some advice and some tips about how maybe it can help you be a little bit more open about it and maybe we can help more people. So stay tuned. What is up everybody? This is Chris from the Rewired Soul where we talk about the problem but focus on the solution and yes, in this video, we're going to be talking about sobriety. So my clean date was June 23rd, 2012. So I have a little over five and a half years clean and I want to talk about how I was in the closet about my sobriety for a long time and what a hard moment I had that made me kind of snap out of it. So please watch this video in its entirety and if you know somebody out there who is maybe not too vocal about their sobriety or maybe is struggling with the same issue, like please go ahead and share this video with them or just share it on social media. Okay. So anyways, man, one of the biggest reasons why it was difficult for me to even admit that I was a drug addict or alcoholic was because I thought drug addicts and alcoholics were scum. Okay. I thought these were people who are stealing from their family, hurting the ones they love and it's true. I did all those things. Like I thought these people were complete degenerates. Okay. And my mom, she was an alcoholic the first 20 years of my life and I never ever ever wanted to be associated with anything on that level. So like that was one of the reasons why it was so difficult for me to admit that I actually had a problem, you know, but it was also one of the reasons why it was hard for me to just be open and honest about this thing because I sat back and I was thinking like, man, if I have so many harsh judgments about addicts and alcoholics, what is the rest of the world thing? You know what I mean? So like when I first got clean, like I didn't tell anybody. I told nobody. So I got sober in California. I'm from Las Vegas. So I went to California and most of my friends thought that I just moved to California for no, no big reason. You know what I mean? The only people who knew like why I was there and about my sobriety was like my parents and some of my close friends and some family members. That was it to everybody else. They just did not know. So I stayed out there and like, it was, it was worrisome.  I was worried about how I was going to date. Like, how do I tell like somebody I'm trying to date like that I'm sober now? You know what I mean? And by the way, part of that is this cause of sobriety thing. Like we're afraid to tell people because of the way that they're going to judge us, right? But anyways, so when I was working on myself and working on my recovery, like one of the first things that I learned was like, you know, this thing is like an allergy, okay? And I've done some other videos about the symptoms of alcoholism or addiction. And if I look at this thing like an allergy, I have an abnormal reaction to alcohol or drugs. Once I start, I can't stop. Okay, I struggle with a mental obsession and a physical craving.   But with the way that alcohol or drugs affect us, we do some really terrible things because of it. And that's why it's looked at so much differently, right? But I get that. I knew that if my employers found out my future employers, because I was unemployed at the beginning, my future employees, if they found out, they might be, you know, looking at me differently, they might be worried that I'm going to relapse or I'm going to steal from them or, you know, what if they had these bad images of addicts and alcoholics in their head? You know what I'm saying? So anyways, I spent my first 15 months in California and I was in a big recovery bubble. Like everybody I knew out there was sober. So like, Hey, you're sober. I'm sober. Cool. But then I moved back to Las Vegas where I got back into the working world, right? I didn't tell my employers, it was none of their business, dah, dah, dah, dah, dah, you know, all these things. And I just kept myself about my sobriety. And what happened was, on June 23, 2014, I went to a meeting and I got a coin. And I was like, walking back home, after this meeting and getting my two year coin, I'm looking down at it. I'm just like, man, like, I never thought in a million years, I never thought in a million years, that I can get two years sober. And then I sat there and I thought about it. I'm like, how many other people out there were as hopeless as I used to be? They're currently this hopeless. And they think that it's impossible to get clean and stay clean for this long. I said, well, I'm, I'm proof of this, but I'm not telling anybody about it. And I'm like, that's crazy. I'm like, that is really, really selfish of me. So first thing I did when I got home, I hopped on the Facebook, I took a picture of my two year coin. And all I did was make a very simple post and I just put two years sober. And man, over the next week, two weeks, I just started getting flooded with messages like people who I haven't talked to in years are like, Hey, man, I think I might have a problem with drinking. Can you maybe help me out? Like, what did you do? How does this work? Or I'd have people who said like, Hey, I think my mom, my dad, my sister, my brother, my friend, I think they might have a problem with alcohol or drugs. What can I do to help them? I started seeing just people immediately coming to me and turning me. I'm like, Oh my God, like addiction is affecting so many people and so many people's families. Like I can't believe I waited for two years to do this. You know what I'm saying? So I look back on it and I regret how long I stayed in the closet about my sobriety because I could have helped a lot more people. But one of the reasons I make this channel is to be more open about it. Like I can't give people hope if nobody knows about what I've been through and how I've stayed clean. Now I do want to make clear because I have this conversation with my clients all the time at the rehab I work at. Like I'm not telling you to do anything. I'm just giving you my perspective. Like I don't want you to watch this video and go scream on the rooftops or go to your like local radio station and say, Hey, everybody, I'm sober. Like you don't kind of do that, you know. Unfortunately, there is still somewhat of a stigma. Like why am I like sugarcoating this? There is a stigma out there, but I've had people who are like afraid that their boss is going to know that they're in recovery. And like the way I look at it now, like honesty, like and the way I look at even relationships, like why would you want to work there? Like why would you want to work there with people who are judging people in recovery? Like when I got sober, I realized that addiction affects everybody.  Like we are just normal everyday people. And like the fact that people are afraid to talk about this, it really breaks my heart. And it's one of the reasons I make these videos to spread awareness and decrease the stigma. Like employers and stuff who discriminate against addicts or alcoholics. Like that is ridiculous. That is ridiculous as well as an HR nightmare, by the way. But anyways, I have personally only heard maybe once or twice in over five and a half years, only once or twice out of hundreds and hundreds of stories, once or twice that a person let their employer know that they were in recovery and it turned out bad. So I'll end with this last little quick story. So I was working for a content company. We wrote content for websites and stuff like that. We ended up getting a rehab client and they wanted writers who knew about recovery. They were either sober or they have family members or they were at least educated, right? And I hadn't told my employer that I'm somebody in recovery. So anyways, we have this account. It's a huge account and the first batch of articles we send them, they are livid. They're like these people don't know anything. So I'm sitting there and this is before I like came out like on social media stuff like that. Or maybe it was right after, I don't know, the drugs that mess with your your memory, you know what I'm saying? Anyways, so what I did was I pulled my bosses to the side and I was so nervous because I knew that I could help out with this account because I'm a writer too. That's why I worked there. And I knew I can help them out with this account, but I was worried about what they would think. So I asked to meet with two of my supervisors and we went into the office and they're like worried that I'm gonna like put in my notice and like I'm worried that they're gonna fire me after I tell them. And I was so nervous, like anxiety, like level one million. And I sat him down. I said, listen, I know we're having problems with this rehab account and they want people who know about sobriety and recovery and drugs and alcohol. I said, just so you guys know, I am like two years sober. So I can help out with this account. And my boss just looks at me and she says, I knew it. And I'm like, what? And like, yeah, it's almost like our addiction when we thought like new nobody knew how drunk or how we were. That's what it was for me. I thought nobody knew like I had been with this company for a while. And and like, you know, there was like holiday stuff or like people went out for drinks after work and I always like have these excuses like now man, I can't go or I would go and I'd say no, it's okay. You know, I don't really drink or I'm not having anything. You know what I mean? So for some people, the wheels were turning so she already knew she already knew so something even more beautiful happened later.  And she was wondering if I could talk to her friend and I'm like, yeah, of course, absolutely. And I was able to talk to her friend and say, Hey, like, listen, my mom was in the same position that you were when I was in my active addiction.   You see what I'm saying. So like, in my personal experience, I've never seen anything but good come from me talking about my my addiction, my struggles, my recovery, all I've seen is the good. So, you know, I really hope this inspires you.  I just want to kind of get your wheels turning and have you kind of think about like what this might be able to do to help others. And you know, like what I realized was like, my motives were extremely selfish by just not telling people. I was so worried about me, I wasn't concerned about how it could help others. It's almost like in my Black Panther video I've made, which I'll link up in the info card above. But yeah, anyways, like I said, if you know somebody who's in recovery or somebody who's in the closet about their sobriety, like just go ahead and like share this video with them, share it on your social media. There might be a lot of people out there in sobriety that you don't even know about because they're in the closet about their sobriety. So please, please, please share this video. Let's share a message of hope decrease the stigma, erase awareness. Okay. But anyways, if you liked this video, give it a thumbs up.  So make sure you click the subscribe button. You can also click or tap on one of those thumbnails right over there. So again, thanks for watching. Go spread awareness, let people know that we got nothing to be ashamed of. And I'll see you next time.


Well, as they say, usually the Japanese do it better. Ooh, that's a hot mug, guys! Hey guys, this is my review for Godzilla minus one. Oh, there's been a lot of talk about it, so I went and sought myself. First off, for those who have been wondering what the minus one comes from, I have had some discussion with other friends who have seen the movie, and the idea is very central into the plot of the film. Minus one, this drives from Japan after they drop the bombs on Hiroshima and Nagasaki after they were defeated, so they're at zero. They are at the pit of despair and loss.  They are even in more in the hole than they were before. And that idea of coming together in the utmost of despair is the central theme throughout the movie. And this film does what we've been wanting from a lot of the monster-verse movies, is a character that you care about. Now, since Brian Cranston got, for some reason, killed off in Godzilla, have we cared about a human character in any of the monster-verse movies of the last while? You could say that there are some characters you might care about in Shin Godzilla, but really that film is more about the idea of the society and government coming together to take on what would be the most realistic version of an event like that. Minus one is central about people who have dealt with grief, who have dealt with loss, who have dealt with dishonor and guilt and how they combat that. The film's main character is this kamikaze pilot who was too scared to do what he was supposed to do. A chickened out and he comes to this island where then Godzilla first attacks and there's a moment where he can he thinks he can do something and again he is too scared to do it. And then after the war ends he comes home and he finds everything in ruins and he just can't get rid of that guilt. He is trying to find means to deal with it, like helping out this girl and this little baby that she has taken on herself to take care of because the parents died because a lot of people died after the bombs dropped.  And then the film starts to central upon the idea of how they take care of Godzilla. Godzilla is the villain of this movie. The human character is not just the main character, but the girl, the baby, the friends that the pilot meets along the way while doing his boat job. You care about all of them. You have a vested interest in all of them. You have a vested amount of care for these characters. And that's rare to say because usually that has not happened in these movies and you're interested in the stripe.   And I keep saying this, but that's again what the movie is about. It is about Japan learning to change their ways whereas the war it was about honor and basically doing whatever including dying for it for the honor of the country. And now they are turning it around. This isn't about honor, this is about survival and they want to try and do what they need to do but still live to see it, to experience what they have left to be able to rebuild because you can't do them when you're dead. And that's the basis of the movie. I honestly had a few moments where I was like, damn, this is hitting me way more than I thought it would. As for Godzilla, he's not in this movie that much. He's almost, I would say about the same amount of time that he was in the 2014 American Godzilla movie. It just worked better because again, he is the antagonist and you are far more focused on the villains and when Godzilla does appear, his scenes are much more impactful. Now there is one thing I do want to say. There have been a lot of people who have been talking about how this movie is like just showing how terrible CG use in Hollywood is. There is some argument for that. This film was supposedly made off of 15 million but apparently even then the director says that he wishes he had that much money but that's kind of a rumor from what I've gathered. So don't call me on it but regardless, it's still far less than any of the Marvel movies which usually vary around $200 million. But there are a few factors. One, there's as far as I know, no big name Japanese actor in this movie. Two, Godzilla is not in that much. So there is not a lot of CG in it. And three, when he does appear, the CG is good in some spots. It's a bit and others like there are some additional elements that look like the straight out of a straight DVD movie. So that's what you get when you have a budget this low in terms of CG work. But there are some shots, particularly when Godzilla is on the horizon of the ocean and say he's coming after a boat or something. His blending with the water is really good. When it's above top down looking down, it's much more noticeable. And there are some bits where he kind of just moves like, do I feel that the budget for current day American Hollywood movies is stupidly high? Absolutely. Especially when supposedly She-Hulk, an episode of She-Hulk was worth this movie. Yeah, there's some weird budget use going around. It's not the be all end all. The effects aren't that astounding. They're good for what it's worth. But to say that they're beating Hollywood movies, no. There still is this level, but that is a discussion in itself about the disuse and the mistreatment of the effects studios. And there are a lot of movies both in the recent years and to come that you could even make that kind of argument for. But I'm getting way off topic. Godzilla minus one is a fun, good Godzilla movie that you care about the characters.  It hits you. Godzilla is a great antagonist in this movie into driving force for the main characters and the secondary characters to come together. After such a tumultuous event, such as Nagasaki and Hiroshima. So in the end, I'm going to give Godzilla minus one a five out of seven. It's definitely my honorable mentions for the year. I don't know if I would watch it again, but I still got to commend it. It's still really good. If you have a chance to go and see in theaters, I absolutely would recommend it. Especially when his atomic breath is used as a little different than in other movies. And I really like how they did it in this movie. Anyways guys, those are my thoughts. Love to know what you guys had to say. What do you think? Is this your favorite new Godzilla movie? Do you have a favorite one? What do you think between this one and Shin Godzilla? For those of you who are kind of wondering about how the movie ends is like, Oh, is there going to be a sequel? Shin Godzilla did the same thing this one did and Shin never got a sequel. So I don't really think this one's ever going to get a sequel either. They just like to do that kind of tease idea. So anyways, let me know. Let's see what you guys have to say. Thank you guys for watching the video. Hope you liked it. If you did, leave a like. And if you're interested in more content like this, please subscribe. Until then, see you guys next time.


Naval Mobile Construction Battalion 14 welcome family members of those killed in action to a ceremony aboard Naval Station Jacksonville to honor fallen shipmates. It's an annual memorial service that commemorate the lives of the ones that gave their life in 2004 in the Iraqi detachment and that were killed and wounded during that time. The NMCB 14 family honor their fallen comrades with a wreath laying during the ceremony as they pledged to never forget the service and sacrifice of those killed in action. Their loved ones certainly served in a brave capacity that most don't do and they step forward they leaned into the danger zone and forever us the Navy the CBs and this country will remember them and their families. From Navy Public Affairs support Element Southeast, I'm Perry Officer Marcus Stanley.


G'day all again and welcome back to the Facebook page. This week I want to talk to you what I'm referring to as the Brigade capability model and essentially again we're targeting level 5 and 4 brigades and I'll give you an example. So some of our brigades at this level have upwards of 100, 120, 140 members. Each one of those members wanting to NAC year, wanting access to training, wanting access to welfare support and so on and so forth. When we actually have a look at some of those brigades we've identified that somewhere between 20 and 30 actually turn out on a regular basis. What we want to do is reach an agreement with our level 4 and 5 brigades of exactly how many members that you need to respond. We think the number will vary somewhere between 30 and 50 odd numbers and then we'll come up with a commitment that we will agree with each one of those brigades to give you the PPC, the training, the support you need to deliver for those 30 to 50 odd members. Now it still means you can have 100, 120 members and some of those will be doing other things if you like and those that have been around a while will understand the old active and reserve model. Very similar. There will be a cohort of people within each of these brigades that will focus just on training and so we can then say well how many truck drivers do you need, how many water squatters, how many chainsaw operators, how many pump operators and then so how many of you got work at the balance if you're still with me, then I can go to DCO training and say look we're short of so many chainsaw operators, we're short of so many truck drivers, can you run that many truck driver courses for us or our infrastructure people, this is how many sets of structural gear, this is how many sets of wildfire gear or welfare people and so on and so forth. I think you get the point. What is the capability of each of our level 4 and 5 brigades that you need to run fires, to go and run operations and let's really focus on building that quality workforce in those brigades and we come to some agreement about what that figure is. Again, we've got in the brigade classification a whole heap of other roles that other people can play and as positions come up they can then replace them. We're piloting that at the moment, we're piloting that in the west region and we're looking to expand that pilot right across the state later in 2018. Watch out for that one. It's a new initiative within the organisation and a step I think we have to take.


The weight of the world and trans-Turman culture should not fall on black women's shoulders. And here in the United States, it's too often the case. We saw it with Roy Moore in Alabama when black women rallied to make sure that he was not elected. And let's not forget that 94% of black women voted against Donald Trump. While these are recent examples of when black women have showed up, the suffragette movement in the 1800s originally started out as a movement led by white women. But people like Sojourner Truth, a former slave, she understood that if white women were getting free, black women needed to be free as well. Another important person to note is Ida B. Wells, a militant journalist.  This legacy of black women saving the day continued through the civil rights movement and the LGBTQ movements in the 60s. The LGBTQ movement could not exist without Marsha P. Johnson, one of my personal favorite freedom fighters and revolutionaries who fought to ensure that we held the intersections of her womaness, her blackness, and her transness. One of the architects of Stonewall and the reason why we have pride in the first place, she understood that we couldn't leave behind race or gender or sexuality in the conversation when it came to who could be free in this country and who couldn't. The tradition of black women saving this country from itself can even be tracked to right now in this decade. Black Lives Matter, Patrice Cullors, Alicia Garza, and Opal Tamedi have taken the reign of formerly single mayoral leadership movements because of movements like Black Lives Matter. We're seeing a new kind of leadership, one that centralizes many voices instead of just one. A popular movement that is happening is threatening to erase black women from its conception.  Thanks to social media, we reminded that over a decade ago, Tarana Burke started the conversation and while it was amplified by many people right now, we fought to ensure that black women were not erased from the dialogue. It's time for us to come out of the closet as intersectional feminists, as abolitionists, as freedom fighters, and as revolutionaries. It's time for us all to come out of our fear and come into our power. We need to challenge the stereotypes and stories that aren't authentically representative of black women and girls. Too often, black women and girls are not in the writer's room and stories that are being told about us rely on cinematic servitude or enslavement. We can invest in organizations led by black women. Org's like the Highlander Center, Color of Change, Southerners on New Ground, and BYP100 are great places to start. We need to remember that the revolution starts first at home and in ourselves. It's time for us all to start having conversations that are courageous about race and gender politics in this country with our friends, our family members, and our co-workers.


Welcome, I welcome you all to this lecture in the course Samasa in Paninian Grammar 2. As is our practice, we begin our lecture with the recitation of the Mangala Charana. Vishvesham Satchitanandam Vandeham Yo Khilan Jagat Charikarthi Bari Bharati Sanjariharthi Leela Ya Vishvesham Satchitanandam Vandeham Yo Khilan Jagat Charikarthi Bari Bharati Sanjariharthi Leela Ya In this course, we are focusing on three types of samasas, avyayibhava, bahuvrihi and dvandva. We first understand the overall theory of compounding that is generally applicable to all types of samasas in which we studied the samartha theory. This samartha theory is stated explicitly by Panini in his own grammar but which is delineated by the commentators on this particular grammar. Notable amongst them is the text called Vyakarana Mahabhasya composed by Patanjali in 2nd century BCE. An important chapter in this Vyakarana Mahabhasya called Samartharnika explains the samartha theory in detail. In a nutshell, Patanjali's arguments can be summed up by saying that Patanjali offers four explanations of the word samartha. Samprekshitartha, sambaddhartha, sangatartha and samsrushthartha. Amongst these four, samprekshitartha and sambaddhartha explain what is known as interrelation of padhas in the sentence. Also described by Patanjali using the technical term vyapeksha. So vyapeksha is explained by the two explanations namely sambaddhartha and samprekshitartha. And then we have these two interconnected elements merging together to form one unit as the output which is ekarthibhava as described by Patanjali. And the explanation of the word samartha in the view of ekarthibhava is sangatartha or samsrushthartha. This was the base of the theory of compounding. We also said that sentence is the input for the process of compounding. The semantic conditioning in the sentence namely the interrelated padhas which are part of the sentence is the input for the process of compounding. And the output of the process of compounding is a nominal root also called apratipadika. We then also studied the concepts of nitya samasa and anitya samasa. In this process we studied the concept of vigraha which is of two types, laukika vigraha and a laukika vigraha. Laukika vigraha refers to the dissolution of the compounds using the words which are used in the usage by the speakers of the language. A laukika vigraha refers to the same dissolution transformed into technical grammatical terminology. We also stated that the beginning of the process of compounding is this particular a laukika vigraha. And then several operations take place. We have already studied some of them. In the previous lecture we studied the purva pada karyas, various purva pada karyas. And before that we have studied the operations like subluk and also the samasanta pratyayya and before that we studied the purva pada nerdharana. Before that we studied the operations of naming the process as samasa and also the semantic conditioning. Let us study some more processes involved in the derivation of the samasa. Specifically the three types of samasas that are the focus of this particular course namely avyayibhava, bahuvrihi and dvandva. There are three operations that we shall study in this particular lecture. There are two varanakaryas. The first one is the sandhi and the second one is the uttara pada rasva, the shortening in the uttara pada. And the third important operation is related with the gender of the compound or the samasa. Let us study these three operations one by one. Let us take up varanakarya or sandhi for our study. Varanakarya or the phonological operations are the operations that are based on individual sounds. However, the environment is that of compounding and this varanakarya is also known as sandhi. The place to do this sandhi is generally towards the end of the derivation process and the outputs of these operations generally do not become inputs to any other further operations. I repeat these operations of sandhi are done towards the end of the derivation process and the outputs of these operations generally do not become inputs to any other further operations. In the samasa samhita is obligatory and samhita is defined in the paninyan grammar as parasannikarsah. The extreme proximity of two sounds is what is samhita. Since samasa is the process of merging two units together to form one unit, both the units are uttered in close proximity, extreme proximity. So samhita is obligatory in a samasa. In the sentence samhita is dependent on the desire of the speaker as it is said in the traditional sources. What it means is that in the sentence two others which are although semantically related but they are independent and separate in nature. So they could be uttered in samhita mode with close proximity or they could be uttered without the samhita mode. It depends on how the speaker wants to speak, what is the desire of the speaker at that point in time. But in samasa samhita is obligatory. So the sandhi which is based on samhita is also obligatory in the samasa. This is a by default position with obviously a few exceptions noted down in the paninyan grammar. And such a sutra mentions optionality in the sutra. We have a very famous verse in the paninyan grammatical tradition which reads like the following. samhita ekpade nitya nitya dhatupasargayoha nitya samasa vaaketu sa vipaksham apeksate What this means is that samhita ekpade nitya ekpade samhita nitya dhatupasargayoha samhita nitya samasa samhita nitya vaaketu sa samhita vipaksham apeksate What it means is samhita is obligatory within one padha. Samhita is obligatory in between the verbal root and the proverb and samhita is also obligatory within a compound. In the sentence however it expects the desire of the speaker. This is the literal translation of this particular verse. In this verse certain conditions are stated where samhita is obligatory. Amongst them samasa is one such condition and therefore we always do samhita and the result of the samhita is the sandhi which is always done in a samasa. But as we said this is done towards the very end of the entire process and once this is done generally no other sutra applies. So the sandhi does not become the input for the other sutras to apply. Now here is an example of a bahuvrihi samasa. The meaning to be conveyed is one who has immeasurable luster. This is the laukika vigraha and the laukika vigraha would be amita plus su plus abha plus su. Remember that amita as well as abha both these words are infeminine with the suffix a added in both to the words amita which is the root word amita and abha and so amita plus a is amita, abha plus a is abha. Now we have amita plus su and abha plus su and then a very important process of subluc takes place and so we have amita plus zero plus abha plus zero and so then the pummat bhava operation on the purvapada takes place after the sutra 6334 applies namely sriya pummat vashitapumska danoong samanadhi karane sriyam apurani priyadishu. This applies and then it substitutes the root form of amita in place of it that root form is amita. So we have amita plus zero plus abha plus zero and then there is also the shortening of the uttrapada and that reduces abha to abha. So we have amita plus zero plus abha plus zero and now at the final stage we have amita plus abha where a coming at the end of amita and a coming at the beginning of abha they both come in close proximity namely samhita and then in this samhita the sutra 61101 namely aakasavarane dirkhaha applies and in place of both these vowels substitutes the long vowel and so we have the finally derived compound form amita abha. A and a are substituted by their long vowel. This is the resultant form of the sandhi. This is how sandhi operations happen in the samasa. Sandhi is obligatory. It is not possible in the samasa to say amita abha without doing the sandhi. This is not possible. In the samasa one will have to do the sandhi and one will have to say amita abha. This is an extremely important feature of samasa. Let us take another example. The meaning is the direction between east and north. So we have purvasyaha uttarasyaascha deshor yad antaralam. So the sutra ding naman yantara le prescribes this particular samasa which is a bahuvrihi samasa. And so we have purva plus gnas plus uttara plus gnas as the aalav ke gav vigraha vaakya and now here 2471 supodhatup pratipadika yoho applies and so both the sups get deleted and so now we have purva plus zero plus uttara plus zero. Now we have purva plus uttara. Now in this samasa the two constituents are such that the purva padha is ending in a and the uttara padha begins with u. Now both these words are uttered in samhita mode that means they are in close proximity. In this condition the sandhi has to happen. So 6187 applies the gudan sandhi happens and we have purva, o and tara. And finally we get purva uttara as the resultant compound output. Since this is a samasa we cannot have purva and uttara as the finally derived output. It has to be one where the varnakarya in the form of sandhi has already taken place. Let us take one more example and this is the example of the avyai bhava samasa. So when the meaning is towards fire we have agnim abhi as the laukika vigraha vaakya. And so the a laukika vigraha would be abhi plus su plus agni plus am. Abhi plus su plus agni plus am. Now here we have the sutra laksanena abhiprati abhimukhe applying and therefore this samasa takes place. And now abhi occupies the first position in the samasa. After that supodhatup pratipadika yoho 2471 applies and both the sups namely su and am they get deleted. So we have abhi plus zero plus agni plus zero. And now when we join abhi and agni together we note that the word abhi is such that it ends in e followed immediately by the uttarapada which begins with a another vowel. In this case the environment for the application of the sandhi sutra 6177 eco-yanachi is fulfilled and so eco-yanachi takes place and abhi is now modified to abhi and then finally we get the derived form abhiyagni. Since this is a samasa samhita is obligatory and so we cannot have the finally derived output as abhi agni. This is not possible there has to be a sandhi so we will have abhiyagni as the output and this will be done only towards the end of the derivation process of the samasa. Let us take the example of dvandva samasa. When the meaning is krishna and arjuna together krishnaha arjunaha che this is the laukika vigraha vaakya and so the laukika vigraha would be krishna plus su plus arjuna plus su. Now we have supodhatup pratipadika yoho applying because the samasa saudhnya takes place at this particular stage. So pratipadika saudhnya takes place so su and su both of them are now part of the pratipadika.  Then we join krishna and arjuna and because this is a samasa both the words are in the samhita mode so they are in close proximity and the condition is such that the word krishna ends in short a followed by the word arjuna which begins with short a. Now in the condition of samhita when two such vowels come in close proximity the sutra 61101 applies and substitutes the long vowel and therefore we have the finally derived output namely krishna arjuna where a and a are substituted by their long version a. Since this is a samasa we cannot have krishna and arjuna as the finally derived output. We will have the output in the samhita mode and so sandhi has to be done. Krishna arjuna is the finally derived samasa output after having done the varnakarya in the form of sandhi. These are some of the operations that happen in the derivation of the samasa. We have studied them in some detail. We have also explained some idea some philosophy behind these operations and we have also stated the place where these operations take place. Now there is one more varnakarya remaining which is uttara pada rasva. This is an operation that takes place on the final sound of the uttara pada. This operation is that of shortening. All the operations that we have seen so far they were related to the purva pada. This varnakarya however refers to the uttara pada rasva which occurs at the end of the uttara pada. So a long vowel at the end of the uttara pada is shortened. That is what this operation is with some specific environments in place like neuter gender as well as uttara pada being subordinate. So when the samasa is in neuter gender the shortening of the final vowel is stated by the sutra rasva napomsake pratipadikasya. 1, 2, 47 of the ashtadhyayi. And when the uttara pada is subordinate the uttara pada rasva the shortening of the final vowel of the uttara pada is stated by this particular sutra. The feminine suffix and the word go which are part of a subordinate word are shortened. That is the meaning of this particular sutra. Rasva napomsake pratipadikasya is self-evident. It means the pratipadika which is in the neuter gender its final vowel is shortened.  This rule operates in a specific environment of a compound where meanings of both the purva pada as well as uttara pada become subordinate to some other meaning. And that other meaning lies out of the compound. And so obviously pahuvrihi samasa is the example of this particular sutra. Let us take an example when the meaning is one who has obtained knowledge or learning. The laukika vigraha is praptaviddhya yenasaha. And the alaukika vigraha would be prapta plus su plus vidhya plus su. Now here the samasa saudhnya takes place. So pratipadika saudhnya takes place. So both the su's now are part of the pratipadika. So now supodhatup pratipadika yo ho 2471 applies and therefore both the su's are deleted. So we have prapta plus zero plus vidhya plus zero. After which the puhmat bhava operation on the purva pada takes place by the application of the sutra. So we have prapta modified to prapta and vidhya. Now because this is a pahuvrihi samasa, both the purva pada as well as the uttara pada, they are semantically subordinate to some other meaning. Both the purva pada as well as the uttara pada, they are semantically subordinate to something outside of this particular compound. So now since uttara pada is subordinate is upasarjana, this uttara pada has its long vowel at the end shortened by the sutra ghostriya upasarjana seer 1248. And so we have vidhya modified as vidhya. And so the output generated of this particular process is prapta vidhya. The input was prapta vidhya yenasaha and the output is prapta vidhya vidhya uttara pada hasva happening by the application of the sutra ghostriya upasarjana seer. We revisit the same example that we saw earlier but we focus on the uttara pada hasva now. So we have amita abha yasya sahaja as the laukika vigraha which means one who has immeasurable luster. Now we have amita plus suh plus abha plus suh as the laukika vigraha. So samasa saudhnya takes place. So pratipadika saudhnya takes place. Now we have both the suhs which are part of the pratipadika. So now supodhatup pratipadika yoho applies and deletes both the suhs. So we have amita plus zero plus abha plus zero. Then the pummat bhava operation on the purva pada happens because of 6334. So we have amita plus zero plus abha plus zero. Now since this is a bohuvrihi samasa purva pada as well as the uttara pada are semantically subordinate to some other meaning outs of this compound. Since the uttara pada is subordinate upasarjana the sutra ghostriya upasarjana seer applies and abha which has a at the end which is a long bubble is shortened and we have abha as the resultant output of the next stage in the derivation. So we have amita abha and then the sandhirul applies and then we get the output generated as amita abha. This is how uttara pada raspa takes place. This is the example of the varanakarya. Now after having studied these operations let us look at the discussion on the gender of the compound. In the dvandva compound the gender of the compound is determined by the gender of the uttara pada. This is stated by the sutra paraval lingam dvandva tattpurushayoh 2.4.26 of the ashtadhyay and this says that the gender of the dvandva samasa as well as the tattpurusha samasa is determined by the para element that is uttara pada in the samasa. So for example if we have kukkutaha mayuri chav kukkutah is masculine gender and mayuri is feminine gender. If we do the dvandva compound of these two padhas the dvandva output would be kukkutah mayuri and the gender of this samasa would be the gender of the uttara pada namely mayuri that is feminine. And so we will get the forms like kukkutah mayuri yaw etc. But if we change the order and put kukkutah as the uttara pada and so we have mayuri kukkutah as the output the gender of this compound will be determined by the gender of the uttara pada which is kukkutah which is masculine and so this compound will be in masculine gender. So we will get the declension mayuri kukkutah etc. The gender of the avyayi bhava compound is by default neuter. This is stated by the sutra avyayi bhavascha that is 2.4.18. So if we have the laukika vigraha kumarasya samipam the samasa form would be upakumara and it will be in neuter gender and so we will have upakumaram. Similarly if we have the laukika vigraha sriyam the samasa output would be adhisthri and this will be in neuter. If we have the laukika vigraha gangamano the samasa output would be anugangam and this will be in neuter. So we have anugangam. Since the bahubrihi samasa is by default a visheshana qualification its gender is determined by the gender of the visheshya as is the general rule in samskrit. So now if we have the laukika vigraha praptaviddhya yena sah. This sah is the head. So the gender of the compound praptaviddhya would be masculine. So we have praptaviddhya. In the second vigraha sah is the head feminine. So the gender of the compound praptaviddhya will be also feminine. So we will have praptaviddhya and tat in the third vigraha is in neuter. So the gender of the compound praptaviddhya will be neuter and so the compound form in the decline form would be praptaviddhya. These are extremely important points to remember as far as these three types of samasas are concerned as we shall study them in detail now. To summarize operations based on individual sounds are done at a later stage at the end of the process of the derivation of the compound. They give the final shape of the word form of the compound and denote one merged meaning realizing aikapadhyya as well as aikarthya. The grammatical gender of the compounds is determined in different manners for each of the compounds. These are the texts referred to. Thank you.


In this video, I'm going to show you how to create interactive quiz directly in your Zoom meeting. Let's get started. In my previous video, I've explained about the advanced poll features of Zoom. If you haven't checked out that video, please do so. The link is in the video description. What's the difference between the poll and a quiz? Well, a poll doesn't have any right answer while a quiz does. In Zoom, if you want to set up a quiz, sign in to your account. To create interactive quizzes for your Zoom meeting, schedule a new meeting by clicking on the Scheduler Meeting button. Or you can open an existing meeting to define your quizzes for that meeting. Let's schedule a new meeting, give the details of your meeting and click on the Save button. Scroll down till you find this option Polls and Quizzes and click on the Create button. You should have two options, Polls and Advanced Polls and Quizzing. If you don't, please refer to my previous video which explains about advanced polls. Click on Advanced Polls and Quizzing. Zoom alerts you that you can define this either as a poll or a quiz. When you're creating an advanced poll, there are eight type of questions that you can pose to the participants. Even though Zoom allows you to choose all eight types of questions for quizzes, in my opinion, when it comes to a quiz, you should stick to the single choice, the multiple choice, matching and filling the blanks. The rest are not really suitable for a quiz. Let's create a very simple geography related quiz. Give a title to your quiz. Let's check how good is your geography. Start with a very simple question. What is the capital of United States? Let's give four choices. So these are the four choices I have entered. Only one of them is correct, but we'll get back to that a little later on. Make it a mandatory question by clicking on the required option. Zoom allows us to add images to our questions. Click on the three dots and click Upload Image and let's upload an image of United States. Navigate to the folder that has the image, click on it, click Open and that's our first question of the quiz. Let's add another question, but this time we will choose multiple choice. In this question, more than one answer can be correct. Let's choose a suitable question. Let's say we want to find out if the participants know which countries belong to the EU. As in the first question, we can make this a mandatory question by clicking on the required option. Click on the three dots to add an image and our second question is done. Let's add the third type of question, which is called the matching type of question. Click on Add question and choose matching. A matching quiz allows you to set the questions on the left hand side and the possible answers on the right hand side. Let us choose a suitable question for this type of quiz. For example, where will you find this mountains? I will list some famous mountains. On the right hand side, I will list the country names. You are allowed to add one additional answer compared to the number of questions. In this case, there are four questions. I can give five possible answers. One of them obviously will be wrong. And our third question is done. I've added an image to the question and also let me make this a mandatory question by clicking on the required option. Let's add the final type of question, which is the fill in the blanks. Click on add question and from the drop down scroll down till you find fill in the blank. Let me freeze a suitable question for this. The largest planet in the solar system is fill in the blank. We can add multiple fill in the blanks to the same question, but in this case, we will keep it to one answer only. Make it a mandatory question by clicking required and add an image. We can add as many number of questions to the quiz by choosing from this four types of questions, the single choice, multiple choice, matching and fill in the blanks. Once all the questions are created, it's time to convert this into a quiz. Go to the bottom, click on these three dots and choose this option. Make a quiz and set the correct answers. To set the correct answer, go to each question, click on the question and use this option called set answer. For our first question, our correct answer is Washington DC. For our second question, we have two correct choices. For the third question, we can set the appropriate answers and for a final question, click on set answer and type the answer, which is in this case, Jupiter. When all the answers are set, click on the save button and your quiz is ready. Let me start this meeting to show you how a quiz works in an actual Zoom meeting. When you are in a Zoom meeting and you want to launch the quiz, click on the polls button. Since we had only one quiz, it appears on the screen. I can click on the launch button to start the quiz. A quiz has several additional options. Click on the three dots. You can choose to show one question at a time. Let's do that. Also, you can display the questions in random order. Let's click on that also. I will click the launch button to launch the quiz. The first thing you will notice is that the questions appear in random order. This was not the first question in our actual quiz. Let me choose the answers. When I click the next button, I get the next question. Capital of the United States. Let me choose Washington DC. Next, the largest planet on the solar system. Let me type Jupiter. Next, where will you find the mountains? Let's choose some answers. Because it's a quiz, I can go to the previous question just to make sure everything is okay. Go previous. And let's say I realize United Kingdom is not part of EU anymore. I can remove it. Go to the next question. And once I have reviewed all the questions to the quiz and made sure everything is okay, then I will hit the submit button. If I am the host, I can check how many people have submitted the quiz. For example, as of now, nobody has submitted. Now I can see one person has submitted the quiz. I can check the answers. And when I want to end the poll, all I have to do is click and poll. Once the poll is completed, you get additional options when you click on the three dots. For example, you can view the results in a browser. You can download the results or you can relaunch the quiz. And that was a quick look at the new quiz option in Zoom. Give it a try in your next Zoom meeting and I'm sure you will keep your audience engaged.


Hi everyone, welcome. My name is Avishag, I'm very excited to be here. And today I'm going to talk with you about dev team metrics that matter. We're going to understand what are these metrics, how we can measure them really, and also what we can learn from them, and how can we optimize our delivery process by start monitoring them now. So before digging into it, I'm going to shortly introduce myself. So I am Avishag, but all my friends call me Vishi. It's shorter. This is my nickname. I live in Israel, Tel Aviv, as you probably hear. I speak Hebrew. This is my main language. So I suffer from accent glitches and also grammar vocabulary from time to time, but forgive me about that. I'm a software engineer at Linear B, and on my free time, I enjoy dancing. And I even used to dance professionally until I joined the army. Yeah. So at 2013, I joined the army in Israel. This is kind of a mandatory thing there. You have to do it when you turn 18. And I joined the intelligence forces. I worked there as a BI developer, and I did a lot of data analyzing of mass of data. I did it for about two and a half years, and then I joined the industry. At 2015, I started working for all scripts also as a BI developer, but quickly I shifted my career and I became a software engineer there. I developed systems in the healthcare solution work, and I stayed at all scripts for almost four years. So that's about that phase of my life. After all scripts, I joined Cisco. I was working there as also as a software engineer. I developed features for Cisco umbrella in the SWG world. Specifically, I developed features in the backend services there and also for the VPN that we provided back then. And on 2021, I joined Linear B. In Linear B, I worked as a software engineer, and now I'm also a team leader there. I'm hands-on, so it means that I still do code work, but this is a really, really fun experience for me, because Linear B is a startup, so I really had a chance to start there when we were very, very little and we were a very small group of people, and I saw all the process there, and it's kind of amazing, and I love to work there. So I did my first degree in Israel in the Ben-Gurion University in computer science. This is a very social experience to be a part of, and that's where I met a lot of friends that are now working as developers, as probably you. So enough about me and let's talk about my friends. So in Israel now, the wedding season is on fire. It means that literally every two weeks I go to another wedding and I have to go do that wedding because this is the thing there, okay? You just have to do that. So when you are going to a wedding, you always like socialize and you talk with all the guests, and some of them are friends. Two weeks ago I went to a wedding of a friend from the university. That means that I met many, many developers, many, many. And when you meet your friends from the university and in general, when you meet like a group of people, for example, like in this event, so there's always this question, so how things go at your work? Like how's your job? Do you have fun or not? How things are going there? And the answer is always binary. It's either you are very, very happy or you are very, very sad. So when you hear the answers, it goes usually like that. This developer starts by telling you, oh, the benefits are amazing. I love the events and I have a lot of time there playing, I don't know, bowling or snooker or whatever. They provide you in the office. But, and when the but starts, it's when you are starting to worry about your friend. So the step developer actually in his actual job suffers a lot from ongoing conflicts that he's not able to resolve because that it's because the team that he works on never like engaged any tool that will help them to resolve these conflicts. He's delivering very, very, very slow. That means that he might be like an excellent software developer and develops all the features and the logic really good, but he suffers from delivering it to production. And he's always has a lot of on calls and pager duties stuff that's going on in production and many, many bad things that just makes him very sad and makes his life literally like miserable and he's not having fun and he's looking to maybe, you know, switch a job or something like that. And this is the sad friends that I have. Okay. And the happy developer might not have like a lot of benefits, like most of the time, yes, because we are in the tech industry. So we know how it goes, but he's happy not because of that. This is not what will keep him in the company for the long term. He is happy because he feels that he has a lot of impact in general to the product and to the customers that the product has. He feels that he works with high quality and high standards. And he also delivering very, very fast because it's not an issue there because they are engaged like have any tools to help them deliver fast, right? And they also like have a really stable production environment. So he's not suffering a lot from like bugs and issues that goes on product. So that goes like basically that. And these all are related to what we call the dev experience, right? The DX-wise experience. And it's basically like we saw that there is a deep relation between this dev experience that we provide to our dev teams and their happiness in the company. So that's about this one. And I want you to keep it in your mind. I want to move on and talk a little bit about Dora Metrics. Dora Metrics DevOps Research and Assessment Metrics. This is a group of metrics that was actually defined by Google after years of research.  And it goes to, we can split this metric, this group of metrics into two categories. We want to measure speed and we want to measure quality. Like speed is like how fast you do things and how fast you deliver your code. And quality obviously is the quality that you are providing when you are developing these new things. So Dora Metrics is a group of metrics that help you to really understand what is your group. And even your individual contributor, what is your speed and what is your quality. And the first metric I'm going to show you is cycle time. So cycle time will be the first metric of Dora Metrics that measure your speed. Cycle time definition is how quickly your work moves from coding to deployed. And it's important to understand this part because as developers, we are not always, our main job is obviously coding, but this is not the only thing that we do. We have meetings. We have designs that we do. We have things that are really not measured by coding, but when we want to measure the pipeline and our delivery pipeline, we are focusing about coding. So cycle time refers into our coding flow. So when we want to measure it, we actually want to understand how quickly we are starting to code and take this code all the way to production. And there are many phases along the way. So I want to demonstrate it with our cycle time. So in my group, in my R&D group, we are measuring our cycle time within four phases. So we have four phases that we are measuring separately. And the summary of all of them together gives me the cycle time. Now, this is the cycle time of an elite team. So this is a really experienced team that are working very, very fast. And we can see interesting things here. So first of all, let's understand how it splits, okay? So we're starting by coding and how we measure it. We're starting to measure it from the first commit that we do, right? The first commit, not the first push, but the first commit until we are working with GitHub. So we are working with pull request and we are delivering with pull request. So anyone here familiar with that? If yes, please raise your hand. Okay, great. Awesome. So we are measuring the coding time till the moment that we are open a PR that is not labeled as either draft or width. That means that then when the pull request is mature enough and we want to deliver it forward to review, this is the moment that we are finished with the coding, okay? After that, we are measuring pick up time. Pick up time is the moment that the PR is ready to review till someone actually from the team reviews it, or not any team, like in general, till someone is really actually start commenting it and this whole cycle starts to go. And then comes the review time. Review time we are measuring from the moment that someone commented on the PR till the moment it's approved or closed in some cases, but till the moment it does. So this is the, this will be the review time. It usually will be like the review time takes a little bit, it's a cycle by itself because you know the review might take like a lot of like transitions there between the reviewers and you and you have to sometimes address their comments and it might take like a little bit more time than the coding itself. And after that we are deploying. So in our R&D group we are, we count our deployments when we are cutting tags. So once we have a tag that is ready to be published, this is the moment that we are counting as deployment and we are finishing to deploy it when we are recognizing it in production, okay? So this is our cycle time and this is how we measure it. But obviously in many, many other groups or sometimes individually your cycle time might look a little different. Maybe you have like, for example a QA phase or some integration phase or many other phases. So it's really under, it's when you are start, starting measuring these, these phases and these cycle time in general, you really want to understand what are these phases that you really want to measure. So that was about cycle time. Another metric that is associated with speed. Deployment frequency. How often your work is deployed to customers. So this is another way that we can measure our speed. It means that the many, the, how many times we are deploying to production. So if we do it many, many times, it means that we are probably delivering fast and we get, and we are reaching to production much faster. And that means that we are probably do this work, this coding thing, this whole process like many times and we do it like in high speed, okay? So when this number is high, it means that our speed is high as well. Moving to quality because speed enough by, speed is not enough by itself. Quality is really important because if you are delivering fast without like high quality, it's really like, first of all, it's not good because of the obvious, because of the obvious reason, but it's also like can impact your speed as well. So yeah, the first thing that we, the Dora metrics want to measure when it comes to quality is CFR. Change failure rate. That means that we want to measure how many times, how often deployments results in an issue or a bug. So you know this process when you're delivering and once you are finished and your new service is in production, right away you have a bug, something that you didn't find out before and this is an event that we want to measure because it points if we are really delivered with high quality or not. Another thing that we want to measure when it comes to quality is the MTTR metric, mean time to restore. How quickly you can recover from issues. So let's say you have an issue already in production. Another way to understand your team's quality and your development quality in general is to know that once you have an issue, how quickly you can resolve this issue. So if you do it fast, it points that your quality in general is good because you probably found the issue a lot faster in the code and you understood quickly where you need to fix it and you also probably fixed it really well because you had a lot of tests, for example. So it points that your quality is high when this metric is actually low, okay? So this group of metrics again, these are the metrics that you want to start to measure and you can even start measuring them today and I will explain in the next few slides how you can do it and these are really important when you want to get the full picture of your group performance and especially when you want to plan forward to the next quarters and stuff like that. So another thing that's worth mentioning here is the first slide that I mentioned at the beginning about the happiness of your development team. So when these metrics are good, it means that your developers, your dev pipeline is happy and also that your developers are happy as well. So keep that in your mind and just understand it where I will explain more about it in the next few slides. So another metric, it's not really associated with Dora metrics but it really affects on all of the metrics, all of this group of metrics is PR size, pull request type. We saw that there is a really deep relation between the pull request size to our speed and our quality.   So you know the answer already and we heard it before, big PRs are not good for you and today I'm going to show you our research when we did it and we are going to give you the actual results of our research and that way you will see really the effect of big PRs on your pipeline. So the first thing we discovered based on this amount of data, so we had many pull requests of our customers, okay, they are allowed us to do that of course, we had 3.9 million comments and about 25k developers, so these are really like big amount of data. We discovered a really like huge thing here that PRs under 200 changes will probably get merged faster and the reason for that is, first of all, big PRs are very scary to review. When I get a big PR, I don't know what to do with it. I probably will return it back to the developer and tell him, organize it for me. I cannot review it. So probably as a reviewer, when I get a small PR, I will have a much better review as well, right, because I have a lot of, I have less to review, so everything that I found, I found very quickly and I have like many comments on the small PRs. When I get like really big PRs, it's either I'm just returning it back to the developer and like find a solution for yourself, I don't know, go handle this thing, or if I'm not a good reviewer, I will probably approve it right away and this is a behavior that we are not allowing in our group. So this is a really huge thing here. So another thing we discovered that also reflects your speed is that when you are working with small pull requests, you are actually increasing your deployment frequency, right, the other Dora metrics we discussed about. So this is something also that affects your speed and can change really your delivery and also your happiness of your pipeline as well. Now let's compare two teams here, one that engage the small PR, the small PR approach and the other one that's not. We can see the relation between these two. So teams that are working with really big PRs have a really big cycle time, like a really high cycle time, while teams that are working with small PRs, not always, this is an average of a week, yeah, but it's not always like that. It tends to be between 20 to 100 code changes. Their cycle time will be shorter. So this is something that you have to understand. This is something that we saw with a lot of data. So probably, I mean, we see this trend in many, many teams that we had research on. So you are probably following with the same like teams and it will also affect, once you will measure your metrics, you can also see this kind of difference between these two. So these group of metrics are the most important ones to measure and you can start to measure these metrics today and how you can do it. You can do it by monitoring WebBooks event on your repose and your WebBooks event on your organization. You have like many free plugins that can help you to understand how to monitor that. You can also like use the spreadsheet or maybe plugins with JIRA or whatever product management tool that you are using and you can also use free tools that are there in the market. For example, jellyfish, linear bee, us, and so on. So these metrics are worth monitoring and if you want to understand what's your speed and quality of the team, you want to start doing it now. So you'll have the realization of how your pipeline health is and also how your developers in the group are because not all the developers will tell you that they are unhappy because of that because they are delivering slow. On one-on-ones that we do in our teams, there are not always these developers that will tell you that but you as experienced developers as well as like junior developers, you can really see that by yourself when you are starting monitoring these metrics. Now let's say we started already to monitor our metrics. Let's talk a little bit about the most common delivery process. So this is the delivery process we do in our R&D group but it applies for most of the companies as well and most of the individual processes as well. So it goes like that. You start by coding and this is not the cycle time, this is the delivery process itself. So you start by coding after either why you are finished and you are opening a pull request and when you have this pull request cycle of review and pick up and whatever all of this all of this phase you will merge it and after the merge part you will have integration part but sometimes you might like integrate your code on your features prior to the merge so it really depends so sometimes the interrogation will be before and sometimes after most of the time it will be in both sides of the of the merging phase and after you are done with that phase you will deploy your code to production. So when we want to calculate the cycle time in our R&D group it really sits really perfectly within between okay but other metrics that we want to measure will be in other places as well so CFR that points on your quality will be affected by your code and your PR because when your code is in high quality in the PR cycle meaning the review is in high quality that will affect the CFR metric right change failure rate that means we'll have like less issues when we are deploying when we do these two parts in high quality. Cycle time as I mentioned meets us in the whole process deployment frequency will be measured when we are deploying things and MTTR as well but if we are looking at the whole process we want to boost it it means that we want to speed it up and the way we did it so far and think that we are familiar with these days are related to the dev experience in general so we need to keep in mind that our goal is to provide the best dev experience it applies either you are working in an enterprise any company any startup company and even as an open source developer an individual contributor when you have a good development experience you are more likely to contribute faster and in high quality as well so the way we did it and the way we are doing it right now like in most in most of my companies that I work at we had the CI CD processors so for most of us here we know that by like it's a given thing for us CI CD continuous integration and continuous deployment so these weren't given to us but I remember myself when I was working at all scripts in some teams literally we had to copy DLLs files from the local machine to the servers so CI CD was not always here for us to help us automate our processes so are you always who is familiar with CI CD okay great so we have many tools that help us doing it Jenkins drone GitHub actions and many many tools like that and this is really boost up our process right from many all things we had to do in the past I don't know 10 years ago 15 years ago we are now doing it automatically without human mistakes that we might do and a lot faster because this is all automated and triggered by actions or by cron schedule whatever so this really helps us in that part but we see there is a gap there so there it's not all not not all the process is covered really with the CI CD and we see that developers are still suffering from what we call idle time so let's zoom in in to the process the code PR marriage part and we'll see that the PR itself when the pull request is alive it starts a cycle by its own so this cycle is split it into pick up time and review time and we see that really this is really really funny but the coding itself not taking a lot of like this is an average data but it's not taking a lot of time and more than pick up and review and the pick up and review it's not it's not that I'm reviewing a PR for five days right this is uh caused by who can guess I mean you know this is not interactive talk so I will tell you the answer so um this is happening because of the transitioning that we do and the destruction that it takes we also know it as context switch as human context switch right so in the computer science word we know that context switch is very very expensive and in our process in our delivery process is very expensive a because um this is number one time consumer in the process as we can see in the data and be a developer working hours are very expensive so this is really something that we can we want to reduce and this is not really a work this is really a most of it most of it here is actually an idle time that we want to optimize for the developers okay so as I mentioned before this is the common process and we want to resolve it by getting into that part somehow so how can we boost this idle time and we can start doing it by understanding that not all pull requests are the same so we have small pull requests and we have sometimes big pull requests that we cannot like do it do otherwise for that matter but we want to understand and we want to somehow categorize them and give more context to their reviewers so this is just an example this is more of a concept um that pull requests are can be split into risks categories for example if it's a really small pr uh only uh read me file changes it will be probably in low risk but when you are changing some security definitions or some um um i don't know environment viable changes and stuff like that it might be a little in high risk so you want to somehow to understand it before you are really opening the pr and this is what we call fpm so along with the ICD we are now giving you the cm the continuous merge now this is not a product this is not a tool yet but this is more of a concept okay it's a it's a new concept that we want to engage in our process and we want to spread the rumor about it so continuous merge along with continuous integration and continuous deployment will provide a full cover on the whole delivery process okay so we now have this continuous merge we don't know yet what it is but if we'll have an automation right there that can boost up the speed of the idle time phases and it will really affect on the whole delivery itself and the whole and the whole process itself and it's even more effective because this is the beginning of the process so if we if we'll put if we'll boost it up will affect dramatically the whole process in terms of like speed so this is very interesting and something to keep in your mind so continuous merge refers to the pull request lifecycle we are really are talking about pull requests here and the coding part of our job and not the other parts that we do but and this is really something that we can start engaging and do just start engaging it to our processes so as a concept we have two ways to do it so either we are going to get our pull requests just more attractive to review and we can do it by really um deliver small prs for review and not all everyone are really experienced with that but we saw that a really good tech design prior to the coding itself can really affect it and when you are working what we call in micro tasks instead of like big tickets instead of like big stories they want you want to promote and you start coding right away if you have a really good deep tech design for it before you are more likely to create and work in small tasks and small micro tasks and in that way you'll have in general um you will be more likely to deliver small prs for reviews and to the pipeline itself and this is one way to do it and another way to do it is uh to somehow get your pull request um attractive by automations so you you have like many tools and many plugins of uh hey i opened the fr please review something like like bots and stuff like that that you can engage to your processes right away and a lot of them are free so feel free to reach out to me after that and i will tell you uh what are these and this is the first way so the other way is to automate your actual merge and this can be done by defining rules to each repository because each repository has different personality each repository and each project can be treated like totally different it depends like on the business that it holds inside so if we'll define some rules to each repository we'll be able to automate our merge and not only merge but we can automate it um any kind of process for example in our i r n v group we defined a a rule that um in our specific big repo we have to have at least two reviewers and if we're changing a code in that security file over there it's called um security file that pie uh we'll have to uh automatically it's automatically assigned um uh someone from the security team as a reviewer automatically without us without the developer have to do anything with that and these small things really matter because this is five minutes there and ten minutes there and in scale in like in big maze of uh of developers it's a lot of time so these two ways are are a way to to engage the the c m the c m approach so here i'm going to show you a few examples of how we did it so in linear b we are doing a dog footing that means that we are using our own product so we have these uh bots that for example if we have small pull requests for a view you know this small pull request of only bumping version bump version blah blah blah axios whatever for this kind of pull request we don't want to waste a lot of time so are we are uh standing right away a request not to a channel but to individual when we are looking for uh immediate approval so once a reviewer will will see it right away without having to click on a link and go to get up you can see it right away you can approve it from slack without like having to do anything and or have any concerns about the pull request that he might get so this is an uh one example another example that we are uh engaged um sorry estimated time to review so when we are asking for someone from someone's review and we are actually attaching by an ai algorithm we develop uh how how long we are estimating this review might take so this gives us gives the reviewer a little context and he knows how to plan his day so he knows that if it's two minutes review i'll just go ahead and release this pr and help my uh friend and make him happier and if it's a longer review okay so i need a uh an appropriate time for it i will just block it in uh in my calendar and go and go on so this is like two examples of how we made our pull requests more attractive to review and in another way uh that we are working on right now we call this solution geese room solution so this is the uh automated categorization that we are trying to develop for our pull requests and we are doing it by a set of rules for each repo and this is the i don't have like an appropriate example here but we have definitions of rule in yaml file for each repo and we have it also like in org level so we have this default rules for the all orgs and we have um rules for each repo that uh are really um like like the example i gave i gave before so if for example we are changing only um markdown files in sum of the passes in the repo we'll be able to get auto approve or auto merge and so this is about that and in general we are here to make our word and our dev experience just better whatever and wherever you are working on either your individual contributor working start up all enterprise and dev experience is like the most main things to start investing to provide the best like way for your people to work and just keep that in mind so if you have like any questions i'll be happy to answer okay okay i think there are no questions right so yeah great great talk uh just the question is uh how does how do these metrics particularly relate to developer happiness because uh i i understand you said that the healthy pipeline ensures happiness but i uh is it just correlative or causative oh sorry the last sentence was is it uh like a healthy pipeline does it essentially mean happy developer or are there other metrics so for develop for develop developers happiness it's not a really one thing this is like a combination of many many many things right you have the benefits you have the social environment and the team environment you have the setting even like for some of the developers the setting is really important but dev we saw that like in our field that dev experience in general affects on the developer happiness so think about it when you are working in scale and where you are working like in a multi repose project and we are working on many many things you want to focus on the features that you want to deliver and less about the nonsense like around it so you don't you don't want for example to treat a dev stage and production environment differently you have this environment variable that you set up somewhere and you automatically um feed it to to to your machine and this is one way to reduce the noise the developer has to handle with this is by the way the jobs like the job of the developer most of the time or the dev ops but this is all related to things to small things that just make his the developers life just easier and therefore happier so yeah if that answer your question okay thank you