Hey everybody, this is trucking van life. I mean my boy Arlen or trucking across the United States We're watching Trucker Josh Vlogs with Josh, Brittney, Diesel, Chevy, Frankie, Peter And now we're going to watch Baker, Diesel, Diesel On this vlog today, the Lord himself has joined us this week on the road And how does it make you feel Diesel? It makes me feel fantastic. It makes me feel important. It makes me feel loved It makes me feel very happy. Look at my tail. Anything else? It also makes me miss mom. I'm a little sad for Josh Mostly happy. It's going to be a good day, man. Good morning everybody. You guys remember that throne I had built for Diesel When we were doing city work and that Peter built the little daycap Well, I kept that little platform that I made. It was a little bit of junky It was sort of made of junk wood and I sort of just threw it together But it worked. Right? It worked good. And it continues to work for us Look at this. Diesel, go check it out.  A little while ago, super soft Underneath there, there's two more blankets. So it's like super soft. It's fit for a king Fit for a lord. Diesel, you want to go show them your bed? Come on. Up up. Come on. Come here. Come here, buddy I was just comfy, man. I just got comfy, thank you, mom Want to go in your seat in the front?  Go show them what it's like It's comfy up there. It's okay. I know there's not a lot of room in here Go on, buddy.  Look at that throne, man Isn't it nice? It's very nice. My dad built it for me with his own two hands He's a wizard.  You're a good guy to look at, man Easy on your eyes Well, I'm a lot to look at. I'll tell you that I'll agree with that one So now he can lay out this way You know before he used to always have his front paws on the ground And the seat was just way too small for him to sit on Now he can lay straight across here I noticed on the way down here, we're here in Carmen again There's a line up of trucks That's my uncle Rudy There's Mike over there And I can't tell who's back there yet There's a bunch of trucks there But on the way down here anyways He would lay down just across the bed here and he'd just rest his chin On that ledge down there, right? And look out the window He's very tired though. I woke him up and he was I know you were all comfy back there buddy But I wanted you to show him your bed This week we're doing more of these pipes More of a... See him right there beside Uncle Rudy's truck Some over here We're going to Buxton, North Dakota Which is just south of Grand Forks It's not as long of a drive It's gonna be a bit of a shorter day today But that's okay. I can enjoy some time with the weasel here then And we'll be back here I'm thinking tonight Once again I gotta wait for confirmation until this afternoon But we're still gonna be busy with this pipe yet until the ground freezes We've had a couple of frosts come in So I don't know how much longer We'll be running here but we'll be running our tails off until then At one of my Thanksgiving gatherings this past weekend It was Canadian Thanksgiving so we had a gathering On Saturday, on Sunday and on Monday Lots of food, I ate so much It was all so delicious But all right, Mary on Britside Reminded me that last year at Thanksgiving We had like a foot of snow on the ground Look at it now, right? Much better this year You still got some green in that grass there See that? Little bit of green, there's some trees Still have some trees over there Still have some green leaves So all in all this year has been a lot better than last year I forgot that we had snow that early We had a lot of snow last year And then some flooding in spring because of all of it So we don't need so much snow this year I'd settle for a white Christmas Just get it all on the ground A couple of feet of snow right before Christmas Let's all enjoy the Christmas holidays And then, you know, it could be gone by New Year's And I wouldn't care My trailer looks much like this right behind me I have exactly the same thing 53 foot step deck Same thing you've been seeing in my videos For the past little while These are my favorite kind of trailers to pull You see, Mike over there has another one just like mine And I believe Pedro's a little bit behind today I think he had something to get done this morning But he's gonna be here soon from what I heard It might be out of here by then It doesn't take too long to get us loaded It's gonna be bam bam bam And we'll be on the road All loaded up with our rolls Diesel, you ready to do some trucking?  You hungry?  Those down here You got some water in there still That's good That's good Pull this out of here There we go Oh, you excited? Yeah Breakfast time, man Breakfast of champions Yeah, grab me a good old scoop out of there You bet It's gonna be good, man It's gonna be good Let me finish it, okay? I always make it into a little soup for him It's easier on his old gums and teeth that way Should I throw that in there? So we just Put a little bit of water in there Soften it up a bit for him Throw that out Over here We always give our dogs salmon oil With every meal How many squirts am I supposed to give? 16 year... Three pumps Three of them Holy smokes There you go He loves that stuff And then Where is it? Where did I put it? Dude, here it is A little bit of seasoning On top He likes his meals to be seasoned with liver Yeah, man, you wanna try some of that? Is that the good stuff? Yeah Man, you've gotten old That's not a problem though You've just gotten so much more calm than you used to It's a good kind of old It's a mature, distinguished, gentlemanly old He's a good boy I just sprinkle some of this on here There we go And then I won't move the truck until he's done eating Otherwise it sloshes around on him So in the meantime I'm gonna grab my phone Make sure I'm on off duty I think I've changed my duty status Of course I did There we go All right, Diesel It's all yours, man Go for it Go for it, bud The truck's a little bit small, but we make it work There you go Oh, yes Yes, look at that tail wag And that's the good stuff, right? That's the good stuff Mom made sure I packed all the good stuff Which reminds me I forgot to add something in there We also give them glucosamine supplements every morning Yeah, I got these too I almost forgot, man Six of them One, two, three One, five, six There you go Add those in there Yeah Helps with his joints That's the good stuff All right And then while he eats I just surf through YouTube or TikTok If I can remember where I put my phone I just got it off sitting on it There we go So it is a little tight in here He doesn't come with me on every trip now Some trips he stays home with his family But I figured it's a short week this week We got Tuesday to Friday here He hasn't been with me in a couple of weeks Eh, just felt right All right As soon as he's done his breakfast down there We'll get him up on his throne And we'll make our way down to Buxton We got a lot of time today It's a two and a half hour drive down there And a two and a half hour drive back Y'all done there? Got it all?  You guys ready for this?  I always love family gatherings I love the holidays The next big one is Christmas, obviously But first we have Remembrance Day So it's not too carried away But I'm very excited about Christmas Ah, a lot of good food A lot of good food But it's always good to get back on the truck And get the wheels rolling again Feels good Feels right You liking your throne, Diesel? I made it just for you That is a throne for a weasel Only But you might have to share it with Chevy For one trip, maybe Maybe, probably not But maybe, is that okay? I guess so It's the only time you're moising him You know That's good We have to learn to share, right?  He's very protective of Britt And he doesn't like the truck as much He didn't grow up on the road Diesel here grew up on the road with me As all of you know And he loves going on the truck As long as he's got a nice comfortable spot to lay like this But I'd like to take Chevy sometime too Maybe for my own selfish desires But I'd like to spend some time with him too Maybe he's gotten over his Dislike of highway You don't know unless you take him on a short one Alright, so one of these days I'll take Chevy on a short one See how he likes it now It's not that he hated it I can just tell he'd rather be at home Stretched out on his bed But now we've got a bed in here, right Diesel? Got a big bed here Got another bed here This one's just for you Okay Alright Alright Just gonna plug this bad boy in here Oops Gotta make sure that I have an auxiliary cable here That plugs into my stereo This truck's a little older It doesn't have bluetooth And if it does, I haven't figured it out I want to get a new deck in here yet That has bluetooth capabilities We'll hold off on that a little bit I want to get a nice one that comes out A little bit But it might block that Maybe... I don't know We'll figure it out I don't want to put a sound system in here yet A couple of subwoofers in the back I don't want to be that guy who pulls up To the stoplight rattling in your license plate Not that But a couple of subwoofers Just for a nice full sound This auxiliary cord is getting old already That's why I want that bluetooth So bad, but... I want a nice full body sound I want a good stereo in here Okay My paperwork's actually cleared at the border already So we're ready to rock and roll His hose likes to settle On the flatbed So we'll go about 15 minutes down the road I'll stop and pull over there And make sure it's all good to go We'll probably be back here before the sun goes down Unless I stop in Grand Forks to Hang out Maybe we'll go for a walk There is a turn approaching Izzy Street here Wow We haven't been watching my video for the past A little while This is Karman It's where we started our days recently Small town in south-central Manitoba Straight south here Is eastern North Dakota Give you a little bit of a sense of where I am We're gonna go down interstate 29 Look at this, they're doing something here They've got a big old crane Diesel, what do you think that is, man? What are they doing out there? Looking at that diesel? About one, two, three, four, five Including the guy at the window in front of me The line-up's not too bad today It's about average Maybe a little shorter an average, actually I've only been here for three minutes And it's moving pretty steady Weasel You ready to go visit America? America Right, Diesel? The United States Of America You ready? I was born ready, man I was born for this Super excited I'm gonna ride an eagle, man I'm gonna catch one and I'm gonna ride him You do that, bud I trust you You have fun I'm gonna tell them all about my pet goose What? You have a pet goose? Yeah, man Every Canadian does, don't they? They have a pet goose Oh, we're kicking I don't know what you're talking about, Diesel We're not going very far I've only got 160 kilometers left to go That's about Exactly 100 miles We'll go 100 miles into the US And then turn around and come back It is a bit of a short trip But I know the questions are coming in In my comments section already And yes, it is worth it for us It is worth it It's actually a It's a nice trip to have I'll see you guys on the other side There it is, Diesel, how's it feel? Hoped and dreamed it would be You haven't been to the US in a while How is it? It's wonderful, man North Dakota, be legendary They're talking to you, Diesel I know you don't gotta try very hard But you gotta remember In North Dakota, you gotta be legendary I say that every time I am below we do I only know how to do that I only do legendary Only Maybe I should have been in North Dakota You're pretty close You're a Manitoban Which is almost the same thing Very little Just a little difference over there I told you guys in a video last week This is Pembina, North Dakota It's the border town Up here in the northern part of the country This is the oldest settlement In North Dakota Settled in 17 something Used to be like a trading post On the Red River They actually came down from What is now Canada And settled this here As a trade route going north They didn't want to go Much further south in here Cause there was a hostile tribes The Sioux South of here Okay Mr. Grainholler I might pass you But you keep fluctuating He's going slower than faster Slower than faster I know that as soon as I pull out to pass him He's gonna want to go faster So I'm just waiting if you'll See if he'll do it on his own There's a bus Some space to move in here anyway I bet you this bus is gonna go fast They usually want to go fast So I'm gonna slow down I'm gonna go in behind him And I bet you anything He's gonna take off on us To drive on these highways long enough You start to understand The speed limit Or the speeds that most types of Vehicles drive Those buses they'll go as fast As they can They have one goal in mind And that's time Trucks like me If they got Canadian plates They're usually not going faster In 65 mile an hour Because to drive in Ontario And Quebec in eastern Canada You have to be limited You have to have a limiter on your truck At 105 kilometers an hour Which is 65 mile an hour So if you've come up behind a truck Who's going slower And you want them to And you see a Canadian plate You know that they're most likely Most likely speed limited Whether they're American or Canadian Often stay between 60 and 65 mile an hour For fuel economy That's why I go 62 And we're doing 62.7 Right now I believe And that's We're going straight into the wind here That's just to save a little bit of fuel So they have a nice wide open passing lane here Anybody who wants to do the speed limit Which is 75 mile an hour Or 120 kilometers an hour Left lanes wide open for you Hammer down Do what you gotta do I'm gonna save a couple of bucks I don't go slower than 62 though That's my slowest speed Some guys they do 55 miles an hour Like 90 kilometers an hour It saves even more fuel at that point But it also costs a lot of time Time is money You gotta find the right balance How much time you want to spend to save money And how much money can you save Before you're just wasting time And losing money Here we are I believe they're gonna want to Unmold me over there And of course my engine fan Kicks on as soon as I'm on the Dusty gravel lot again right Engine fan doesn't kick on All the way down here Or anywhere else if I'm on a paved lot Engine fan kicks on And dust goes everywhere And trucks filthy right away again Oh, there's Mike Getting unloaded Figured I wasn't too far behind him That was Mike just passing by We're at the Grand Forks Flying J Took the weasel for his walk His mighty, mighty very lordly walk It was magnificent I looked amazing Everyone was looking I knew it I saw them They were like who's that Who's that guy Who's that guy Who's that guy I am So I just grabbed a little snack here A hot dog I'm not gonna eat too much Cause we're going home Got this empty trailer here I'm just gonna head home for the night I should be at the house By around six o'clock It's a short enough day That I can make it home yet And be back there in the morning It's not too far out of the way No little ways but I was just thinking to myself I was gonna go sleep Right at the customer again Be the first thing in the morning But I was really thinking to myself Jake another guy I work with Was saying he was going home He lives around the same area And is dying back And that area is me as well I was like oh Maybe I should go home too I was thinking to myself You know what If I have the opportunity To go home Why am I not going home Most of the time We're way out on the road Somewhere it's just It's not even an option To go home for the night In the middle of a trip right In the middle of a week But if I have the opportunity And it works out with my hours And everything Well why not Right why not I'm gonna Park the truck and trailer Head home Have an evening Have supper at home Maybe watch a movie Relax a little bit And we'll leave from there Tomorrow morning What do you think of that Diesel I think it's wonderful Got you some trucking Now we go back home Don't tell me you're tired Don't leave in one day I'm old now Let's not waste another minute Nice Pete I like the color It stands out It's not for me I like the blue That I have a little better It's more of a darker blue Whatever color that is Is it teal Is that the color of that Doesn't look bad on that truck Looks good Calm down Karen We're gonna stop the red light I don't know what I would have done I could have gone to the customer Stayed there Edited my videos Enjoyed my evening there By myself But why not go home Back there by 7.30 Tomorrow morning again So I'll have to get up Around 5 a.m. That's worth it They have the yield I have the green arrow I love these American interstates They just make sense These wonderful on-ramps It's like I wish we could catch on to that One thing Please be careful My hot dog's there It's my hot dog Hey Get your own hot dog Hold on buddy I put my hot dog on his seat there We had a very strong wind Coming out of the west That was trying to push me On to the shoulder All the way north So I went up to Morris In Manitoba And I took highway 23 Eastbound So the wind is pushing me Along here now I'm going to take highway 59 north Highway 59 is a little bit more sheltered Than highway 75 I'm hoping I can Have less wind to deal with For a shorter amount of time Straight first try every try


