TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Technology

    On-Call Me Maybe

    A podcast about DevOps, SRE, Observability, On-Call, and everything in between.

    Advertise

    Copyright: © 2019 On-Call Me Maybe

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    Happy Accidents with Jenny Gee-Link of Tangerine Mar 28, 2023
    Show notes

    About the guest:Jenny Gee-Link is a Quality Assurance Automation Engineer at Tangerine. She has an extensive background in Mobile Applications, Wireless Technologies, and Telecommunications, having previously worked at large Telecommunications companies such as Motorola. When she’s not working, she always seems to have something on the go. Her spare time is spent on volunteer work with her kids’ school and on the board of directors for the local daycare, picking up another language, tinkering on the piano, and even out biking on the local trails. Binge-watching the latest shows? Nah. Life’s way too short for all that!Find our guest on:LinkedInFind us on:On-Call Me Maybe Podcast TwitterOn-Call Me Maybe Podcast LinkedIn PageOn-Call Me Maybe Podcast MastodonOn-Call Me Maybe Podcast InstagramOn-Call Me Maybe TikTokOn Call Me Maybe Podcast YouTube ChannelAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:Tangerine BankPerlMotorolaUniversity of TorontoMotorola StarTAC PhoneMotorola Razr PhoneBlackberryT-Mobile SidekickMSC (Mobile Switching Center)Base StationAdditional Links:Gen Z embraces flip phonesTranscript:ANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host Ana Margarita Medina with my awesome co-host...ADRIANA: Adriana Villela. ANA: Today, we're talking to Jenn Gee-Link, who works at Tangerine as a Quality Assurance Automation Engineer. We are very excited to have you here today. One of the first questions that we have for you today as you join us is, what is going to be your drink of choice?JENNY: Thank you. Thank you for inviting me. Thank you for having me at your podcast. I'm honored. I'm happy to be here. Regarding your question as to what is my drink of choice right this moment, just to get over my cold, my pseudo cold, my sore throat right now, it's hot water, hot tea, hot cocoa if it's not too hot, too, too hot and burning my tongue. But that's pretty much my choice for now until I get better. [laughs]ANA: I've been drinking a lot of tea. My roommate was sick. My partner was also coughing. And I'm just like; I'm just going to drink tea with honey, like, protect myself.ADRIANA: Yes.ANA: Stay hydrated and, like, just [laughs] [crosstalk 01:28]ADRIANA: Protect the vocal cords. ANA: Yeah. ADRIANA: Totally.ANA: What about you, Adriana? What are you drinking today?ADRIANA: I've got fizzy water. It's Bubly sparkling water, and it tastes like cherry, so...JENNY: Love that. ADRIANA: It's an improvement over my usual water drink I have whenever we record, but I do have water on standby as well, so... [laughter]ANA: I'm definitely like the non-fun one for the day. I have water, just regular water for the day. I was going to make a mocktail, and I was like, maybe for the next recording. [laughs]ADRIANA: That would have been fun. [laughs]ANA: We shall see. So, Jenn, we've had guests from all walks of life come on to our podcast and talk about their journey. And we love hearing how people got started in tech. Like, what caught your eye?JENNY: That's actually a very good question because how did I get here? I honestly don't know how I even got here.[laughter]ADRIANA: My favorite answer to date, yeah.ANA: That's okay.JENNY: I don't know how I got here. Oh, I remember there was one time, I do remember this; way back in school, I was applying for just a summer job in the U.S. and just for the fun of it. I was applying back in December for a summer job. Why? You're probably like, why? Why do you apply for summer jobs in December? Well, apparently, the Americans they do all their summer job hiring in January for preparation for summer jobs starting in May. So they do all the interviews in January and everything. They start prepping all HR people to pull you in wherever you are in the world so that by March 1st, they already have people lined up ready to go. So they fly them in ready for April 1st, May 1st. And then I'm there, voila, for a summer job. Anyway, I didn't know, and I was going like, okay, here I am in computer engineering. I didn't know anything. I knew nothing. And I saw in this job posting, "Do you know Python?" I go like, hmm, I don't know Python or anything like that. Oh, oh, oh, and do you know Perl? No, I don't know Perl. [laughter] Okay, let's look it up. Let's Google. Let's Google it up. Then I was like, okay, bam, on my resume, I can say I know Perl. [laughter] I can simply say on my resume, "I know Perl. I know how to do that." [laughter] And lo and behold, I got selected for an interview. And they say, "Hey, you know Perl? You must be an expert on this." I go like, "Yeah, sure. [laughter] Give me a job, please. Please do. Please. Please do." They go like, "Great. You're coming in May 1st you start.ANA: Oh my God. [laughs]JENNY: And I go like, [gasps] yeah, that was it. That was absolutely it. They flew me in. I'm like, "Okay, I know Perl." "Okay, but what year are you in?" "Third year." "But how much Perl experience do you have?" "I read this document. [laughter] That's all I know." And they said, "Well, good enough. You're here already. It doesn't matter. [laughter] Oh, by the way, you get paid $22 an hour." "Oh my God, this is awesome." [laughter]ADRIANA: You're rich, right? By university standards. [laughter] ANA: As a college student, I'm like, well, I mean, as a college student, but just in general, that is really good money for a first job when you're anywhere. [laughs] ADRIANA: Yeah. Totally, totally.JENNY: Yeah, absolutely. That's all I did. On the job posting, they were looking for someone that knew Perl. I really spent 40 minutes reading that document [laughter], and then I can say on my resume I know Perl, which is true. It is true. Did I know how to run it? Yes, Perl blah, blah, blah.pl. Okay, what does it do? Hmm, [laughter] I don't know. And I got paid 22 bucks an hour. And I said, "Oh my God, this is awesome." I got flown in. I had an apartment. Yeah, my apartment was covered by my income. That's okay and everything. And I had extra money to spare after being paid 20 for 40 hours a week, sure. And I had more money left over at the end of the summer. And I go like; this is awesome. So that's how I started off with.[laughter]ANA: You mentioned you were studying computer science, computer engineering.JENNY: Computer engineering, that's right. That's right. ANA: So, what got you into computer engineering? JENNY: Oh, because I didn't get into other things. [laughter]ANA: This story just gets better.[laughter]ADRIANA: This is like the best story. [laughter] What did you apply for? JENNY: Civil. [laughs]ADRIANA: You applied for civil engineering, and they put you in computer engineering? JENNY: [laughs]ADRIANA: See, this is the state, like, Jenn and I went to school, like, we were in university together. We were in different programs. I remember around that time, computer engineering was the hot stream of engineering that everyone wanted to be in. And it was funny because you ask half the people, "Why are you here?" "It pays well." "My mom wanted me to study computer engineering," [laughs] or I guess in your case, "I got rejected from civil engineering."[laughter]JENNY: My physics mark was really shitty, and they were like, okay, you're not going to get in here. [laughter] And then it was like, but why didn't you apply to chemical? Because chemical I was actually really good at, I was getting top marks. And chemical was my third choice after computer. [laughter] So civil didn't want me. [laughter]ANA: Almost. You almost made it to chemical.ADRIANA: That is so funny. [laughter]JENNY: Civil didn't want me, so computer took me. And then chemical, I guess they would have wanted me had they gotten the opportunity, but hmm -- [laughs]ADRIANA: Computer engineering got to you first. [laughter]JENNY: It's sad. It's really sad. [laughs] So that's where I ended up with. But why did I stick with it? Because after school, the company that I eventually got hired into, Motorola, I was put into a team for not just the cellular networks but the whole telecom network, the whole entire framework. And that was an eye opener for me as to how your cell phone calls started off with on that little handset going all through the base stations to the MSCs and then to the mainframe where I actually set the call setups and everything. So that's ultimately where my interest was coming from, just from my first job. In school, you learn. You kind of are taught it and everything, but you really don't know how it works until you're actually getting your hands deep into it so that you know that, hey, this call starts at this stage, to this stage, to this stage and eventually gets to this. And then wherever I am in the world, eventually, it gets routed to wherever, here to there. And everything comes right back out to whichever...whether you're talking to someone on the telephone line, or to someone else's cell phone, to an IP phone, or anything like that. So that kind of communication, I thought, was really, really cool, and that's where I started off with. And I'm kind of...even though I'm now in banking, and I'm not quite touching that right now, I'm still very well-versed with how things are working here and there and how things are working in the industry. So that's where I'm at. [laughs]ADRIANA: That's so cool. And the other interesting thing, too, from when you started in telecom, is that it was probably around the time when cell phones were finally starting to become popular where it wasn't just the "use cell phone for emergency calls." It was like, oh, I can use it to talk with my friends. And then texting was starting to become popular on those little, [laughs] tiny keypads where you had to press the key like three times to get to the letter C. [laughs]JENNY: Right. Right.ANA: I miss those days.ADRIANA: [laughs] Yeah, the simpler timesJENNY: I worked on the original StarTAC phones, I did.ADRIANA: That's so cool. [laughs]JENNY: I worked on the original Razr, the Motorola Razrs. I worked on the original -- ADRIANA: Oooh, that was a sleek phone.JENNY: Oh, it was a sleek phone.ADRIANA: Super sleek.ANA: I owned the Razr.ADRIANA: [laughs]ANA: I also owned the other Razr that was like a non-flip phone, the pink one. Yes, that was...I remember being like; I must own this phone.ADRIANA: Oh, pretty. [laughs]ANA: And it was one of the first phones that had integrations with Apple, so it was like an iPod phone. And it was like the coolest commercials ever. And I was like, oh my God, yes. [laughs] So I'm a Razr girl.JENNY: I'm glad to hear that because it is, like, if you look it up on Wikipedia, it was, or is, was, the most bought phone in the world, and it's still now; why? There are different reasons, but it was the most popular phone. I'm not saying the iPhone is not. It is very popular now. But if you look it up, you can see it's right up there.ANA: Have you all heard that there's this group of Gen Zs that are trying to make it a thing to bring flip phones back? JENNY: Yes. ADRIANA: Yeah, it's hilarious.ANA: [laughs] How do you all feel about that? ADRIANA: I mean, I loved having my flip phone. I loved having a flip phone. It was so awesome. And I was really sad, like, I love my iPhone, but I was really sad that it was no longer a flip phone. There's something very satisfying about just flipping it open to make a call. [laughs]ANA: And on that note, I personally miss the sidekick. Being a millennial, the sidekick was like, full keyboard.ADRIANA: [laughs]ANA: Moving on from Blackberry, I was like, oh, look, it's got that cute, like what? Like 280 flip of a screen. [laughs]JENNY: Oh, that's right.ADRIANA: Oh, yeah, yeah. I never used one, but I remember there was a period in what? Like the early aughts where it was popular.ANA: Like 2005?ADRIANA: Yeah, 2005 to 2000 and, I don't know, 10, 8, something.ANA: 23? [laughter]JENNY: So, ultimately, yeah, phones I actually worked on. I still work on them now. But even back then, I even knew about the whole underlying infrastructure as to how all the calls are going through, how to intercept, to change to look for certain things. So every single keypad that you make, I see it. If you're in the back end, you could see every single thing. Oh, someone's putting in their credit card information into their phone; I see it. You can see it. It's all there. And it's really interesting when people sort of say, "Oh no, I'm keying in my credit card. I'm keying in my birthday and everything." Well, don't worry, well, for the most part. [laughter] It's pretty safe. It's pretty safe. Unless you have some judge that has put out a request for this sniff, we need to get this information out. So I've gone around to many different parts of telecom, at least specifically for cell phones and such. It's interesting how it all goes around the whole circle, how things get around, and people see how it works and everything. ANA: That's super cool.ADRIANA: That's awesome. So then, how do you go from cell phones to testing software?JENNY: That's really interesting because one of the biggest changes that happened to me about 10...yeah, ten years ago is the need, at an infrastructure level, as how can we emulate how many calls are happening at the same time? I mean, right now, our biggest problems, at least for the telecom level, is to say, how do we reproduce a high call load? How do we reproduce that? And how do we reproduce not just at one spot, how do we reproduce it at a state level, at a tri-state level? And that need was mandated by the government to actually prove that, hey, does the software work? Can it handle that load? Whoever's buying the software they're paying billions of dollars for this, but they need proof to say that can it handle it? Will it die at the utmost need of time? I mean, we wouldn't want something like that to happen. We've already seen instances where networks have gone down, and I'm not going to name them or anything like that or name instances, but we've already seen it. We've experienced it, and it's pretty crappy. It's really shitty when hey, the cellphone network or telecommunication network is down because there's an overload. So that's one of the reasons why that came out, why I came out in testing now, because there was an absolute need where the buyer wants proof that can it handle it? We need to show it. The developer has claimed that it works, but they haven't tested it. They haven't tried it. They really haven't. I mean, one cell phone call, sure, that's one.ANA: [laughs]JENNY: But you need to make a couple million. And it's not just for one at one point; it's like a couple million for over a period of 18 hours, 24-48 hours, more than that. And that was the need, that was absolutely the need. And how much testing is done right now, I'm not going to comment. [laughter] But there is definitely a need for testing. Absolutely.ANA: What are some of the practices that go into doing these types of testings? Like, is it all using stuff that's built internally that's very specific to your organization? Or are there bigger projects that are used…

    Full show notes at the publisher

    Building for Developers with Daniel Kim of New Relic Mar 21, 2023
    Show notes

    About the guest:Daniel Kim (He/Him) is a Principal Developer Relations Engineer at New Relic and the founder of Bit Project, a 501(c)(3) nonprofit dedicated to making technology accessible to underserved communities. He wants to inspire generations of students in tech to be the best they can be through inclusive, accessible developer education. He is passionate about diversity and inclusion in tech, good food, and dad jokes.Find our guest on:Daniel’s TwitterDaniel’s LinkedinDaniel’s TwitchFind us on:On-Call Me Maybe Podcast TwitterOn-Call Me Maybe Podcast LinkedIn PageOn-Call Me Maybe Podcast MastodonOn-Call Me Maybe Podcast InstagramOn-Call Me Maybe TikTokOn Call Me Maybe Podcast YouTube ChannelAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:New RelicOpenTelemetryCNCF Cloud Native Interactive LandscapeObservability Day - @ KubeCon EU 2023KafkaCassandraDistributed Tracing for Kafka with OpenTelemetry with Daniel Kim at Kafka Summit London 2022Tracing Kafka with OpenTelemetryKey Metrics To Uncover the Root Cause of Kafka Performance Anomalies with Daniel Kim and Antón RodríguezBit ProjectAdditional Links:Genki Forest - Lychee Sparkling WaterMajor League Hacking - SRE FellowshipNational Academy FoundationTranscript:ADRIANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host, Adriana Villela, with my awesome co-host... ANA: Ana Margarita Medina.ADRIANA: And today, we are talking to Daniel Kim, who works at New Relic as a Developer Advocate. Welcome, Daniel. Super excited to have you on the show.DANIEL: I am so excited to be here. I feel like I'm on a celebrity podcast, so I'm very excited.ADRIANA: Ooooh, dang. [laughter] I actually remember when you and I met at KubeCon. You were like, "[gasps] Do you host On-Call Me Maybe?" And I'm like, "Yeah." And then you're like, "[gasps] I listen to that podcast." And I'm like, "Oh my God, this is like the best moment of my life to meet someone who actually likes our podcast." So I was super stoked.DANIEL: Also, the title is the best. ADRIANA: Yes.ANA: [laughs]DANIEL: I mean, On-Call Me Maybe. Shout out to Austin.ADRIANA: Yeah, for real. He came up with a great title. First, we always ask our guests, what are you drinking today?DANIEL: So I'll open the can live on the podcast. ADRIANA: Whoo.ANA: Whoa. [laughter]DANIEL: So I just opened a can of my new favorite obsession/drink. It's called Genki Forest. And it's a Lychee sparkling water, and it is so good. I've been drinking like four cans of it every day and -- ADRIANA: Oh my God, sounds awesome. DANIEL: I have to start to ration my stockpile. So that's how good it is. So I could not recommend it more. And it's so refreshing.ADRIANA: I need to find this stuff in Canada.ANA: That sounds delicious. And I think I'm going to have to buy some for myself to be able to share back on socials and be like, "You know what? Daniel was right when he was on our podcast. This drink is amazing," because I'm also a huge lychee fan.ADRIANA: Yes. Yeah, you had me at lychee, honestly, yum. What are you drinking, Ana?ANA: I have nothing fun for today. Today is just water for me. But I am eating raspberry jello. Is that a drink? [laughs]ADRIANA: It's drink-like. DANIEL: [laughs]ADRIANA: I mean, jello takes on the form of its container. Does that make it liquid? I guess, [laughs] until it solidifies. I've got some fizzy water. I'm just finishing up a can. It's called Bubly. It's sparkling cherry water. And then I've got water on standby because I'm almost done with my can.ANA: Yeah, it's always good to stay hydrated. I'm now kind of jealous of not having a Lychee sparkling water with me. That's all. [laughs]ADRIANA: I'm like dying here because it sounds delicious, and it's given me all the bubble tea vibes. DANIEL: Yes. I had such good bubble tea last weekend. I love bubble tea. It's kind of an obsession for me.ADRIANA: Oh my God, me too. [laughs] I even make it at home. [laughs] The bill was getting too high with the bubble tea, so I'm like, I need to figure out how to do this at home. [laughs]ANA: Reasonable. I've yet to actually have bubble tea in a while. ADRIANA: [gasps]ANA: I passed by Boba Guys yesterday in San Francisco, and it's like one of the spots. And I was like, I want some, but I was going in for a dental procedure. ADRIANA: Ooh, boo.ANA: And I was like, I'm pretty sure I can't have this now, and I can't have it later. ADRIANA: [laughs]ANA: So I've been thinking about bubble tea since then. So now that y'all mentioned it, I'm like, hmm, good to remember I can't have that yet.DANIEL: [laughs]ADRIANA: When I'm in San Francisco next year, y'all are going to have to show me the awesome bubble tea shops. ANA: That's all, Daniel. I don't know the city anymore. And I feel like he frequents a lot more shops than I do.ADRIANA: [laughs]DANIEL: Yeah, I have some recommendations. ADRIANA: Awesome.DANIEL: We'll definitely go for some boba.ADRIANA: Yay.ANA: It's going to be like tracing San Francisco for bubble tea. We'll need a blog post. [laughs]ADRIANA: Oh my God, yes. DANIEL: Oh yes.ADRIANA: That's right, the drink tour, the boba drink tour. I love that.DANIEL: All the spans we could collect.[laughter]ADRIANA: I love it.ANA: So, Daniel, for folks that are just getting to know you, how did you get into tech?DANIEL: So I got into tech because I didn't know what I was doing in life beforehand. I was planning on becoming an electrical engineer. And I started my first day of my master's program, and I was like, wow, this really sucks. Because I was looking at what I was doing, and I was like, I don't feel anything looking at these math equations. And I was looking at these really complex diagrams, and I was like, if I have to do this for the rest of my life, I'm probably going to be very sad. So I decided to actually quit my master's without any plan and cold email all of the founders of the startups that I have used in the last year of my college experience. And one of them got back to me, and then I got hired the week later. So that is my journey into tech of randomness and me not liking where I was going in life.ANA: What were you studying as in bachelors that you used some tools?DANIEL: So I was doing circuits. I was figuring out how circuitry works, how semiconductors work, just very complex mathy things. Because when I first started my program, I thought electrical engineering was all robotics and cool things that you see in The Matrix, but it is just literally all math. And I was like; this is not what I signed up for. [laughter] I remember on the college website for the electrical engineering major, they have a picture of a hologram and robots. And I was like, this is what I'm signing up for. [laughter] This is so cool. But the reality kind of hit the first year, and I was like, maybe this is not for me.ADRIANA: So you wanted to make our evil robot overlords, is what you're saying.DANIEL: Exactly, but that didn't happen. ADRIANA: Oooh.DANIEL: I'm not good enough at math for that. [laughter]ANA: I feel that.ADRIANA: I mean, honestly, it's so cool that...I think it's like a really important life skill to realize that, hey, I don't like this, and I don't want to do this. DANIEL: Yeah, for sure.ADRIANA: I think it takes a lot of understanding of yourself and a lot of courage to be able to do that. So hats off to you for having done that and wanting to pursue something that made you happy.DANIEL: Yeah, I think I didn't have enough fear.ADRIANA: [laughs]DANIEL: Because I don't think I would have done that again if I went back in time. So I'm happy that it happened because I'm so happy with my life right now.ADRIANA: Yay.ANA: What is it that you do now? DANIEL: So what I do now is a lot better fit with my personality. I like to think that I have a pretty fun, outgoing personality, and that's kind of what I get to do in my daily job. I get to work with a lot of customers, engineers, developers from other communities, OpenTelemetry community members like Adriana and Ana. I get to work with all these amazing people in the community to not just sell a product but help developers understand what observability is. And that's kind of my favorite part of my job because I don't have to sell anything for my job. My job is to literally make other developers happy and help them learn and gain skills. That is like the dream job, right? ADRIANA: Yeah. DANIEL: Because I don't want anything from anyone. I just want to help people on their journey. And yeah, that's kind of my passion, too; I want to help developers learn and gain skills and be better engineers, which I love about my job.ADRIANA: That's awesome. I think that's such a lovely description of the type of work you do.ANA: And it's also nice when you're able to feel like your personality fits your job role. I always say bring your whole self to work. But I feel very similar, like, when I joined developer advocacy, it felt a lot more natural to me since I was already such a community-giving person and caring about other people that it was like, oh, now this is part of my job description, rad. I was going to do this anyway.ADRIANA: Yeah, I totally agree. Like, when I first heard about developer advocacy, I'm like, that's a job? Like, this is what I want to do. [laughs] Sign me up.DANIEL: Yeah, when I found out about it, too, I was like, wow, I didn't know this was a job either. So I'm so happy that I stumbled upon the job.ADRIANA: How does one stumble into a DevRel job? [laughs]ANA: Yeah. How do you stumble into DevRel? [laughs]DANIEL: This is actually a really weird, funny story. When I was in college, I had a lot of cojones. [laughter] So I didn't like...I was desperate, so I would do anything. So I actually Twitter-DMed, the CEO of GitLab. ADRIANA: Oh my God. [laughter]DANIEL: And I was like, "I want to come to your conference," that was happening in the city. And he responded in like 20 minutes. ADRIANA: Whaat?DANIEL: And he was like, "Okay, here are like four tickets for you and your friends." ADRIANA: Whaat? [laughter]DANIEL: And then this is a core memory for me. When I went, they had this wall of bagels. Like, they had this entire wall covered with bagels that you could grab off the wall to make yourself a bagel sandwich, and I was like, this is really cool. Because that was my first tech conference I've ever been to, and I was like, wow, this is really cool. And I heard all of these people called developer advocates or evangelists and all these engineers talk about what they're passionate about and like DevOps and really cool things that I'd never heard about. And I was like, that's a job? Where you get to have bagels and teach people about really cool technologies? And that's kind of how I stumbled upon developer advocacy. I think that was the first place where I saw a developer advocate giving a demo, and teaching, and working with the community. I was like, ooh, this sounds fun. I want to do this.ANA: [laughs] I love that you just ended up DMing a CEO of a respectable tech company. That's usually what makes a lot of people in our communities, like, you just shot your shot, and something worked out in the space.DANIEL: So, you know what's really embarrassing? Sometimes I meet people, and I realize that I DMed them like six years ago, and they didn't respond to me. So the last DM is college, me trying to get an internship.ANA: That happens to me all the time. Like, I'm hanging out with someone at a conference or, like, connect with me on LinkedIn or Twitter. And I follow them, and I go to send a message. [laughter] And it's like, 2016, they reached out for help. No answer from Ana. ADRIANA: Oh no.ANA: And I'm like, oh, I'm sorry. [laughter] Like, some years I'm available to respond to every email, and some years I'm not. [laughter] That year, I was not.ADRIANA: Oh my God, that's too funny.DANIEL: Yes, so I was definitely a hustler when I first started out. Yeah, going back through my DM history, it's kind of embarrassing all of the DMs that I sent that got no response. But I'm glad that the people who responded did respond because they helped me, like, guide, and gave me advice to the person I am today. So I'm really happy about that.ANA: Do you think that those opportunities are still out there for folks to just randomly message people they look up to or leaders in the space?DANIEL: Yeah, for sure. I feel like also teenagers and people who are coming up in the community are a lot more savvy with social media than I was. Because I remember the first time I cold-DMed someone, it was just like, "Hi, you're so cool. [laughter] Can I meet with you?" And that's not what you're supposed to do. [laughter] But little, old innocent me was like, oh, they'll definitely respond. I think other people who at least reach out to me come with questions that they want answered that's very pertinent to my job. Like, I've noticed that a lot of the folks that are coming up approach folks with a lot more intent and with really good questions. So I think those folks get to meet all of their heroes and get to interact with everyone in the community. So I think it's all about how you approach people that makes all the difference.ADRIANA: Yeah, absolutely.ANA: I think I read on Twitter at some point one of those advices is if you're going to cold email or cold DM someone, either be very specific about what you're asking for or put out there what you're willing to give in return, like, I'll give you this and would you mind giving me that? Whether it's an introduction or a 15-minute coffee, or feedback on anything.DANIEL: Yeah, for sure. Also, being persistent is important. Because I realized that some of these people I tried to DM probably get thousands of DMS a day. So following up in a respectful manner, I think, is also pretty important. Because I think some of the DMS I finally got responded to, I had to kind of follow up multiple times before I got someone's attention. So I think that was also really important. ANA: Don't give up if they don't answer the first time. DANIEL: It's probably not because they hate you because that's what I thought in the beginning. ADRIANA: Right, right. DANIEL: And I've seen these people's DMS, and I'm like, that is definitely not the reason.ADRIANA: They're just busy. So when they have a chance to respond back, it almost feels like you've won the lottery, right? [laughs]DANIEL: Exactly, exactly. ANA: Or they have ADHD, open the message, forget to respond. And they totally meant to answer, but they didn't. [laughter]ADRIANA: Oh yeah, that's true. There's that angle too. I've totally had that happen to me before more than once.ANA: [laughs] So I'm just speaking from experience of a lot of my DMs that I owe people responses to before Twitter went, like, sad face. [laughter] Yeah, that whole thing [crosstalk 13:02]DANIEL: I kind of refer to that situation like, yeah, the thing over there, yeah. And it's really sad because I feel like Twitter is where I built a lot of my relationships with the community. And it feels like my home was getting wrecked, and I'm like; I don't know [laughs] beca…

    Full show notes at the publisher

    The Crooked Path to Tech with Jen Shute of Slalom Build Mar 14, 2023
    Show notes

    About the guest:Jen Shute Benson (she/her/hers) is a Senior Director of Platform Engineering at Slalom Build. She has worked for over 25 years in the tech industry. Her early career included quality engineering, application support engineering, and systems engineering. She moved into leadership and has managed Cloud Infrastructure, Cloud Solutions, DevOps, and Platform Engineering teams. She has managed two major cloud migrations at large-scale enterprises before moving into the world of consulting. At Slalom Build, in addition to leading Platform Engineering teams in 3 geographic locations, she supports multiple markets and clients and is heavily involved in ID&E initiatives within her Platform Engineering capability and at the Slalom Build level. Jen also volunteers as a mentor for Slalom’s Women Who Build program. She is a member of Cloud Girls and co-chairs the membership committee. Cloud Girls is a non-profit organization dedicated to community building and celebrating the success of women in cloud careers, and giving back through awards and charitable programs.Find our guest on:LinkedInFind us on:On-Call Me Maybe Podcast TwitterOn-Call Me Maybe Podcast LinkedIn PageOn-Call Me Maybe Podcast MastodonOn-Call Me Maybe Podcast InstagramOn-Call Me Maybe TikTokOn Call Me Maybe Podcast YouTube ChannelAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:HugOpsSlalom BuildHRISMicrosoft AccessQuality Engineer (QE)DreamweaverHerokuActive ListeningCloud GirlsAdditional Links:Slalom Women Who Build ProgramTranscript:ANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host, Ana Margarita Medina, and with my awesome co-host...ADRIANA: Adriana Villela.ANA: Today we're talking to Jen Shute, who is a Senior Director of Platform Engineering at Slalom Build. Thank you for joining us today.JEN: Thank you for having me. I'm very excited to be here with you today.ANA: In true On-Call Me Maybe fashion, we always like asking our guests, what are you drinking today? JEN: Okay. So I've brought with me some kombucha. It's organic brew, Dr. Kombucha, and it's a new flavor that I've never tried before. It is blood orange ginger, and it is very good. I highly recommend it to anybody who likes kombucha.ANA: I'm a huge kombucha nerd, and it makes me want to have one of those this morning too. That ginger sounds delicious. What about you, Adriana?ADRIANA: Today I've got water. ANA: Nice.ADRIANA: Nice and simple, my go-to drink. [laughter] How about you, Ana?ANA: I'm going to make some water and some caffeine. So if you've listened before, it's usually the yerba mate with mint. I'm doing one of those today; just trying to pick up the energies. With all these California storms going on, I'm like; I need all the positivity energies that I can get.ADRIANA: Oh yeah, you guys finally got a break in the weather. Somewhat. [laughs]ANA: We had a 24-hour break, and we're back to another three, four-day storm. ADRIANA: Oooh.ANA: So it's like, I think, four atmospheric rivers hitting California. ADRIANA: Holy cow. ANA: And for folks that are interested, they should look at the maps of what it was like the drought in California in December and what it's looking like now and the fact that some parts of California are still in drought and a lot of parts are very much flooded. It's crazy. Global warming is insane.ADRIANA: Yeah, well, definitely a stark contrast to Toronto. We actually got snow today. I woke up with, I'd say, five centimeters of snow. What's that in inches? Like two and a half inches. So yeah, we got a dose of proper winter after rain for the last couple of weeks, so yay. [laughter] Definitely better than the floods. I'm sorry you're having to go through that. That does sound very awful. So I hope it subsides soonishly.ANA: Thank you. Definitely HugOps to California. I feel bad for all of it. And, I mean, I think the entire world has been having some crazy weather right now, and hopefully, it is a bigger wake-up call to those that are currently not looking at it or being proactive about the actions that they take against the environment.ADRIANA: Yeah, I totally agree. What's the weather like in your neck of the woods, Jen?JEN: I'm in Ohio. And I think I generally I'm pretty close to what you have in Toronto. You know, I haven't been outside today. I just kind of peeked out the window to see if we got any snow since you mentioned you had snow. It doesn't look like it. But I think we're probably in pretty similar climatic regions, so we both got a little lake-effect snow and --ADRIANA: Yeah, totally.ANA: I like snow. I would not be able to live somewhere with snow. I think this rain made me realize --ADRIANA: [laughs]ANA: This type of weather just makes me extra sad, and that's really hard. ADRIANA: Yeah, that's true.ANA: So with snow, I would not be able to live, like, I've always lived tropical or next to water. I think California is the coldest I've ever lived, which says a lot. [laughs]ADRIANA: Oh dang. Oh yeah, that's right. You lived many years in Miami, right?ANA: Yeah, I've lived in Costa Rica, Nicaragua, Miami, and now San Francisco Bay area. So pretty privileged, I would say.ADRIANA: Nice, warm weather. I do miss that. I do miss that. [laughs]ANA: Well, Jen, since we have you here, we wanted to hear how you found your way into technology. What was your path like from that moment when you were like, this was cool too. I can make money. JEN: I actually had a really roundabout path, and I think that's not uncommon for people in tech. In college, I took psychology, so I graduated with a psych degree. I worked in human services for a couple of years. I found that I was not making enough money, unfortunately, to support myself. So I tried to figure out what's a transition I can do? Like, I don't feel like I'm ready to, you know, or I'm at a point where I could go back to school. And I thought human services might be a shift that I can make a little easier. And so I got a job in HR. At the time, it was myself, and there were three other women that I worked with in our team. And I was the only person, you know, I was in my 20s at the time. I was the only younger person. And we had a HRIS where we kept all of our HR data, and nobody else really wanted to use it. And so I kind of became the person that took over that HRIS, and I did all the management. And it kind of got to the point where if we needed to be tracking something that we weren't...I'm kind of aging myself, but it was an Access back end. I learned --ADRIANA: Oooh. Good times. I remember Access. [laughter]ANA: Same. I'm certified in Access 2005. [laughter] ADRIANA: Oh my God. [laughter]JEN: So I learned how to go in and add fields and did a couple of trainings at the company that created the HRIS that we were using, and I actually ended up getting told about a QE position they had there. And I had always kind of thought that people who worked in tech were super cool. I always thought that's something I could never do. But I went ahead, and I applied for the job, and I actually got the job. So that's how I got into tech. So I worked in QE for probably about five years. And then I switched over into systems engineering and then kind of worked my way through. And as things changed and we started moving to the cloud, I started working more in the DevOps realm and cloud. So that's my journey so kind of a roundabout way, but it got me here.ADRIANA: That's such a cool path to tech. And what are the things that you're like, oh my God, so much has changed in tech from when I started to where I'm at now? What do you think is the biggest thing where you're like, holy cow, I could have never envisioned this happening tech-wise?JEN: So this is a great question. And I feel like it's a hard one to answer because I would love to say everything. Like, when I first started, I was testing software for a client-server application. And when I moved into systems and infrastructure support, I was supporting a monolithic application that was on-prem. And what we're looking at is scalable systems that are resilient, and self-healing, and containerized. I almost have to say, like, everything has changed, and I would not have predicted any of that.ADRIANA: Yeah, that is so true. I kind of feel the same way. I mean, my first foray into programming was on a computer that wasn't even on a network. There was no internet that I was aware of at the time. I think it existed at the time, but I wasn't aware of it. Writing code in QBasic, [laughter] like, I don't even think QBasic exists anymore. [laughs]ANA: Or even looking back at the text editors we were using, like, I was using some obscure one. ADRIANA: Yes.ANA: And then I ended up using Dreamweaver 8. And to think I was doing more of like websites and stuff, so using FTP to upload sites versus just going into the server in other ways. Like, it's interesting to look back on things like it.JEN: I mean, it really makes you wonder, like, what's next that we can't even imagine yet. How advanced are we going to be when we're going to be looking back on this and be like, "Oh my God, remember when we were in AWS?"ADRIANA: Yeah, it's true. And as radical a change as it is from starting out in one's career versus now, at the same time, I think everything's just been slowly evolving towards where it is. I was having a conversation with my dad the other day, and he was like, "Yeah, I was doing stuff in the cloud before it was even a thing."ANA: [laughs]ADRIANA: And he was talking about, "Yeah, I was using Heroku." And I'm like, oh damn, yeah, I totally forgot about Heroku. Stuff like that has paved the way for where we are right now, which is super trippy.ANA: It is always interesting to see when Heroku comes up in conversations.ADRIANA: [laughs]ANA: Because everyone literally always forgets about it. It had always done so much movement around empowering developers. So it's interesting how developers, like, it was one of their first aha moments in this type of platform space. But because other vendors have such larger marketing budgets, you kind of put it somewhere else in your brain, and like, who taught you how it works? You forgot about it. It's interesting. So with the current job that you do right now, Jen, what is it like managing the staff that you have in your day-to-day?JEN: I mean, first of all, I have an absolutely fantastic job. I really have found a home at Slalom, and so I love what I do. My role is pretty diverse. I do people management; I do sales support, I do client relationship management, project oversight. The thing that I really like most about it is I'm constantly learning. This is my first time that I've worked in consulting in that world at all. And so that's even been, like, over the last three years, such a growth opportunity for me. So it's great. It's busy. It's learning every day. ADRIANA: So at what point in your career did you...it sounds like you were more hands-on with the coding earlier in your tech career. And now you're, I guess, a little more hands-off, and correct me if I'm wrong. At what point did that transition for you? And how was that transition for you because it's not always for everyone either, right?JEN: It was gradual. I worked as a, like I said, systems engineer for a number of years. And I moved into my first management role managing a small team. I'm going to say it was probably ten years ago, although if I looked at my resume, I might be off, you know, plus or minus three years, you know, initially managing small teams. I really was still able to get hands on keyboard and help my team with troubleshooting issues. As my responsibilities grew, I kind of moved into one of those roles where you're in meetings most of your day, and there were things that I liked about it and things that I didn't. I do miss feeling like I could just jump in and grab a keyboard and help my team out when they need help. And there are times I think, man, I really want to go back and do that again. One of the things that I love most about my job is being a coach and mentor and helping other people grow. And I think, too, that probably also comes from that psychology background. And my career choice was really to go into some kind of counseling, and so it's kind of taking that and implementing it in the role that I'm in right now. There are times I miss it, but I also really love what I'm doing right now as well. And given the choice, I probably would choose to do both, but I like what I'm doing right now. I wouldn't give it up, probably to go back in time.ADRIANA: Cool. That's awesome. And it's really cool also having the psychology background to lean on to help you with being a people manager because dealing with people is friggin hard. [laughs]JEN: Exactly, yeah. It sure can be. ANA: [laughs] And it's a part of that...because I think there are a lot of people that go into management just because, one, they feel like they need to in order to have a career progression. And then there are some people that go into management because a company needed managers, and they got thrown to be a manager. So when you do find managers that, one, want to be people-first managers but, two, find such huge passion and have the skill set to do it, it is kind of like those unicorn managers that are really hard to come by. Because it's that, like, once you make people happy, believe in themselves, that's when they can really bring their best selves to work and do their best job.ADRIANA: Yeah, and really being able to mentor them is, I think, key. I mean, I think both Ana and I we wouldn't be where we are if we didn't have good mentor managers that helped us along the way. So knowing that you can shape someone's life in a positive manner is super awesome.JEN: Yeah. And I have to say, I've been really lucky, too, because I think a lot of times the way you learn how to be a good mentor and a good manager is by having good mentors and good managers. Some of my managers that I've worked for in the past that I can point to and I can say you know what? I really grew under that person, and I learned to be more confident and I learned how to take care of my people. And so I guess it's also kind of passing on what had been given to me in the past.ANA: What would you say are two or three things that you would pass on to folks that are wanting to become managers, people that want to be people-first managers or those managers that are trying to be more human-focused, or those VPs that are like, I should probably care about all my staff a little bit more, but I'm so overwhelmed with work?JEN: So to think about what are the things that I think I would tell someone to be a really good manager, or mentor, coach, give feedback. Give kind feedback, but give feedback and give it timely. And try and give good, specific feedback and help that person with how they could do something better. So I think feedback is key. And then I think the other thing is having empathy and listening and hearing what someone is telling you. I've actually recently even myself I've been working on active listening, and it's a real challenge because a lot of times, I want to reach out and relate to that person and connect by saying, "Oh yeah, me too. I had this similar..." But I've…

    Full show notes at the publisher

    Security is Thy Friend with Michael Kehoe of Confluent Mar 07, 2023
    Show notes

    About the guest:Michael Kehoe is an author, speaker and Sr Staff Security Engineer at Confluent. Previously he was a Sr Staff Site Reliability Engineer (SRE) at LinkedIn architecting LinkedIn’s move to Microsoft Azure. Before graduating with a Bachelor of Electrical Engineering from the University of Queensland (Australia), Michael interned at NASA Ames Research Center building small-satellites known as Phonesats.While working at LinkedIn, Michael led the company's work on Incident Response, Disaster Recovery, Visibility Engineering & Reliability Principles. He has also been embedded with the profile, traffic, espresso (KV Store) teams. After leading LinkedIn’s last physical data-center build, he is now the architect for how LinkedIn builds its infrastructure in Azure.Michael has spoken at numerous events all over the world and has authored the books "Cloud Native Infrastructure with Azure" and “Reducing MTTD for High Severity Incidents”.Find our guest on:TwitterLinkedInGitHubPersonal BlogFind us on:On-Call Me Maybe Podcast TwitterOn-Call Me Maybe Podcast LinkedIn PageOn-Call Me Maybe Podcast MastodonOn-Call Me Maybe Podcast InstagramOn-Call Me Maybe TikTokOn Call Me Maybe Podcast YouTube ChannelAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:ConfluentLinkedInSRELightweight Directory Access Protocol (LDAP)eBPFLiz RiceGeneral Data Protection Regulation (GDPR)Terraformtfsec (security scanner for your Terraform code)Cloud Native Computing Foundation (CNCF)Azure PolicyOpen Policy Agent (OPA)Kubernetes Admission ControllerAdditional Links:Cloud Native Infrastructure with AzureReducing MTTD for High Severity IncidentsTranscript:ADRIANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host, Adriana Villela, with my awesome co-host...ANA: Ana Margarita Medina.ADRIANA: And today we are talking to Michael Kehoe, who works at...I don't know where you work. [laughs] MICHAEL: Confluent.[laughter]ADRIANA: Confluent. Excellent. Welcome, Michael. [laughs]MICHAEL: Thank you, ladies. It's so great to be recording with you both.ADRIANA: So, first things first, what are you drinking today?MICHAEL: Today, it is just water. I just got over a cold recently. So we're recording this in the middle of the day. So water for now, but I've got some coffee liqueur to finish before I get on my plane tomorrow. So I think that will be my after-work drink this evening.ADRIANA: There you go, goals for the end of the day. MICHAEL: Absolutely.ANA: That seems really tasty to look forward to towards the end of the day, so I'm definitely a bit jealous. For me, I'm actually very much feeling in the very festive mood. And I decided to get a white chocolate peppermint mocha with peppermint from Starbucks. ADRIANA: Yay. ANA: I'm on that holiday cheer kick today.ADRIANA: Hooray, hooray. I've got a can of Perry lime with me and some water to supplement. So not super exciting, I'm afraid. ANA: [laughs]ADRIANA: But hydration is hydration, so good vibes all around. [laughs] All right, cool. Well, Michael, we always like to hear from our guests, like, how'd you get into your current career path?MICHAEL: When I was very young, four or five, I had an interest in computers. And during school, I had the opportunity to tap into that a little bit, but not too much. When I was in college, I got an opportunity to work for my university's IT department. I went to school back in Australia, and the universities are generally much larger there, so we're talking about a user base of 40,000 students, 10,000 staff across dozens of campuses. This role was in their network department. I started doing low-level tasks, making sure that switch ports worked in offices, setting up network switches. And that got to evolve into helping build out new data centers. It also allowed me to go and do more network engineering tasks. So my university was an ISP as well for not only the university but also commercial customers as well in the form of both residences but also other universities, other schools. So this gave me a lot of experience to go and help build out actual solutions, build customer experience, customer service mentality a little bit. I got some exposure working with our Linux team as well. So I got to learn Puppet. I got to learn a little bit of LDAP and was able to start putting these different skill sets together. At the same time, Google recruiters came to campus, and they had a presentation on SRE. And I'm like, oh, this is so cool. You get to do a little bit of coding, a little bit of Linux, a little bit of network, and problem-solving as well. And I really loved the combination of those skill sets. This is back in about 2012, 2013. There was this blog, I think it's still around, called "High Scalability," which talked about real-world architectures of different tech companies. And I immersed myself in that to learn how all these things work. And so towards the end of college, I did some job interviews, and, thankfully, was able to interview at LinkedIn for an SRE position, and thankfully got the job and then went from there. I was on the Profile team at LinkedIn, and then from there went on to a more central team that handled more infrastructure across the whole site and practices and procedures. And during that time, I also got seconded to a number of different teams to help them through some trying situations. So I got exposed to everything from the Ingress traffic layer all the way to backend key-value databases and grabbed a bunch of experience across teams, which was really awesome to be able to learn such specific knowledge across a variety of different experiences.ADRIANA: Cool. So you actually got an SRE role right out of college, then. MICHAEL: Yes. It was really challenging to do that. A lot of companies won't hire SREs out of college because it's very difficult to get that experience in college unless you've done an internship where the bar is a little bit different. But yes, I graduated and got on the first plane after grabbing my visa and got to work. And I'm very grateful for the opportunities I had at LinkedIn, especially to be able to just immerse myself in so many different areas of the stack.ADRIANA: That is wild.ANA: You also got a chance to come into SRE at a prime time. It hadn't necessarily kind of picked into a lot of big companies starting to use it, and the book had not come out yet. So folks were kind of still like, oh, there's this thing that you do to keep systems up for humans and Google calls it SRE. And, I mean, at that time, knew that Facebook called it production engineering, but that was it. Like, nobody was really trying to name-grab or anything. It was a really interesting time, so...ADRIANA: Probably wasn't solid like it is now [laughs] because it was kind of at the forefront, right?MICHAEL: I mean, I think at the time, there was a loose definition of what it was. And for those hyper-scale companies like Facebook, like Google, like LinkedIn, and others, I'm sure they worked out what made sense for their companies. At the time, I think a number of other companies were like, what is this thing? And post-Google SRE book publication, companies are now trying to work out how do I make this work in my organization? And we definitely seem to be at the point where like, okay, this book isn't canon; it is meant to be a guide. And each company finds their own way to put these various principles into practice in a way that makes sense for both the culture of the business but also in terms of how the business is run.ANA: 100%. And I think that we're still seeing that shift to people realizing that it's not a one-size-fits-all. I think we've had a lot of those conversations in our podcast recently where it's like, nope, you can't just grab the book and apply all to all your systems. It's all a lot of hard work. And as you said, culture comes into play. But the way that Google does it, the way that Facebook or LinkedIn does it does not apply to your enterprise company or your startup.MICHAEL: Right. A friend of mine who worked at LinkedIn also has his own podcast series. He has a quote that "Culture eats technology for breakfast," which is very true.ANA: I know that you, like, I met you when you were working at LinkedIn. You were working specifically on EBF and just sharing SRE practices. What do you feel about that space now, considering EBF observability has taken a huge rise? And as you were talking about it in 2018, you were the only person at conferences speaking on it in a sense.MICHAEL: Right. I wish I had more time to spend on it, [laughs] honestly. So eBPF, when I was talking about it at, I think, O'Reilly Conferences and also the SREcon series it, was in its infancy in the industry. The foundations of eBPF started in; I think, 1991. And then the first commits to what's now known as eBPF was late 2013 or early 2014. And so it took a couple of years for people to start picking it up. And now you see companies specifically like Cilium that have really accelerated its growth, and they've created a very well-known product. I think the great thing about that space is it is more or less an open-source technology eBPF. So anyone can go and create something exceptionally powerful with it, which is great. Obviously, Cilium has cornered the market and makes it more user-friendly to go and use in a Kubernetes containerized environment. But there's nothing really stopping me from going and building a high-performance load balancer or DDoS system if I really want to.I think for the space that I'm in now in security, we can go and do very low-level, kernel-level auditing of system call events, or go and do deep introspection of network flows without having to worry about the overhead of that software. And that's so exceptionally cool. So while Cilium has cornered the market for now, I can't see a reason why other companies won't come out with eBPF-based network flow monitoring and different IDS solutions that fit a broader market than just platform-hosted Kubernetes.ADRIANA: Now, for our listeners who might not have heard of eBPF or have heard of it but aren't really sure what it is, can you provide a super high-level definition description?MICHAEL: Sure. So BPF essentially allows you to run your own programs in kernel space without needing a kernel module. The best example of this is tcpdump. You define your own filter, and that filter actually gets compiled into kernel bytecode. And then the kernel actually goes and pauses the packets coming through your network interface, rather than going and doing that in user space, and that is massively efficient. So that concept is not particularly new. tcpdump has been around since the early '90s. But with eBPF, you can go and create your own filters and programs, go and create those in userspace. And then, they go and get compiled and get run safely in kernel space, which generates the efficiency of the program. So you can go and do network-level parsing, load balancing, or even look at all the system call events happening on a machine, do that in kernel space, get the results back in userspace, but do it at exceptionally high throughput, which makes it very attractive to system operators such as myself.ANA: That's super awesome. I mean, it gives a lot of flexibility, and you get to use it in what ways works for your team.MICHAEL: Absolutely. There are endless ways you can take it. Definitely, the bar to entry has been a little bit challenging, just because you need to be able to write programs that actually run in the kernel, so understanding all the intricacies of those C or Assembly if you're really eager for these programs. It is a little bit more challenging, especially for... I've written some network programs, you know, you need to understand the packet structure exactly to make things work. But yeah, if you know what you're doing, the possibilities are endless. And I think that's what makes it really exciting.ANA: I haven't been following too much of the trends around it. But are we also then seeing, I guess, this being used a lot more in the security space?MICHAEL: Definitely for doing container-based networking, yes. And Cilium also allows you to do the identity-based policies as well, which I think is very exciting. Because you sort of say, all right, this service can talk to this service, and a bunch of layers of abstraction take care of that for you. I think there's still a space where...the hyperscalers have definitely done it. Like Cloudflare, if you go and look at the eBPF tag on the Cloudflare blog, you'll find endless amounts of ways that they've used eBPF, probably the same with Facebook as well. The rest of the industry, we really haven't seen eBPF IDSs come to the forefront yet where we can really do deep introspection. Falco uses eBPF as well to do some of its system monitoring. So we're getting there, but I don't think we're going to fully mature for probably another two or three years. I know Liz Rice, who is another person who has written on eBPF before and also works at Cilium; she's working on an O'Reilly book at the moment, which is really going to take us back to first principles and walk people through how to build their own programs. So I'm sure when the publication of that book happens next year, we'll again see a jump in interest in the space.ANA: That's exciting. One of the questions we also haven't touched upon is how did you transition from SRE to security?MICHAEL: While I was at LinkedIn, I had an interest in the space. LinkedIn, I think they still do it, had a Security Champions Program. So they took someone from each engineering department and allowed them to go through a quarterly training program. So you did some online Stanford cybersecurity courses and got paired with a security team member to go and work on a security-based project in your engineering team. So I did one of those programs while I was at LinkedIn.While I was working on some of my projects towards the later part of my tenure at LinkedIn, I was heavily engaged with the security team on helping make our cloud infrastructure secure there. When I was looking for a new role, I was really excited to go and do something a little bit different, something a little bit new, and somewhere where I had a lot of space to grow and a lot of things to learn. So making the jump to Confluent and joining their security team was an exciting step. I definitely have learned a lot to date, especially since Confluent is a true multi-cloud vendor. So there are a lot of interesting challenges to be solved there.ADRIANA: To continue on the security thread, I feel like, in some ways, security is a thankless job, right? Because I've been in companies where security policies are enacted, and developers are like, "What the hell, man? I need to be able to do my job for blah blah blah blah blah." But then there's like all this stuff happening behind the scenes that security folks can't necessarily talk about. What are your thoughts around this?MICHAEL: So there's definitely a balance for infosecurity professionals defined in their roles. For myself, I see my partnership working on two levels, sort of similar to SRE, number one, the business needs our role to be successful for the business to keep growing. Working for a SaaS vendor, customers want certain requirements of our platform, certain guarantees, and it's up to us to help ensure that those are in place.…

    Full show notes at the publisher

    Transform Thyself with Shingi Kanhukamwe Feb 28, 2023
    Show notes

    About the guest:Shingi Kanhukamwe is an Executive Transformation Advisor working with Export Development Canada. He has 11 years of Agile experience and 9 years focused on leading transformation initiatives in large, complex organizations. He has worked at various financial organizations and has also worked as a consultant. Find our guest on:LinkedInFind us on:On-Call Me Maybe Podcast TwitterOn-Call Me Maybe Podcast LinkedIn PageOn-Call Me Maybe Podcast MastodonOn-Call Me Maybe Podcast InstagramOn-Call Me Maybe TikTokOn Call Me Maybe Podcast YouTube ChannelAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:Content ManagementIBMDigitizationCloud-Native TransformationSociotechnical systemsMainframeNetflix’s culture explainedTranscript:ADRIANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host, Adriana Villela, with my awesome co-host...ANA: Ana Margarita Medina.ADRIANA: And today, we are talking to Shingi Kanhukamwe, who is an independent consultant working on organizational transformation. So, Shingi, welcome.SHINGI: Thank you. I'm so happy to be here.ADRIANA: First things first, important question. We start off for all of our guests; what are you drinking today?SHINGI: I am drinking a kombucha, ginger-lemon kombucha.ADRIANA: Ooh, awesome. Exotic, I like it. How about you, Ana?ANA: I'm honestly always a huge fan of anything ginger. That's actually what I had for my breakfast caffeine which was like yerba mate with ginger tea. It was delicious. But for today's podcast recording, I'm on just regular H2O.ADRIANA: I, too, am drinking water. I was for a previous recording drinking some green tea, but I ran out of that, so water it is.SHINGI: Oldie but a goodie. [laughs]ADRIANA: Exactly, can't go wrong with water. One question that we also like to ask our guests is, how did you get your start in tech?SHINGI: Actually, growing up, I'd always been really interested in technology, so probably starting about the time I was 9 or 10, I got really interested in computers. And I spent so much time on my computer that my parents were getting worried about my future because [laughter] they're like, "You're spending too much time on this thing. Like, is there a future with these things?" To the point where they were just like, "Okay, we're not buying another computer because you just spend way too much time with this thing." So what that made me do was it made me try and squeeze as much performance out of the machine as possible. [laughter] So I would do all these things to kind of try and get the machine to run programs. Like, I'd boot the machine into DOS and load programs directly from there. But I also got more interested in kind of...I was kind of like, well, what can I do? Well, I can't change the hardware.ANA: [laughs]SHINGI: But what can I do from a software perspective? Like, what optimizations can I leverage to get more out of this computer? Because they're not buying me a new one. ADRIANA: [laughs]SHINGI: And I actually got interested in terms of, like, oh, I can't buy a whole new computer, but can I buy certain parts? Like, if I borrow more RAM, like, is that going to help? ADRIANA: Ooh.SHINGI: That's how I got interested in technology from a personal perspective. Weirdly enough, that didn't end up resulting in me studying computer science. But I did a lot of self-study from a networking perspective. So at one point, I was really interested in networking and just thinking about pursuing a career path. So yeah, the first job I got was actually a communications job working on Parliament Hill for a Member of Parliament. But a big part of the job was actually technology because I ran the website. And back in 2004, there was no content management, [laughter] well, not that there wasn't content management in the marketplace. There wasn't content management where I worked; let's be specific.ADRIANA: Right. Right.SHINGI: So it was this PHP monstrosity where -- [crosstalk 3:24]ANA: [laughs]ADRIANA: Oh wow.SHINGI: You were liable to break stuff when you were just updating the content. That was super fun. So I think, like, yeah, in terms of my relationship to tech career-wise, it's always been like a theme. But I never actually ended up working as a developer or an engineer or somebody who's like in networking in hardware. It was always doing jobs that involved some degree of competency/technical literacy. So after that, my focus was kind of in the area of digital marketing more from the marketing technology side of things because, at that point in time, some exciting things were happening around marketing automation and what you can do with a modern content management system and analytics, and being able to do things based on triggers. After that, I started moving more into the organizational transformation space because I had the opportunity to be part of a project where we needed to move away from a very antiquated point-of-sale system with the organization I was working with at the time. So it was an insurance company. It sold products through brokers, but we were still using this green-screen IBM software. ADRIANA: Oh, geez. [laughs]SHINGI: And there were like two customers left in Canada on it. And it got to a point where IBM was just like, "Listen, there are two customers on this platform. It just doesn't make sense for us to maintain it as a going concern for two customers. So you've got like nine months to figure things out before we sunset this." So the organization kind of freaked out because they'd never done anything in less than a year [laughs] from a technology standpoint. ADRIANA: Oh my God.SHINGI: So no matter what the undertaking was, it just wasn't possible. The default answer was always one year plus. So everyone kind of freaked out. And this served as a bit of a catalyst to think differently about how we would approach this. So at that point in time, all of a sudden, people were bought into the idea of, like, well, why don't we try this agile thing in terms of how we approach this project? Because if we do this the normal way we do it, we know what's going to happen, and we can't afford for that to happen because it's our point of sale system. So that was a massive success. And then you would think the company would rethink how we structure our technology delivery capability and build on the lessons learned. That's not what happened. [laughter] We just went back to how we used to do things. [laughter] It was like, yeah, that was a one-off. It worked, and it was nice. And yeah, we went back to business as usual. But by that point in time, I was kind of puzzled because I was like, okay, so we tried something different. Clearly, it worked. And there's some value to thinking differently about how we do things from a technology delivery perspective. So why would we switch back to how we were doing things? Yeah, so I got a bit frustrated, and I left and started pursuing more work from a transformation perspective to be part of thinking differently about how we deliver technology solutions. What set of conditions makes for better outcomes? What sort of processes? What kind of context do you have to create around that? So that really became the area of interest for me. And that's kind of been the theme in terms of the type of work I've done ever since.ADRIANA: Cool. That's awesome. Having done a lot of this tech transformation type of work, what do you see are some of the commonalities around this in terms of what are some of the common pitfalls that you see a lot of these large enterprises getting into? And what are some of the common successes as well?SHINGI: One of the biggest pitfalls is thinking that it's all about getting off whatever our legacy technology is. It's all about getting off the mainframe, or it's all about getting on to the cloud. ADRIANA: [laughs]ANA: It's true. SHINGI: So, yes, it's important for us to modernize the technology infrastructure, but the thing is, you have to realize that the technology infrastructure is kind of like an iceberg in the sense that it's reflective of a whole way of working, and the mindset, and organizational structure. So you can't just plug out whatever technology you've got and think that you can plug in the new stuff, and it's just going to work. You have to think about it more holistically. And usually, the other big thing, too, is that there's too much of a desire to be too aggressive out of the gate. So because the change is actually bigger than you think, it's better to kind of test the change in some small way in the organization to really understand what you're in for if you actually want to make an impact of the kind that you're looking for, typically, when people are talking about transformation.ADRIANA: That's a really good point. And do you find usually when you're working in these types of transformations, like, what's the appetite from leadership? Are you typically working with leaders who are super gung-ho about this? Or are they kind of being voluntold by other leaders? Like, what's the climate like?SHINGI: It varies. And it depends on what the narrative is around the transformation. So that's a big driver in terms of the behaviors that you're going to get and the context around it as well. Like, is it a new leader coming into the organization, and they're driving a certain kind of mandate? Or have we had something bad happen, and now we're really feeling the pain, and we need to make a change in terms of how we've been investing in our technology? So depending on what that context is, you get some very different patterns in terms of how things play out.ADRIANA: So what's the bigger motivator? Is it the new leader who wants to, like, let's change things completely? [laughter] Or is it the organization who's like, okay, this ain't working; [laughs] we got to fix it?SHINGI: Yeah, I think the new leader scenario is particularly challenging in the sense that obviously anybody who's coming to an organization as a new leader wants to show their value and put their stamp on things. But at the same time, there are reasons why those problems have persisted as long as they have. I remember one organization that I worked for had had several leaders come in and out, and it was always the same thing every time. It was like, oh yeah, we're finally going to get off mainframe. [laughter] That organization is still on mainframe today. ANA: Oh, my God. SHINGI: This conversation has been going on for like 30 years, [laughter] literally. ADRIANA: I don't think we'll ever rid ourselves of the mainframe. SHINGI: [laughs] And also, like, that's the other thing, too, is to think about what the actual aims are because do you need to really get rid of mainframe? Like, is that the issue? Mainframes are not terrible in and of themselves. I mean, it's a very reliable technology that, in a lot of organizations, has been highly optimized in terms of whatever they're having to do. ADRIANA: Yeah, that's true. That's true. SHINGI: It's not a foregone conclusion that, like, oh, if we just get rid of mainframes, all the problems will resolve.ADRIANA: And if anything, there's a lot more complexity that's created around it. I've been in an organization where they were trying to modernize around the mainframe, so it's almost like they create a moat around the mainframes, what it feels like, where they, you know, new services come in, and they plug into, you know, they feed into the mainframe. And they create these whole levels of abstraction over the mainframe. And it's, I guess, in some ways, like trying to put lipstick on a pig [laughter] because no matter how hard you try, the mainframe is still there. [laughs]SHINGI: Yeah, I mean, it's tough to actually plot a path out of the dependency because, typically, mainframes are running critical systems. So biting the bullet in terms of actually starting to shift workload away from mainframes is a big deal. And are you the one who wants to be on the hook [laughter] for actually making the switch in a real, meaningful way? Because if it goes wrong, it's on you.ADRIANA: Yeah, it's true. It's true. And there goes your reputation. [laughs]SHINGI: Yeah. And the other thing, too, is the timeframe that's typically associated with moving away from that type of technology is usually pretty short because all of a sudden, someone or some group of people decided this is now THE thing to do. And it needs to get done yesterday because we're behind.ANA: Always. [laughs]ADRIANA: Yeah, yeah. It does feel like, in some ways, some of these deadlines are arbitrary. And then you got people scrambling for what seems to me like no good reason if they had just taken some time to understand the landscape. And I think these are some of the pitfalls that I've seen myself where a new leader comes in, and they're like, "We got to change all the things."And then they don't take the time to talk to the people on the ground to see, okay, why is it that things are the way they are? They just want to make the change, and they want it yesterday like you said. And then I feel like that ultimately leads to their demise and the demise of the so-called transformation program. [laughs]ANA: It's that idea of not doing the planning or prepping kind of like going in 100%. We're doing all this, but you never know why you're doing it. Is it really needed? Like, asking, I guess, meaningful questions.SHINGI: Yeah. And kind of gauging what's realistic in terms of moving forward with the transformation objectives and balancing the risk because there's a huge amount of risk when you're moving off of mainframe infrastructure. It is typically running critical functions for an organization. And it's not that you can't get there. It's just, yeah, if you're going in with this idea that, oh, in a year, I'm going to make it happen and the five other people before me didn't know what they were doing, [laughter] you're about to be number six. [laughter]ADRIANA: So true, so true.ANA: I've definitely gotten the career advice of, like, oh, make sure to call people from that company who have left in the last three months before you join any organization just to find out what were really the hurdles when they were trying to push change, specifically within that infrastructure space and modernizing and digitalizing things or cloud-native transformation.SHINGI: And the other thing, too, I would say, is, so there's one part around what you need to do from a technical perspective. There's a big part around the culture and the ways of working. So you need to actually move on a bunch of different dimensions simultaneously. Like, if you just are pushing purely from a technology perspective, you're not going to end up getting very far. Because, like I said, the technology itself exists in the context of the organization's culture. It exists in the context of the organization structures. It's entangled in terms of how the organization works. So if you're going to try and actually change things, you need to take a systems approach. Otherwise, you're going to, at best, you'll end up with these pockets where you've been able to do some things, and the rest of the organization is kind of doing things the way they've always been doi…

    Full show notes at the publisher

    Philo-SLO-phy with Alex Hidalgo of Nobl9 Feb 21, 2023
    Show notes

    About the guest:Alex Hidalgo is the Principal Reliability Advocate at Nobl9 and the author of "Implementing Service Level Objectives." During his career, he has developed a deep love for sustainable operations, proper observability, and using SLO data to drive discussions and make decisions. Alex's previous jobs have included IT support, network security, restaurant work, t-shirt design, and hosting game shows at bars. When not sharing his passion for technology with others, you can find him scuba diving or watching college basketball. He lives in Brooklyn with his partner Jen and a rescue dog named Taco. Alex has a BA in philosophy from Virginia Commonwealth University.Find our guest on:TwitterLinkedInMastodonFind us on:On-Call Me Maybe Podcast TwitterOn-Call Me Maybe Podcast LinkedIn PageOn-Call Me Maybe Podcast MastodonOn-Call Me Maybe Podcast InstagramOn-Call Me Maybe TikTokOn Call Me Maybe Podcast YouTube ChannelAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:Nobl9SREConChefHugOpsAdmeldCustomer Reliability Engineer (CRE)Service Level Objective (SLO)SquarespaceImplementing Service Level Objectives: A Practical Guide to Slis, Slos, and Error BudgetsOpenSLOOpenSLO Slack CommunitySlothO'Reilly Google SRE BooksRundeckBreak Things on Purpose Podcast - Alex Hidalgo Additional Links:Google SRE Book - Service Level Objectives Transcript:ANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and just about everything in between. I am your host, Ana Margarita Medina, with my awesome co-host...ADRIANA: Adriana Villela.ANA: Today, we're talking to Alex Hidalgo, who works over at Nobl9 doing all things Principal Site Reliability Engineering. We're very excited to have you join us.ALEX: Thanks so much for having me.ANA: So, to kick us off for today, we love asking our guests, like, what are they drinking for today's podcast episode? What's keeping you hydrated?ALEX: Water that I put in a refilled bottle that I got on the airplane flying home from SREcon a few weeks ago.ANA: What about you, Adriana?ADRIANA: I've got green tea. For once, I have something different. I always have water, so yay. ANA: That is funny because I'm usually the one with the fun drinks. And today, I'm on water because I just forgot to grab anything different. [laughter] There's that whole, like, constantly thinking about too many things and having to hop on between meetings. It's like, what do I need for my next meeting to have near me? Like, do I need my notepad? Do I need my water? And if you're moving around your office, or your house, or commuting, it just gets a lot.ALEX: I always forget water half the time when I do these things because I have a neighbor who's actually the founder, and composer, and conductor for the Brooklyn Symphony, which is really cool. So he has this studio in the basement that he lets me use on occasion for stuff like this. And it's great because it's got pretty good sound quality. And my dog, Taco, he's prone to bark in the background for no reason. But that also means I have to take everything apart, like my mic, and my webcam, and my USB dock, and my laptop, and throw it all in a bag and rush downstairs because I probably just had a meeting. And then half the time I get down here, I'm like, I'm about to talk for a very long time, and I forgot to even bring water. But today, we're all set.ANA: Yay. It's like rescheduling. And then how many restarts have we had to do of computers [laughs] and browsers?ADRIANA: We're so happy we finally made this happen today. [laughs]ANA: It is kind of nice because it does bring to the front what we love talking about, that reliability aspect of stuff. And everyone kind of finds their passion for reliability in a very different way. For me, I kind of stumbled upon it, and it was like, oh, this is really cool. But I know that Alex has a really interesting story and how they got into their career path. So I would love to hear from you.ALEX: So yeah, I'll try to keep the beginning part of the story short and gloss over a few things. But I was into computers from a very early age. My dad started teaching me how to program in BASIC when I was about nine years old. And then, in middle school, my friends and I taught ourselves C and eventually C++. And we decided we were going to write our own video games. We learned OpenGL and how to make 3D trains and things like that. And I just maintained this passion for computers throughout my high school years to the point that I actually chose not to go to college. I figured I could go get a decent tech job right out of school, and turned out to be mostly correct. I ended up doing network security work for the Department of Energy. I did well. I actually got promoted within just a few months. I mean, I started doing overnight nighttime monitoring. I was watching a computer screen, watching potential alerts come in, trying to decide whether or not these were actual attacks on the network or just false positives, and most of them were just false positives. And I did well, but after about a year there, I realized I kind of hated it. So I decided, you know what? Maybe computers aren't for me at all. Maybe they're meant to be a hobby, and I'm not meant to work with them for a living. And I realized, you know, I was still pretty young. I could still pack up everything and go to school, and so that's what I did. And I ended up studying philosophy and history. Then after that, spent my 20s working all sorts of jobs, restaurant work, front of house, back of house. I worked in a warehouse for a little bit. I sold furniture. I made most of my money as a DJ for about a year. ANA: Wow. ALEX: Just all sorts of random odds and ends. Then a whirlwind of circumstances landed me in New York City in early 2009. And so the 2008 recession, that downturn was still really, really in effect. And even though I now had this shiny degree in philosophy and history, right? [laughs] Very highly marketable. [laughter] I wasn't sure what I actually wanted to do. And so I started to apply for all sorts of random jobs. I thought maybe I wanted to work in publishing, for example. And my money was running out. I didn't have a lot of money. I was able to stretch it a few months. And suddenly I was like, you know, I really need a job. And I met these two dudes who were at a bar one night, and they were crushing tallboys of PBR on their foreheads. [laughter] And so I went over to say hi, and turns out one of them needed to hire someone new at their IT firm, just kind of like a help desk-y small to medium business support kind of place. And I was like, you know, I can still do this computer stuff because it always remained a hobby for me. And so I said, "Sure, why not?" And I went in, and we did a very brief interview. And I started just a few days later. And that was great because the day I got my first paycheck, I was using quarters and change. That's all I had left. Like, literally, I was down to change to go buy a cheap Bodega sandwich and to ride the subway. I'd just made it. And doing that job, it was help desk support. But also, I got to do some Linux work and networking work because some of our clients had those kinds of setup. And no one else had this...it was a 10-person company, like, no one else knew that aspect of things. And I realized I actually did like working with computers. The thing I didn't like was working for the government as a 19-year-old. That was the thing I actually hated way back when. And so I did that for a few years. And then, I ended up moving to a company called Admeld as what we call the technical operations engineer. This is kind of before we consolidated on titles like SRE and things like that. And it was a really cool company to work for. They were pretty early adopters of Chef. They were pretty early adopters of the true DevOps approach to things. Suddenly, I was learning what DevOps meant, learning about HugOps. I was learning about blameless culture, which is something I had not really been familiar with in most of the jobs I'd worked [laughs] up until that point. It was great. And then, not too long after, Admeld got acquired by Google. And so suddenly, my title went from technical operations engineer to site reliability engineer. And I was like, what does this even mean? So I spent the next few years still supporting the Admeld platform because we were making money, right? Like we couldn't just turn it off. I didn't even really have a chance to learn about true SRE principles for the first few years that I was at Google. I got to learn a ton more about different kinds of tooling. And my coding skills went way up. And it was so a great formative time for me. But then it came time to turn Admeld off. I was the last SRE on the team. Everyone else had transferred already. I was the last one standing. And I got to run the Chef knife ssh command that logged into every single server because we were on physical servers, I think, like 1,500 or 1,800 of them, something like that. And I got to run that final command that shut them all off at the same time.ADRIANA: Oh wow.ALEX: Like, that was a great feeling. [laughter] But then, after that, I transferred on to some other Google SRE teams, spent about two years on each. I spent a few years on managed systems. I spent a few years on prodmon, the production monitoring team. Then I spent a few years on CRE, the Customer Reliability Engineering team. And all this time, I learned more and more about true SRE principles, especially things like SLO and proper incident management, and things like that. I even ended up starting traveling all over the world, teaching other SRE at Google how to do their jobs. Like, this is where I found my passion for writing, and education, and sharing the things that I've learned, especially on the CRE team, where a big part of the job was essentially teaching Google's largest cloud customers how to SRE, everything from pure educational effort to actually sitting down with them and looking at the architecture or looking at the codebase sometimes even. I mean, like, here's how we can improve.And that's where my true love of SLOs started. At prodmon, we actually adopted them and adopted them very well. And so, I was very familiar with what an SLI was and what an SLO was, and I got it. Like, it made some amount of sense. But on theory, we decided that in order to properly engage with all these different companies, many of whom were not even in the quote, unquote, "tech sector" at all, major retailers, and things like that, that we needed a common vernacular. We needed to be able to communicate with each other correctly and know what the other one was saying. And we decided that that language would be SLOs. So a huge part of any initial engagement with one of these CRE customers was, first, let's teach you what SLOs are, and then let's help you set them up. And then once we have that going, once we have service-level objectives that talk about the reliability in a holistic and meaningful way, then we can help you become more reliable because that was the whole point. So yeah, that's when I fell in love with SLOs. And I moved on a few years later and spent some time at Squarespace, where I was still focused on SLOs quite a bit, was able to get them to adopt them, and eventually ended up accidentally writing a book about them. And that's kind of why I'm at Nobl9 today because we're a company focused entirely on helping you do SLOs better. We're a company focused entirely on providing you with the appropriate tooling so that you can do them in the best possible way because not everyone has that tooling. And a lot of monitoring vendors they let you do SLOs in some very basic ways but not with all the bells and whistles. So yeah, I somehow ended up spending the last about six years of my career focused almost entirely on service-level objectives. That's how I ended up, well, here today.ANA: It's such a fascinating journey just because there was that where you were already into technology. And then the whole detour to study philosophy but getting a chance to then take all these skills that you take from liberal arts, education, and humanities and just talking to people and communicating that you get to put it to work and education with your customers and writing books.ALEX: Yeah, I mean, I actually think...I like to joke... So I majored in philosophy; I minored in history. And I was actually just like two or three classes away from a minor in creative writing as well, so English. At the end of the day, it didn't seem worth doing. I like to joke sometimes. I took the three most useless degrees: philosophy, history, and English [laughter] and combined them all into one degree. But that's not actually true. I found that the skills that I learned, not just studying philosophy, history, and English, the ability to synthesize ideas, express them clearly to others, learning how to write well, learning how to communicate well, that served me very well in my career.I also think my time in the restaurant industry, for example, is another really good example of learning service. You are a server. You're providing a service for someone. It's not a chance that that's why we call our computer servers servers, and that's why we call our services “services” because they're servers that provide a service for someone. And you really learn how to think about these things holistically when that's your entire job when your job is just to provide a service for these clients coming in. And you want to serve them reliably, even if that's not always the term you're using. And even if you don't explicitly have service-level objectives, you kind of do. If you're working in the kitchen, you want X percent of your dishes to go out without them coming back, and that's a service-level objective. [laughter] And the customer being happy with their dish is a service-level indicator. We just use different languages in different industries. But it turns out we all kind of know these things. They're all kind of inherent to the human condition, I think.ADRIANA: That is so cool. It's funny how, even though oftentimes...like, a lot of our guests have taken the so-called crooked path into their current tech careers. I'm a huge believer that everything that you've done in your life up until this point has led you to be able to do the job that you do right now and that if you hadn't had your past experience, would you even be as good as what you are doing now? So it's so cool that having the restaurant experience and even having the philosophy degree gives you different perspectives, different appreciation of things in a way that maybe if you'd done like a CS degree, you might not have had. ALEX: Yeah, I very much agree with that. I think about it quite a bit. And especially in the SRE space, in the DevOps space, in the TechOps, production, engineering, platform engineering, whatever we want to call it, [laughter] everything's really kind of rebranded sysadmin. And feel free to @ me about that on Twitter. [laughter] But in that space, yeah, I think it's very often the case that people don't have traditional compsci degrees. I remember one time I was on a team where I think we may have had one new grad who had studied computer science. But everyone else on the team...we had an ex-chemistry professor. We had a psychology major. We had, you know, essentially the entire team. And it was a g…

    Full show notes at the publisher

    New Year, Same Us with Adriana Villela and Ana Margarita Medina Feb 14, 2023
    Show notes

    About us:Adriana Villela is a Sr. Developer Advocate at Lightstep, based in Toronto, Canada, with over 20 years of experience in technology. She focuses on helping companies achieve reliability greatness by leveraging Observability, SRE, and DevOps practices. Before Lightstep, she was a Sr. Manager at Tucows, running both a Platform Engineering team and an Observability Practices team. Adriana has also worked at various large-scale enterprises in both individual contributor and leadership roles, including Bank of Montreal, Ceridian, and Accenture. Adriana has a popular technical blog on Medium, co-leads the OpenTelemetry End-User Working Group, and is a HashiCorp Ambassador. Find her on Mastodon at @adrianamvillela@hachyderm.io to talk all things tech.Ana Margarita Medina is a Staff Developer Advocate at Lightstep, where she speaks on all things SRE, DevOps, and Reliability, and is a podcast host for On-Call Me, Maybe. She is a self-taught engineer with over 12 years of experience, focusing on cloud infrastructure and reliability in the last few. She is also part of the Kubernetes Release Team (v1.25 - v1.27) and has been advising CNCF's Keptn project since 2019. When time permits her, she leads efforts to dispel the stigma surrounding mental health and bring more Black and Latinx folks into tech. Catch her on Mastodon at @anamedina@hachyderm.io about traveling, diversity in tech, and mental health. Find us on:On-Call Me Maybe Podcast TwitterOn-Call Me Maybe Podcast LinkedIn PageOn-Call Me Maybe Podcast MastodonOn-Call Me Maybe Podcast InstagramOn-Call Me Maybe TikTokOn Call Me Maybe Podcast YouTube ChannelAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:AWS Well-Architected Framework - Sustainability PillarAdrian Cockcroft on "Architecting for Sustainability"HashiCorp NomadTracetestMalabiHeliosTrace-Based TestingHashiTalks 2023Julie GundersonConf42: Don’t Forget the Humans with Julie Gunderson and Ana Margarita MedinaKeptnLitmusChaosChaos MeshArgoCiliumBackstageKubernetes Release TeamCrossplaneAdriana’s blog series on running ArgoCD on KubernetesESCAPE 19: Chaos Engineering in a Multi-Cloud World with Ana Margarita MedinaOpenTelemetry End-User Working GroupOpenPolicy AgentAndi GrabnerObservability-Landscape-as-CodeTerraformService-Level ObjectivesStephen TownshendSlight Reliability Episode 39 - The Future of SRE with Adriana Villela and Ana Margarita MedinaAdditional Links:CNCF Working Group on Environmental SustainabilityCloud Carbon Footprint Project on GitHubTechstrongTV - What 2022 Taught Us About SRE’s FutureTranscript:RIAAN NOLAN: Don't worry about failure. Fail fast if you do fail. None of us are superstars or anything, so your name doesn't mean shit anyway. [laughter] So put your code out there; if people think it sucks, it sucks; if they like it, they like it. The best thing is just paint your picture. Do your thing, and put it out there because that will help you grow. LIZ FONG-JONES: And I think this is an area where we, as developers of observability tools, can really help because an SLO has to be a living, breathing thing, not just a thing that you put up on a dashboard and you look at it 90 days later and, oops, we blew our SLO.NORA JONES: But we're also all engineers. We've been a part of the big technical aspects of it all. And we've seen the social aspects not really be spoken about very much. I think it's a big miss. And it's honestly a business advantage to be able to talk about the social aspects as well. So we're really trying to give every company that advantage.ADRIANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host, Adriana Villela. And with me, I have my awesome co-host...ANA: Ana Margarita Medina.ADRIANA: And today, we are kicking off Season 2, and I'm super, super, super excited to be doing that. We've had a little hiatus over the holidays, and we've had time to get refreshed and revitalized. Ready to take on 2023, hopefully, knock on wood. How are you feeling? [laughter]ANA: I'm hoping that the year continues to get better and that this year is better than last year, and that we see more amazing things happen in the industry, but that everyone takes care of themselves a little bit more.ADRIANA: Yeah, cheers to that. Now, in proper OCMM fashion, we must ask each other what we're drinking. So, what do you have today? [laughs]ANA: This morning is my famous Guayakí's organic Yerba Mate in enlighten mint flavor. You'll probably find me either having a latte or one of these as I kick-start my day. So we're still rolling out here in the Bay Area. We're trying to get the engine running for today's day. How about you, Adriana?ADRIANA: I've got green tea. I made myself green tea just before we recorded because I figured I need something a little bit more interesting than the water. I mean, water is great, and drink your water, but green tea today. It's kind of a dreary, rainy day in Toronto today, not compared to the rain that y'all have been getting in California, so big hugs to you. Yeah, every day in the news, there's new stuff [laughs] about the rain. I'm like, ehh. [laughs]ANA: There's definitely a big hug sent out to California. But I feel like there are so many places in this world right now that, with global warming, they're suffering from such terrible conditions of weather. The amount of flooding that I got to see in pictures and online and in parts of California was just mind-blowing that it can happen. But it's just a reminder that we take care of the world. And even though this podcast focuses on reliability, sustainability is equally as important. And maybe this season, we will get a guest that talks a little bit more about that, or next season. Or if y'all want to chat with us on social media, we're always happy to hear folks' thoughts on it.ADRIANA: Yeah, absolutely. And also, a note for our guests: we now have a presence on Mastodon, TikTok, and Instagram in addition to our LinkedIn and Twitter presence. So you can find us on multiple social media platforms now.ANA: And you can even put in a request there of your favorite podcast guest that you would love to see be part of On-Call Me Maybe.ADRIANA: Yes.ANA: Questions that you want to ask any of our guests, questions for us, any feedback. We'd love to hear it. Let us know what you thought about season one or if you missed us between this break.ADRIANA: Oh, you know, I want to circle back to what you were saying about sustainability and technology because I don't know if you feel this way. So I've always, like, the environment has been near and dear to my heart since I was really young. And I kind of feel guilty working in tech knowing that the type of work that we do contributes to a certain extent to environmental problems because when you think about things running in the cloud, you've got servers running all the time, consuming a crap ton of energy. And I feel a little bit guilty. And I'm always curious as to how there can be a marriage between what we do and environmental sustainability if there's sustainable tech.ANA: Hmm. I think that is an interesting question, like, is there sustainable tech? I think, as an industry, we are waking up to the conversation of sustainability slowly. And it has increased more than ever in the last two, three years. And once again, I think this is actually something to attribute to COVID. We've had more of a demand within the supply chain. We've also had slowdowns on air pollution due to travel, and folks are starting to realize, like, oh, if we were to make this change, our world is happier, our world is sadder. And I think that cause and effect made people be like, oh shit, my actions do matter. And then specifically to technology, I remember...I want to say it was three or four years ago. If you follow Amazon Web Services, they have something called the AWS Well-Architected framework. It covers five different pillars of how organizations can actually be building their applications. This covers things like making sure that you have a reliability pillar, that you have a security pillar, that you have an operational pillar. But two, three years ago, one of the vice presidents at Amazon Web Services, Adrian Cockcroft, created the Sustainability Pillar and created this entire sector within Amazon Web Services that was going to focus on reducing the footprint that they were imprinting in this world or just letting their customers be more aware of it. And I thought a big organization such as them taking that step is a step, and it gets the conversation moving. And then it trickles down to what actionable things can companies do? Well, even starting to look at capacity planning is one way to move forward in the sustainability conversation. Like, if you have all of your servers constantly just using 20%-30% of your resources, maybe you shouldn't be running a fleet that large, and maybe you can make it a little bit smaller. And therefore, your footprint is a lot less, and you're damaging earth a little less.ADRIANA: Yeah, that's so true. That's so true. Because I think sometimes we get so caught up on reliability that we need to make sure customers are happy, systems are up and running that sometimes it can be easy to over-provision resources, especially when you have the cash to burn.ANA: [laughs]ADRIANA: Maybe not so much when you don't have the cash to burn. In that case, yeah, it's like...[laughs] and it's worthwhile doing an audit of your systems to make sure that, like, yes, I actually need all of that capacity versus, oh, shoot, I'm using like 10%-20% of my resources.ANA: Do you have any thoughts on some of the things folks can do to audit what their spend is? I know that there are consultants out there that would help you lower your cloud footprint bill. But when we're thinking about this audit, a lot comes to mind. Because I think this is actually something interesting to throw out there as we kick off the New Year, as folks are going into their jobs thinking like, what are we going to do to survive the economic atmosphere that we have but also bring in a positive value to this organization?ADRIANA: I'd say the biggest one for me is definitely making sure that you're using what needs to be used. A more maybe not so direct to cloud usage but even related to a certain extent to the type of work that we do, which does involve some travel, is reducing business travel. That's a huge one. I would say consulting travel that's a huge one.So when I started my career back in 2001, I worked at a consulting company, and it was expected that you were going to be traveling to work at client sites. You were lucky to get an in-town project. I was actually quite lucky that most of my time with the company, I worked on in-town roles. But my husband, who's still at the company, he spent, I think, the first ten years of his career traveling for work. When the pandemic hit and all of a sudden, everyone's working from home. To me, it was like, oh, well, this finally proves to folks that you don't have to travel for all the work things.ANA: [laughs]ADRIANA: So, to me, it's like, make those travel plans if they're absolutely necessary because a lot of the stuff you can accomplish just working from home. Even traveling to an office, if you're working from home, it means that you're not commuting to an office. So it means that you are not driving or you're not taking public transit, which mass transit is awesome, and I will take mass transit whenever I can. I personally hate driving. But even taking mass transit, if you don't need to take that mass transit to get to the office, you're already, I'd say, helping offset some of that carbon footprint compared to having to commute.ANA: That is true. And it kind of makes you wonder, like, what goal, what wish list can you put this on on reducing your footprint as an individual, as an engineer, as an organization? Like, what small step can you take today that could actually accumulate by the end of the year to be a pretty significant amount?ADRIANA: Yeah, totally. Another one that comes to mind is I remember at some workplaces; I would always try to log in and out of...when I had a tower, I'd log in and out of my desktop power off for the day. But some companies will put so much crap on your machine that the process of booting up your machine and shutting it down for the day is so lengthy. I remember for a while, at some companies, I'd just leave my machine on.It kind of defies logic that there's so much crap on your machine that now you're compelled to leave it on to get a little extra bit of productivity, so even something simple like having the ability to power off your machine. I think with a laptop; it's a lot easier because even though I don't power my laptop off and on regularly, I don't always have it plugged in. I'll only plug it in when I absolutely need to. My personal habit is I always turn off my power bar when I'm not using it because even though it does consume a small amount of power, it still consumes power. So it's these little, little things that you can do in technology to help offset the footprint. And if you've got enough people doing that, well, you can actually make a pretty decent dent.ANA: I 100% agree. I want to say that I don't always take a lot of these actions, but they definitely come to mind sometimes where it's like, it's that small thing of unplugging your laptop before a long weekend or any weekend. Or just kind of being like, you don't need to be connected to power to run updates, or even to just constantly be charging because I'm not going to be using you for a longer length of time. But even like you said, I think it's actually a really nice idea to be like; this is the power strip for my entire work setup. When I'm not at work, the entire strip itself can be off. That's actually something I've always wanted to implement for when I travel; when I go away that it's like, "Alexa, power all of this off," or "Power strip goodbye."ADRIANA: Yeees.ANA: And we know that we are not consuming power, like, less risk of any fire emergency. And at the same time, you're just like, my devices are actually fully sleeping, not connected to the internet, not connected to anywhere.ADRIANA: Yeah, so you have some peace of mind, a little bit of mental health injected in there, too, right?ANA: [laughs] Are you telling me you're sending my devices on a mental health break?ADRIANA: [laughs] I think sending your devices on a mental health break sends you on a mental health break, [vocalizing] tan-tan-tan. [laughter]ANA: On that note, I'll always throw my little snippy where I say that if you travel with your laptop, you're not really going on vacation. [laughs][laughs]ADRIANA: Yes, I totally agree. I've never gone on a vacation with my laptop, thankfully. I always make it a policy when I'm on vacation; I'm on vacation. I'm not going to respond to your Slack messages. You can text me if it's for fun stuff. ANA: [laughs]ADRIANA: Otherwise, we're not talking, [laughs] and I will block your ass. [laughs]ANA: It's funny because this was just a conversation I recently had with my best friend around laptop going on vacation or not. And I'm one that says, "Don't take your laptop on vacation," and known to do it. And sometimes that I…

    Full show notes at the publisher

    An OCMM Retrospective with Adriana & Ana Dec 06, 2022
    Show notes

    About us:Adriana is a Sr. Developer Advocate at Lightstep, based out of Toronto, Canada, with over 20 years of experience in tech. She focuses on helping companies achieve reliability greatness by through Observability and Incident Response practices. Before Lightstep, she was a Sr. Manager at Tucows/Wavelo. During this time, she defined technical direction in the organization, running both a Platform Engineering team, and an Observability Practices team. Adriana has also worked at various large-scale enterprises, including Bank of Montreal (BMO), Ceridian, and Accenture. At BMO, she was responsible for defining and driving the bank's enterprise-wide DevOps practice, which impacted business and technology teams across multiple geographic locations across the globe. Adriana has a widely-read technical blog on Medium, which is known for its casual and approachable tone to complex technical topics, and its high level of technical detail. She is also a HashiCorp Ambassador. Find her on Mastodon at @adrianamvillela@hachyderm.io to talk all things tech.Ana Margarita is a Staff Developer Advocate at Lightstep and focuses on helping companies be more reliable by leveraging Observability and Incident Response practices. Before Lightstep, she was a Senior Chaos Engineer at Gremlin and helped companies avoid outages by running proactive chaos engineering experiments. She has also worked at various-sized companies including Google, Uber, SFEFCU, and Miami-based startups. Ana is an internationally recognized speaker and has presented at: AWS re:Invent, KubeCon, DockerCon, DevOpDays, AllDayDevOps, Write/Speak/Code, and many others. Catch her on Mastodon at @anamedina@hachyderm.io about traveling, diversity in tech, and mental health. Find us on:On Call Me Maybe Podcast TwitterOn Call Me Maybe Podcast LinkedIn PageAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:AWS re:InventOpenTelemetryKubeConBreak Things on Purpose PodcastTranscript:ANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host, Ana Margarita Medina, and with my awesome co-host...ADRIANA: Adriana Villela.ANA: Today, we're going to be recapping what this year has been for us, some of the stuff that we have been up to, what we're looking forward to in the next year, and talking a little bit more about tech culture and what we could be doing to make it better. We're so happy that you have been listening to us this season, and we look forward to having you join us next season. To kick it off, what's your drink of choice today, Adriana?ADRIANA: Today I've got water. Super boring. I should have something warmer, though, because it's actually really cold here in Toronto today. We've got snow, our first snowfall of the day. I mean, sorry, first snowfall of the year, I should say.ANA: Ooh, that's actually pretty exciting. Like, I'm not someone that likes cold environments, but snow is really pretty. I'm not going to turn down being in cute snow clothes with a little beanie. [laughs]ADRIANA: Yeah, totally. Exactly. As long as it's not super, super cold.ANA: Well, hopefully, you'll get some hot drink for the day to cozy up with the snow. ADRIANA: Yeah, totally. ANA: For me, today I'm also doing water, and I'm finishing up my morning drink, which is orange-infused yerba mate. I kind of sometimes switch between coffee to tea. So it's kind of nice.ADRIANA: Nice. Nice. Yeah, I think we have a similar drink in Brazil called mate. It must be the same thing. It's got to be the same thing. The name is similar enough.ANA: Like, at least the little bit of knowledge that I know about mate is that it comes from South America. And my best friend is Argentinian, and she actually just gets the actual leaves of mate. And you boil them, and you drink them in these little, leather metal containers that help keep it hot. ADRIANA: Oh, yeah, yeah, yeah. ANA: And you have the metal straw. So I've seen it more down there than in the cultures that I come from.ADRIANA: That's cool. Now it makes me want to go to the nearby Brazilian supermarket and pick one up. [laughs]ANA: You should do it.ADRIANA: For nostalgia. I should; I should. Next time I'll come equipped with some mate. We can have a mate-mate off.[laughter]ANA: I'll make the OG Argentinian mate for that day.ADRIANA: Nice. [laughs]ANA: Is there any drink that in Brazil y'all drink for holidays or that you and your family really like having as a tradition?ADRIANA: No. I mean, I think I dishonor my culture because I don't like coffee. [laughs] My dad's really into coffee, but my mom never was into coffee. I'm much more of a tea drinker. Or I'd say my go-to holiday drink is a Starbucks hot chocolate, and I usually do it with coconut milk, which gives it a really nice silky texture. ANA: Ooh, I might have to try that. I just had their hot chocolate maybe two weeks ago. And I forgot that I actually really enjoy getting a hot chocolate from Starbucks. Like, it's a different experience than just making it a home.ADRIANA: Yeah, it's like a warm hug.[laughter]ANA: Yes, that definitely sums it up. I think for me, like, I just blanked out. But in my culture, we have different things that we do for the holidays. And in Costa Rica, we have rompope, which is our traditional eggnog that we drink during the holidays, and it's literally my favorite thing to drink. It's just not really available out in California. I think in Miami, it was easier for me to find it. So over the last seven years, what I have picked up as my holiday tradition is making coquito which is a Puerto Rican drink.ADRIANA: Ooh.ANA: Which is like coconut milk, condensed milk, evaporated milk, cinnamon spices. The culture of Puerto Rico is that you make it with rum. So you can do it with Brugal, and you serve it over ice, and it's extremely strong. So it's more of like their holiday party drink. So I always make it non-alcoholic, and then I'll pour Flor de Caña Nicaraguan rum and have it with it. And it's just like, cozy up. It's the holiday season, like, start celebrating from Thanksgiving to the end of January.ADRIANA: Oh my God, that sounds amazing. [laughter] I will have to try that at some point. You had me at condensed milk, so...ANA: Yes. I mean, that's what it is. It's that sweetness. It's that sweetness and boozy. It's also a culture that you make it for your friends and family, and that's your gift for the holiday season.ADRIANA: Aww.ANA: So, one of my past jobs with a credit union in Miami, I got gifted it in like one of the holiday seasons, and it was just really thoughtful of like another family is inviting you to celebrate holidays with them. ADRIANA: Oh, that's so sweet. I love it. So, we've been podcasting for a while, I guess, now, right? So I guess this is our year in review [laughs], where we get to reminisce on some of the highlights of the year. You know, it's a good time for reflection. So keeping in with that end-of-year theme, like, what experiences are you grateful for? And who are some of the people that shaped who you are today?ANA: Yeah, I mean, I think things that I'm grateful for have varied a lot year by year. I think this year I'm really grateful for the close group of people that I have around me; it has been co-workers, husband, open-source community. It has been my close friends and just uplifting. I remember the last winter season; I had a lot harder time mental health-wise. So kind of trying to remind myself of, like, oh no, like, leverage your community to not struggle this much this winter as we already have the sun going down at 4:30 p.m., which just makes my heart cry. [laughs]ADRIANA: So depressing. I hate it. ANA: [laughs]ADRIANA: The only thing making it less crappy today is the snow. [laughter]ANA: True. Send some snow over to California, please, but not too much. [laughter] ADRIANA: Yeah, just a little, tiny bit. ANA: And then, to answer your second part of the question, I think there are a lot of people that I'm grateful for for making me who I am today. I think my dad instilled in me a lot of values of being community-driven, giving back to folks, and constantly just learning and staying curious, like, an entrepreneurial mindset. And then there are two mentors that I always go back to as folks that made such a huge impact in my life growing up that I wouldn't be in the career that I have today. And one of them is my sixth-grade technology teacher, Mr. Rios, who taught me just computers and the web are a really cool thing. And he published my HTML websites on his website. ADRIANA: Aww.ANA: And that gave me confidence of technology is cool; go code. And then, I had a manager for an internship in my ninth-grade summer of high school named Soleil. She was just an amazing woman of color leader that was fierce in business and really tried to explain to these high school students, like, you have to present yourself the way you want people to respect you and also think about your career really early, and those decisions are going to make an impact. So if it wasn't for them, I wouldn't be having a successful career in technology. So I think this holiday season, I'm always like, hmm, thank you. Thank you, all.ADRIANA: Aww, that's awesome. That's really sweet.ANA: What about for you? Who are you grateful for that has made you who you are today?ADRIANA: I'd have to say top one is my mom, and I lost her earlier this year to cancer. And I had to actually rush home early from KubeCon to be with her for her final hours, and that was really rough. But I'm also so grateful that all my family was there. My dad, my sister, my daughter, and I were there for her final moments. And every day, I think back to the lessons that she instilled in me, which were she always wanted my sister and me to be fiercely independent career women, and she got her wish. I mean, for her, the most important thing was no matter what, just make sure that you set yourself up that whatever life throws at you, you're able to come out maybe with a few scratches, but you still come out okay in the end, and I'm so super grateful for that. And she's always taught me to be super driven. And I think we both, [laughs] you know, I'm pretty sure she was undiagnosed ADHD. She was like a little rocket ship. I mean, we'd take 10K walks regularly. I think I definitely get that from her. So I'm very grateful for that. And I would say my dad and my sister have been so supportive in the last little while, like, after losing my mom and gotten closer over that, which has been super nice. My dad is actually the one who got me into tech. [laughs] He's a software architect. I mean, last week, he's like, "Yeah, I'm learning this new language called Zig, and it's supposed to be like an easier version of Rust." [laughter] I'm like, holy crap, man, you eat computer languages for breakfast. [laughter] So yeah, he's always on top of the techy things. I got into DevOps because of him. [laughs] When I was bitching one time after a really bad release, and all the things that went wrong did, and he's like, "You should look into this DevOps thing." ANA: [laughs]ADRIANA: I'm like, ooh, cool, and that got me hooked, so eternally grateful for that. And my husband has been ridiculously supportive of my career. And he's been at the same company for, like, 25, 26 years. And I'm the one who's had career changes and job changes over the last 20 years of our marriage, and he's super chill about it. [laughter] Even though at one point I'm like, "I'm quitting tech, and I'm going to become a professional photographer," and he's like, "No problem." [laughs]ANA: Aww.ADRIANA: So that was cool. And my daughter, Hannah, like, honestly, she's the sweetest person. And she's always there to cheer me up whenever I feel crappy, so I super appreciate that. And I've had a couple of really awesome mentors, too; my friend, Bernard, who unfortunately suffered a stroke a couple of years ago and is still in hospital unresponsive, but I always think of him because he's the one who got me interested in observability. And he's one of those people who could see...I guess he saw what my mom saw in me. He's like, "Oh, you're really good at what you do. And you should never forget that." It's so nice to have someone who believes so fiercely in you and can see past, you know, you're your own worst enemy. And I had so many mental blocks, like, doubting my skills. And so he continues to inspire me. And every day, I think of him and every day where I am right now, especially in this career as a DevRel, in observability I'm grateful to him for that. And another mentor I can think of is a manager that I had many, many moons ago named Lawrence when I worked at Bank of Montreal. He was just like the most supportive manager, and I feel like he's the gold standard of managers because he was easy to talk to. I could play pranks on him. ANA: [laughs]ADRIANA: I got him a bullshit button as a joke one time, [laughter] and he took it super well. And I also got him a giant calculator as a prank, [laughs] and he took it all in stride. And I think being able to have that kind of a chill relationship with the manager while they're still interested in helping you grow and mentor you I think that's priceless, so yeah.ANA: I mean, most definitely. It's like, I see you as a human, and I'm going to help you flourish in every single personal way that I can versus only in the box of tech or in the way that you bring value to an organization. I was going to mention that I'm still very sorry about the loss of your mom earlier this year. And I'm glad that you've been able to spend time with your family to be together and help build each other up because there's a little hole in your life in the holiday season. I know it gets hard. And I know you, and I have talked about it of what it's like to lose parents and continue on. The best we can do is just make them proud.ADRIANA: Exactly. Exactly. Honor them by honoring their teachings. ANA: Yeah, most definitely. ADRIANA: I also want to say a big shout-out to our DevRel family because, honestly, y'all have been super supportive throughout all this. I had to rush home on October 27th, and everyone's like, "No problem, do what you need to do, like, no sweat." And everyone's just been, like, I don't know, you guys sent me some lovely flowers and just some lovely messages. And it was super nice. So really appreciate it. Y'all are awesome.ANA: We're humans first. That's all that matters. We just get to work on really cool technology and get to build communities around it.ADRIANA: I'm so grateful to have the opportunity in the last couple of jobs to work at places that are less robotic about the corporate-y stuff and really value the humanity of the employees. Like, I don't feel like a number. I feel like the work I do matters, and I think that's so important.ANA: I've worked at places where it said that humans come first, and then things change. And I think a lot of it also varies team by team, manager by manager. Things can change really quick, which really sucks. But I try to be an advocate for that even when the situation around me might not be like that. It's like, nope, I'm putting my foot down. We are humans. There are limits…

    Full show notes at the publisher

    DevRelin’ 😎 with Austin Parker & Ted Young of Lightstep Nov 29, 2022
    Show notes

    About the guests:Austin Parker is the Head of Developer Relations at Lightstep and has been creating problems with computers for most of his life. He’s a maintainer of the OpenTelemetry project, the host of several podcasts, the organizer of Deserted Island DevOps, an infrequent Twitch streamer, a conference speaker, and more. When he’s not working, you can find him posting on Twitter, cooking, and parenting. His most recent book is Distributed Tracing in Practice, published by O’Reilly Media.Ted Young is the Director of Open Source Development at Lightstep and one of the core maintainers of the OpenTracing project. Ted has spent the last 15 years building distributed systems in a variety of environments: computer animation, national elections, and elastic computing platforms. Find our guest on:Austin’s TwitterAustin’s MastodonAustin’s LinkedInAustin’s WebsiteTed’s TwitterTed’s LinkedInFind us on:On Call Me Maybe Podcast TwitterOn Call Me Maybe Podcast LinkedIn PageAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:Lightstep360.orgBill McKibbenThe Sunrise MovementOpenTracingOpenCensusOpenTelemetryKubeCongRPCBASIC Programming LanguageDockerConCNCFCoreOSLiz Fong-JonesOTLP (OpenTelemetry Protocol)QPS (Queries per Second)New Era CapsDenise YuHydroflask BottlesStar Trek: VoyagerLava LampAdditional Links:Distributed Tracing in Practice (O’Reilly Media)The Future of Observability with OpenTelemetry (O’Reilly Report)[YouTube] Myths and Historical Accidents: OpenTelemetry and the Future of Observability Part 1[YouTube] Data by Design: OpenTelemetry and the Future of Observability Part 2[YouTube] What OTel is and isn't: OpenTelemetry and the Future of Observability Part 3Transcript:ADRIANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and everything in between. I am your host, Adriana Villela, with my awesome co-host...ANA: Ana Margarita Medina.ADRIANA: And today, we're talking to the whole DevRel team at Lightstep, woo-hoo.ANA: Woo!ADRIANA: And it's taken us how long to get us all together on this? I think this is our third attempt.ANA: Yeah, it's actually third attempt. It's taken five months in the making.ADRIANA: [laughs]ANA: But it's here. We're finally getting this episode out the door to our listeners.ADRIANA: Yay. So we start with...our first question is always, what are y'all drinking?AUSTIN: Red Bull, sugar-free TED: Coffee. AUSTIN: I had an espresso earlier.ANA: Y'all are kind of crazy to still be doing caffeine at this time, like, East Coast 4:00 p.m., Pacific time 1:00 p.m. I have a strict cut-off of no more caffeine at 12:00. I just finished drinking my yerba mate, 160 milligrams.AUSTIN: Yeah, I drink caffeine. I don't know; I don't really have a ton of problems with caffeine. So earlier this year, when we did Deserted Island DevOps in Michigan, I was like, okay, as the organizer of this, I can finally make unreasonable craft services requests. And so I was like, we got to have sugar-free Red Bulls because I like energy drinks. I like sugar-free Red Bull. So as it was requested, there was a, you know, they would fill it up. And that was actually maybe a mistake because I think I drank like three or four of them, and I was too nervous to eat. So I think I just kept drinking sugar-free Red Bulls. And about noon on the first day, I felt like I was vibrating on my skin. ADRIANA: Oh my God. AUSTIN: So I did find my limit of sugar-free Red Bull, and it's about four in two hours.ANA: [laughs]ADRIANA: Yikes. When I was in university, I used to have a can of Coke usually for a 9:00 or 10:00 a.m. class because I don't drink coffee. [laughs] I remember experiencing the vibrating in my skin sensation back then, and then I'm like, yeah, maybe I shouldn't do this anymore.TED: Caffeine has no discernible effect on me anymore, which in and of itself is probably bad.[laughter]ANA: It might mean something.AUSTIN: It's a sign. It's a signal. [laughter] It's some kind of signal, at least.[laughter]TED: The adrenal glands are just like, we give up. We give up.AUSTIN: So we've stopped trying. This guy is going to do whatever.[laughter]ANA: I've switched over to water for the rest of the day. So, what about you, Adriana?ADRIANA: I've got water. I do plan on having a lovely mug of green tea later, though. Caffeine doesn't; at least green tea doesn't affect me if I have it late in the day. I'll have homemade bubble tea at like 9:00 o'clock at night, and I'll be fine, so yay.TED: With your own tapioca boba?ADRIANA: Yeah, yeah.TED: Whaaat?ADRIANA: Yeah, I get it on Amazon, yeah. And I can control the amount because I like it, but I find it too filling. So I'll have like just a few. ANA: Two pearls. ADRIANA: Yeah. [laughs] Sometimes five if I'm feeling super adventurous. But yeah, it boils in like one to two minutes, and then it's done. So that's my plug for homemade bubble tea. TED: Whoa.ADRIANA: Mind-blown. [laughs]AUSTIN: I've not had boba in so long. I miss it. I used to get them when I came up to San Francisco when I would travel, back before the pandemic and everything. I would always really get into some boba. ANA: That was the case when I worked at the San Francisco Uber office. We would always take walks around the block, and we would end up at Boba Guys or Asha Tea House. And it was just like the perfect 45-minute break, nerd out, get some sun, get boba. Sometimes it was a work expense because it was a work meeting, and I was like, this is nice tech privilege.ADRIANA: Yes, yes. I would totally do that, too, at one of my old jobs. It was like the daily bubble tea round. [laughs] And I used to work in Downtown Toronto, so there's like tons of places now. So never wanting for bubble tea.[laughter]TED: They always dunk way too much sugar into it for my liking. ADRIANA: Yes. TED: So the idea of homemade boba sounds really enticing.ADRIANA: Yeah, that's why I like it too because I find they do put too much sugar, and I can control the amount of sweetness because I can't even take the amount of sweetness that Starbucks puts in its hot chocolates, like, it's sugar overload for me.ANA: When I request bubble tea, I'm always like the 75%-80% sweetness person, so I'm the complete opposite clearly.ADRIANA: [laughs] I mean, you do enjoy condensed milk in your drinks, too, right?ANA: And I cannot do sugar-free Red Bulls, like, no. Sorry, y'all.[laughter]AUSTIN: I mean, it's fine.ANA: I mean, you're caring about your health which is better than what I do, so I think --AUSTIN: I mean, I like sugar in things, but I just don't like it in drinks these days. I don't know; I've been trying to reduce sugar intake in general.TED: I mean, it's not like regular Red Bull tastes good, so you might as well get the sugar-free, right?ADRIANA: [laughs]TED: Like, it's not like you're losing something. AUSTIN: Well, that's true. I mean, there are not a lot of energy drinks that taste good. Is this just like an energy drink review podcast now?[laughter]ADRIANA: I guess so.AUSTIN: All right.ADRIANA: Apparently, apparently.[laughter]ANA: I still think Green Monster tasted really good growing up. That was definitely a go-to.AUSTIN: Hmmm. See, Monster Zero, I think, tastes better than the regular ones. And then, for a while, I went for the Bang energy drinks. Those are a lot. ANA: I just get turned off by the marketing. AUSTIN: Well, the marketing is also bad. I feel like we need a new kind of energy drink revolution or energy drink model or concept, like something --ANA: There is actually something new that I just discovered. And I discovered it because somehow I was going through Twitter, and I found a founder who follows me on Twitter who's also Costa Rican, lives in San Francisco, and is building a company on making coffee without coffee beans. ADRIANA: That's cool. AUSTIN: Interesting.ANA: I don't know the name of it. TED: What does it mean? ADRIANA: [laughs]ANA: It's using, like, cocoa nodes. I don't know how they're not processing the cocoa beans, but you're still extracting caffeine. And you still get the same flavor profiles that a lot of coffee lovers are able to get out of it. At least, that's what I gathered from reading her tweets or company's tweets. AUSTIN: Is it like a sustainability thing or? ANA: Yes, yes, yes. It's a sustainability angle of it, too, where it's like with the way that climate change is going, we're not going to be able to keep up with the coffee demands, so we need to look for alternative routes.AUSTIN: I like people when they try to head off, or they look at the dystopia, and then they just kind of like say, "You know what? We're going to just jump one step ahead of that.ADRIANA: [laughs]AUSTIN: We aren't at the collapse quite yet but let's go ahead and see how much VC cash we can wring out of monetizing the rot." ANA: I mean, I'm super biased as being from Costa Rica, but they're one of the biggest exporters who are known for their beans that I'm like, to be a founder...that it's like, as a country, we stand for taking care of our environment and sustainability always being part of the way that you grow up, like, to then carry that on in Silicon Valley, I was just clapping hands, just excited. [laughs]AUSTIN: I know it's a cool idea. Don't get me wrong on this.ANA: Well, I will take us to our technology podcast.ADRIANA: Technology. [laughs] Yes, let's get into the technology meat of it. So I guess, for starters, Ted was my co-host on one of the On-Call Me Maybe episodes where we had Luiz Aoqui talking about Instrumenting Nomad with OpenTelemetry. Let's use this as an opportunity to get to know Ted and Austin better.AUSTIN: I nominate Ted to go first. ADRIANA: Awesome, awesome. [laughs] I feel like when we met in person at KubeCon, you striked me as way more interesting than me. [laughs] So I feel like you've got really cool stories to tell, like how you got into tech and how you got into OpenTelemetry. [laughs]TED: I have definitely lived a very non-linear life, which leads to, like [laughter], oh, there's the one time I was racing an electric car in Denmark kind of thing or whatever. Tech, I initially moved to San Francisco to be an animator. So I guess I got started in the animation industry but in 3D animation. And I did have a computer science degree, so it was very techy. Besides animation, I was really interested in what's called rigging, which is where you set up the armature, like all the controls you use to move the characters around and make all the muscles squish up and stuff like that, and that was a lot of fun. But I actually got into, like, internet stuff through environmental activism, especially climate change stuff. It's kind of hard to remember, but back in the day, it was not something people really had a big opinion about. It was very hard to get news stories written about this stuff if you weren't connected to a university campus or in a particular subculture. Like, climate change was just this super weird, vague concept. So we started using this fun thing called the internet to start doing mass mobilizations and media stuff, particularly with this guy named Bill McKibben, who turned it into this called 350.org, and eventually, that turned into the Sunrise Movement. Oh, I'm out, like, too old. [laughs] So I moved on and then ended up getting into distributed operating systems stuff which was super nerdy. But basically, we didn't have very good platforms to build this scalable tech on. And there was Heroku, but that was about it. So I was working on an open-source version of a Heroku-like platform called Cloud Foundry. And then through that, got really, really annoyed at how difficult it was to observe what these things were doing and recreate it, especially because it was an operating system that we're shipping to all these big companies, and they're operating it, and then they're having problems. And I'm needing to recreate what it is that they're doing, and I can't just stand up their version of this system. So I really became obsessive about stuff like tracing, which was not a big, popular concept at the time, and the ability for all of these different users who were running this thing who had their own collection systems, and they were using their own observability tools but being able to pump into all of those things. And that combo led to me becoming really interested in OpenTracing because it was like this perfect combo of, like, oh, it's distributed tracing, but it's just the interfaces. You can connect this up to any back end, and it really scratched an itch for me. And the open-source projects I was working on around containers and stuff like that were kind of like a tire fire as far as the way the corporate backers of those companies were treating each other. It was also an opportunity to help build a new open-source community that sucked less. And so, for all those reasons, Ben Sigelman convinced me to hop over just this newfangled thing called Lightstep that existed for like a couple of months. So I joined the Lightstep train. I think I was lucky 13 when I got hired.ADRIANA: Nice.ANA: Did you join OpenTracing project? Because that's what was going on then, right? This is pre-OpenTelemetry.TED: Yeah. So before OpenTelemetry, there was a smaller project called OpenTracing that was much more narrow in scope. It was just focusing on tracing, and it was also just focused on instrumentation and interfaces. Like, the most annoying part of all of this, when you get into tracing instead of just logs and metrics, is that you have to propagate this context. And that is this huge lift for anyone who gets interested in this concept and just tries to do it on their own. They discover it's just this huge lift to do this context propagation, both serializing and deserializing this stuff and then shoveling it through the runtime of your program. And so OpenTracing was designed to really just solve that problem for everyone without getting up in anyone's business about what they were going to do with that data. The scope of the project was a lot smaller. But while I was working on that, I became really obsessed with the idea that we needed to unify all of these different signals. It wasn't just about distributed tracing; it was like logs and metrics, and you could generate metrics out of your traces and all this stuff. So I got really interested in this idea of having a unified observability platform because that was actually this other problem that I had, which was all of these data sources being disconnected from each other. And in order to do that, you really need to have a unified telemetry system. It works much better if all the data is coming out in an integrated fashion. And around that time, another project called OpenCensus had kind of come out of Google as well that was more focused on solving that problem. And the merging of these two things led to OpenTelemetry.ANA: I remember being at the KubeCon where they announced the merge and OpenTelemetry is a thing. And I was just like, this all sounds really cool. I hadn't really been too exposed to the space. I knew about the problems being in SRE, but I was like, okay, this all sounds really cool.TED: Yeah, I was really proud of everyone to be willing to merge all this stuff and create a standard. We needed to merge because having multiple projects in this space actually was working at cross purposes because this is this cr…

    Full show notes at the publisher

    Adventures in Open Source Software with Riaan Nolan of Servian Nov 22, 2022
    Show notes

    About the guest:Riaan is a Principal Consultant with Servian, based out of Brisbane, Australia. Originally from South Africa, Riaan has worked for multinational companies in China, Portugal, Germany, the US, and Australia. He has a keen interest in Automation, Infrastructure as Code, and Configuration as Code, with a strong focus on DevOps ways of working.Riaan is also a HashiCorp Ambassador.In his spare time, Riaan enjoys hiking in nature, camping, trail running, and motorcycles. Find our guest on:Riaan's TwitterRiaan's LinkedInRiaan's GitHubRiaan’s WebsiteFind us on:On Call Me Maybe Podcast TwitterOn Call Me Maybe Podcast LinkedIn PageAdriana’s TwitterAdriana’s MastodonAdriana’s LinkedInAdriana’s InstagramAna’s TwitterAna's MastodonAna’s LinkedInAna's InstagramShow Links:ServianHashiQubekubectlMiniKubeHashiCorp Ambassador TerraformTerragrunttfenvDBTHelmDocker AMD64 ProcessorAArch64Apple M1 ProcessorApple M2 ProcessorVaultSRE / Google SRE Book (aka “SRE Bible”)Spring Boot Google BorgLightstepNew RelicWerner Vogels (VP & CTO at Amazon)Additional Links:Blog: Running HashiQube on Multi-Arch (Arm and x86)/ Multi-OS (Linux, Mac, Windows) with Docker Desktop and VagrantTranscript:ANA: Hey, y'all. Welcome to On-Call Me Maybe, the podcast about DevOps, SRE, observability principles, on-call, and just about everything in between. Today we're talking to Riaan Nolan, who's going to be sharing some really cool tips for us today. And we're very happy to have you join us today.RIAAN: Thank you very much. Good morning, Ana and Adriana. Nice to see you, guys. And thank you for having me on your podcast.ADRIANA: Oh, we're super excited to be talking to you today.ANA: So the first question we like starting a podcast with...since it's early morning for you, and it's midafternoon for me, and almost evening for Adriana, what's your drink of choice for today's podcast?RIAAN: Well, it's 7:00 o'clock here by me, just after 7:00, so I'm having coffee. But normally, I love beer, anything cold, since I live in Brisbane, Australia. It's normally quite hot on this side. But it's coffee today. Cheers.ANA: Cheers. I got carrot and orange juice. So it's somewhat tasty.ADRIANA: Nice. Got plain, old water. [chuckles]ANA: Gotta stay hydrated with whatever heat's going on in this world. Super sad panda for this global warming.RIAAN: Oh, it's summer by you guys now.ADRIANA: Yeah, yeah. We had a heat wave here last week in Toronto where we got hit with like 40 degrees Celsius, so 100-ish Fahrenheit, so that was very unpleasant. And my AC broke in the midst of it, so boo. We got it fixed, fortunately, but boo.RIAAN: Wow, that's cool. I can't wait to have that weather. I'm such a fan of hot weather. Really, I love it. If it's 38-40 degrees Celsius, I really love it.ADRIANA: I do dig it as well, having grown up in Rio de Janeiro, but it definitely got very stifling inside the house. [laughs] But yeah, I'm for warm weather as well. I do enjoy a nice balmy temperature.ANA: It's really weird for me because the entire United States is having temperatures of 80 degrees, 90 degrees-plus, and I reside in San Francisco, California. So sorry I use Fahrenheit, even though I grew up with Celsius; [laughter] that's a disclaimer. And secondly, San Francisco has been really cool, like not freezing cold, but it's been chilly, like 50-60 degrees Fahrenheit. And I go on the weather applications, and the entire United States is red. And then you look at Spain and France, and they're having deaths due to the heat. And I'm just like, I am so scared for whatever is going to happen overall in the world. But when you're one of the only cities that is not going through the heat wave, I'm like, so what are we going to get? Like, we're going to get something. What is it going to be?ADRIANA: It's coming for you, I think.RIAAN: I think it's that La Niña, the opposite of the El Niño at the moment. And that's what makes the weather a little bit lopsided, a little bit weird.ANA: And it's interesting because it's like, weather is one thing [chuckles] that I refuse to try to get into and try to understand. I have the understanding of how water precipitation and condensation hurricanes work. But then it's like, my complex systems start at DevOps and SRE. [laughs] I refuse to start an entire other study of how other systems work.[laughter]ADRIANA: You've got enough complexity in your life. ANA: I think so. RIAAN: That's funny, you know.ANA: So as we were breaking into having these conversations, I actually want to bring up the amazing conversations that happen virtually in COVID where I think we're geeking out a lot more. We have a lot more virtual calls. And it could be similar to the hallway tracks. We have conferences and meetups, but it's really awesome to be able to share tools. And we got a chance to share some of our favorite tooling and talk about Riaan's open-source projects. So I'm going to give you the mic for you to share a little bit more of what you have actually been working on and contributing to open source.RIAAN: Thank you. So as you know, I'm a HashiCorp ambassador also with Adriana, my colleague.ADRIANA: Woo. RIAAN: I'm HashiCorp staff. So the one tool I've been working on is HashiQube, and it runs all of the HashiCorp tools and MiniKube, and it now runs in a Docker container. So I'm really excited about that. It helps me a lot when I have to proof of concept stuff up. Sometimes just put up a...what do you call it? The Ansible Tower running on top of Minikube, and then I can use that to connect to Vault to sign certificates or get secrets. And if I have to use Docker or if I have to Terraform something up, it's just a little tool that I can quickly use to do that.And then, on the other side, there's a little tools container that I've been working on that's on my GitHub. And that's just a little container with Terraform, and tfenv, and Terragrunt, and DBT, and kubectl, and Helm that you use for data projects or infrastructure projects. And it's just a little container that I try to get it to run on AMD64, and AArch64, the M1 chip, so the M2 Apple chips. So that's how I keep myself busy with and tinkering with that.ADRIANA: That's awesome. I'm personally a big fan of HashiQube. And I think that's how we connected initially. RIAAN: Yes.ADRIANA: And it's funny because I found out about HashiQube from a former co-worker of mine when we were doing some local Hashi setup. And he told me about HashiQube, and then I started playing around with it. I'm like, oh my God, this thing is the coolest thing in the world. Because I can now mess around with all the Hashi tools without having to rely on some Nomad cluster running in the data center. And for me, that was amazing because that meant I could be in control. (I like being in control.) I didn't want to have to rely on someone. And we were running...we had our own private cloud. So it wasn't like I couldn't just as easily spin up a virtual machine the way that I would if we were on a public cloud. So for me, this was an amazing salvation because I was able to tinker.And I also want to say, as a plug for HashiQube, the stuff that I did in my local environment in HashiQube pretty much translated when I moved stuff over to deploy in the data center, so super stoked for that. So yeah, I can't say enough good things about HashiQube. And I've blogged a lot about HashiQube as well in my Nomad explorations.RIAAN: Thank you.ADRIANA: So awesome. Check it out, check it out. [laughs]RIAAN: Thank you. I'm glad it helped you. It certainly helped me when I was sitting on the train or trying to learn a new thing here, you know, seeing our Vault can connect to MySQL and create database users and seeing that lease expire, that time to live. It's fascinating and so easy to do now. You just spin up a MySQL container with some arguments, and there you go in and plug it into Vault database engine, and off you go. So, yeah, it helped me also a lot.ANA: We have so many tools out there. That's always nice when we have easier ways to onboard, especially when it comes to making the space that we work on better. That actually made me think about...I know both of you are huge open-source contributors. And I know some of our listeners are too. What was your biggest reason for going into contributing to open source and especially starting new projects for the ecosystem?RIAAN: I've always been interested in open source, and I've always been using Ubuntu. But something that I enjoyed doing is also contributing to open source and helping other people learn. And I saw one of your questions is how do you cope with failures? And this is so much related to this topic because if you contribute and you can push to GitHub, and other people can pull your changes and test it out for you, and work together on this, then it kind of helps learning and dealing with failures a little bit easier. Because every single day, you have that aha, it's working moment, that little bit of happy endorphins in your brain that just fires, and you get it ready, and then you can make that commit. And sharing your work with other people, it's really enjoyable. It makes life interesting and fun.ADRIANA: I was going to say when you put your work out there, when you open source your work, you are basically making yourself vulnerable to the outside world. The reward is immense because you can have people who come in and start using your product. And they're like, oh, this is awesome, but here's a way to make it better and contribute, and you help each other improve. But it can be so scary too because you open-source something, and then you can have some jackass go, "Well, this is crap. I would do it much better if it was me, and this was what I would do." And so it can be really scary. So I think it's so important to put yourself out there, even knowing that that could be the reaction that some may have from putting your work out there in public.RIAAN: Totally. I mean, you've seen the way I do HashiQube. It's a bunch of Bash scripts and Vault commands and stuff. It's nothing really fancy or anything, but it works, and that's version one. And if people can make it better, then even great. For me, the intention of putting it out there is to help other people, and share the stuff, and get things going easily, being able to test new versions quickly, or just get something up. And I always look at it from that perspective, if your intentions are pure, then haters are going to hate, and there's nothing you can do about it. Haters will hate. And I try to just live on the bright side of life. And if they can do it better, then great, help contribute. If you can't do it better and you want to slam me or whatever, that's also okay. Some people sometimes just have a difficult day, and they bark at you. And coming out of this COVID thing, you can definitely feel the stress levels. It's been a little bit on the upper side of life. Of course, mental health awareness, we just had Mental Health Awareness month, I think, last month. So you can definitely feel people are sometimes on the edge. There is war in the world. We haven't had war in such a long time. And now it's there full-blown in the open. And, of course, the media want to capitalize because bad news sells. And this is not good for anyone. So what can you do? You got to just look on the brighter side of life and stay true to yourself and do what makes you happy and try to help other people. What else can you do? And plus, if people say you could do it better, I always tell them, "Man, I come from Africa, and if you think that I'm the best out there, you're the idiot. Africa... you are the first world; if you want to make it better, make it better." [laughs] Just a little bit of a joke. Us Africans are actually super clever, but just a joke.[laughter]ANA: I think it's also, as you say, the world being kind of really crappy right now with folks just trying to push through as much as they can. I think I've heard the sentiment from a lot of people that open source was just their outlet where it was their only way to cope with all this idle time that they had or the lack of in real-life connections like family and friends or health reasons you can't really see anyone. Being able to connect with one another and build a better ecosystem really, really pushed people. There are a lot of pros and cons. You need to have a lot of psychological safety within an open-source project to be able to have a code of conduct that it's if you're an asshole in PRs, [laughs] GTFO. You can't be there, and the organization is going to hold you accountable. They'll go to bat for you, and code of conduct breaches will get put in into a repo.RIAAN: It will, you know. But I could think of nothing more exciting than learners telling you, "Your PR sucks." [laughter] I would frame that, blow it up, and put it on my wall. Look, learners told me my PR sucks. [laughter] It comes with the pressure of stuff. Sometimes these projects do with all of the good intentions. With all the time we've been trying to make stuff simpler, I just feel that it's been getting more and more complex, and complex and more complex. And as soon as you look through the microscope lens and you look deeper, then there's more to see. And I think we will get there. We are definitely still on the journey. I saw a tweet from Kelsey Hightower the other day saying DevOps is dead; long live DevOps. ADRIANA: [laughs]RIAAN: And isn't that so true? Most companies we work for are only now doing this transition into DevOps and the ways of working, and we've been in this so long that it's already kind of last decade for us. But still, it's still so fresh in the minds of corporates that it's actually fascinating.ADRIANA: Yeah, it totally is. It's funny because I think Ana and I were talking about that earlier with regards to DevOps at the enterprise level is so different from DevOps at the non-enterprise level. Because at the enterprise level, you are dealing with bureaucracy, red tape, moving parts. You've got the lifers who do not want to change. You've got the VPs who are basically marking their territory and also are going to be resistant to change because you're encroaching on their little kingdoms. It is such a complex sociotechnical problem. I don't even know that there is the solution for it. I think the only best approach to start taking with that is you need some sort of like, honestly, I think you need the CEO on board with this stuff or the CTO. They can push that down to the lower levels, basically providing that psychological safety, if you will, to the other folks saying "Yes, it's okay to follow DevOps practices." But it's so hard to get up to those levels because those guys are so far removed that how do you have that conversation? I mean, even the ones that were technical have been so far removed from tech.RIAAN: What I think we're going to do is we're going to outlive them. And the way we are doing it, we are already prepping the next generation, the next wave of DevOps people. So as we get older, we're also going to move into management, but this mindset, this curious, this forgiving, this no-blame culture, I believe, is going to stay with us. Let's say you go up into management, CIO level, CTO level, you will still have this foundational layer of DevOps in the fiber of y…

    Full show notes at the publisher

    Previous 1 2 3 4 Next

    Related Podcasts

    Reply All

    1

    Reply All Games & Hobbies
    Inside VR & AR

    2

    Inside VR & AR Gadgets
    Note to Self

    3

    Note to Self News
    BrainStuff

    4

    BrainStuff Natural Sciences
    This Week in Tech (Audio)

    5

    This Week in Tech (Audio) News
    Hands-On Tech (Audio)

    6

    Hands-On Tech (Audio) Technology
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights