If you don't know me, then come say hi to me. I just a quick 30-second bio for people who don't know me. I've been in open source a really long time, like since 2002, because I'm really old. I was a PHP developer for a long time. And then about six years ago, I switched over to the more community side of things. I pivoted my career a little. And now I work at GitHub. I've been at GitHub about four years, doing community-ish type things there. I do live in Cincinnati. If you need any recommendations for awesome places to eat or see or do, probably want to ask someone else, because I live in the suburbs. And I never come downtown. So I'm like, oh, it's cool down here. We were excited to come out last night and have dinner downtown. I was like, oh, yeah, I feel like a tourist in my own town. Yeah, so I got my degree in organizational behavior. And I find the behavioral science side of open source super fascinating, which is why I'm giving this talk. I kind of geek out on this stuff, so my apologies in advance for my excitement. So let's get started. So what, if we were going to say, what makes open source open? Can you guys see this OK? I was kind of a little worried about the white text on black. So there's basically two components, right? There's people and code. Those are the kind of the things that come together to make open source. And obviously, a lot of talks at RubyConf are about code. So this one's just going to be about people. All right. So if you are going to define how people make open source software, I think this is a pretty good definition. Individuals working in groups collaborating together online. So what we want to do is kind of take this definition and break it down into these different layers. So we have individuals who are working in groups and they're collaborating together and they're doing it all online. So if we just start with that first layer there of the individual, like just you, me, our individual things. If we look at Wikipedia, it tells us that there are no less than 107 different ways in which we act completely, utterly, irrationally. So 107 different ways. That's a lot of ways. That's a lot of ways. And we always think like we're the ones being rational, right? We're the logical ones. Turns out that's not true. Like we're never rational, right? Like very rarely are we super rational. So and this is even above and beyond like the unconscious biases you might have heard of like sexism, racism, all of those isms. This is above and beyond all of that. So we're not going to talk about all 107 of them because we would be here a really long time. And you all would be super bored. So I'm just going to pick a few that I've seen in my 14 years of just kind of observing open source. Things that I kind of see like patterns. So hopefully to kind of demystify some of these things, maybe explain why people act the way they do. My goal here is to kind of allow you to empathize a little and maybe recognize some of these biases in yourselves. Oh, sorry. So let's start with the first one. The negativity bias. So this is the bias that I see a lot. And it basically says that as human beings in general, we're going to place more importance on negative experiences and feedback. We give them more weight than we do the positive ones. And behavioral scientists trace this back to survival times, right? Like if your cousin eats a plant that kills him, probably don't want to do that, right? So we will remember that. We will remember not to eat that plant. And that will be very important to us in our brains.  All right, that's cool. But we really want to make sure we don't eat that one that's going to kill us. So we place a lot, lot, lot of importance on the negative feedback that we get. They register quicker in our brains. Like we know if something's bad immediately. It takes us a few seconds to figure out if something is good or not. And it doesn't seem like a big deal. But it actually really is when we're just bombarded by stimulus all day long. So when we have a negative experience, it also goes immediately into our long-term memory. But when we have a positive one, you need about 15 to 30 seconds to really appreciate that this is a positive thing that's happening. And then it will register in our long-term memory. They have a greater impact on us, negative experiences. So if I give you 20 bucks, you're going to feel pretty good. But if you then lose that $20, you will feel worse than you did before you got it. It's not an even zero-sum game. You're going to feel way worse. So it's just an interesting kind of phenomenon how that is. You would think that, oh, I had it, and I lost it. Oh, well, no big deal. But no, that's not actually the case. That's not how things work. They have an adverse effect more than two times of our positive experiences. So every time you have a negative experience or someone in your open-source project has a negative experience, then you're going to need to have at least two more positive experiences before it's kind of an even playing field. We also learn faster from negative experiences, like all these behavioral science research studies. That's how you're going to learn the carrot and the stick. The stick teaches you much faster than a carrot does. It's probably not the healthiest way to learn and provide feedback. But they will learn. People will learn very fast what not to do and when things are bad. So take that for what it is. How many people in here participate in or are managing an open-source project? A few of you. OK, so some of this stuff applies at work, too, or at home, like wherever. It's just human behavior. So it's applicable to open-source, but also just in your everyday lives. I think this is interesting. We have five times the neural networks dedicated to negative affect over positive affect. So negative affect are things like fear, grief, sadness, shame, guilt, all those icky things that we feel. Positive affect is joy, comfort, kindness, compassion, laughter, all those things. So we have five times the neural networks. So we're constantly scanning for threats. Like that's what our brain does, is constantly scanning for threats, scanning for things that are going to harm us. We spend a lot of time analyzing, worrying, processing negative feedback, way more, five times more than we do positive ones, which I find really interesting. It's like if you're aware of that, you can kind of mitigate it a little bit.  That is not your fault, it's just like human nature. We also have more words to describe negative things that we do positive things, which I find also very interesting. Let's see. So when you look at this picture, what do you see? Shout it out. A broken window? Yeah, a broken window. And I wanna also ask how many people in here would consider themselves problem solvers? Like do you consider yourself a good problem solver? Most people in this room would consider themselves a problem solver. So the interesting thing about problem solvers is when you're a problem solver, you're always on the lookout for problems to solve. And when you're doing that all day, because that's your job and that's what you feel like your role is, and all your friends are doing it all day, it kind of carries through, right? So you're constantly scanning for problems to solve.  Like it's all just terrible, software's terrible, we hate it, right? We see that all the time. But I think this is a really interesting quote here. So the fundamental difference between creating and problem solving is simple. In problem solving, we seek to make something we don't like go away. But in creating, we seek to make what we truly care about exist. So it's just kind of a subtle shift in the way we perceive our own jobs and what we are here to do and what our software is here to do. So if you go back and you maybe reassess kind of your initial analysis of this picture, you might also say that this is an almost perfect window, right? There's only one pane that's broken. Think the rest? Maybe that one in the left-hand corner, I can't really tell if that's broken or not, but most of the panes are fine. There's just one small pane that needs to be replaced and then the window's perfect, right? So it's just a subtle shift in the way we think and the way we look at the world as creating something that, I wanna create a beautiful perfect window, not this shitty broken window. I don't wanna look at this anymore. I'm just gonna have to just smash them all. I don't know. Okay, so enough negativity bias. That's a lot. I know, I'm sorry. I love how I kick off the awesome talk with all this, aw, wah, wah, sorry. I should have put that at the end, I guess, but the next one we're gonna talk about is Denning Kruger. Who's heard of this before? A few people, right. So essentially what this and its other side is imposter syndrome, which you probably have all heard of because we talk about that a lot in software. It's basically just that we are not very good at judging our own expertise and like how we are relative to others. And I didn't see Brandon Hayes' talk yesterday, but I heard that that was kind of like the whole key to that is just kind of like defining where you fit. So I think that's super, super helpful because otherwise we just don't know and it's really frustrating to be on the receiving end of someone who has Denning Kruger or even someone who has imposter syndrome. That is an awesome contributor but doesn't maybe feel confident enough. Like that's a shame. So I just wanna challenge you to maybe look at your own expertise a little more objectively for good and bad. Like I don't know where you fall on this spectrum but for good and bad maybe just take a look at how you are and what your skills are. The next one we're gonna talk about is Confirmation Bias. Awesome, right? Like all you have to do is just go to Facebook. Like I should have just replaced this with just Facebook or Twitter. Because like for the most part you already know what an article's gonna say based on who's tweeting the link. You already know what it's gonna say for the most part, right? Because what happens is when these two pieces of our brain are acting in conjunction with each other that's when Confirmation Bias sits in and we just filter out anything that doesn't jive. Anything that doesn't jive with what we feel and what we know to be true. They have to, in research they have to be very careful about this because you kind of expect to know what the results are gonna be and you can't allow any of your own Confirmation Bias to be a part of that. And it's really interesting that this piece when something is very wrong like that's like shit's happening in your brain. It's like you know we feel like it's in our gut but it's really in our brain. So it's like you're not crazy. It's actually something that's going on. And then when we have all these stimulus all day long like we have this big piece of our brain that's helping us filter what's important and what isn't and what we should pay attention to and what we shouldn't. So when those two things come together that's when we have Confirmation Bias. And I think what's also interesting is that Confirmation Bias is really plays into this. Right? If we think that we're an imposter like we think we suck, we're gonna just see the things that reinforce why we think we suck. So if you help mitigate your own Confirmation Bias and try to just look at things a little bit more objectively then that will also help with this problem as well. Okay. Let's talk about illusion of transparency. Has anybody heard of this before? One guy, in fact, yes. So basically it's just saying that we overestimate the ability for others to know what we're thinking. We think everybody knows. Like why don't you know what I mean? Why do I need to document this stuff? Like you should know what I meant here. The code speaks for itself, right? But that's not true. That's not true because we lack the context that's in your brain. Like I'm not a mind reader. I don't know. And if you leave me the option to connect the dots I'm gonna connect them in my own way not necessarily in the way that you mean for me to connect them. Does that make sense? Right, this is why I have a whole other talk. A whole other talk on documentation why it's so very important.  But it's super, super important because even for your future self, like you need to just write things down because people don't know what you're thinking. They don't know what your situation was at the time. And it's interesting that they did a few studies actually where they would tell one person to think of a song and then tap it out and then they would have the other person guess what song it was, right? It seems simple enough. And what happens is we estimate like 95%, we think yeah 95% of the time people are gonna get the song. It's clear what the song is. And they only get it like a very, very small percentage of the time cause it's like there's zero context around that. Does that make sense? The curse of knowledge. Anybody heard about this? The curse of knowledge? Gail has, she's smart. Just love her. So the curse of knowledge says the more that we learn the harder it is for us to empathize with beginners. Which part of my job at GitHub is to, I run the patchwork events which are events for beginners to get GitHub and open source. And so it's very interesting to me when I see mentors cause it's like a mentor driven thing. And it's really eye opening for mentors to kind of put themselves back in a beginner's shoe. Right? And the way this kind of came about was actually in economics. They were doing a study around sales people and why the most knowledgeable sales people weren't selling the most product. Like you would think, oh the more you know then you're the expert, like you're gonna sell a ton. But that's not actually the case. Because they had been, they're so far ahead they can't remember what it was like to not know things. Also I wanna just ask you guys what, so okay. So who in here learned to code or learned to do their job from a traditional four year college? Like a computer scientist or whatever. Okay, a handful. Anyone in here do a boot camp? Somebody, a few people. Who in here is self taught? That was me. Awesome. And then how many people learn by reading books? A few, okay about half. And then anybody learn by watching videos sometimes? Okay. So my point is if you think about all of the different ways that we can learn to code and learn to do our jobs, there is no one path, right? Like we're all over the place. And what we're learning is just based on whatever this person who's teaching us knows and whatever they think. Like it's going through their filter as well. So there are thousands of gaps in our collective knowledge. So when we mock someone who doesn't know something or we get angry or we lose patience with someone who we think should know it, maybe just take a step back and realize, well I learned that in boot camp but maybe they aren't teaching that in a computer science degree. Or maybe this person just didn't read that because they're self taught and they just need a little bridge for their knowledge. It's much better to share your knowledge than get upset because someone doesn't know because we're coming from so many different places, so many different backgrounds all over the place. So here's another one. False consensus effect. So basically we overestimate that everyone thinks that we're right. Everyone knows it, I'm in the common group. But that's actually not true because we're super diverse and what you think may not be what everyone else thinks. So don't fall into that trap. I just got a little shot of the super fruit infusion. Shit's awesome, I love it. It's like energy refreshed. Okay, let's talk about rejection sensitivity. So this is a thing that gets me excited, I don't know why but it does. So this basically explains the fact that your sensitivity to social rejection is it's a spectrum, right? So we have some people on this cent and who have no sensitivity to rejection. Like they do not give AF, like they don't care. And as a result, I mean in a way that's kind of cool because they're just doing their thing but also like you need a little bit of sensitivity to rejection to just fit in socially and to not like be a complete asshole, right? So you have these people on this end and then you have people on the other end who are just like 100% sensitive to every single thing that is said and they take it as a personal affront even like just having to stand in line.  Like so that's like way off the charts as well. So most of us are somewhere in the middle, you know, we've fallen here mostly. But what's interesting is that you don't fall in the same place as someone else. So when we tell someone, oh, you're just being too sensitive. Right, like that's actually not fair because it's a little bit more complicated than that. And scientists honestly don't know if it's because of experiences, if it's a learned thing, or if it's just when you're born, if that's like where you fall.  Like it's not that simple, right? It's a little more complicated than that. So just like be aware that someone's, just because you're not on the scale and the same place as someone else, that doesn't mean they're wrong, they're just different than you. And we should allow for that, we should allow for that. The really interesting thing I think is that our brains, they haven't shown that they don't know the difference between physical pain and rejection, social rejection, but they will say that the same parts of the brain become active. So we are feeling it.  Like it's a real thing, it's not imagined, it's a real thing. And our brain will release the same painkillers that it does, the same opioids go into our system to try to like make us feel better. So it's really, really interesting, there are actual physical changes happening when you feel like you're being disrespected or misunderstood, we'll talk about that in a second. So yeah, so we're pretty complicated, right? Like I only touched on a handful of these things. Like there's a hundred and seven of these things. There's a lot going on. So we're complicated, we know this. So let's jump to working in groups. Then things are gonna get even more fun, right? Cause we're now putting all of our messy shit together in a group, so it's pretty awesome. So let's talk about this in-group favoritism. So this is a thing that happens when we, it's kind of along the same lines as tribalism, which I'll talk about in a second. But when we find our people and that's awesome and you feel like you belong and it's great, but it can also be a little bit dangerous if you are taking your group and elevating them above other groups. Like that's not good. And I think there's been some talk about this kind of culture of contempt that we have in open source.  Like no one cares. Why in the world should I care what kind of phone you have? Like it literally affects me this much, zero percent, what kind of phone you choose to use. What kind of language you choose to write in. Like most of you write Ruby. I wrote PHP, it doesn't matter. Like I just want people, some people use GitHub, some people use GitLab, whatever.  Like that's all I care about is that you're happy and you're using something that you like. That's all that should matter. Right, so we should be a little bit aware of this.  When it's like we're all just trying to make awesome, cool things with open source. This is kind of interesting too. When we see someone that's in our group, there's like a part of our brain that will process information about them, like how we feel about them and things. When we see someone who's definitely not in our group, it's a whole other side of our brain that we're using. Which is very curious to me. And this kind of also goes into with the tribalism as well. It's like we completely put our whole identity into whatever tool, whatever it is. So therefore like if someone, you know, if someone says something bad about like Vim versus Emacs or whatever, like we're gonna like that's our identity. No, you know, we're gonna have a rumble or something. So it's just something to be aware of and something to try to mitigate against because we're all doing the same thing. We all want the same things. So we don't, who cares, whatever. This is interesting too. Feeling understood is a huge deal for us. More so than you probably thought. And there's a whole awesome book, which I think I linked to at the end, called The Science of Respect and how important feeling understood and respected is to us. It's extremely important. And when we feel misunderstood, then that negative affect just kicks right in, that piece of our brain. So it's a big deal. And of course then it's moderated by our sensitivity to rejection, which they found was interesting. So wherever you feel on that, on that spectrum, wherever you fall, you're gonna also, that's also gonna kind of dictate how you feel about being misunderstood. And for some people, it's a little bit more important than others. Same thing with belonging. Like we really, really, really want to belong.  And this is the whole thing of open source, right? Like we all wanna belong to something. We all wanna make it better together. So not to throw the GitHub thing in there, but that was our little tagline, better together. But yeah, like we really do. Like we really want to belong. So it's complicated. It's really complicated when you put everybody in groups. So now let's actually have our group do something. We're not just hanging out. We're not just social, you know, whatever, chilling. It's already complicated. But now we're gonna actually try to write some software, produce something. So we're gonna look at this really quick. Who's heard of SCARF? Anybody? Probably meh, maybe not. Okay. So SCARF is gonna help us understand what motivates people in certain groups. And then it's the extent to which people feel threatened or rewarded. So like what's gonna motivate them in the group? Or demotivate them to participate? Sorry, I'm gonna scratch. So here's the five domains of SCARF. Status, certainty, autonomy, relatedness, and fairness. And these are the things, these are the buckets that people fall in of what's important to them. So status, of course, is where they fall in relation. So it's like acknowledgement, recognition, status. Like for some people, that's super important. Like they don't care about the money, right? Obesource, none of us really care about the money. But they just wanna be recognized. They wanna feel important in the group. And that's really important to them. And this is actually at a subconscious level, like we're not even aware of it, of how deep it goes. Certainty, some people for this is so important. Like they don't want any ambiguity. Any ambiguity is going to be like a perceived threat to them, which is why for some people it's really important for documentation. How do I contribute to this project? What am I supposed to do? Just tell me what I'm supposed to do. What are the rules here? What are the ground rules? What's your code of conduct? These things are important to me that I know. That I know what I'm supposed to do here. What are the expectations? And when we have, for these people, when they have more certainty, it's like a reward. Okay, all right. So I'm kind of one of these people. I'm like in the middle. So like I dragged my family to the Grand Canyon over the summer. We have three kids and teenagers. And so they were super excited, not really. But I made them come anyway. And I literally planned every minute of every day. And it was jam-packed. It was awesome, awesome. It was like a super Clark Griswold moment, but I didn't care, it was amazing. And I was talking to Leon Gersing. You guys probably know that name. And Leon is like completely the other way, right? Like he's just like, let's just get in a car and just go. So he like took his kids across country for seven weeks, nothing planned, when we're tired, we'll just find a hotel, it's no big deal. And I could just feel, as he's telling me the story, I could just feel like my anxiety, just like, what are you in, why would you do that? Like, oh my goodness. But for some people, certainty is really, really important. So just keep that in mind. It may not be important to you, but for someone else, it might be. So if you allow for that in your open source, if you acknowledge that, oh, okay, then that's really gonna help you gain contributors, make people feel better about contributing or using your product. Yeah, oh yeah, yeah. And then for, yeah, the threat, people see it as a threat. Like, I don't know. I don't know what's gonna happen. I don't like that. So it's immediately on alert, right? Because my brain's scanning all the time for high alert. And then of course, ambiguous social situations. I'm sure some of you maybe in here feel that when you come to conferences. I know I do. It's like, it's really stressful if you don't know anyone. Like, I'm a PHP person. And my husband was a Rubyist. That's his Twitter, was Rubyist. But, you know, and I know a few local people, but like, I don't know very many people. So for coming here was super stressful for me. Because I thought, oh gosh, I don't know anyone. You know, where are we gonna sit at lunch? Like, all of that stuff, all of that stuff. So anything you can do to kind of mitigate that for other people is really helpful. It makes it for a much more inclusive community. Autonomy, autonomy is a big deal, right? Especially I think at open source.  Like, I don't wanna have to ask for a mission. I just wanna have control over something. Control over something. And if these people have that sense of autonomy, they will have better well-being. They'll be healthier. It's amazing the difference that for these people, if they are stuck in a powerless and a control, no control situation, that is not gonna be good for them. That's not gonna be good for them. So as an open source contributor or an open source project maintainer, you have to acknowledge the fact that some people really want to help you, but they need to be able to do it, right? So you can't control everything. That's a little bit hard. And then finally, relatedness. Like, we just wanna belong. We wanna be part of something. We wanna join this community. We wanna be part of something.  Like, they just wanna feel like they belong and that they're a part of what's going on. And then finally, the F in Scarf is the perceived level of equality across outcomes. So this is a little bit tricky, actually, because it seems like what's fair is obvious, right? What's fair? But it turns out that the idea of something being fair is a completely emotional thing. It's not a rational thing. So some people could say, well, it's not fair that underrepresented groups get all this extra attention and maybe they get a scholarship and I don't. That's not fair. But if you're a part of those underrepresented groups, you might say, it's not fair that we haven't had access to this technology. We haven't been included. Like, we're here, we wanna be seen. So by maybe giving a scholarship to an underrepresented group member, then that now it's fair, right? So there are varying degrees of what's fair and what's not fair. So we just need to be aware of that. Like, what you think is fair and you think is rational and clear, like there are other perspectives around this idea of fairness. And when something is unfair, that's a big deal in our brains. Like, we have a real hard, it's like feeling misunderstood. Something's not fair. Something, if we're misunderstood, like those are two really big hot buttons for us, whether you knew it or not. So, hey, collaborating. It's a complicated thing. You see where I'm going with all this, right? Like, it's getting increasingly more complicated as we go down the line. Yeah, you guys are with me.  Then we're throwing them together in groups. Now we're gonna make them try to do stuff. Oh, and now let's just put it all online because that's so much easier, right? In a way, it is certainly open to, you know, geographical, it takes the geographical limitations away, but it also makes things a little bit harder. So let's look at this really quick. Has anyone seen this online community membership lifecycle? So once you see it, you're kind of like, oh, yeah, I get that. Yeah, I see that, right? But someone actually took it and wrote it out. And I want you to kind of just think about where you fall on this scale. So the first one is the referral. So they're like the lurkers, they're not quite in the community, they're not quite contributing yet, but they're just watching to see how things go. The next one is the inbound. So maybe they've submitted their first poll requests or maybe they've commented on something. They're just starting to participate. The third is the regulars.  They probably come into conferences. Maybe they're starting to go to user groups, but they're regular faces. We all know them. And then you have the leaders who have been around a long time and they just, for whatever reason, have kind of risen to the top or are very well respected in the industry. And then you have kind of the elders, which I don't really like that because I'm probably an elder in PHP anyway. It's like, I'm only 45, I'm not that old, but yeah, so they're kind of like still there, but just kind of, you know, maybe allowing other people to take over, right? So what's interesting is if you look at this and you look at the scarf, the status, the certainty, the autonomy, the relatedness, and the fairness, you can see how it might be different depending on where you are in that life cycle, right? If you're new, then you maybe want some certainty. Like you want to kind of know what you're getting into a little bit more than an elder because they've been around, they already know that stuff and they have all the context already.  Like not all the things may not be important to you all the time. I think if you are, you know, one of those people who likes certainty, you'll always like certainty, but it's just the degree to which that will affect you. So it's something to be really aware of.  There's this thing called the online disinhibition effect. And it's really trying to figure out why we just turn into assholes online, which when we're maybe normal, like awesome people, but online.  So the first one is the whole anonymity, right? Like there are places where you can still be anonymous, which is like good and bad, right? Like it's kind of a toss up. It's a catch 22, but you don't know me. So I can say whatever the hell I want, it doesn't matter. Cause like what are you gonna do about it, right? Like you don't know who I am. So you don't know me. The second one is that you can't see me.  So it's very liberating to just be like on an even playing field with all the other faceless nameless people, right? I can't get judged because I'm a 45 year old mom from Cincinnati, right? Like I can do whatever because you can't see me. The third one is see you later. So it's super easy, as we all know, to drop a comment in on Friday afternoon and then head out and like just let it go and never come back or come back like a couple weeks later and see what kind of destruction you brought while you were gone, right? It's super easy to do that. And there's like no real, you know, no real effect from that.  Number four is it's all in my head. So I can make up whatever I want about who I'm interacting with based on what I've seen. So I could see something that Scott put on a form somewhere and I'd be like, well I bet that guy is this, this, this and this based on the sentence that he wrote. And I can make it be whatever. So I can immediately like either super like him or I can super hate him based on what I've, this world that I've kind of created just without context. Again, like connecting my own dots. I can totally connect my own dots about somebody else just based on, you know, whatever. It's really easy to do that. And therefore I can justify my shitty behavior is what I'm saying. And then number five is it's just a game. Like it's just, it doesn't matter. It's just a game. It's just online. Who cares? Like it's not real life. There's this idea that it's not real life. And then number six is that your rules don't apply here. So you know, there's this kind of like empowerment. Like I can do whatever I want online and you're not the boss of me kind of thing, right? People can just say whatever. It, I think a lot of forums have controls in place to not have that happen, but there are some places where, you know, it's a free for all. And that's kind of why I think we need some sort of rules because if there aren't any, then, then what do we have?  So sometimes you need rules. You just, you need them. One final thing on this. We haven't yet figured out regarding body language. So there are some conflicting research reports about what percentage of communication is attributed to body language over verbal communication. It varies, but we can safely say that it's non-zero, right? Like there is some percent of communication that is non-verbal. And we lose all of that online, whatever that is, we've lost that. Emojis help a little, I guess. You know, put the little smiley, passive aggressive emoji after your comment, but it still doesn't really make up for a face-to-face conversation hanging out with somebody, having a meal with someone, like getting to know them as a person. It doesn't really make up for that.  That's harder. It's making our jobs harder is what I'm saying. So yeah, it's complicated to do things online, and it takes a lot of work. It takes a lot of work. So we have individuals, working groups, collaborating together online. I want you to just kind of keep some of these things in mind, and these slides are up on speaker deck so that you can look through them. I've linked to every single research paper that I referenced here. That's that nerdy that I just like to read like behavioral science research papers in my free time. But it's just super fascinating to me, and it really can help you with your sense of empathy when you realize that there are hundreds of factors affecting why someone's acting the way they are or why people aren't using your open source project or contributing to it, or why someone at work is the way they are. Like there's hundreds of factors. So I hope that you're able to maybe recognize these a little more in ourselves, like mitigate them, because you can actually overcome like we're not cave men. We can overcome our negativity bias, our confirmation bias, all of those things. We can absolutely overcome those. It just takes a little effort, and it takes a little bit of acknowledging that that's what's maybe happening in these situations. So, and I also want to just have everyone just like, let's just give each other a little bit of a break. Like we're pretty hard on each other, so just kind of want to maybe give each other a little bit of a break. I am Elizabeth N. I know it's super confusing because my name is Elizabeth Barron, but I'm Elizabeth N, because I was Elizabeth Narramore. See, see what happened, yeah. Everywhere else. So GitHub, Elizabeth N, Twitter, Elizabeth N, Speaker Deck, Elizabeth N, everything else. So yeah, that's the other lesson here as ladies. When you get married, if you get married and you decide to change your name, nightmare is a nightmare because all your personal branding is gone, right? Just kidding. I don't really care about personal branding. But Elizabeth at GitHub, if you want to chat, say hi, whatever, you need anything at all, I'm here for you. Here are the three pages of reading, like reading that you can do, but it's really interesting. So I hope that you guys got a lot out of it and thank you very much.