Penguin presents. Want to play? By P. J. Tracy. Red by Sarah Borges. Chapter 1 The Brandy had been absolutely essential. It always was on Sunday nights when Sister Ignatius took it upon herself to cook and serve Father Newberry a proper meal. In this part of Wisconsin, that usually translated to hamburger cooked in canned cream soup. The shape varied with the good sister's swims, sometimes meatballs, sometimes meatloaf, and on one memorable occasion rolled tubes that looked disturbingly like a casserole of severed penises. But the basic ingredients and the resulting indigestion were always the same. Father Newberry had learned long ago that an asset couldn't touch it. Only the brandy helped, blessing him with a quick sleep, where he passed the time in happy oblivion while his stomach fought the demons of Sister Ignatius's kindness. On this particular Sunday night the demons had been multiple. In some sort of aspiring gourmet fit the sister had baked meatloaf and, God only knew, how many different kinds of canned soups. When he'd asked her to name the ingredients of this daring culinary experiment she tittered like a schoolgirl and locked her lips with an imaginary key. Ah! A secret recipe! He had smiled at her rosy face, greatly fearing that clam chowder lurked somewhere in the ocean of oily liquid in which the meatloaf had drowned. And so it was that the juice glass had been filled with brandy for an unprecedented second time, and Father Newberry had fallen fast asleep in the recliner facing the television. When he next opened his eyes the screen was a snow field of jittery flakes hissing ecstatic, and the clock face read 5 a.m. When he went to turn off the lamp by the window he saw the frosty car in the church lot and recognized it immediately. It was a forward falcon of indeterminate age, dying slowly of the cancerous rust that devoured old cars in a state that salted roads as liberally as they salted food. In a moment of weakness he wished he could just sneak off to his warm bed and pretend he'd never seen it. His only sin was in the wish, however, for he was already moving toward the door, tugging his cardigan close around his abused belly before stepping out into the dark chill of an October morning. The church was old and almost Protestant in its plainness, for these rural Wisconsin Catholics eyed all things magnificent with deep suspicion. The Blessed Virgin wore the gleam of plastic and bore an unsaintly resemblance to the mannequin in the window of Frida's house of fashion on Main Street, and the only stained glass window was oddly placed on the north side where the sun could never set at a fire with brilliant color that might offend. A dour place in a dour parish in a dour state, thought Father Newberry, missing the California of his youth, nearly forty years gone now, speculating again that all bad priests were sent to Wisconsin. John and Mary Klinefeldt were kneeling in a middle pew, heads resting on folded hands. Utterly still in a devotion the Father had always thought almost obsessive. It was not unusual for the aging couple to visit the church during off hours. Sometimes he thought they preferred solitude to the company of fellow parishioners they believed corrupt with sin. But to the best of his knowledge they had never come so early. It did not bode well for a rapid return to the cosy rectory, and Father Newberry was loath to ask what trouble had brought them here this time, since he already knew the answer. He sighed and moved slowly down the aisle, reluctantly propelled by a sense of duty and a good heart. Good morning, John. Good morning, Mary. He would say. What troubles you today?  It wasn't simply homophobia. It was a zealous crusade against what they called the abhorrent unnatural offense to God's eye. And listening to their self-righteous accusations always left him feeling sad and somehow soiled. Please let it be something else this time, Lord. He prayed as he drew near the middle pew. I have, after all, already endured the penance of good sister Ignatius's meatloaf. And indeed it was something else. What was troubling John and Mary Kleinfeld this morning was not the suspected presence of homosexuals in the parish, but the indisputable presence of small, tiny bullet holes in the backs of their skulls. Sample complete. Ready to continue?


