 Hi, I'm Josh and I have a question That I can't answer because I'm hitting the laser. Are you being the right person for DevOps? Are you sure? How do you know? Fortunately, we have this talk to find out this talk started out because my wife bought this sign and put it in our kitchen And I love it marriage is more than finding the right person. It's being the right person And I think this is an important reminder for all of us The Phoenix project I assume most of you have at least heard of it Hopefully most of you have read it highlights the relationship between the CEO and the CEO and it's described by one of the main characters Is this dysfunctional marriage where they both feel powerless and that held hostage by the other is this the same between ops and dev From the dev perspective, which I know there are many here. Why does it take so long? Why can't you give me what I asked for that wait for all your processes? I'll never be able to get anything done on the ops side. We say, well, why can't you be more patient? Why can't you use what I've provided? What's why is it not good enough without these processes? We risk problems with availability and manageability issues all are perfectly reasonable so being the right person for DevOps is Actually being more than just your role whether you're ops or dev You have to be more about the relationship between the two Ways you can fix this communicate and learn about your partner Identify what's important to them? How do they like to be communicated to what is their communication styles great talk? We had yesterday about differences in communication learn about your your peers and your co-workers Talk less listen more. I mean we've heard this when we were in elementary school You got two ears one mouth use them accordingly. We love talking about ourselves Take advantage of that and let other people talk Hearing is not listening. I know some of you are hearing me talk and some of you aren't listening. That's okay Active listening means that you are hearing what is being said you've internalized and you could repeat that back Right, just remember just because you hear something doesn't mean you were listening Increase your empathy when you're listening and you're communicating so listen actively right be engaged and when you respond Don't respond defensively Respond selflessly think about the other person and be an empathetic or sympathetic if you can't be empathetic to what they're talking To you about which leads to thinking of others. It's not always about you You are just a contributor in the work now This is to diminish your value But what you do impacts other people and you should be mindful of that and think of others While think of not thinking of others consider doing for others be sensitive when others actually need help and Then engage in that help and it's easier when you've actually dedicated time to do that Right apply time in your day or in your week to help other people Also teach other people you have a great deal of knowledge that you can share Experiences that they maybe haven't experienced yet even if they're a senior developer ops person or a junior person Go under the premise that there are no stupid questions. Okay, there may be stupid answers, but there should be no stupid questions Be trustworthy. This one's very very difficult because you have to be selfless sometimes to be trustworthy You have to be honest with people right take yourself out of the equation to agree and be Transparent and let people know that they're getting honest feedback and honest information from you consistently Now we move on to taking care of yourself You have to keep your interest as you work and apply into the work and organizations you do be more than just the work You do all the talk about burnout a big part of that is maintaining focus on yourself and applying those interests Take some me time. Enjoy a vacation. I used to hate vacations now. I love them. I've doubled down I've tripled down on vacations. They're so important and there's nothing better than mental health days Right. This is your brain is part of your health. Take the time Invest in yourself expand your knowledge Right understand that you can go more than just being deeper in your subject matter Understand how your subject matter affects other people and affects other systems Celebrate together. You're not doing any of this on your own You have other people identify how people like to be praised and do so be vocal don't be silent about it But be respectful Take time to celebrate once you have reached certain milestones and accomplishments Actually enjoy yourself and take a break. Don't go right to the next sprint or go right to the next project But do we sink right after the celebration and everybody's you know ready to go Because the key here is in order to be the right person for DevOps You have to be improving yourself and you have to be working to improve for other people So the question is is when you leave here, are you going to be the right person for DevOps? Thank you