Why get them Jays from? What? Jays is clean. You like them? I ain't never even seen those Jays. 13th? Exclusive. Where you get them from? They're fake. I made them. No! How is it great if everybody had a fake pin, Jerry? You know what I'm saying? You remember Shaxx? I'm not fake, I was playing. I had a pair of Shaxx. I had a pair of Shaxx. I had some Shaxx. Yo, that's fair to go, man. I was playing. I was joking. This is real. I was looking at the color wave, I was like, I ain't never seen it. I ain't never seen it. The lake of Jays now.


And now, another tale well calculated to keep you in. What is it like for a man to know his own future and to be able to prepare for his own fatal accident? Listen now to The Time, The Place and The Death, written by Peter Fernandez. There it is again, senor. There it is. Yes, yes, the ace of spades. Never have I seen anything more positive. Three times through the cards and they turn up in the same sequence. This then is a warning to me. A warning? Oh no, senor. This is a fact. This is a prediction of the inevitable. No. But you have seen for yourself three times. Yes, that's true. But to die now in the prime of life in perfect health. Who can dispute fate? I am sorry, senor, but you're fortunate that you know now. Do not question further. Accept. You will be happier. Accept? Happy? To know that very soon I will cease to live? Happy to know that only about two weeks are all that remain to me of this exquisite life? Would you care to go through the cards again, senor? No. No. Thank you. How much do I owe you? No. No charge. Instead, I wish to offer you my deepest sins. Hi, Henry. Good afternoon, Irene. How nice to see you. And on a Tuesday. Tuesday isn't one of your usual days. I trust I'm not causing you any inconvenience by dropping in unexpectedly like this. I'm quite alone, Henry. Good. I have some sensational, some marvelous news for you, my dear. And amusing, I'd say, from that smile you can't quite conceal. My dear Irene, have you ever wondered where and under what circumstances you will die? Henry, what a funny question. I don't intend to be funny. Oh, you know what I mean. Irene, yes, dear.   Everybody dies eventually.  This card, this ace of spades is my proof. This card, this exact card turned up three times this afternoon. Three times following a sequence of other cards which also was revealed three times. It's a fact, Irene.  Oh, my poor, poor Henry. Sympathy? You failed to comprehend, Irene. As a matter of fact, it took me a while to get used to it. But now, don't you see, I've never been happier. How could you possibly be happy? Because I've never been able to face the future. Blindly, I've always sought oracular advice. And I'm happy that I know my death will be soon. Now I must also know the details. The details? Henry, you're giving me the shudder. May I have a pencil and some paper? Yes, yes, of course. When I was 22 years old, it's quite some time ago, I visited my first fortune teller, invest all your money in AT&T. She told me, well, I'd saved about $700 and I invested it. I'm now worth considerably more than that. I know you are, darling. Okay, here's your paper. Thank you. Then there have been numerous romantic interludes during which I've dallied with the temptation of marriage. But in every instance, my dear Irene, I've been saved by a seer. Unfortunately. What are you writing there, Henry? A list. There are so many possibilities of how I'll die. I'd like to consider them. But this is all I have so far. Number one, accident. I mean, no matter how carefully one crosses the streets, these days he risks his life. The strong possibility. Number two, crime. I'm a gentleman of considerable meanness. Oh, yes, indeed, darling. But isn't that list rather unnecessary, Henry?  What an absurd suggestion. Then pay someone to do the job. Irene. Well, frankly, dear, I think you should forget the whole thing. No, I'd better be going and I'll take this list. I can add to the possibilities as they occur to me. Now here, my dear, take this money. Why, Henry? It should be sufficient to buy an attractive dress, which you must wear to my funeral. Well... Good afternoon, Irene. Good afternoon, Henry. In just a moment, we will return for the concluding act of... Here's Hollywood star Mona Freeman. Who feels like acting with a miserable cold? I relieve cold distress the fast way, with four-way cold tablets. Yes, tests of all the leading cold tablets proved four-way fastest acting. Amazing four-way starts in minutes to relieve muscular pains and headache, reduce fever, calm upset stomach, also overcomes irregularity. When a cold strikes, do what I do. Take four-way cold tablets. It's the fast way to relieve nasty cold distress and feel better quickly. Four-way, only 29 cents. Our program will continue in a moment, after a word about another fine product of Grove Laboratories. Head dandruff for years. Now get rid of it in three minutes with Fitch Dandruff Remover Shampoo. Three minutes with Fitch regularly is guaranteed to keep unsightly dandruff away forever. Apply Fitch before wetting hair, rub in one minute, add water, lather one minute, then rinse one minute. Every trace of dandruff goes down the drain. Three minutes with Fitch, embarrassing dandruff's gone. Fitch can also leave hair up to 35% brighter. Get Fitch Dandruff Remover Shampoo today. What's going on? Miss Chippendale. Miss Chippendale. You all right, sir? Come here quick and bring some water. Your gentleman friend had an accident. Oh, my goodness. There's gunning rubies. Please, please. It's all my fault. I should have fixed that step. Please, sir. Is he dead rubies? I don't think so. He told me something like this would happen. Not two minutes ago. He told me. Oh, here, there's water for my vase of flowers. No. His eyes are open. Here, sit. Sit up. Sit up. Oh, thank you. Henry, are you all right? Irene? Yes, dear. Have I died? Oh, thank goodness, no, Henry. Now you see that ace of spades was wrong after all. I don't think it was. It's that fourth step from the land and when the weather is damp, it warps and the edge sticks out a little. Some other people have tripped on that step. Well, then why haven't you fixed it, Rudy? You're the janitor. Oh, I've tried, Miss Chippendale, but the lumber yard was out of the right kind of wood. My list. I don't need it now. I know everything now. I know the place and the circumstances. You do? Yes. I'm going to die as a result of that fault in the stairway. What? Really, Henry? Well, but don't you see, fate has given me a warning. The rest is up to me. I must now fix the date and arrange the details for afterwards, having escaped death once under such miraculous conditions I'll never escape a second time. Well, imagine just an inch or two from that knob. The lumber yard said they're getting a shipment in next week. Then I can fix that step. If you do, my good man, you'll have to answer to me. What? Good afternoon. But it's impossible, Henry. Nobody can foretell the future, except perhaps the weatherman, and you know how accurate he is. Take my advice and forget all about it. Oh, it's your shot. My dear friend, I've received a warning, which I believe. I'm in a very enviable position. I'm now able to arrange a suitable date for my death. It can be any day upon which I decide, and the appointment must be kept. Ah. Oh, good shot, Henry. Tomorrow? No, tomorrow's too soon. But next Friday? Ah, Friday. That would be a fine day on which to die. Next Friday isn't any good, Henry. Why not? That's my usual day for visiting Irene. Oh, but of course, how forgetful of me. Well, I don't wish to die on Saturday. There are too many interesting parties I might attend. Sunday. The day will be Sunday. Perfect. They can bury me on Wednesday. Oh, another good shot, Henry. Now I must see my lawyer about a will at once. I'm leaving almost everything to dear Irene.  Well, I can't leave her penniless. No, no, of course not, of course not. And then I must arrange for the funeral, the burial, so many last-minute details. Perhaps I won't have time ever to see you again, unless you can be in Irene's apartment with her next Sunday for our farewell. Well, I... If that Joseph, I'd like you to be there. At, shall we say, 5.30. I'll descend the stairs to my death at 5.52. Yes, 5.02's always have been benevolent numbers for me. Uh, yes, yes. I'll be there, my dear Henry. And on Wednesday, of course, you'll attend my funeral. Of course, of course. And, uh, I shall mourn for you deeply. Splendid, the funeral will be at 3 o'clock. Oh, 3 o'clock? Oh, but, but, but Henry, that's the afternoon they'll be judging the terriers of the Westminster. And I've registered both Tristan and Esaulder. Oh, no, no, no, I'm, I'm, I'm very sorry, but I, I just can't. I am sorry too, Joseph, but at least can I expect you to be at Irene's on Sunday? On Sunday? Oh, yes, Henry, yes. I shall be there. Good evening, Irene. Joseph, it's so late. Oh, may, may I come in? Of course. Oh, my darling Joseph. Irene, my love. I'm so very glad to see you. Irene, I just left Henry. He thinks he's going to die. I know all about it. Another one of his fortunes. But, but, he's going to make all the arrangements. He, he actually believes it. Well, it's possible, you know, I've heard of stranger things. But, but, Dear, it's, dear, Hold me, Joseph. Hold me closely. Yes, yes, yes. Like this. Mmm. Now, uh, uh, listen to me, Irene. Mmm. When Henry dies, he'll leave all his money to you. How, how do you know that?  When he dies, you'll be a rich woman, Irene.  You're sure I need his money as much as you do I'm going to make sure. On the day he has planned for his death.  Oh Joe. How poison. He will come here to the send those stairs we will have a drink a final sat there well drink his will be well laced with. The police will know that his ring was poison of course good that's what we want because he will have made all those preparations they will decide that committed suicide. There'll be no way for them to know otherwise. What do you think now I think my darling that you and I will both some day soon be very very well. Yes sir is there some way I can help you or would you rather look around I wish to order one of these yes sir is there any special kind of wood you desire if only I knew what kind of wood that stairway is made of that might be rather suitable. But it too might work I desire a mahogany I'll just write this down. Yes and the trimming Sir Silver I want a first class general very well two thousand dollars certainly will take care of everything so excellent I'll make you out of check for the amount right now that's perfectly all right so just a deposit will be sufficient you can mail the balance to us later but I won't be able to later you see the coffin in the service are for myself. That's a great joke I am not joking I am dying on Sunday I want to be buried next Wednesday I believe you're serious sir I assure you I am forgive me I understand goodbye you'll be given a magnificent send off a good bye sir and good luck. Sir may I help you wait let me make a guess I'd say that you're a man searching for an exquisite put on air I wish to order a floral reef. Oh yes sir it is to have a diameter of five feet yes sir five with a blue ribbon blue blue and the flowers are to be orchids orchids on a week it's my favorite flower the reef will be delivered next Monday to the address on this card now about the inscription yes yes on the ribbon it's to say to myself sincerely make a point no no no no change that to read to myself with great love oh yes perhaps there is nobody who thinks as highly of me as I do no sir yes I'll take the put on air now the black one I shall miss myself should be here any moment if I know and he's never late no here here's the capsule with the arsenic. Oh it looks so harmless doesn't it. Now when he comes in offer him this drink then break this capsule with your finger there right here and pour all of the contents into his glass.  Such a little thing. Think of tomorrow darling think of all his money. That's all I thought of years. There he is then quick put this next to the liquor bottle yes. How is it good good good you'll never know this answer. Nothing to it as soon as he drinks the arsenic we'll just call the police and it will all be over. Good afternoon Irene hello Henry come in my dear thank you and you said I'm so pleased that you could arrange to be here and no Henry get down to you thank you. You're looking very well Henry certainly not like a man who's spending the last few minutes of his life it's a beautiful day Joseph and I had a delightful lunch earlier.  Don't leave I must. Think of what you're doing to me. What will become of me. I'll be so lonely when you're gone. Oh there there I mean. As for being lonely I'm sure Joseph will be pleased to add another usual night to his schedule. Oh yes of course of course now aren't you feeling better dear. Yes yes much. But Henry there is one thing more before you go one last favor to me name it my dear here's a drink Henry I want us to have a last drink together you need to have enough to spoil your death no there isn't time it's now five forty nine I've never been late for an appointment in my life I have only three more minutes I must go and Joseph thank you for the many games of billiards for the fine friendship of all these years that would be sure to send me a spray of orchids on when Henry I insist that you have a drink with us now well Joseph Henry this is it yes yes I can see that step the fourth from the bottom now it'll be such a perfect funeral and that cemetery plot eternal beauty there a perfect life and now a perfect death the next one is the next step I'll close my eyes and step off into space goodbye goodbye beautiful world good heavens you made it okay you fix that step I did not I got the word but today's Sunday I don't work on Sunday then the step is no longer walk it's just the same as the day you fell but you were so careful today even when you shut your eyes I stood over there watching you you didn't trip even a little you went so carefully that I can read you're all right you're not dead dead no Joseph but then nothing happened oh I saw images of my childhood my whole past flashed before me and then I realized that this afternoon just now I escaped my own death that's true and now don't you see now I shall live forever oh no well this certainly calls for a celebration Henry from now on every day will be a celebration here's your drink and thank you Irene yes there's something I must do first before anything else so what's that I must telephone I'll put my drink down right here and it won't take a moment but Henry I'd like to propose a toast to you well then go right ahead Joseph it would be bad luck for me to drink my own toast but Henry hello this is the funeral directors Henry Perth Johnson you're expecting my body in a short while well I've decided to cancel all the arrangements yes that's right and no I didn't die and no I'm in the best of health next week no my good man canceled it permanently thank you Henry Henry now wait Joseph before you make a toast to me I would like to propose one to both of you I mean do something it mustn't happen no Henry what's the matter here give me that class I'll make a fresh drink for you touch this drink yet a toast give it to me Henry please why is there something wrong with it oh no no no it is just a strange smell to this drink reminiscent of gardens in summer and rose arbors and now I recognize it arsenic decidedly surely you realize that I cannot die now under any circumstances yes we really here you are Henry a fresh drink and I'll take that glass thank you Henry sweet sweet Henry will you ever be able to forgive forgive I've already forgotten do you Irene and you Joseph my closest and my dearest friend you've been listening to the time the place and the debt written for suspense by Peter Fernandez in a moment the names of our players in the word about next week's story of suspense are you out of tune due to irregularity then help yourself get back into him with Kellogg's all-brand pleasant isn't it the feeling of well-being you get when constipation from lack of bulk is no longer a worry when harsh irritating drug laxatives can be thrown away because Kellogg's all-brand is the normal natural way to regularity its whole brand content gentles away constipation supplies your system with the bulk-forming foods you need for youth for regularity and it tastes good too fact is Kellogg's all-brand is the one and only whole brand cereal that combines proved effectiveness with appetizing taste and Christmas so if you're out of tune help yourself get back in tune as millions do with Kellogg's all-brand a double l-hyphen vran Kellogg's all-brand heard in tonight's story were Eric Dressler as Henry Claudia Morgan as Irene and Mercer MacLeod as Joseph others in our cast included Brina Rayburn Maurice Tarplin Peter Fernandez and Dwight Weist listen again next week when we return with turnabout written for suspense by J Bennett another tale well calculated to keep you in