From the SiliconANGLE Media office in Boston, Massachusetts, it's theCUBE. Now, here's your host, Dave Vellante. Hello everyone and welcome to this breaking analysis. We're here to assess the VMware vSphere 7 announcement, which is the general availability of so-called Project Pacific. VMware has called this the biggest change to vSphere in the last 10 years. Now, Project Pacific supports Kubernetes natively in VMware environments. Why is this important? This is critical for multi and hybrid cloud because Kubernetes and its surrounding orchestration enable application portability and management. As we've been reporting, VMware is one of the big players eyeing multi-cloud, along with a crowded field of aspirants that include IBM with Red Hat, Microsoft, Cisco, Google, and a host of specialists in the ecosystem like Hashi and Rancher. As well, some players have focused in their respective stack swim lanes like security and data protection, storage, networking, et cetera. And with me to dig into this announcement is Stu Miniman. Stu is a senior analyst at Wikibon and co-host of theCUBE. Stu, good to see you, let's get into it. Great to talk about this, Dave. Okay, so vSphere 7, what is being announced and why is it relevant? Yeah, so Dave, as you said in the open, this is the general availability of what they talked about at VMworld 2019 as Project Pacific. So it really is integrating Kubernetes into vSphere. The way VMware, of course, will position this is that they're now enabling the 90% of the data centers around the world that have VMware. Hey, your Kubernetes enabled. Congratulations, you're cloud native, everything like that. Only being a little facetious here, but this is very important. How do we get from where we were to live in this more cloud native environment? So containers in general and Kubernetes specifically are being a first class citizen. There's a lot of work, Dave. And my understanding of this has been going on for a number of years. It's not like they just started working at this six months ago, a overhaul to how this works because it's not just, oh, we're going to stick a couple of containers on top of the guest operating system in the virtual machine, but there is a supervisor cluster for Kubernetes at the hypervisor level. And there's a lot of in the weeds things that we're all trying to understand and figure out because you've got a hypervisor and you've got VMs and now you've got the containers in Kubernetes and some of them are living in my data center. Some of VMware, of course, lives on multiple clouds like the VMware on AWS solution. So this will go there. And how do I manage that? How does this impact my operations? How does this change my application portfolio? Because the early value proposition from VMware always was, hey, you're going to put VMware in there. You don't need to touch your applications. Everything runs like it did before. You were running Windows apps on a physical server. You moved into virtual. It's all great. There's a lot of nuance and complexity. So when VMware says this is their biggest change in a decade, I'd say probably is. I think back to, you know, I remember when ESX 2.0 rolled out in vMotion, really changed the landscape that was big. The vVols moved to really allow storage to really understand that architecture and really fix storage was a huge undertaking that took many years. This definitely stacks up with some of those previous changes to really change the way that we think about VMware. The advertising you've even seen from VMware some places is don't think of them as VMware. They're Cloudware or Containerware or the like because VMs are still there, but VMware is much more than VMs today. So this feels like it's VMware trying to maintain its relevance in a cloud native world and really solidify its, I mean, let's face it, VMware is a platform. Pat Gelsinger says, ride the waves. You know, try to many times and many angles to try to ride the cloud wave and it's finally settled on the partnerships with AWS specifically, but others. And so really is this their attempt to become cloud native, not get left behind and be cloud naive, as many say? Yeah, great question, Dave. And absolutely there's the question as to, you know, what's happening with my applications?  Those applications, well, customers don't even know what they live on. Do they live on virtualization environment? Is it containers? I don't need to worry about because SaaS takes care of that. If I'm building modern applications, well, I'm probably not starting with VMs. Containers are the way that most people are doing that or, you know, heck, they might even be going serverless now if we take these environments. So how does VMware make sure that they have the broadest application support? Kubernetes really won the container orchestration wars. And this is a way that VMware now can enable customers to move down that path, to modernize their environments. And what they want to have is really some consistency between what's happening in the cloud and happening in the environments that they control themselves. So VMware is saying that containers are now a first class citizen within vSphere. What does that mean? Why is that important? First of all, are they really? And what does that mean? And why is that important? Yeah, so Dave, my understanding is, you know, absolutely it's there, you know, the nuance that you will put there is, you know, we're not just running, you know, bare metal servers with Linux and running containers on top of it. It is, you're still sitting on top of the hypervisors. One of the things I'm trying to understand when you dig down is, you know, at the device driver level, VMware always looked a little bit like Linux, but the people that use it and operate it, they're not Linux people, Dave. These, you know, the OS, the number one OS that always ran on VMware was Windows and the traditional applications that ran there. So when we talk about containers and we're enabling that in a Kubernetes environment, there are some questions about how do we make sure that my applications get certified? Dave, you've got a lot of history knowing things like SAP and Oracle need to make sure that we've tested everything and this works. This is not what we were running traditionally in VMware. And if VMware just thinks, hey, vSphere 7, turn the crank, everything certified, well, I would tell customers, make sure you understand that your application has been tested, that your ISV has certified this environment, because this is definitely, as VMware says, a huge architectural change. So therefore, there was some ripple effects to make sure that what I'm doing in this environment stays fully supported. Of course, I'm sure VMware is working with their huge ecosystem to make sure that all the pieces are environment. You mentioned things like data protection. We absolutely know that VMware is making sure that day one, the data protection plugs in and is supported in these environments when you're using the kind of Kubernetes persona or containers solutions in vSphere. Wow, this sort of brings me to my next question. I mean, we were talking to Bernard Golden the other day and he was saying, Kubernetes is necessary for multi-cloud, but it's insufficient. And so this seems to me to be a first step in, as I say, VMware maintaining and growing its relevance, but there's got to be a roadmap here that goes beyond just containers and portability. There's other management factors. You mentioned security, enabling the ecosystem to plug in. So maybe talk about that a little bit in terms of what's necessary to really build this out over the next decade. Yeah, and actually it's a great point. So first of all, vSphere, of course, is the core of VMware's business, but is only a piece of the overall portfolio.  Tanzu is their cloud native overarching piece of it. And one of the updates is their product, Tanzu Mission Control, which is an existing product really came out of the Heptio acquisition, is how we can really manage any Kubernetes anywhere. And this is pure software, Dave. I'm sure you saw the most recent earnings announcement from VMware what's going SaaS, what's going subscription. VMware's trying to build out some of their software portfolio that isn't kind of the more traditional shrink wrap software. So Tanzu can manage any Kubernetes environment. So of course day one, hey, vSphere seven, it's a Kubernetes distribution. Absolutely it's going to manage this environment. And but also if I've got Kubernetes from Azure, Kubernetes from Amazon, Kubernetes from other environments, Tanzu can manage across all of those environments. So what VMware has always done, if you think back in the early days of virtualization, I had a lot of different servers, how do I manage across those environments? Well, VMware was a layer that lived across them. VMware is trying to do the same thing in the cloud. Talk about multi-cloud and how do I manage that? How do we get value across them? Well, there's certain pieces that VMware is looking to enable with their management software to go across them, but there are a lot of other companies, Amazon, Google, actually not Amazon yet for multi-cloud, but Microsoft and Google absolutely spent a lot of time talking about that in the last year, as well as you mentioned companies like Rancher and Hashi Core Pop absolutely play across lots of these multi-cloud environments. Well, let's talk about the competition. Who do you see as the number one competitor? Well, so the number one competitor absolutely has to be Red Hat Dave. So when I've, we've been in the Kubernetes ecosystem for a number of years. For many years when I would talk to practitioners, the number one, you know, what Kubernetes are you using? Well, the answer for many years was, well, I'm grabbing it, you know, the open source and I'm building my own stack. And the reason customers did that was because there wasn't necessarily maturity and this was kind of the leading edge, you know, bleeding edge customers in this space. The number two besides build my own was Red Hat and it was because I'm a Red Hat customer, a lot of the Linux tooling, the way I'm building things, the way my application developers do things fit in that environment. And therefore that's why Red Hat has over 2,000 OpenShift customers, leading distribution for Kubernetes.   Well, Maritz told me years ago, he was, yeah, it's true, we're with everybody and you can see that sort of playing out. But what if, I mean, if you look at what VMware could do and some of their options, if they, what if they gave it away, that would really be a shot across the bow at OpenShift, wouldn't it? Yeah, absolutely, Dave. Because look, Kubernetes is not free. If you're enabling Kubernetes on my Google environment, I, you know, just within the last week, saw some things that were like, okay, wait, if you're testing an environment, yes, it is free, but, you know, started to talk about the hourly charges for the management layer of Kubernetes.  So, in Amazon or Google, and absolutely, Dave, it's an important revenue stream for Red Hat. So, if I'm VMware and, you know, maybe for some period of time, you make it a line item, it's part of my ELA, you know, a good thing for customers to look out for is when you're renegotiating your ELA to understand if you're going to use this, what is the impact? Because absolutely, you know, from a financial standpoint, you know, Pat Gelsinger and the VMware team has been doing a lot of acquisitions. Many of those, Dave, have been targeted at this space, you know, not just Heptio, but Bitnami and even the Pivotal acquisition all fit in this environment. So, they've spent billions of dollars. It shouldn't be a net zero revenue to the top line of what VMware's doing in this space. Yeah, so that would be an issue from Wall Street's perspective. But at the same time, it's, again, they're playing a long game here. Do we have any pricing data at this point? So, I still have not gotten clear data as to how they're doing pricing now. Okay, and then others that are in there and in the mix, we talked about Red Hat. I mean, certainly Microsoft is in there with ARC. I've mentioned many times Cisco coming at this from a networking perspective, but who else do you see in there, Anthos with Google? Yeah, and, you know, Dave, all the companies we're talking about here, you know, Pat Gelsinger has had to leverage his, you know, Intel experience to how to balance that line between partnering with everybody but slowly competing against everybody. So, you know, we've spent many hours talking about the VMware-Amazon relationship. Amazon does not admit the multi-cloud solution yet and does not have a management tool for supporting all of the Kubernetes environments, but absolutely, Microsoft and Google do Cisco, have strong partnerships with all the cloud environments and is doing that hybrid solution. And, yeah, Dave, just a thing to expand on a little bit there. If you talk about vSphere, you say, okay, vSphere 7's rolling out. Well, how long will it take most of the customer base to roll to this environment? There will be some that absolutely want to take advantage of Kubernetes and will go there, but we know that it's typically a multi-year process to get most of the install base over onto this. And if you extend that out to where VMware is putting their solution into cloud environments, there's that tension between, you know, is there a match actually between what I have in my data center and what is in the managed environment managed by VMware and Amazon or managed to support some of the other cloud environments. So the positioning always is that you're going to do VMware everywhere and therefore it's going to be consistent everywhere. Well, the devil's in the details because I have control of what's in my data center and I might have a little bit less control as to some of those managed services that I'm consuming. So absolutely something to keep a close eye on. And not just for VMware, everybody is having these concerns, even if you talk about the native Kubernetes distributions, most of the Kubernetes services from the cloud providers are not immediately on the latest revision of Kubernetes. Right, so okay, well, let's talk about that a little bit. Remember when OpenStack first came out, we said it was a Hail Mary against Amazon. Well, a new Hail Mary, and it looks like it has more teeth as Kubernetes, right? Because it allows portability and of course, Amazon doesn't publicly say this, but it's not, that's not good for Amazon if you're porting things, applications moving things around, moving them out of the Amazon cloud and that makes it easier. Of course, Amazon does support Kubernetes, right? But they've got alternatives. So, Dave, it's fascinating. So I've talked to many practitioners that have deployed Kubernetes and one of the top reasons that they say that why they're using Kubernetes is so they have options with the cloud. When you also ask them what cloud they're running, they're running Amazon, do they have plans to move off of it? Well, probably not. I had a great customer that I did an interview with at one of the KubeCon shows and they'd actually started out with Azure just because it was a little further ahead with Kubernetes and then for the services they wanted, they ended up moving to AWS. And Dave, it's not a click a button and you move from one Kubernetes to another. You need to match up and say, okay, here's the five or six services I'm using. What are the equivalents? What changes do I need to make? MultiCloud is not simple today. I mentioned HashiCorp as one of those companies that help people across these environments. If you have a Hashi solution and you're managing across multiple clouds, you look in the code and you understand that there's a lot of difference between those different clouds and they simplify that but don't eliminate it. There's just, there is not a way today to this is not a utility when you talk about the public cloud. So Kubernetes absolutely is existentially a little bit of a threat to Amazon but Amazon's still going strong in that space and the majority of customers that have deployed Kubernetes in the public cloud are doing it on Amazon just because of their position in the marketplace and what they're doing. So let's double click on that. So Jassy in an exclusive interview with John Furrier before last year's re-invent said, look, we understand there's a lot of reasons why people might choose multiple clouds. We can go through them M&A, developer preference, and I think people want to have optionality and reduce lock in potentially but I've always said by the way, just as an aside that the risk of lock in is far down on the list relative to business value. People will choose business value over no lock in every time. About 15% of the customers might not agree. Nonetheless, Jassy claimed that typically when you get into a multiple cloud environment he didn't use the term multi-cloud that it's not a 50-50. It's a premier primary cloud supplier. So it might be 70, 30, or 80, 20, or even 90-10 but it's really that kind of, you know, imbalance. First of all, do you see that? And then what does that mean for how they approach this space, multi-cloud in particular? So I'm sorry, you're asking how Amazon should approach this space? Yeah, I mean you've said that you think they'll eventually enter this marketplace. Yeah, absolutely Dave. First of all, in general, yes, I do agree. It is not, there are certain financial companies that have always chosen two of everything because for regulation and certain we need to protect ourselves. We're going to have two suppliers. We're going to keep them as even as possible but that is a corner case. Most customers, I have a primary cloud. That's what I'm doing. That's what IT tries to get everybody on and you need to have, is there a reason why you wanna use a secondary or tertiary cloud because there's a service that they need. Of course, you know, Google, you often run into, it's like, oh, well, there's certain data services that they're doing well and of course the business productivity solutions that Microsoft's doing or the relationship with Oracle that are driving people towards Microsoft. But just as we saw Amazon soften on their hybrid solutions, we spent a lot of time at Reinvent talking about all their various hybrid solutions. Since their customers are going to have multiple clouds and even you take most of their customers that have M&A involved, you buy another company, they might be using another cloud. As Microsoft's position in the marketplace has grown, you would expect that Amazon would have not just migration services, but management services to match what customers need, especially in this Kubernetes environment. Seems that it seems a natural fit for them. It's possible they might just leverage partnerships with Red Hat, VMware, you know, and some of the other players for the time being, but if the market gets big enough and the customers are asking for it, that's usually when Amazon responds. So let's wrap with sort of what this means to the customer. And I've said that last decade, really multi-cloud was a symptom of multi-vendor and not so much of the strategy that's changing, you know, clearly, you know, these jokes. CIOs are being called in to clean up the crime scene and, you know, put in edicts, corporate edicts around security and governance and compliance and so forth. So it's starting to become a complicated situation for a lot of companies. We've said that multi-cloud is going to be there. People are going to put the right workload and the right cloud, et cetera, and there's advantages to certain clouds. But what should customers be thinking, specifically as it relates to vSphere 7? Yeah, so Dave, the biggest thing I would say that people need to look at, it is that understanding in your organization that boundary and line between infrastructure and application. People have often looked at, you looked at the ascendancy of VMware and VMs and then what's happening with cloud and containers and we think of it from an infrastructure standpoint that I'm just changing the underlying pieces. This is where it lives and where I put things. But the really important thing is it's about my data and my application, Dave. So if I'm moving an application to a new environment, how do I take advantage of it? We don't just move it to a new environment and run it the same way we were doing it. I need to take advantage of those new environments. Kubernetes is involved in infrastructure, but the real piece is how I have my application, my developers, my app devs working on this environment and therefore it might be that if VMware is the right environment and I'm doing a lot of it, that the development team says, hey, I need you to give me a pool and provision this for me and I can have my sandbox where I can move really fast. But VMware helped initially customers when they went from physical to virtual move faster from an infrastructure standpoint. What it needs to do to really enable this environment is help me move faster on the application side. And that's a big gap from VMware's history. It is where the pivotal people and Heptio people and Bitnami and all the new people are helping along to help that whole cloud native team, but that is a big shift from customers. So for this to be successful, it's not just, oh, the virtualization admin, he upgraded to the new thing, he made some changes and said, okay, hey, I can give you a Kubernetes cluster when you need it. It's really understanding what's going to happen on the application side. And a lot of that is going to be very similar to what you're doing in cloud environments. And I think this is Dave often where you hear customers, they say, oh, well, I did that cloud and it was too expensive and it was too hard. And I repatriated everything else. It says, well, you probably didn't plan properly and you didn't understand what you were getting yourself into and you jumped into the deep end of the pool and oh, wait, I forgot how to learn how to swim. So that is where we, Dave, the technology part's always the easiest piece. It's getting all of the organizational and political things sorted out. And the developer, we know how important that is. We're seeing it's great to see VMware pushing faster in this environment, kudos to them for how fast they've moved. Project Pacific 2GA, that is really impressive to see and can't wait to hear the customers roll out because if this is successful, we should be hearing great transformation stories from customers as to how this is enabling their business, enabling them to move faster. And that has been one of the favorite stories that I've been telling with customers on theCUBE the last couple of years. The vast majority of VMware's business, of course, is on-prem and what essentially they're doing here is enabling developers in their customer base and they have half a million customers to really develop in a cloud native manner. The question is, from a cultural standpoint, is that actually going to happen or are the developers going to reject the organ and say, no, I want to develop in AWS or Microsoft, et cetera, in the cloud. And I think VMware would say, we're trying to embrace it no matter where they want to develop. But there's still going to be that interesting organizational tension or developer tension in terms of what their primary choice is, is there not? Yeah, Dave, absolutely. We've been saying for years that cloud is not a location, it is an operating model. So this is helping to enable that operating model more in the data center. There's still questions and concerns, of course, around consumption on demand versus whether you've bought the entire thing as more and more services become available in the public cloud. Are those actually enabled to be able to be used in my data center or hosted environments? So this story is not completed, but we are definitely ready. I believe we're saying it's the multi-clouds chapter three of what we've been watching. Well, and you're seeing a major TAM expansion yet again from VMware that started with ESX and then of course went into networking and storage and now they've got a cloud security division. We're talking about the cloud native capabilities here and on and on it goes. Stu, thanks for helping us break this vSphere 7 announcement down and good job. Thanks, Dave. All right, and thank you for watching everybody. This is Dave Vellante for Stu Miniman. We'll see you next time on theCUBE.