Wow So wow I haven't tried with the Liberian English. Okay, so it's Well see ok But when you hear it It sounds like Like What language is that? It's It's like very English So it's very rare to like very will never hear another Oh Breakdown like that ever again in Africa I'm so happy to be here because I've learned something new today But you know what I'm sure You're so hungry So we're gonna give you some Now like here we don't have for a sake one dish Because Liberian We are playing debate in our pool All the other bad stories you hear You can't touch Liberian food Back So we eat If you get a pot of chicken, beef and seafood In one pot And I didn't know that wasn't a thing until I was in Ghana You have pork soup, you have beef soup You have chicken soup We cook everything together We season very well and we're known for our pepper Liberia was Yeah, Liberia was once part of the pepper post The pepper post was something that It still exists But we're known for hot, hot, hot pepper So if you're ready for the flames The spice I'm so ready I need water So I just can't wait to eat Just take me where We're gonna take you in here It's like you're getting cooking for your mom's kitchen So you see back here You'll see the big pot top And it's honestly the best cooking Liberian food you can get So right here in this alley You're gonna get some of the best Gains, Tava Ghee, dry rice Tala green, all Liberian stuff Right here I'm gonna sit down for them to bring the food on We're gonna order it up here at the station They're gonna raise the table It's easy to be full For the rest of your day Thank you so much So Rebecca, what you got on the menu today? I get beans, Tava Ghee, dry rice And dry rice Okay, so what are you gonna try? Like hearing dish that you should try Is beans Tava Ghee And it has a very light hearing dish I want a typical authentic Liberian dish Beans Tava Ghee Alright, so we'll have beans Tava Ghee We'll have dry rice This is my favorite Tava Ghee I just said Lama Ghee Wake up and eat this at 7 o'clock in the morning For breakfast This is a full breakfast meal I hope you can, after you eat this meal You'll be able to go out and do more filming I think you may need a nap I hope I don't sleep So right here we have Two Liberian dishes So you wanted to taste Liberian dishes Stuff or eat Okay, so it's this Kind of sauce It's a little bitter But this is beans Tava Ghee If you tell a Liberian I have Tava Ghee They'll be excited If you tell somebody we have beans Tava Ghee Take it to a whole new level Because it's like the favorite dish One of the most favorite dishes in Liberia With beans added on it So that means their stomachs will be full There's sustenance So until I move back Liberians are one of the few people That put multiple different types of beans In one pot So you'll probably find chicken Beef Dry fish All kinds of different meats in there It's like a palm nut soup That's how it looks like Let's taste it What is the right way? Anyway You can dump the soup on there You can scoop the rice Then we have dry rice over here Which is another Liberian dish We've got the gravy here We have fenasi Which is roasted Sunflowers that they grind down It makes this very nice sauce We've got fried fish Slantine pepper Palm oil It's like a plethora of greatness Dry rice Let's try it out Let me try this one You don't need my opinion Because it's my food So I'm going to be naughty I've been eating a lot of beans It's a pretty hot thing Oh my goodness I wasn't ready for that I have a peanut allergy You put peanut butter In our salad It's so good Apart from being spicy Palm oil A lot of our food is palm oil So you even add Palm oil It's not the most healthy thing But it's delicious You can make it fried Or you can make it with red oil Palm oil You always make everything with pepper I don't want to go for this again Time Let's try the dry rice That's not going to be too spicy I'm sweating It's so good I really love the taste It's the pepper Can you talk about the Ganyan Slough? This is not too much My parents might eat the most amount of pepper It's too spicy You guys have no idea what I'm saying Too spicy What? I put my like this one I'm not saying I don't like it I love it but the pepper is too much So this is dry rice It's a medley of things We usually eat it on Saturday So if we go to restaurants on Saturday We call it dry rice Saturday My parents like to eat certain dishes on certain dates So dry rice is usually reserved for Saturday But it should be on an everyday menu Because it's one of my favorites Delicious That's red oil If you watch my videos I love fish I love any kind of protein This one contains a lot of protein Because you have the egg The sausage, the fish The red oil combination And it's like pepper Really red pepper My parents don't know how to make pepper sauce Wow So they take the hot peppers The plant pepper Oil it down Make it soft enough to mash into a sauce And they bottle it up And they put pepper in every dishes But then they take the pepper sauce And pile it on top That pepper cooks in it Not even pepper sauce added onto it Laverins are known for burning their mouths You can see them eating They'll be sweating All their sinuses will be clear But they'll still be eating And it'll be so good Clear all your sinuses Clear all your sinuses This is so delicious This one is so good It's one of my favorites I'm not gonna lie I knew it would be You guys If you have never been to Liberia I'm not gonna lie to you This is what you've been missing This in the morning I'm not going anywhere I don't eat it in the morning I reserve it for Dinner time, lunch time People come to work every morning And their breakfast is A bowl this size And it's part of the culture It's part of the culture And I'm glad that I became part of this culture Because this is just a food That if you don't eat this This is what you're missing I wish I could show you how to cook it And you can cook this in your various homes Because of all my work No, that's not a lot I'm not used to it Go ahead Get rid of the spoon Do it the right way When you eat with your hand It's just good To communicate with your hand And your mouth It's all parts of working together To get to a common goal What is the name again? Dry rice And everybody has different ways of making it Some people make it with corned beef With the rice You can add okra You can add grape You can add pepper You can add chicken Fried fish You know the egg Everybody has their spin to their recipes But this is the basis of it And it's really just a medley Of all the things that make Africa great I personally like to put okra in mine Another thing I don't know If they eat it anywhere else But venice They grind them into Kind of like a powdery spice And it can be added on kufu It can be added on dry rice It adds a special taste to everything Yeah, this is definitely My very traditional meal You just taste it You got the pepper, you got pepper to death Which happens all the time But then you got I'm gonna challenge myself I know I don't have enough time here I'm gonna try this one Do it again Ok, we got to do it with the hands Let's say a prayer Is the last pepper with the hands? Same amount of pepper I told you, the hand Dissolve everything I felt the pepper so much Because I was using the spoon This is why you need to try using your hand to eat Lying to you guys This is the kind of baby I hope you guys enjoy this amazing episode I'm gonna see you in the next one Don't forget to go check out the youtube channel Go subscribe How many subscribers do you have now? Four thousand Four thousand Let's get to ten thousand subscribers Let's get you more water


Good afternoon, everyone. I am Mohit. I work at Red Hat. I'm a senior software engineer there and I'm based out of India. So today, the topic we are focusing mostly on how to integrate the OpenShift integration with Visual Studio Code. As a normal developer, we have an idea to integrate different IDs, different command line integrations, and work with every other terminals inside our development scenarios. So as a normal developer, if I need to work on Kubernetes or say I need to work on OpenShift, I need to memorize a lot of commands and I have to work them on this different CLIs. Then again, I have to say deploy a Java application onto that OpenShift instance. I need to go ahead and code my Java scenarios in any ID, and then I have to deploy it back to the OpenShift cluster. So it's a two-and-fro scenario. So in this talk, I will be explaining that how to integrate the seamless experience for a developer, everything can be directly done and integrated using a VS Code Editor. So say you have a scratch VS Code Editor. VS Code Editor is basically from Microsoft and it's open source. So you just install a VS Code Editor, nothing is there and from Red Hat, we have developed an extension which basically integrates OpenShift into it. So you go to a Visual Studio Marketplace, you download that extension and you start working onto it. So basically today my talk will be more on the demo side that how things are working and less on the slides. So let's move on. So what problem are we going to solve here? So there's a scenario for a developer that, okay, it works on my machine, but it's not working on your scenario, then how we tackle it? So when everything is on the Cloud, you know if something is not working for you, it's not working for others because it's already there. So we are targeting solving that. So now for OpenShift, we have different clusters. Now one cluster can perform different operations. So we have a cluster which does a game scenario, which has a back-end on MongoDB and a front-end on, say, any web application, Angular, React, whatever it is. We have a different cluster which caters to Node and other cluster which caters to Java or say Go or Ruby or Python, whatever you have. So all those clusters can be seamlessly integrated at one place so the developer need not worry about what clusters is present at what scenario. And now after deploying those changes, now we make others changes into the code, we merge different PRs, we add fixed different issues. Now how to deploy those changes quickly to the OpenShift instance? This extension will help you do that with one push and whatever push is there, you can just watch the changes and that will be giving you all the logs directly into your editor. You will not go to a different command line to see what are the logs, what is failing, how the Jenkins is reacting to those logs. So everything at one place. So what OpenShift solution provides is, you can have a say S2Y image basically from a base image so that can be a Java, that can be a node, any application which you want. That can be from your local or say workspace folder which is there or even any code which is deployed on your GitHub. So directly first that code, deploy onto your OpenShift instance, make changes, push that code and everything is deployed at the end. And the last one is even you can do it from any say, you have a tar file which does all these scenarios. So you need not worry about do I have a source image or do I have a Git repository? Even if you have a tar file to it, just press that to it and that cluster will be up and everything will be running. So now from Red Hat has different extensions for VS code. So this one is basically OpenShift connector and this is available at Marketplace. I will be showing you how this works. The second extension which we have is basically an extension pack. That extension pack does is you have this OpenShift connector, you have different Java debuggers, you have different Maven plugins and those basically get integrated into it. So say you want to do a Spring Boot application from scratch to end. So everything can be done just installing that extension and moving forward. So this is the scenario how things are. You write your code in VS code, whichever language you prefer. You deploy that into OpenShift using the extension. Now once that code is deployed, whatever changes you make, whatever scenarios are there, just do a push and those changes will be automatically redeployed to that cluster. So for this we are using local instance of OpenShift. So right now we are using MiniShift which is running a local OpenShift cluster that is our open source and even we support the dedicated OpenShift premises which can be there. The second is CLI tool and the third one is OpenShift do tool which basically is at the back end which does all those operations. VS code is the front layer which performs all the operation but at the back end we have OpenShift do tool which performs all those push, watch, the lock changes, whatever cluster is there. You need to describe the cluster, what type of cluster is there. So everything on that. So let's go ahead and do a quick demo. Right now I'll directly go to how the different linking between the service and component works so that later on I can explain that how things are and how seamless this experience can be. So I'll just move the recording a bit ahead. So if you see this is a Git repository for a front end application. So I will use this Git repository to create my component. I'm not using a source image I'm not using a tar file. As I mentioned earlier, these are different scenarios. So right now I'm using this Git repository to create the front end. The idea behind this game is to have a Node.js front end which is using this open source phaser JavaScript on game engine and the Spring Boot back end application which uses the Red Hat OpenShift Java API to connect with Kubernetes and OpenShift. The back end service written in Spring Boot lists all the platform objects which we have running in our project. And the goal of the game is to shoot them and destroy them. Those objects can be different build conflicts, different pods, deployment conflicts, services, routes. And as we can see when we end this demo. So let's move back to VS code and go ahead and create a component for Spring Boot. For that I have this Git repository present in my local workspace. So go to the terminal in VS. So now the front end was created using a Git repository. Now the back end will be created for my local workspace. So right now I'm demoing difference in ways you can do it. Even you can have this repository and GitHub and just clone it and make it working as a component in your service. But right now I'm just showing it from my local workspace. And I built the binary for it. So NVN package. So this will start the build. So as you can see, I need not switch any different CLIs on any other instance to run this from my workspace. Everything is done directly from VS code. So you see the build is success. We have got that jar file. So let's go back to the OpenShift extension. In my application, I go ahead and I create new component. So there are three different ways to create components. One can be directly used to using a Git repository. One can be used using a binary file and one can be used from the local workspace. So right now as we have already created a binary file. So let's go ahead and use that. So once we select that, it asks us to select this binary. So we go to a target folder and we see this jar is already there. We select that jar and we say, okay. So now we need to name the component. So we name it Wild West backend. What is the component type? So it's a Spring Boot application. So we select Java. So now when you see these are the different component types. So when I started the cluster, I showed you there, you can list the components or you can list the services which are there. So these component types are basically what is enabled in your cluster. So some clusters will have many component types. Some of the cluster will have non-component types. So dependent upon your cluster and its environment, these things will be listed down. So for my instance, I have all the components being installed already into my local MiniShift instance. So that is why it showed me a pop-up mentioning that I can select a Spring Boot, I can select a Node, I can select any other component type. We select latest for the component type version. And now you can see the component Wild West is successfully created. So if you see here, this component is already created. So the next thing is to create a fronted application, which is in Node.js. So we go back to this repository and we just clone the Git, we go to the application, we again do a new component. This time we'll be directly using the Git repository. If this repository already there in our local workspace, I can also use that. But for this demo, we are using Git repository, we paste the URL, we name it Wild West frontend. And there's a Node.js application, the type of the select latest for the component type. And now it asks us, do you want to clone the Git repository for the created component? So for this demo, we will say no. And as soon as the component is getting started, you can see whatever changes which are needed for the push is there on the terminal. So we did not switch to the OpenShift console, go to the application, see the deployment configs and see what builds are running, what are the steps which are being performed. So all the logs can be directly seen on the VS Code terminal and whatever changes we want to do, we can do parallely in the workspace and the build will be running. So whatever deployment is there for the... So now let's wait for the build to finish so that we can link these two components and see the game working. So now you can see this component is created on port this and this is set as an active component. So now as we have two different components here running, let's go ahead and describe this component. So here if you see, there are different scenarios which are listed. So you can describe that component, you can see the logs which are running, you can even create a URL for that, basically creating a route for that component and even making those changes you can push, you can watch and even open that, say if you have a node, just a web interface, simple web interface, you can just directly open that into a browser. So everything basically from a developer perspective is done directly inside this editor and whatever open shift scenarios you need to cover can be done through this. This is basically the front end component. So once we describe that, we can see this is the component is of type node js and this is the git repository source and when we describe the backend component that basically tells us it's a Java component with sources directly taken from the binary file. So whatever information we need for that component or an application can be directly done from the UI itself. So now the next step is to link these two components together. So we go ahead and do link component. So as we all only have one X different components, so the pop-up basically lists us, okay, do we need to link the wild-based backend? So we select this, we want to link this and now we have to select which port are we doing this. So the UI here is pretty smart here so that if you have say multiple services running or multiple components running and if you want to link one component, it will figure out that, okay, which component needs to be linked to that or which service needs to be linked to that so that the developer need not worry, okay, what type of service has to be integrated there. We select port 8080, front end. So now after this, the linking between the back end of the front end is done. Let's move to see how the game basically developed. So now an application in the browser. So for that we need to create a route. So once we go and open that in the browser, VS Code asks us to create the route automatically and it will open the browser. The other way is to directly create a URL from here and then open it in browser. So we'll directly go ahead and open in browser. It asks that there is no route created, should we go ahead and create it? We say yes. Once the route is created, the application will definitely open in the browser and you can see now the front end and the back end are linked and this is the game which loads. Now the user can play this game and click on this. This is how the... So basically this game is basically shooting all those parts or all those routes which you have into a service. So the front end is basically the component which we had and the back end is basically at the meantime creating those routes and meantime whatever service you are getting, killing, those are getting into the back end and being done synchronously. So this basically gives an example that how you can integrate different front end and back end application, do some changes, deploy it in OpenShift within few minutes and everything is up and running directly from your editor. And this basically is the experience which you want to give the developers. All the changes from the OpenShift extension. So the only thing you need to do is just install VS Code, go to the marketplace and install that extension and that's it. And this is for developers who are writing in say, I'm a Java developer and I want to code in Java. It works for me. But if say if someone else is a developer who is very fluent in Node, it works for him the seamless way. And in the future we are also supporting different languages like Go, Ruby, Python. Everything which is out of the box will be supported directly with this extension. So it is nothing specific to a language. It is just specific to whatever the developer prefers and wants to integrate that with the OpenShift instance. So this is it for the demo. If you have any questions, any curiosity for that, let me know. So this is the GitHub link for the Odo tool which we are using at the back end and this is for the link for the marketplace where this is OpenShift connected there. So pretty easy experience which you want to give to the developers because things are changing pretty quickly and everyone wants to integrate things with their OpenShift or Kube clusters. So this is how Red Hat is helping the developers onto that. So, another question, yeah? Yeah, so the question he has is if we make any changes to my backend or say my Java application, how Odo does that and how VS code implement it? So right now your Java component created is basically a component, right? Whatever changes you make to an editor it automatically saves and it automatically does a new push and those push are automatically being done at the back end. So as a developer you need not worry that you need to again get a tar file and again do a deployment. That push will automatically be running at the back end. Yeah, that image has, yeah. Yeah, that image has that capability to whatever changes are there, it looks at the watch and as soon as there are changes it runs a new build and that build again will be integrated to that front end and things will move. Yeah, new push is always there whenever you make some changes at the back end or even at the front end. Yeah, basically that scenario you have say 0.1 jar whenever when you new push that jar is replaced by the new one and that things works. Yeah, so whatever changes there in the backend side for the component side or service side is done by Odo and VS code does integrate that from the developer perspective. So your question is does it support only container-based or you can do a VM-based deployment also on that? So I would say if you have your application or any scenario in your OpenShift cluster if it is running onto that cluster this extension will support that. Yes, yes, thank you.