So, I guess more thematic than I realized when I originally put this talk together and submitted it, this talk is about including people and it's also about working on open source and having empathy with people. So I guess this is the continuous block. So I'm going to talk about including people in projects and in open source, but before I do that, let me introduce myself, I'm Andre Arco, I'm also indirect on all the internet things that that's my, actually crap, that's my old avatar and I didn't update it. That was once my face on the internet. That's all right. I work at Cloud City Development where we do web and mobile development and I mostly do senior Rails consulting for teams that need a senior Rails person to join them. If that's up your alley, that's definitely something that we're good at. My coworker from Cloud City, Raine Hynerix will also be giving a talk later tomorrow, so it's pretty cool. I wrote a book, kind of wrote a book, half wrote a book. I coauthored the Ruby way of the third edition, helped update it for Ruby 2.2 and 2.3. I'm clearly biased, but I think it's a really good book about Ruby. I work on a thing you may have heard of called Bumler. I guess I'll just say that working on Bumler has been really great because it's meant that I end up getting to talk to everybody in the Rumi community because everybody ends up using Bumler and it's been really interesting and really educational to do. Related to that, I have Bumler stickers. I brought 100 just for you. I can get one later. As Jonan said, I started Ruby together. The pitch there is really just you work at a company that needs Ruby gems to work, but you probably can't afford to hire an entire person to make sure that that happens, so give us a fraction of a person worth of money and we will give you an entire person worth of work. Lots of companies that totally works out and everyone ends up with lots of work for a small amount of money. It's pretty cool. I also have Ruby together stickers. I brought 200 of those. You can come get one later. As you can probably tell at this point, I've realized that developers don't actually care about business cards. They only care about stickers. I'm going to oblige. You're going to get stickered. Back to the inclusion stuff. Right off the bat, I would like to point out that it's kind of weird for me to be talking about this, actually. I'm a stereotypical default programmer dude. I'm white. I'm a guy. I'm tall. People just assume that I know what I'm talking about when I tell them things. It's really convenient in some cases and really confusing and frustrating in other cases. So this talk is actually more the result of a lot of research and a lot of conversations with people who are not stereotypical default programmers. But the main reason that I'm giving this talk and not one of those people with more firsthand experience is that I am the only person who can give this talk and still be considered equally technically confident afterwards.  Why are you bad at programming? Why are you not good? And so I don't have that problem. So I'm talking about this. Right. So this talk is about, this talk is derived largely from my work on open source projects, mostly including Bundler. But the things that I'm going to talk about are universally applicable to any time that you are working with another person. So if all you ever do is write software by yourself for yourself, maybe go get a drink and you can come back after my talk's over. But if you're like the rest of us and you actually work with people on software that will be used by people, I'm going to have some things to tell you. So, yeah. Everything I'm about to talk about is my experience of doing good things or not good things, doing things that turned out sometimes very badly and then not doing that later or doing things that seem to go well. But what worked for me may not work for you. Like I just said, people will listen to me and believe me in a totally unreasonable way. So me just telling them things sometimes works. Figure out what will work for you, figure out, like, pay attention, try things, experiment, but like have hypotheses, check to see if it works, change how you're acting, if what I'm suggesting is not working out for you. Keep experimenting until you get the results you want. So I'm going to give some background about diversity. Just want to make sure that those scare quotes are present. And I'm going to talk about some things that you can do to try and improve the situation that you're in or the projects that you're involved in. And the topic of diversity, again, scare quotes, has gotten a lot of press lately and unfortunately there's been enough history of sexism and harassment that when Bloomberg magazine published an article by Paul Ford called what is code that tried to explain exactly what programming is aimed at like the mainstream businessy world who thinks that coding is cool but doesn't really know what it's about.  That is not a good reputation to have in the wider world, especially since based on the people that I'm looking at right now, Ruby is not in fact all sexist dude bros. So it's really a problem that we have, that reputation kind of like in the wider world. So over the last couple of years I've spent a lot of time doing a lot of research, talking to a lot of people who have encountered problematic experiences. And I'm going to try to summarize some of that and then talk about things that you can do to improve it. To start with diversity as you probably noticed is not actually the right word to use to talk about this. The reason that underrepresented people are underrepresented is not because they don't exist. Graduating computer science majors make up a significant minority of all of these groups that are wildly underrepresented in tech. The reason that these people are underrepresented in the actual workplaces where we all spend our time and make our money is not because they never got the education that was required to participate. It's because their opinions aren't listened to, their feedback isn't acted on, and their technical skills are suspect based entirely on things that have nothing to do with their actual experience or skills. So cheat sheet, here's the fastest way to start increasing diversity in tech is start talking about inclusion and including people don't talk about diversity because while that may be a like visible side effect of inclusion, the reason that we want to do this is so that people feel included not so that we can say, look at how nicely divided this pie chart is. That's not actually a good end in and of itself. So at this point in the conversation, a lot of people usually say, but I've felt so welcome and included, this can't be the reason for this problem. And unfortunately that position is demonstrably wrong. The underlying issue here is that people are being denied education, being denied jobs, and being denied promotions just because of bias against them. Co-workers, managers, and this goes all the way up, executives, VCs, people really in other words, right? Like no matter where they are, people have been shown to unreasonably overvalued work done by young white straight men and unreasonably undervalued work done by literally anyone else. It might be because their gender is different, it might be because their sexual orientation is different, it might be they have a disability, it might be age, it might be race, it might be weight, it might be there's a really long list of things that it possibly could be. But for example, just changing the name or race or gender on a resume is enough to consistently get it from yes, we'll hire this person to no, we would never hire this person, like without changing any of the other content. So like this is a very clear demonstrated repeatable problem in not just the Ruby community but like in tech in general, in the workforce in America in general, it's a problem. So even though there is a lot of repeatable research showing these biases, people disagree with me every single time I talk about this. They say, but tech is a meritocracy, everyone is valued based on their contributions. Unfortunately, that is also demonstratively false. In fact, research shows that counter to that claim of meritocracy, when you do performance evaluations and make hiring decisions in an organization that has publicly stated that they strive to be meritocratic, those decisions are more biased than in organizations where people know for a fact that it's not a meritocracy. Ultimately, people who get rewarded for their actions assume that their actions were intrinsically deserving of that reward, and then conclude that anyone who didn't get the same reward must have not done as good of a version of that, right? Like, oh, they didn't get paid as much, they must not be as good as me at programming. And that is unfortunately not true at all. Research shows that, as I was just saying, when it's a meritocracy, you're even more biased and you're even more wrong in your evaluations. So after I've said that, people are like, oh, but well, if that's not the problem, the problem is really the pipeline problem, right? There's not enough people coming in to programming who are in all of these underrepresented groups. And as I kind of alluded to earlier, not even close. There are actually a totally minority but reasonable number of people getting computer science educations and then not able to get computer science jobs. Even worse, when we first invented computers, programming was a 100% women's job, right? Computering used to be a job title and the computers used to do all of the calculations that the mechanical and electronic computers were having to do. And so they were the only people who knew what calculations needed to be made and so they had to tell the computer how to do it. As you can probably guess, as programming rose in prestige and compensation, it declined in women doing it and today, programming as a field is less than a quarter of women and last time we checked on a downward trend, right? Like this is not, oh, if we just had more women in the field, this would fix the problem. No, that wouldn't fix the problem. The field used to be all women and the problem is still here so that is clearly not actually the solution, we need to change how we act and how we include people in our communities. The last-ditch effort that people usually throw at me after this is businessmen say I really like the idea of including people but I run a company and so I will only hire diverse teams if it's financially beneficial to me. And I wrote a blog post specifically just about this in the past but the short version is really simple. Companies are so entrenched in their existing biases that they're willing to ignore research that shows that teams that are diverse are actually more productive and more financially rewarding but they would still rather take the easy way out and hire non-diverse teams because that doesn't require any effort even though the end result is worse. And the underlying problem there is even worse than that. Like there is no excuse for treating a group of people as inherently inferior. Like attempts to include underrepresented groups for the sole purpose of improving productivity is guaranteed to fail because you're not actually trying to include them, you're just trying to exploit them for their productivity enhancements. If the reason that you're interested in diversity is not to include people, you will never end up with diversity because you're not interested in including people and your discussion. So, since you're still here, I'm guessing that you're interested in including people. Including people is not just a checklist of things to say and do consistently, it's an attitude that you need to adopt during social interactions. That attitude needs to be not just present but you need to be acting in a way to counter the condescending hostile attitudes that are kind of just floating in the air around open source and around programming in general. So, working on any open source project or really any software project, there are usually three groups of people involved. There's the end users, the potential contributors and the existing team. It's easy to be inclusive towards one of those groups and still be hostile towards the other groups. So, in the Linux kernel, for example, end users are welcomed. Linux is for everyone. Anyone can use it. Contributors on the other hand are semi-regularly told that they're brainless imbeciles or much worse language, which is not super good at welcoming the actual team that works on it. Yeah, so you need to not just include the team, you need to include people who are willing to contribute to the project and you need to include the users who are actually gonna be the ones using the product in the end. So, let's start with end users. How can you be welcome and inclusive for people who actually use the software that you build? Whether this is an open source project or a closed source project, you're gonna have users even if this is like a completely internal tool and the user is yourself. But if the user is more than you, which chances are pretty high that it will be at some point, people will pay attention to the other people who work on software, people will pay attention to the other people using the software. They will pay attention to the fact that the documentation only ever says he. They will notice if your software encounters an error case and raises a message that says that's stupid, don't do that. So, here are some really straightforward ways to make sure that people who are end users and using the code that you write will feel included. Start with a code of conduct. At this point, there are a lot of examples of codes of conduct. Coraline Ata Emkey, who unfortunately wound up not able to come to this conference, has created a sort of template code of conduct called the contributor covenant and she's really active about updating it when necessary to make sure that it is as inclusive as we have currently managed to come up with. It makes it, a code of conduct makes it clear that the project intends to provide a safe space for people who are using it to talk about it without being harassed and without one, chances are that anyone in an underrepresented group is going to think twice about participating in your project because if you're in an underrepresented group, chances are good, you already get a ton of crap on the internet and why would you also want to give free work to a software project that you're going to get crap for having given free work to? Next up, documentation. Documentation is a thing. You probably don't have as much as you think you should, chances are high you're embarrassed about it, that is okay. I work on a lot of projects, none of them have as good of documentation as I would like. People are happy that those projects exist anyway. The ground rules for helpful inclusive documentation are pretty straightforward. Use she or they instead of he if you have to include pronouns in your documentation, write some documentation that is explicitly aimed at newcomers. The number of projects that exist that assume that you already know everything about the project when you start reading the documentation totally astounds me. How do you get people involved in your project when all the existing documentation is only for people who are already involved in your project? This may mean finding people who are not already involved in your project so that you can explain to them how your project works and they can write it down because you may have no idea what is actually unknown about your project at this point. If it's your project, chances are pretty high that you already know everything and what you write down is only gonna make sense to someone who already knows everything. For a really fantastic guide to writing genuinely helpful user facing documentation, Jacob Kaplan Moss did a talk called Writing Great Documentation and he outlines four kinds of documentation that your project needs to be useful to all of the people who will be looking at the documentation. The first thing is tutorials. Tutorials explain how to accomplish a specific task. This should be a thing that you can accomplish start to finish in 30 minutes. You should then find a link to the next tutorial or to other documentation about that particular topic. You should write topic guides. Topic guides explain a single topic in detail and so if you want to learn more about just that particular thing because that's what you're interacting with, you can read the topic guide. And then you should write an API reference because sometimes people will just wanna know like what every single possible thing that you can do with your project is or they'll remember vaguely that you can do a thing and they don't remember the method name or the exactly which parameters to pass and that's when an API documentation is invaluable. And API documentation is the most likely to already exist but they're also most likely to be useless for someone who doesn't already understand your project. And this is actually a great example of why Rails has both really extensive API documentation and a really extensive guides project that's full of topic guides because if you wanna know how to write a Rails routes file, opening the API documentation for the router is not helpful and I already know how the router works and it's not helpful to me. Finally, troubleshooting documentation. There will be problems that come up again and again and again. If you can fix those problems in your code, if you can come up with a way to write code that will say, hey, it looks like you're having problem X, this may mean that you need to solve thing Y and then this will work, like put that in your code and show that to the person. Don't say unexpected error, have a great life, right? Like that is not actually helpful. If you can't put it in your code, put it in your documentation and say, oh, you're having trouble, like here is the list of steps that I will tell you to do if you show up in GitHub issues. Here's, I just wrote it down, try that first. This, based on my experience with Bundler, that like list of here's things that you should try before you file a ticket that says I really think this is broken. By my best guess that solves maybe like 60 to 70% of people's problems. That is a huge time saver for me and a huge time saver for those people because they don't need me to be awake and responsive in a chat room somewhere to get their problem solved. Speaking of troubleshooting and issues, how your project handles issue reports is a huge indicator of how inclusive your project is. If you respond to a new issue with that doesn't even make sense, close. It's not very inclusive. If you respond to an issue with why on earth would you do that, right? Like this is not, I guess this is not rocket science but like this is a very normal attitude in open source. People are like, oh it didn't work, well you're doing it wrong, don't do that.  Like this is not actually helpful if what you are aiming for is including people. Like maybe those people genuinely want anyone who is having trouble with their software to just go off somewhere and be unhappy. But that's not what I'm aiming for, right? Once, so start, when you're accepting an issue report, start with the idea that whatever the reporter is saying makes sense to them, right? Like it is, chances are very high that no one is showing up and going through the effort of opening an issue, showing like here is the problem that I had without having actually had a problem and if they're having a problem that means either something is broken in your code or something is broken in your documentation because it didn't work out the way that they expected it to. Try to figure out what context the reporter has that you don't, always thank them for taking the time to report the issue because if they're reporting an issue, this is a potential problem for you, right? Again, I guess a way that I have heard this put is there is no such thing as user error, right? If the user is having a problem, you either designed the error message badly or you designed their expectations via the documentation badly and one of those things probably needs to be fixed. And even if the report that they sent you is not a bug, let them know places that they can get help, let them know what they can try, like don't just say, this is not my problem, go away, right? Like that is unfortunately, absolutely the norm in open source projects and honestly from what I've seen inside companies, that is also the norm, right? Like there's some poor computer science, some poor customer support person saying to the engineer, well, this user did this thing and I feel like it's actually a really common response for the engineer to be like, well, the user's doing it wrong, tell them not to do that and that is actually unhelpful for everyone, right? The engineer feels misunderstood and put upon the customer support person feels useless and the end user feels like you don't actually care about them at all. Closely related to issue reports, chat channels, IRC, Slack, email, Twitter, follow the code of conduct in all of those places, make sure the code of conduct is being followed by other people in those places, especially when they're like actively representing your project, right? And anyone who is officially representing your project, right? Like if they're on the core team or if they're you as the owner of the project or whatever, harassment and condescension are like just not okay. Like maybe let's not do that ever, that would be awesome. And finally, this is true for every project but you have to enforce the code of conduct on everyone no matter how quote unquote invaluable to the project they are because that supposedly super productive giant jerk has driven away, God only knows how many super productive non-jerks who would have been happy to work on your project except for that jerk that you think you can't afford to lose. Now let's talk about welcoming contributors. So everything I said so far about welcoming users totally applies to contributors. Everything I said about issues totally applies to pull requests. A safe environment without harassment is absolutely a requirement for getting like including contributors to your project. Documentation helps but there's definitely more you can do to welcome contributors specifically as opposed to just users. The biggest thing you can do to encourage people to help is to ask them for help. I will do this at the end of the talk to give an example. Most people think that they need to be experts on something before they can help and that is almost universally not true. Especially if you're in a situation where you don't have a lot of interaction with people who are new to your project, you have no idea how confusing it is for a person who's new to your project to start using it and it would be super awesome. For me personally I have gained incredibly valuable things from talking to people who are new to a project to understand how I can be helpful to them as a project maintainer. I guess to make this incredibly clear I have never had any idea how anything worked when I started working on a project. I started working on Bundler and I spent I think two weeks just saying out loud, how does, what, what, why would you, what? And like and eventually after a couple weeks of persisting through that it started to make sense but it is not because I like had any idea what I was doing when I started it is just because I said I don't understand how this works and that makes me angry and determined to figure out how it works so I'm gonna keep sitting here frustrated until it makes more sense. When you ask for help, when you write documentation explaining how people can contribute make it clear that they don't need to be an expert and make it clear that you would really like their help based on whatever level of understanding that they have because that is really valuable. Another thing that I do that I found really helpful for getting people started on the project is scheduling times to pair with contributors so this ties in nicely to the last talk. I am also one of those open source project maintainers who says oh you'd like to help, that's awesome. Let's schedule an hour of pairing and at the end of that hour of pairing let's see if you feel like you can tackle the next thing yourself or if you wanna schedule another hour of pairing. Like this is a thing that makes it incredibly, this is an incredibly powerful way to get people to the point where they feel like they can maybe make changes without needing to be scared. Write development documentation, this is totally different than end user documentation. You need to write documentation that says so you wanna work on this project, here's how you check it out, here's how you set up the dependencies, here's how you make sure everything works, here's how you run the tests and here's who runs the project, here are the policies for contributors, here are the criteria for accepting pull requests, here's how you contact other people who are working on this project if you have questions. Don't stop there though, if there's anything that you have to do repeatedly as a developer put it in a document that explains the steps, write a release guide, write I guess write a list of every type of help that you would like to get. We have a list like this for Bundler and it says I would love to get pull requests that fix typos. You too can be an open source contributor, if you can find a typo in Bundler, send me a pull request, I will say thank you so much for fixing this and merge it and you'll have a commit in Bundler. I mean that's not the end, right? We're also totally happy to get help with triaging open issues, writing more documentation, refactoring code, writing more tests, fixing bugs, implementing new features, all of these things need to be done but my point is if you can find typos you are competent to work on the project and so we tell you that explicitly in the I'm interested in contributing to Bundler document. Pull requests are pretty close to issues actually. The person opening the pull request has context that means that what they are doing makes sense. Even if the code that they sent you makes no sense to you and even if the code that they sent you is code that you would never ever merge which sometimes happens. I feel like it's like maybe three quarters of the time I get a pull request and I'm like this is so great, you just like did my work for me, I'm just really jazzed right now and about a quarter of the time I'm like you just did a thing that's really great for you and is gonna make every other person who uses this sad. And so rather than saying you're a horrible person why did you send this, what I say is I really appreciate you taking the time to write this code and share it and I really want to understand your problem and see if there's a way that we can solve your problem that doesn't make everyone else who doesn't have this problem sad and that has actually produced some of the best features in Bundler eventually although it's taken a lot of work. Ultimately it's important to apply all of these principles to your team, right? Respond to code of conduct violations aimed at your team members, not just at you. Make it clear that you have the back of your entire team and tell them that you appreciate their help. Apply the same principles we just discussed for users and contributors to team members, assume that what they're doing makes sense to them, find the context that you're not sharing so that you can understand how to resolve whatever it is that you disagree about and give them positive feedback and ask them for help when you need it. In the end everything that I've suggested comes from the underlying principle of having respect and empathy for other people. Other people don't have the context that you do, they don't have the skills that you do, they have different skills and almost all of the time they're just trying to do their job. They can tell when you're trying to help them and they will react based on that. On the other hand, if you're not reacting well, they can tell and they will respond to that as well usually by taking their efforts and themselves somewhere where people won't treat them like crap. Treating others the way that you personally would like to be treated or that you personally are treated is not enough. You need to think about the context that other people are in and treat them in a way that is respectful and empathetic to them. Listen to people in underrepresented groups, pay attention to how tech as a field mistreats those people and actively work to fix it. Call out problems when you see it, let people know that what they're doing isn't okay. Tech as a field is biased and exclusive and the only way that it's gonna get better is if all of us act to change it. Last, let me finish by doing this myself. I run a popular open source project. We want to include many, many more people on the team than we currently have. If you have ever thought about contributing to open source that felt intimidated or excluded particularly, please talk to me because I would like to both improve that situation for Bundler and tell other people what they can do to make things better. I wanna change tech so that everyone feels capable, welcome and empowered to improve things. That's it.


Hi everybody. For those who don't know, I'm running this regular column. It's the person of the month. My goal is to introduce you to the important names in our community. The first one I did was about Rude van Rossem, the creator of the language, to put a face on a name so that you can maybe meet with these people. You can connect during Python. You can just know who they are, why they are doing this in Python, and maybe they can inspire you to be involved in projects and have fun. Today I selected Lin Rude because I'm switching between Canadian people and international people. Here are a few logos of the things she's involved with, which I'm going to detail a little. So Lin Rude is mostly known as the founder of PyLady San Francisco. And the interesting thing about her is that she's like a new, you could say she's a new Python programmer. Academic formation is a bachelor in finance. And she started a course of computer science in 2011, but she failed. It was a hard-wired course, and she did not complete it. But during her hackathon, she actually discovered Python, and she understood everything, and then she fell in love. And that was the start of her journey. So you can see in two years she's a well-known figure of the community doing lots of interesting stuff. And she did not start with formal education or complicated computer science, just jumped in. An interesting thing is that she joined Women with Code, which is an organization devoted to teaching programming to women. And she actually became co-organizers right at the start. And a year later, she founded PyLady San Francisco. I think most people know about PyLady's. If you don't, you're welcome to look at the website, a talk I did a few months ago. It's an international support and mentoring group for women in Python. And you can see just a year after starting Python, she gave a talk at EuroPython, then PyCon US, PyCon Canada, PyCon US again. And she works at Red Hat on something called FreeIPA, which is an identity management integrated solution. She's also a member of the Python Software Foundation and the Django Software Foundation, which shows that this organization and the community in general help people who help the community become more diverse and supportive. If you go to speakerdeck.com on her profile, it's linked from her website. I give the link at the end. You can see how she started. Right after she learned something, she starts teaching it. And it's true about Python, but also about communities. Like she's doing talks about how you can teach Python, but also how you can build communities to teach Python. And some of her key insights is that to get more women and more people from all kinds into Python, the big problems are confidence. Like maybe many of you think you're not qualified enough to submit a talk to PyCon, but actually you should. That's why we have PyLady's group, so that women who wouldn't have that confidence maybe to speak in front of a regular crowd, which is mostly male, can have a space free of judgment to talk. It's also about being inclusive, which is why the Python Software Foundation makes effort to foster diversity. And it's building the community. We're not just building code, we're building community. I think we're all living this here. A project I'd like to highlight from Lynn is a new coder. It's a website called newcoder.io. And it comes again from a problem she found, something she wanted to do, and when she learned it, she thought it. So it's a website where you can feed tutorials. When you're completed or when a friend of you has completed the basic talks, you can dive into Python or learn Python the hard way, all the basic tutorials on the web. Okay, no, I know the basics. Maybe you have something you want to solve, but you're not finding the middle ground tutorials, or maybe you have no ideas of how you can further your learning. If you go to newcoder, you have concrete tutorials about using the Twitter API, data visualization, stuff like that, so that you can find your next project to go from novice to middle or advanced Python programmer. Lynn loves the documentation culture of the Python community. Everything is documented, and if it's not, we complain about it and we try to fix it. And with this project, she solves a part of this problem. It's also an open community and an open website. We should translate it into French. We should add tutorials. We can all contribute using GitHub. I'm leaving you. Yeah, that's a part of her talk. Again, go to speaker deck and look at the slides. It's really insightful if you're interested in teaching her insights. So I'm leaving you with a quote. You can read it for yourself. And some links. This is going to be online, so you can check everything out. Thank you.