Good morning friends, I am Purva and today we will discuss the following question. Let vector A is equal to i cap plus 4 j cap plus 2 k cap, vector B is equal to 3 i cap minus 2 j cap plus 7 k cap and vector C is equal to 2 i cap minus j cap plus 4 k cap. Find a vector vector D which is perpendicular to both vector A and vector B and vector C dot vector D is equal to 15. Let us now begin with the solution. Now let vector D is equal to D 1 i cap plus D 2 j cap plus D 3 k cap B perpendicular to vector A and vector B. Now since vector D is perpendicular to vector A, therefore we have vector D dot vector A is equal to 0. This implies vector D is D 1 i cap plus D 2 j cap plus D 3 k cap dot vector A is i cap plus 4 j cap plus 2 k cap is equal to 0. This implies D 1 into 1 is D 1 plus D 2 into 4 is 4 D 2 plus D 3 into 2 is 2 D 3 is equal to 0. We mark this as equation 1. Now again since vector D is perpendicular to vector B, therefore we have vector D dot vector B is equal to 0. This implies now vector D is D 1 i cap plus D 2 j cap plus D 3 k cap dot vector B is 3 i cap minus 2 j cap plus 7 k cap and this is equal to 0. This implies D 1 into 3 is 3 D 1, D 2 into minus 2 is minus 2 D 2 and D 3 into 7 gives plus 7 D 3 is equal to 0. We mark this as equation 2. We are also given that vector C dot vector D is equal to 15. Now vector C is equal to 2 i cap minus j cap plus 4 k cap dot vector D is D 1 i cap plus D 2 j cap plus D 3 k cap is equal to 15. Now this implies 2 into D 1 gives 2 D 1 minus 1 into D 2 gives minus D 2 and 4 into D 3 gives plus 4 D 3 is equal to 15. We mark this as equation 3. Now solving equation 1 and 2 using cross-multiplication method we get D 1 upon 28 plus 4 is equal to D 2 upon 6 minus 7 is equal to D 3 upon minus 2 minus 12 and so we get D 1 upon 32 is equal to D 2 upon minus 1 which is equal to D 3 upon minus 14 and this is equal to say some lambda and this implies D 1 is equal to 32 lambda D 2 is equal to minus lambda and D 3 is equal to minus 14 lambda now substituting these values of D 1 D 2 and D 3 in equation 3 we get 2 into 32 lambda plus lambda plus 4 into minus 14 lambda is equal to 15 this implies 64 lambda plus lambda minus 56 lambda is equal to 15 this further implies 9 lambda is equal to 15 which implies lambda is equal to 15 upon 9 and we get this implies lambda is equal to 5 upon 3 now D 1 is equal to 32 lambda so we get this implies D 1 is equal to 32 into 5 by 3 since lambda is equal to 5 by 3 and this implies D 1 is equal to 160 upon 3 D 2 is equal to minus lambda so we get this implies D 2 is equal to minus 5 upon 3 and D 3 is equal to minus 14 lambda so we get this implies D 3 is equal to minus 14 into 5 by 3 which implies D 3 is equal to minus 70 upon 3 therefore the required vector D is equal to 160 upon 3 i cap minus 5 upon 3 j cap minus 70 upon 3 k cap hence we write our answer as 1 upon 3 into 160 i cap minus 5 j cap plus 70 k cap hope you have understood the solution bye and take care