Some of the best storytellers were actually introverts who were able to work through their shyness to be able to connect with others around them. Welcome to the Art of Charm Television, I'm Johnny. And this month on the Art of Charm podcast, we have dove into storytelling and you can catch that podcast in the links below. Now, I know what you might be thinking, storytelling, oh, that's only for extroverted people. Well, I could understand why you might think that. It's an outgoing act. You're looking to capture the audience and attention of the people around you. But let me ask you this. You have stories to tell, you share stories with your friends and family, don't you? So let's have some fun with this. Don't you think if storytelling was only for extroverted people, that introverted people would slowly become extinct because they just didn't have the skills to connect with others around them. In fact, some of the best storytellers were actually introverts who were able to work through their shyness to be able to connect with others around them. Lady Gaga and Elton John and Ryan Reynolds, just to name a few of self-subscribed introverts that were able to beat their introversion through working on it. So here are a few tips in order to help you become a better storyteller. Number one, keep a running journal of notably great events and interesting things that happen to you. Write them down, flesh them out, put them in a story form. Number two, you can even index them so that you know their proper place. Have funny stories and formative stories and scary stories. That way you'll have stories to go to when you need them. Number three, look for those opportunities to share these stories with your friends and family. Holidays and other social events are great times. And number four, don't think that just because you're sharing a story, that it needs to be long. In fact, some of the most impactful stories are quite short. Now, if you enjoyed these tips on how to become a better storyteller, continue to watch more from this playlist. See you guys later. But I feel alive.


Women are the new men. I'm a man, believe it or not, and we are on the way out. We are fast becoming an extinct subspecies, as relevant as Neanderthals. And as subtle, I'm afraid. Women are the new men. Women are more educated than men. Women are more employable than men. Women have skills like networking and empathy which are much more relevant to this post-modern world. The coming world is the world of women. We, with our muscles and brawn and sweat, had given women the infrastructure to carry forward, to perpetuate and propagate the species. And now women don't need us anymore. Women don't need us even for procreation. There's IVF, there's sperm banks. They don't need men anymore. They don't need men as companions. They shun men in relationships. They outrank men in many workplaces. They are beginning to realize, they have been realizing for decades, maybe a century and more, that men are not really necessary. And so they're phasing us out. They're outsourcing their needs either to other women or to technology. We are being replaced, substituted, dispensable, interchangeable.  And so here come the women, the new men of the future. But you see, among us, among us men, there were some good sorts. There were some good types. We were not all bad. Remember us as we fade gently into the night. Remember those of us who had written masterpieces in literature. Remember those of us who had created the most amazing paintings and sculptures. Remember those of us who had constructed welfare systems. Remember those of us who were great doctors, medical doctors and brought healing to large swathes of humanity. Remember those men who, day in and day out, acted as providers, put their shoulder to the burden, came back home to feed, to sustain. And to support their families. Remember those of us who had created business empires in which today many women rule our employed work. Remember those of us who had created all these great institutions which are now providing women with equality and access. Because you see, men did all this. Now women wanted to participate, but they were denied access. Women were enslaved in large measure throughout this period. They were considered chateaux, a form of property that were traded. They were sexually abused. They were subjugated and rendered submissive. In some societies and countries they could not even divorce. But it was not all bad and not all men were bad. I would venture to say or dare to say that the vast majority of men were actually good people. Good persons who tried their best within the context of their cultures and societies, of course. Now these cultures and societies were sometimes patriarchal. Sometimes they did not grant women equal opportunities, equal access, equality in any way, wage equality, voting equality. It's all true. It's all true that women had been mistreated for a very long period of time and there's a lot of pent-up anger in women. There's a lot of rebellion and a lot of defiance and it's only natural. It's only natural to be angry at your oppressors. It's only natural to regard men as tyrants, as insensitive brutes and some of them are. Some of them were. But you see, this is where women had gone astray. And yes, I am generalizing because it's true and it's applicable. And no, I am not a misogynist. I am being frequently accused by men of being ginocentric, of being actually the opposite of misogynist. I'm often accused by men of being a misandrist, a hater of men. I'm not a hater of men. I'm not a lover of women. I'm not a hater of women. I'm not a lover of men. I'm a scientist. I observe. I observe. I classify. I categorize. I describe. I generate predictions and hypotheses. I test them. I falsify them. That's what science does. There's no bias. At least we try to eliminate bias. So what do I observe? You see women having attained a measure of equality, having gained access, having risen within the ranks of workplaces and the family itself, having transformed society from the grassroots, which is a very commendable collective act of feminism, the suffragists to the feminists. Having done all this, having imbued society with a softer touch, with empathy, with networking, having injected feminine elements into education and the law and so on. Having done all this, women then had gone astray. And yes, the majority of women had gone astray. This is especially prevalent, visible and observable in the younger generations. And I refer you to previous videos I've made where I cite dozens of studies to support what I'm saying. You see, the younger generations of women, they emulate men. They want to become men. They want to exclude men completely, except perhaps as sex toys. They want to supplant men. They want to be men. And not only do they want to become men, but they want to become the wrong kind of men. Not the men that I've mentioned before. Not the good people among us men. Not the men who had constructed bridges, who had created civilizations, who had offered magnificent literature, who have generated the most sublime music. No, these are not the men women want to imitate nowadays. They want to emulate and imitate psychopathic men, bullies.  The kind of men that even we as men shunned. You see, even among men, there's no consensus. It's not a monolithic race. Even we men, we judge harshly womanizers, we judge harshly psychopaths and bullies. We don't like them. We think they're bad guys. We have names for them, equivalent to slut shaming. And so rather than emulate and imitate the good people of the past, the charity workers, the medical doctors, the painters, the sculptors, the musicians, rather than imitate this cadre of great men, industrialists, everything, rather than go after this model, adopt them as role models. Women had adopted psychopathic bullies, womanizers and predators as their models. They emulate and imitate this riffraff, this scum, this low life jetsum of manhood. They think women think that to act tough, to be infinitely promiscuous, to drink to the point of senselessness, to get wasted. Women think these are badges of honor. These are hallmarks of virility. This makes them honorary men. They don't realize that only a fraction of men are doing these things. And they are widely not considered men by other men, at least not good men. And yet women emulate bad guys, tough guys, bullying guys, egocentric guys, narcissistic guys, psychopathic guys. And finally we end up in a society where women are about to repeat all the mistakes that men had committed when they handed over the reins to these types of bad guys. Women collectively had eradicated and abolished the magic and the charm that used to exist between men and women. This effervescent, indefinable, imperceptible, non-capturable entity. This electricity between the genders, when they look at each other across a crowded room. This is gone. This is dead. Because today when you look at a woman, what you see is a psychopathic bully. A man. You see a man, a bad imitation of a man, may I add. A man with different genitalia. Studies, numerous studies, and I encourage you to watch my video on hookups. Numerous studies demonstrate that the social, sexual, psychological costs of this convergence of the genders of this gravitational pull towards psychopathy, unigender psychopathy. The price we are paying societally and individually, collectively and personally. This price is both insurmountable, irreparable, irreversible and threatening to the existence of a species much more than any pandemic could, because you see if women were to truly disappear and reappear in the form of bullying, psychopathic, narcissistic men, which is exactly what's happening in the younger generations.  I have dedicated my life to the study of narcissism and psychopathy. I was among the pioneers of the topic in the early 90s and I can tell you today when I come across young women, everywhere, from Russia to China, from the United States to Israel, whenever I come across young women, I see in front of me narcissistic psychopaths and it doesn't matter how educated they are, it doesn't matter how well brought up they are, it doesn't matter, the family background doesn't matter, nothing matters, they emulate the role of a narcissistic psychopath. Sexually they are dysregulated and unbounded, they engage exclusively in drunk, casual sex, they curse, they behave the body language instead of a man, femininity and womanhood, a gun. And no, I'm not an okay boomer, I'm not a traditionalist, I'm very liberal when it comes to sexuality. I don't believe there's such a thing as sexual perversion, perhaps with the exception of pedophilia. That's not the issue at all, sex. Sex is an indicator, seismograph of this mind-bogglingly, mind-bogglingly big bank shift in sexual scripts, in romantic scripts, in how to behave as men and women so that we form a wholeness, a completeness, a totality. We men feel orphaned, we feel alone, we feel abandoned. All of us were born to women, this experience of being abandoned by a mother is excruciating and devastating and debilitating and incapacitating. And here we are, abandoned by all women on a barren planet, a barren planet populated by an increasing number of narcissistic psychopaths.   We are sorry, we are sorry, but we are alone. We are lonely, we are sad, please come back. Please don't become what some of us, a tiny minority used to be, psychopathic predators. And even if you fell prey to psychopathic predators and narcissists, know that they are a small minority, know that the majority of men are not like that. They're good, they're helpful, they're supportive, they're empathic, they're loving, they're caring, they're compassionate, they're affectionate. And they want to create new life with you in every possible way. Don't go away, don't give up on us. We may have become much less useful, but we're still here and we still love you. Thank you for listening.


This is also very important to understand the key concept which are used in test and measurement. So, jyapta kame un terms ki complete understanding nahi hogi, it would be very difficult for us to comprehend those technical concepts. Many important technical concepts necessarily came into plan when attempting to understand the proper use of psychological tests. Like agar ek hum assessment karein, test karein and we are not aware of the time that either it is valid and reliable and what does reliability and validity means, to us test ko hum usko use bhi nahi kar sakte, because we have to claim certain things before using a psychological test. This includes the concept of reliability, validity, sources of error and standard errors of measurement. So, we have to see ke kya humara test to hai wo in sabteero se huzar kar ek usable instrument ban chuk hai ya nahi. So, talking about the reliability as a first concept. Reliability refers to the property of repeatable results. Ab reliability kya hai ke jab hum ek test to hai usko ek population pe mayar karein hai, to kya across the time span is going to mayar the same thing in an accurate manner or not. Tests of relatively stable phenomena, for example, should have high test detest reliability. Agar wo trade jisko hum mayar karein hai, wo ek assi state hai, jo ke ek permanent ek position rakhti hai ki individual mein, tisne hum intelligence ki baat karte, to intelligence to hai, it is relatively a stable mayar, to usko hum jitni bhi dafa jo bhi test apply karein ge, do intelligence ka score more or less same hi aega. Agar ko individual jo hai, wo intellectually jo hai, wo low hai aur uska jo IQ level hai, wo below 70 hai, wo ap uski po jo bhi intelligence ke test apply karein ge, wo reliable hongi aur wo sub test usko ek below the average intelligent person hi reflect karein. So this is the case ki jaha par hum liability ki baat karein ki reliability is something disko hum repeat bhi karte hai, to it gives you the same results. For example, if a test is designed to mayar a trade such as introversion, then each time the test is administered to the subject, the result would be approximately same. Agar hum koi introspective behavior dekh re hai, hum apna within stealth dekh re hai, ki ek individual jo hai, uske andar kitani zyada wo honesty, to wo honesty jo hai, wo uske introspective observation, uske behaviori assessment mein poha zyada grossly change nahi hogi, wo virtue uske andar jitna hai, wo usko jitni bha bhi aap test karein ge, wo apko utna hi valid aur utna hi reliable aapko nazar aega. Then comes to the reliability, validity. Validity is the extent to which the test mayar, what it claims to be mayar. I mean, whatever we are claiming that this test is going to mayar a certain phenomena that is exactly mayaring the same one, it is vital for a test to be the valid in order for the result to accurately applied and interpret. Agar hum kite hai, ke haan ek individual jo hai uske andar shame and guilt ka component mayar karein. Lekin wo test actually shame and guilt mayar nahi kaha, wo basically shayad anxiety aur depression ka scale hai. So, it means that this is not a reliable and valid mayar, exclusively it is not a valid mayar to mayar the certain properties, so it should mayar what it claims to mayar. For example, a test might design to mayar a stable personality trait, but instead mayar transitory emotions generated by situational or environmental conditions. We claim to yeh karein ki yeh jo test hai, yeh let's say ke ek permanent jo hai, wo aap ki state ko mayar karein. Let's say, hum kitein ki yeh aap ke mood ko mayar karein. Lekin wo jo test hai uske items hai, wo aap ke temporary mood ko dekhne hain ke, is waak iss situation ke andar aap ko kesa lag raha hai. So, may be wo jo aap ke emotions hai, wo jo aapka mood hai, wo true or valid picture nahi hai, aapki permanent state of mood ki. So, to become a test as a valid mayar, it should mayar what it claims to mayar. Hum usko thoda sa twist nahi karsate uske instructions ko hum manipulate nahi karsate uske construct ko hum derail nahi karsate. A valid test ensure that results are the accurate reflection of their dimension undergoing assessment. Like for instance, agar humana scale ye mayar kare hain ki wo ek specific trait aggression ko mayar kare hain, to it should only mayar aggression yet not abuse.