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
    Software How-To

    Greater Than Code

    For a long time, tech culture has focused too narrowly on technical skills; this has resulted in a tech community that too often puts companies and code over people. Greater Than Code is a podcast that invites the voices of people who are not heard from enough in tech: women, people of color, trans and/or queer folks, to talk about the human side of software development and technology. Greater Than Code is providing a vital platform for these conversations, and developing new ideas of what it means to be a technologist beyond just the code.
    Featuring an ongoing panel of racially and gender diverse tech panelists, the majority of podcast guests so far have been women in tech! We’ve covered topics including imposter syndrome, mental illness, sexuality, unconscious bias and social justice. We also have a major focus on skill sets that tech too often devalues, like team-building, hiring, community organizing, mentorship and empathy. Each episode also includes a transcript.
    We have an active Slack community that members can join by pledging as little as $1 per month via Patreon. (https://www.patreon.com/greaterthancode)

    Advertise
    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    227: Doing DevRel Right with Jonan Scheffler Mar 24, 2021
    Show notes

    02:28 - Jonan’s Superpower: Jonan’s Friends The Quality and Reliability of One’s Personal Network Finding Community The Ruby Community in Particular – Focus on People and Programmer Joy Happy Birthday, Ruby! 09:07 - How Developer Relations is Changing (DevRel) Kicking Off New Relic’s New Developer Relations Program Outreach and Community Growth Value Developing Developer Empathy & Adjusting Content in the Spirit of Play The Correct Role of DevRel 22:41 - Doing DevRel Right Feedback Loops The Definition of Success 31:45 - Engaging with Communities & Networks via DevRel Using Twitch, YouTube, Discord, TikTok, Twitter, etc. Consider the Platform The Relicans Emily Kager's TikTok @theannalytical @cassidoo @laurieontech 40:22 - Internal DevRel Content Review Meetings Make Friends w/ Marketing/Internal Communications (Comms) Be Loud & Overcommunicate 53:32 - Addressing Trauma & The Evil in the World “I respect facts but I live in impressions.” In The Mouth of Madness Reflections: Mando: We are who we spend time with. Rein: If you want to understand how someone behaves, you have to understand their environment and experiences. Jess: If it works, it’s going to be obvious it works. Jonan: Talking about the things that suck and talking about who you are in a real way. This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well. Transcript: PRE-ROLL: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started. JONAN: Welcome back to Greater Than Code. This is Episode 227. I am Jonan Scheffler and I'm joined today by my guest, Jessica Kerr. How are you, Jessica? JESSICA: Thank you, Jonan. Well, I’m great today because I get to be here with my friend, Rein Henrichs. REIN: Aw thanks, Jessica. And I'm here with my friend, Mando Escamilla. MANDO: Thanks, Rein and just to bring it back around, I'm here with my friend, Jonan Scheffler. Jonan Scheffler is the Director of Developer Relations at New Relic. He has a long history of breaking things in public and occasionally putting them back together again. His interest in physical computing often leads him to experiment with robotics and microelectronics, although his professional experience is more closely tied to cloud services and modern application development. In order to break things more effectively, he is particularly excited about observability as of late, and he’s committed to helping developers around the world live happier lives by showing them how to keep their apps and their dreams alive through the night. Welcome to Greater Than Code, Jonan. How are you doing today, bud? JONAN: I am great. I liked the part where I got to intro your podcast. That was a lot of fun, actually. MANDO: It was fantastic, man. JONAN: This bio, this guest sounds really interesting, if I would be permitted to say so myself as the guest. MANDO: So we like to start off every podcast with our normal question that we ask every guest, which is, what is your superpower, Jonan and how did you acquire it? JONAN: My superpower is my friends. They are my superpower and I acquired them after a long career in software and talking to a lot of humans. I don't know actually why, but it's been easy for me to make friends in software. I felt like early on, I found my people and then I just got lucky and it's going okay so far. I'm very fortunate to have them. MANDO: Well, we're fortunate to have you, bud. It's interesting that you say this, I mean, just like Slack for operators, DevOps folks, and Savvy folks, there’s been a lot of discussion as of late on the quality and reliability of one's personal network in things like finding new jobs, finding new opportunities, learning and growing in your career, and stuff like that. It’s been interesting for me personally, because my experience, Jonan sounds a lot more like yours. I was very lucky to find some strong communities of folks that were very welcoming to me. I found my people pretty early on, but a lot of the folks in this other community that I'm tangentially related to seem to have had wildly different experience. I don't know if it's like a software development versus operator kind of thing and in-person versus not in-person kind of thing. It's something that struck me as weird. JONAN: I think it varies by community, too. I've gone to a lot of conferences for a lot of different languages and depending on the conference and depending on the community, I think that you're going to have a different time. I think if I were starting over again, I would probably follow about the same path—attend small conferences with tight focuses and get to know a couple people early on who seem to be having a lot of those conversations, watch for a social butterfly and tag along for a bit and you'll get introduced. MANDO: I'm pretty sure that I met Rein at a local Ruby conference here in Austin. Is that right, Rein? REIN: Sounds right. Sure, yeah. MANDO: But I think it was one of the first Lone Star Ruby Conferences where we met. REIN: Yeah, that sounds right. JONAN: Yeah. I think speaking of butterflies, I also met Rein, I think at one of the very first conferences I attended back in the day. Being welcomed and seeing the application of the Pac-Man rule, where when standing in a circle, you always leave a space for a guest to join and someone joins and you open up again in-person back in the Ruby community in that day was, I think inspiring for me; directed how I decided I was going to be when I showed up here. So thank you, Rein. REIN: It's funny. I remember when I was new to the Ruby community and not sure what to do. I was new to programming, too. I started going to the local Austin meetup actually and the welcome I got as someone who didn't go to college for computer science, someone who wasn't a professional programmer, someone who was just thought it was cool and thought maybe that I could get paid to do it at some point in the future really made a big difference in my life. JONAN: Jessica, how did you get started? JESSICA: Good question. Before I answer it, I noticed that we're talking about Ruby conferences and Ruby programmers and indeed, I learned Ruby in order to go to Ruby conferences so that I could talk to Ruby people because part of the superpowers that that language gives you is friends or buds back in the day, but still is because the Ruby conferences are still super friendly back when we had them. REIN: Yeah. MANDO: Yeah, that's a really good point. I was a professional programmer for probably 5, or 6 years before I started doing Ruby programming. I would say that for those first 5, or 6 years, before I joined the Ruby community, I didn't feel at all like I had any kind of community or group of people. JONAN: What do you think inspires that in a community? I think strong leadership is part of it. Matt has certainly received his share of criticism over the year, but I think that fundamentally, he was trying to build a place where people focused on people instead of the glyphs that we type into our little boxes. I think that matters. What else do you think there is to that? REIN: We here at Greater Than Code also agree with that sentiment. [laughter] JONAN: Seems to align, doesn't it? JESSICA: Yeah, that focus on people and Ruby was always about programmer joy. It was always about the experience; it was always about being happy and there wasn’t that expectation that the optimal thing to do is to go in a corner and type. JONAN: Yeah, I think it's very fortuitous timing that we're actually discussing Ruby so much on the 24th, which was the day that Ruby was named 28 years ago on February 24th, Ruby became the name of this language. So happy birthday, Ruby. JESSICA: Aw. Yeah, happy [inaudible]. JONAN: It really has changed my life. I have regularly, whenever I've seen Matt at a conference, got up to thank him for my house and my kids' college education. Before I got into software, I did a lot of things, but none of them would have brought me either of those. I spent probably 10 years in factories and hotels and casinos. I was a poker dealer for my last gig before I got into software and the number of opportunities that Ruby opened up for me, I can't as long as I live be too grateful; I'll be paying it forward till I die. JESSICA: Yeah, but not the language it's the community—the people, the friends. JONAN: Yeah, exactly. It's the community. It's the people who welcomed me with open arms and made sure that they were contributing to my growth in a far more altruistic sense than, I think is reasonable to expect. I mean, I had nothing to offer in return except a good conversation and high fives and hugs and they spent their time in their energy taking me around conferences and making sure I met people and it was great. REIN: I remember when you first went to New Relic and you were first thinking about, “Hey, maybe I could do this developer relations thing.” What I remember about that, in addition to your obvious aptitude at talking to people about things, is the help that you got, the advice, the mentorship that you got from your friends in the community. I remember at the time being blown away by that; by how many people were willing to just take an hour of their time to talk to you about what it was like for them as a DevRel and things like that. JONAN: Yeah, and I'm still very fortunate to have those people who have helped me build this team here. When I did the onboarding, I put together an elaborate onboarding process. I was able to hire all ten of the DevRel engineers here at the same time. We spent a week doing improv training and having speakers come in as guests and I was able to invite all of these DevRel leaders from over the years to give a perspective on what DevRel was in their eyes, but it is today and always has been clear to me that I am only here where I am by the grace of the communities that I was lucky enough to join. I wonder if developer relations is changing; if it's at a different place than it was when I started out. I feel like certainly, pandemic times have affected things, but all that aside, the segment of the industry is still pretty small. There are only maybe 10,000 people doing this work around the world. It's hard to believe because we're quite loud, right? [chuckles] We’ve got a lot of stages. You see a lot of us, but there are many of us and I think that the maturity of the discipline, I guess, is progressing. We are developing ways to measure the effectiveness. Being able to prove the value to a company is going to change the game for us in a lot of ways. REIN: Yeah. I would love to talk to you about that at length, [chuckles] but for the purposes of this podcast, let's say that you're someone who wants to start a program at a company that doesn't have directly tangible make numbers go up in a business sense value, but you believe that if you're given the chance to do it, that you can show them the value. How do you get that opportunity? JONAN: That's a really good question. Kicking off a developer relations program is, I think it's the same as building most major initiatives within a company. If you had an idea for a software project that should be undertaken, or a major feature that mattered to you, it's about building allies early and often. Making sure that when you show up in that meeting to have the conversation with the decisionmaker, that nine out of ten people in that meeting already know about the plan. They have already contributed their feedback; they feel ownership of that plan and they're ready to support you so that you have the answer going in. I think the mistake that I made often in my career was walking into that room and just pitching my idea all at once and then all of the questions that come out of that and all of the investigation that is necessary and the vetting appears as though this wasn't a very well-thought-out plan, but getting the people on board in the first place is vitally important. I think also you have a lot of examples to look through. You have a chance to talk about other programs and the success that they've brought, the companies where they started off. It's not a thing that you need to start in a big way. You can put a couple of people on the conference speaking circuit, or a couple of people focusing part of their week on outreach and community growth and see where it takes you. If you start to see the numbers, it becomes a lot easier case to make. REIN: You were talking about how you're excited about being able to make this value more tangible in the future. What do you think is the shift that's happening in DevRel that’s making that possible? JONAN: So I think there are actually kind of a lot of factors here. One is that DevRel had a division almost of method where some people, probably by the leadership of their companies, were convinced that what they should be doing is talking about the product all of the time. You're there to talk about the product and evangelize the product and get people to use the product. That is part of your role, but it shouldn't be, in my opinion, the primary role that you play. You should be there in the community participating. In the same way that Rein stood in that hallway and welcomed me to Ruby, I need to stand in that hallway and welcome newcomers to all the communities of which I'm part and in so doing, build that group of friends and build that understanding of the community and their needs. I develop empathy for the developers using our product and, in the industry, generally and that's invaluable intelligence. I sometimes think of ourselves as these like operatives—we’re undercover marketing operatives out there in the developer world talking to developers and just understanding them and it at one point, took a turn towards, “Well, I'm just going to talk about New Relic all the time,” for example. It feels good to see all that content and see all those talks. However, you're only talking to your existing audience. No one is Googling “what exciting things can I do with New Relic,” “seven awesome New Relic tips.” No one's searching for that. They're out there looking at things that are interesting. They want to click on a link on Twitter that is about some random topic. Running Kubernetes on Raspberry Pis and soldering things to Yoda dolls. That's the kind of stuff that I'm going to click on in my free time and in that spirit of play, that's where I want to be engaged and that's where I want to be engaging people. So I think there was this turn. That's part of it…

    Full show notes at the publisher

    226: Incarceration and Technology with Kurt Kemple Mar 17, 2021
    Show notes

    01:49 - Kurt’s Superpower: Lifting Others Up: “A rising tide lifts all boats.” 07:00 - “Self-Taught” vs “Self-Guided” vs “Self-Motivated” Developers 11:32 - The Intersection of Incarceration and Technology Destigmatizing Incarcerated Folx Hiring the Formerly Incarcerated Providing Stability to Folx Coming Out of Incarceration 22:15 - Having Privilege Working in DevRel to Raise These Issues Bias and White Privilege 26:51 - Helping and Advocating For the Formerly Incarcerated 29:32 - The Interview Process as it Relates to the Formerly Incarcerated Background Checks Rolling Jobs 36:26 - Always Be Applying (ABA); Technical Interviews and Fabrication/Bending Truths Voluntary Disclosure: I'm an Impostor - Incarceration and Living a Lie 45:29 - Problematic Binary Identities 47:07 - What can companies and hiring managers do? / Problems with Hiring in Tech and Tech Interviews Make No Assumptions Avoid Feigned Surprise Don’t Treat People Differently Don’t Take Advantage Don’t Interrogate 01:05:19 - Contextualizing Advice Reflections: Kurt: Community is what you surround yourself with. Laurie: Having empathy and understanding as a hiring manager for people who have perceivably negative things in their background. Jacob: Polyglotism and not being so gatekeep-y. John: Being reminded of how terrible our carceral state is here in the U.S. This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well. Transcript: PRE-ROLL: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started. JACOB: Hello, everybody and welcome to Episode 226 of Greater Than Code. My name is Jacob Stoebel and I’m joined with my co-panelist, John Sawers. JOHN: Thank you, Jacob and I’m here with Laurie Barth. LAURIE: Thanks, John. I’m excited to introduce our guest today, Kurt Kemple. Kurt Kemple is a technical writer, speaker, and software developer living in Virginia Beach, Virginia. He’s very passionate about the intersection of technology and incarceration. Currently, he works for Apollo GraphQL, as a Developer Relations Manager and when not working he can be found by the ocean or relaxing with his family, which sounds really incredible. So Kurt, I'm going to have you start us off by answering the question we ask all of our guests, which is what is your developer superpower? KURT: Well, first thank you for that awesome introduction. It's a pleasure to be here. So diving into what is my superpower, I thought about this a lot and I'm not really someone who I feel has some innate skill or ability that really makes me stand out in any particular area. But I think one thing that I do really well is I care very much about lifting up the people around me. I work actively to generally help others more than I'm helping myself. I think the rising tide lifts all boats kind of mentality and I think that that is definitely something that sets me apart is I gauge my success by how successful folks around me are. JACOB: That sounds fantastic. Was that something you felt like you've always done, or was it something do you consciously develop, or did it just sort of come around? KURT: I think it evolved out of situations in my life. I've dealt with a lot of stressful situations and pretty tough upbringing and I think a lot of it is just finding opportunities to make sure people don't have to experience those things and not being so drastic that it's always in relation to something very life altering. But there's something about removing roadblocks for other folks that you have the ability to do that is very rewarding to me and I think I just started to realize that later in life that that's something I value greatly. LAURIE: That's really interesting to hear because I think in a lot of areas of technology and in the industry, we often hear people saying like, “I had to do it, so you have to do it, too.” I've heard that with sort of the toxic interview, it's almost like hazing mentality and the tools may be abstracted, but if you don't know the super, super low-level piece of it, then you're never going to understand it the way I do sort of mentality. A lot of this gatekeeping stuff comes from that. So it's really refreshing to hear that you feel sort of the opposite of that. KURT: Yeah. Like I remember very distinctly, many times starting out programming, like getting the response: RTFM. It's like, people, they don't want to help for whatever reason. They want you to – it's like almost like a badge of honor; forcing folks to figure things out for themselves. There's something to be said with taking on learning as your own responsibility, but part of learning is knowing how to get answers and ask for help when you aren't figuring it out and so, I definitely really cannot stand to see that kind of lift the ladder up behind me mentality, or pull yourself up by the bootstraps type mentality. JACOB: So who are those people around you in your role with Apollo? Who are the people that you would measure the success of? KURT: Yeah. So it's actually spread out across multiple things, but I'll start from Apollo. I'm a manager of the developer relations team so definitely my direct reports absolutely care about how well they are doing as well as the DX organization, it extends out to their world. We're all part of developer experience and we want to make sure that things we're doing is helping lifting up the education team and DX as a whole. And then of course, that spreads out into Apollo, which is just by helping developers be successful with Apollo, we're actually helping a policy succeed. But when we talk about developer relations, really that's just communities I'm involved with at all. So that could be anybody from the communities that I'm a part of, whether that's content creation, DevRel, things around GraphQL, or developments, it could be anything related to that. Pretty much any person that I have interaction with, I start to look at ways in which I can help them move forward. JOHN: It's funny the phrase “bootstrap” is so embedded in our culture because it's coming from – it’s technical terminology at this point, but it's so interesting and I think important to think back to the origin of that phrase, “pull yourself up by your bootstraps” was satirical because it's obviously, not possible to do that for you. You can't lift yourself by grabbing your boots and that's the whole point, but it's almost like turned over on itself and becoming oh, that's just what you do as economic policy or a social policy despite the fact that it was originally the complete opposite of that. KURT: Yeah. It's funny. I never really thought about that, but it's very true. They took something that was meant to be like satire, like, “Oh yeah, just pull yourself up by your bootstraps,” and then turned it into something serious. I still view it as satire. To me, it's the silliest phrase ever, but a lot of folks take that very seriously. JACOB: What else is satire or was originally satire was the word, “meritocracy”? KURT: Oh wow. JACOB: Yeah. It was basically like oh, the new aristocracy of people who think they're on top because of their merit; it's the meritocracy. It's something else I think about is the phrase self-taught; ex self-taught developer, self-taught engineer, or the million Medium posts of how I taught myself to code in 12 weeks. What does that mean, taught yourself? Do you have no interactions with any human? JOHN: You didn’t think a human produced? LAURIE: Yeah. The self-taught thing is actually really complicated and nuanced in my mind because a lot of people like to claim it and say, “Well, we're all self-taught because we all read blog posts and have to teach ourselves other things because as a developer, you're always learning new things and so, we can all claim that title.” And then there's the area of people who consider themselves self-taught, but they were working one-on-one through DMs with someone that is a working developer and they know really well. But then there's actually a last category of people, which is what I feel the label was sort of designed for, which is they never had any formal classroom experience that taught them like, the variable goes on the left side of the expression. So they had to learn just those super fundamental syntactical things through reading and through example videos and potentially sometimes asking questions, but it was a very async process. I think that's what self-taught is designed to imply that there wasn't a curriculum laid out in front of them and that they didn't have a helping hand along the way. I think there's something incredibly powerful about that and I hate the idea that it's been co-opted as well, everyone's self-taught, I'm like, “No, I got to sit in a computer science program and have teachers tell me what I needed to know in a certain order.” Was that necessarily the best way for me to learn? No. Did I have to go in and teach myself how to do things after that fact and for the rest of my career? Absolutely. But did I have some of those baseline foundational things conveyed to me based on someone who knew the order of operations of learning this topic? I did. So I am not self-taught in any sense of the word. KURT: Yeah. I think that's very interesting point and what I've been using. So I'm the other end of that spectrum. No official – that's actually not true, I took intro or intermediate web development course when I was incarcerated. But this was basically, here's a book on HTML, CSS, and JavaScript and good luck. But aside from that, I had no real formal education, but I've adopted the term self-guided, which I feel is a better descriptor of that. Because it's more about guiding yourself through a curriculum to learn programming and it's like, you're pulling bits and pieces from wherever. You can find it to create your own curriculum is essentially what you're doing. But I did learn from lots of other folks along that journey, both through asynchronous communication and DMs, watching videos, reading, blog posts and stuff. So it's not like I was in a room with no outside influence and had a computer and was like, “I will code.” But I think I really like that term, self-guided, because that's a better representation, I feel like of what actually happened. LAURIE: I love that and it reminds me of when I was in high school where you get to take independent study and it's sort of the same concept of you get to go in-depth on a topic, but you're determining what shape that takes and where you go and what you focus on. JACOB: What successful means. KURT: Yeah. JACOB: And then no one will probably care, to be truthful. No one will actually care if you don't do it. LAURIE: Yeah. Yeah, that's the other thing; self-motivated is a big part of that. Like, no one's grading papers or assignments. There's no papers in coding. [laughter] No one is grading assignments. You don't have deadlines that are imposed by other people. If you buy the course and you never watch a single video, the only one accountable for that is sunk cost fallacy of having wasted the money. There's nothing forcing you to power through and that's actually a great way to prepare yourself for coding on the job. Because it's like, technically, there's just this ticket and you need to be looking at it and feel the sense of oh no, I need to get this done because no one can actually force you to do it! [laughs] KURT: Yeah. That's very accurate. [chuckles] JOHN: Concurred. It sounds like from your bio there that the group of people that you consider yourself to be responsible for helping to lift up is beyond just the team that you're responsible for. So I’d love to hear more about the other groups that you're working with on that level. KURT: Yeah. So, I think it's interesting when we talk about community and groups and to me, community is not like a thing with guidelines and boundaries, community is whoever you surround yourself with and so, to me, there is no React community, or GraphQL community. There's just people in my community who happened to know React, or GraphQL and I think it's an interesting way to look at community because it breaks down a lot of barriers. But if we do talk about specific groups, I am very into the intersection of incarceration and technology and the reason why is because I myself am formerly incarcerated and getting into tech had such a drastic effect on my life. So it’s just naturally, I want to and again, a lot of this motivation for lifting others up stems from this. I feel like I am often sitting on a gold mine and I feel selfish when I know that there are people who were in a similar situation who are coming out of prison and don't have any idea that this industry exists, that they can have a future in it with some self-guided learning, some hard work, and a lot of perseverance. It's by no means easy, let's be real. Coding is a very difficult skill, but most folks can accomplish that goal of learning it and it just feels like if I'm not actively working to help expose people, who are coming out of incarceration, find this industry and see if it's a fit for them, then I feel like I'm just like holding something that I should be freely giving away. I think a lot of where it comes with lifting others up is that feeling of, I'm holding something that other people should have access to and that's education, information. When we talk about self-guided, it's actually one thing about picking your own curriculum that is anxiety inducing is, am I picking the right things to learn? The industry is huge and you could pick so many different things and I lucked out that I was introduced to something that was a good path into tech for me. I would like to provide folks coming out the information that the industry exists, but also a little bit of guidance around some of the different ways that you can go and break into it. So I'd say that is definitely a community, or a group of folks in my community that I care deeply about is those who are transitioning from incarceration back into society. LAURIE: I'm curious if – obviously, this is an experience and a community that a lot of us don't have a lot of insight into and it's great that you do and you have those connections. Can you talk to us a little bit about the kinds of things that we all can do to make that transition easier to support those groups of people, whe…

    Full show notes at the publisher

    225: Uncovering and Breaking Patterns with Tim Banks Mar 10, 2021
    Show notes

    03:31 - Uncovering Patterns Making the Covert Overt Reasons for Covertness 13:22 - Taking Care of People as Whole People People Are Dynamic – Not Stagnant Roles Are Constantly Changing Iterating on Practices William A. Kahn: Psychological Conditions of Personal Engagement and Disengagement at Work Financial Compensation Metrics and Observability 28:43 - The Tech Industry: Now vs Then (aka we still have A LOT of work to do) Gatekeeping Accountability Inclusivity New Zealand Maori leader ejected from parliament for refusing to wear 'colonial noose' Whitewashing 45:59 - The Messaging Around Diversity and Inclusion Doing the Right Thing 51:26 - Changing Mindsets Using Privilege to Speak to Power Reflections: Rein: Capitalism and White Supremacy are the same thing. The Invention of the White Race. We have an obligation to not just make it possible for people to exist in the industry, but to also make it healthy. John: It’s always great to have these conversations as reminders. Tim: Figure out why something makes you uncomfortable. Look and uncover the pattern underneath that in yourself. Be comfortable with being uncomfortable. If you run away, you’re never going to grow and things are never going to get better. This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well. Transcript: PRE-ROLL: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started. JOHN: Hello, everybody. This is Greater Than Code, Episode 225. I’m John Sawers and I’m here with Rein Henrichs. REIN: And I’m here with our guest, my friend, and Dungeons & Dragons party member, Tim Banks. Tim Banks has a career spanning over 20 years through various sectors. Tim’s initial journey into tech started as a US Marine in avionics. Upon leaving the Marine Corps, he went on to work as a government contractor. He then went into the private sector, working both in large corporate environments and in small startups. While working in the private sector, he honed his skills in systems administration and operations for large Unix-based datastores. Today, Tim leverages his years in operations, DevOps, and Site Reliability Engineering to advise and consult with engineering groups in his current role as a Principal Solutions Architect at Equinix Metal. Tim is also a competitive Brazilian Jiu-Jitsu practitioner, having won American National and Pan American Brazilian Jiu-Jitsu championships in his division. Hi, Tim! TIM: Hi! Good to see everybody in here. REIN: Yeah, I did that on the first take and I'm very proud of myself. TIM: I am so, so proud of you. That was amazing. REIN: Tim, it's time for the question. TIM: Right. REIN: What is your superpower and how did you acquire it? TIM: So my superpower is using empathy to uncover patterns that people haven't seen in the past and I think that's a superpower because a lot of people can look at something, there's a lot of folks out there that can see a pattern just on the surface like this does that, this does that, this does that. But when you really talk to groups and you talk to people, you can see some common things that aren't necessarily things that are going to have an output or a metric, but you can see how people feel about a thing. And then when you get enough people who feel a certain way about a thing, that's not going to be a coincidence, it's going to be a pattern. So finding those patterns is my superpower. As far as how I acquired it, it's hard for me to say. The easy way to say is over time, but over time and myself being a person who necessarily wasn't listened to, or seen, or heard trying to explain how things are, why things are the way they are without having metrics. So having been on one side of that equation, I've been able to see people on the other side of it. REIN: So Tim, you said “to uncover patterns.” Can you say a bit more about the word uncover? Because I feel like that might've been a specific choice that you made to use. TIM: Yeah. There are typically, as we see with anything else, especially being tech or people that like to take things apart, I'm sure as we all did as kids, there are things that you see on the surface. There are things that you see, this pattern or this thing happening here, but you take the face plate off of something, or you delve down below the API, or you delve down below the operating system and there are so many other things that are happening beneath that. If you kick over amount of dirt and you see an ant hill, the ants have their own system, how they do things down there that you don't necessarily create, but you're just going to see it and you have to uncover a few things. You have to move things around. You have to look below the surface to see some of these patterns that happen just below the surface that bring the things at the surface to fruition. REIN: This reminds me a lot of I guess, it's a mantra that I learned from Virginia Satir, which drink if you're playing that game, make hidden things visible, make the covert overt and make the general specific and related to you, me, here, now, and the current situation. TIM: Yeah. I think that's actually a good – I had not heard of that one before, but I do like that a lot. REIN: So when you say uncover, that makes me think, make the covert over. TIM: Yeah, I think so. I like that. It's interesting because people sometimes think that things are covered up to make them hidden and it's not necessarily, they're hidden like someone has hidden them so you can't find them. A lot of times they're hidden in plain view. You don't find them because you're not looking for them and when you actually start to look for some of these things, some of the underlying causes, you'll be surprised what you find. It's like a lot of us here have done RCAs on things and oftentimes, if you do a good RCA, you're going to go through a few levels and different layers to find what the actual root cause. Like, most of the times the root of something is not at the surface, it's way down. So you actually have to go down and dig to uncover these things, to really find out what's at the base of something. REIN: So since this is the show where we talk about the social side of things, I want to ask you about these things that are covered that are maybe covered for a reason and maybe that the reason that they're covert is that people are trying to protect themselves and they don't feel safe to make them overt. So do you think about these situations and how do you go about making that safe to talk about? TIM: So I do think about these situations and there's a couple of reasons why. First, obviously, is in the professional world you can't always call people out immediately for things. Even if you know that there's something that's a lie or something that's not right, there are the political reasons why you have to be tactful or you have to be very deliberate and cautious about how you uncover these things because even if people aren't necessarily intentionally hiding things, or it is their mind that I must hide this as he'll feel safe, people's egos are the number one obstacle, I think to innovation. Someone has staked out a claim. Someone has a territory. Someone has some domain that they have, that they are a gatekeeper thereof and it is their ego that makes sure that you have to pay homage to them or to that ego in order to get anything done. So figuring out what they're protecting, whether they're protecting their job, whether they're protecting their ego, whether they're protecting levels of influence so that they can rise in their career. You have to figure out what that is, that what that thing is that is important to them so that way you can make sure that it's either protected, or you can make sure that there are more than one person that have access to that thing so you can make your way. At personal levels, there are things that people cover up because they don't feel safe and doing the work of trying to make them feel safe so you can talk about these things, I think that's the hardest thing that we do in the industry. Solving technical problems is easy compared to solving people problems, or cultural problems, or societal problems because those are the problems that we've had for millennia that we, collection of people in a common industry, are trying to figure out. Saying to somebody, “Hey, I see these patterns here of work, or absenteeism, or productivity, or whatever it is and I need to know what it is that's going on so that we can fix that,” and make them understand that you are there to help them and there to fix that problem, whatever it may be, that takes some work on the part of the person who's trying to uncover that pattern. It takes vulnerability and it takes confidentiality. It takes empathy. Especially if it's something that you've never dealt with before. Someone's going to tell you, “Hey, I have this problem,” and you're going to say, “All right, well, I know leadership or I know management or unknown this senior technical professional here, but I don't know the answer to this problem, but I can say that I will help you find it and then we can work together on it.” And a lot of people don't like to say, “I don't know the answer.” We see a lot of people that are very technically savvy and because they're very technically savvy, they are now considered to be experts in all kinds of domains. Nobody in particular—Elon Musk—but there are people that are looked to be some kind of great genius just because they happen to know how to code something, or architect something. I think when you display the vulnerability of saying, “I don't know.” Or you are upfront about your problems or upfront about your struggles, it makes people feel safer about being upfront about theirs and then you can go through the work of trying to solve those problems. Well, first of all, identifying if it's a pattern, and then solving the problem that's causing those patterns. JOHN: I like that you use the metaphor of anthill earlier on in this, because rather than when you describe something as pattern, it's very abstract and feels like an object. But when you talk about an anthill, it's individual entities working together in a system. It's something that exists on its own, made up of other individuals. It's not just some object that we can examine and I think that brings it into thinking about it in a different way and much like the way you've been describing how you talk about these things and how you work with people. Very humanizing and I like that. TIM: Yeah. I do think there's a lot of us when we're looking at an organization, whether we're looking at a society, or government, or whatever it is, a neighborhood even all of us have the role that we play whether we're aware of it or not. It's a role not necessarily either we're assigned, that we signed up for, or that we just have by nature of and by coincidence of our birth. But we all do something that contributes in some way to the organizations that we're in. When we look at that as that – okay, that role covers a lot of things. No one is just one thing; no one is just a software developer, or no one is just a cashier at a grocery store, or no one is just an artist. No person is monolithic. No one is defined by their job save except maybe the police and that's not a slam—they're always at work apparently. But there are all these things that we have that yes, as you look at an ant farm, this one ant does all these various things, but they have this contribution to the colony as a whole. And I do think that when we look at it as a pattern, if we look at one individual person and all the things that they do, it is important to see that they are more than just a worker. We are not ants. We're not that specialized. We have all kinds of things that we contribute to. So like the colony metaphor breaks down there just to understand that all of us have different things that we do outside of just what our role is to make money or to contribute. We all have dreams. We all have hopes. A lot of times, the fact that these dreams or hopes have been unrealized or worse yet, they have been forcefully deferred by the society as a whole affects that role that we have. It affects how we view ourselves. It affects how others view us. That's what we bring when we sit down at our desk every morning, that collection of all those things rides along with whatever your skills are, that is it's not compartmentalized. As much as people may want to say they can't compartmentalize these things, you can't. You can’t contain it forever. So when these things start to manifest themselves in different ways, we as people—whether we are neighbors, whether we are leaders in government, whether we are coworkers, whether we're management—need to do whatever we can to make sure that these people can become a whole and they can thrive. When people thrive on a personal level, they thrive on a professional level. Maybe not at the job that they're in, maybe not at the company that they're in, but wherever they end up, when they thrive as people, they are going to thrive as professionals. REIN: I also want to throw in another element of the ant colony metaphor, which is that ant colonies are dynamic. They're constantly changing. Tunnels are caving in, new ones are being constructed; the colony itself changes over time. You were talking about the complexity of a person in a given moment, but their roles within the company are also constantly shifting based on how they interact with other people. TIM: That's true; how they interact with other people and how the companies need change. I mean, no company is typically monolithic in and of themselves. They always have to be growing, they have to be thriving, and they have to be moving into different segments and as that happens, your roles change within that company. What's been being kicked around Twitter these past few weeks is people talking about like, “I don't understand why people leave jobs,” and I was like, “Well, yeah, they leave jobs because they want to go do other stuff.” People don't like to stagnate, typically and people who do like to stagnate, most companies don't want to keep them around. So stagnation is not really in human nature. As resistant as we are to change, we are all extremely adaptable. It's built into our damn DNA so we tend to do that well. I do like the fact tha…

    Full show notes at the publisher

    224: Better Allies with Karen Catlin Mar 03, 2021
    Show notes

    02:31 - Karen’s Superpower: The Ability to Simplify Things Simplifying in a Team Context 05:55 - Better Allies – Everyday Actions to Create Inclusive, Engaging Workplaces; Triaging and Curating Research @BetterAllies Better Allies: Everyday Actions to Create Inclusive, Engaging Workplaces (Book) The Better Allies™ Approach to Hiring (Book) Present! A Techie's Guide to Public Speaking (Book) 14:15 - Maintaining Anonyminity (at first); Prove It Again Bias Channeling White Men; Men Listening to Other Men Whistling Vivaldi: How Stereotypes Affect Us and What We Can Do (Book) [Podcast] 'Whistling Vivaldi' And Beating Stereotypes Reduce the influence of unconscious bias with these re:Work tools Build the Culture Instead of Fit the Culture 26:09 - Culture Add + Values Fit Recognizing Bias Instead of Removing It Meritocracy 32:11 - Network Effect: Venturing Beyond Homogenous Networks Marginalization + Privilege Can Be Self-Reinforcing 50 Potential Privileges in the Workplace 41:58 - Doing This Work is Everyone’s Job 48:12 - People to Follow Minda Harts The Memo: What Women of Color Need to Know to Secure a Seat at the Table Jeannie Gainsburg The Savvy Ally: A Guide for Becoming a Skilled LGBTQ+ Advocate David Smith & Brad Johnston Good Guys: How Men Can Be Better Allies for Women in the Workplace Corey Ponder Learning the ABCs of Allyship 51:13 - The Decline of Gender Parity in the Tech Industry Women in Tech -- The Missing Force: Karen Catlin at TEDxCollegeofWilliam&Mary 58:15 - Making Statements and Changing the Status Quo Reflections: Rein: Getting better at praxis: for every white dude with a beard you follow on Twitter, go follow 10 Black women in tech. Damien: How bias can interfere with an action right before the action happens. Chanté: We’re all allies. We cannot do this work alone. Today you might be the ally, tomorrow you may be the bridge. Arty: Expanding our homogenous networks. Change takes courage on all of our parts. Karen: Turning period statements into questions or adding “until now” to those statements. This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well. Transcript: PRE-ROLL: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started. REIN: Welcome to Episode 224 of Greater Than Code. Take two. So full disclosure, we recorded this or more specifically, didn't record this conversation so we're going to do it again. I'm your co-host, Rein Hendricks, and I'm here with my co-host, Damien Burke. DAMIEN: Thanks, Rein. And I'm here with my co-host, Chanté Thurmond. CHANTÉ: Everyone, Chanté here. And I'm here with Arty Starr. ARTY: Thank you, Chanté. And I'm here with our awesome guest today, Karen Catlin. So after spending 25 years building software products and serving as a vice-president of engineering at Macromedia and Adobe, Karen Catlin witnessed a sharp decline in the number of women working in tech. Frustrated but galvanized, she knew it was time to switch gears. Today, Karen is a leadership coach and a highly acclaimed author and speaker on inclusive workplaces. She is the author of three books: "Better Allies: Everyday Actions to Create Inclusive, Engaging Workplaces," "The Better Allies™ Approach to Hiring,” and "Present! A Techie's Guide to Public Speaking." Welcome, Karen to the show! KAREN: And it is a pleasure to be back with you and to be having this conversation today. Thanks so much for having me. ARTY: And we very much appreciate you being here again with us. So our first question we always ask at the beginning of the show is what is your superpower and how did you acquire it? KAREN: Okay so, my superpower is the ability to simplify things and I joke that I think I acquired this superpower simply as a coping strategy because there's so much information out there. We're all bombarded with things and maybe my brain is just not as big as other people so I constantly am trying to simplify things so that I can understand them, remember them, convey them, and so forth. And I'll share, I think it served me well, not only as I embarked on my computer science programming school and just trying to like grok everything that I was trying to learn as well as then entering the field initially as a software engineer. Again, simplifying things, divide and conquer, break things down into those procedural elements that can be repeated and generalized. Certainly, then as I moved into executive roles as a vice-president of engineering, you're just context switching all day long. Again, I just had to simplify everything that was going on so that could really remember things, take notes on things, and make decisions based on what I thought I needed to do. Yeah. So that's my superpower. ARTY: That's a great superpower. So in the context of the workplace and you've got teams trying to things out, maybe a design problem you're working on, trying to solve. How does simplifying things come into play in a team context like that? KAREN: Well, it comes into play a lot of ways. I'm remembering one example where there was some interpersonal conflict between two people and I was hearing both sides, as one does, and talking to them both. I got them both in a room because they just weren't seeing each other's point of views, I thought, and they were just working at odds to each other. Hearing them both talk, I was able to say, “So at the heart, this is what we're all trying to do. This is what we are trying to achieve together,” and I got them to confirm that. That was the first step in simplifying just the discussion. They were getting a little emotional about things. They were bringing in a lot of details that frankly, weren't necessary to really understand what was going on and I was able to focus them on that shared purpose that we had for the project. It doesn't even matter what it was. Actually, it was so long ago now I can't quite remember what the issue was, but I remember hearing afterwards one of the people say, “You are so good at simplifying things got down to the heart,” and I'm like, “Yes, I am. That's my superpower.” ARTY: It sounds like even more than that, or maybe a slightly different frame of just the example you just gave. It's not only simplifying things, you are distilling the essence of what's important or what someone is trying to say, and getting at what's the underlying message underneath all the things that someone's actually trying to communicate, even if they're struggling too, so that you can help two people may be coming from different directions, be able to understand one another. That's pretty powerful. KAREN: Well, thank you and I love the way you've just framed it, Arty and oh, those are big shoes to fill. Woo! I hope I've been able to do that in a number of different settings as I think back, but that's yeah, it is powerful. I think I probably still have some stuff I can learn there, too. CHANTÉ: Arty, thank you for teeing up this because what I am curious about in relation to what Karen just mentioned as her superpower, which I think is amazing, is obviously, you have authored a number of books. When it comes to allyship, it sounds like this is a great time where we can get somebody to distill and to simplify and not to oversimplify because there's an art to it. But I would love if you could maybe take us down the pathway of how did you arrive at this moment where you are authoring books on allyship and maybe you could give us a little bit of the backstory, first and then we could get into the superpower you've used along the way in your tech journey. KAREN: Okay. CHANTÉ: And how you're coaching people. KAREN: All right. Chanté, thank you. Yes, I'm happy to. So the backstory, first of all, I never set out to become an author, or to become a speaker, or this expert that people tap into about workplace inclusion. That was not my goal. I was doing my job in tech. I was a vice-president of engineering at Adobe. I was leading engineering teams and realizing that there was a decline happening before my eyes in gender diversity. Now I started my career in tech a long time ago and I started at a time when there was sort of a peak period of women studying computer science in the United States. And so, when I started my career, it wasn't 50-50 by any means, but there was plenty of gender diversity in the teams I was working on, in the conference rooms I was in, in the cube lands that I was working in and I saw a decline happening. So while I was still at Adobe, I started our women's employee resource group—goes back gosh, like 14, 15 years now—and I've started mentoring a lot of women at the company and started basically, being a vocal advocate to make sure women were represented in various leadership meetings I was in, on stage, at our internal events and conferences, giving updates at all-hands meetings, like well, thinking about that. I love doing that work so much and loved doing that work less so my VP of engineering work, I must admit. So about 9 years ago now, I decided to do a big change in my career pivot in my own career, I started leadership coaching practice. A leadership coaching practice focused on helping women who are working in tech in any capacity, any role. But women working in this industry, I wanted to help them grow their leadership skills so they could stay in tech if that's where they wanted to be and not drop out because they felt like, “I just can't get ahead,” or “I'm seeing all the white men get ahead,” for example, “before me.” So I started this coaching practice. I soon realized, though that I had a big problem with my coaching practice and the problem wasn't with my clients—they were amazing. The problem, I don't think was me. I think I'm a decent coach, still learning, still getting better, but decent. And realized the problem really that I was facing is that before I could truly help my clients, I needed to make their companies more inclusive. All of them were working at tech companies where the closer you get to the leadership team, to the C-suite, to the CEO, just the mailer and paler it got. With all due respect to anyone who's male and or pale, I'm white myself, anyone who's listening, who's male and/or pale, like that's just what the demographics were and still are in most of our companies. Also, that coupled with this mentality of, “Hey, we are a meritocracy. People get ahead in our company based on their merits, their accomplishments, the impact to the business.” When in reality, that's not what happens because if it were then the demographics across the company would be uniform, regardless of what level you are at. So the white men were getting ahead more than others. So I was like, “I need to make their companies more inclusive. In fact, I need to make all of tech more inclusive to really help my coaching clients,” and yeah, laugh, right? A big job, one person over here. Now, what's the first thing anyone does these days when they want to change the world? You start a Twitter handle. So I started the Twitter handle @betterallies. I started in 2014 with a goal to share simple everyday actions anyone could take to be more inclusive at work. In hindsight, I was leveraging my super power as I started this Twitter handle. I leveraged it because I started looking at the research that social scientists do about diversity in the workplace and not just gender diversity, but diversity of all kinds. The research that shows that they were uncovering, that shows the challenges that people of non-dominant genders, as well as race, ethnicity, sexual orientation, identity, age, abilities, and so forth. What are the challenges these people face in the workplace as they navigate that? Others are doing this great research and I really am—and this builds on what Arty was saying—I used to think I curated this, but really, I was triaging the research. I was triaging it to simplify it, get it to its essence, and figure out with all this great research that gets published, what is someone supposed to do with it? How is the average person who works in tech supposed to take action with this great research that's out there? So I triage and curate and I do it not just based on the research, but also what I'll call cautionary tales that appear in our news, in our Twitter feeds, and so forth. I'll give you two examples to make it real. One is based on research. There's research that shows that men interrupt women more than the other way around and so, based on that research, I go over to Twitter and I type in something like, “I pledge to notice when interruptions happen in the meetings I attend and redirect the conversation back to the person who was interrupted with a simple, ‘I'd like to hear Chanté finish her thought,’” and something like that that's research-driven. Then the more, the cautionary tales that pop up in the research or in the news that we consume, I remember a few years ago when there was so much that was coming out about Uber and its non-inclusive workplace. Just one of the many things we learned about was that the CEO at the time and founder, Travis Kalanick, he was using the nursing mother's room for his personal phone calls. That's not cool because then the nursing moms can't get in there to do what they need to do. So I would go over to Twitter and just a little bit of snark added, I was like, “I pledge not to use the nursing mother's room for my personal phone calls unlike Travis Kalanick at Uber,” [chuckles]. That kind of thing. So I'm just tweeting a couple times a day. I start getting Twitter messages to this anonymous Twitter account—by the way, it was anonymous at the time—and these Twitter requests would be like, “Hey, does anyone at the Better Allies Initiative do any public speaking?” and I'd be like, ‘The initiative? Huh, it's just me tweeting a couple of times a day. Okay.” But I wanted to speak about this topic and I want to retain my anonymity. So I would write back and say, “Yes, one of our contributors does some public speaking. We'll put you in touch with her,” and I go over to my personal Twitter account type something in like, “Hey, I'm Karen Catlin. I contribute to Better Allies. I love public speaking. What do you have in mind?” So I started speaking on this whole approach of everyday simple actions people could take, the Better Allies approach, and every time I gave a talk, someone would ask, “Hey, Karen, do you have a book? Because we want more of this.” For a few years, “I kept saying, no, I don…

    Full show notes at the publisher

    223: Emotions, Achievement, Joy, and Goals with David MacIver Feb 24, 2021
    Show notes

    02:15 - David’s Superpower: Being Confused Norms of Excellence The Inner Game of Tennis: The Classic Guide to the Mental Side of Peak Performance 11:56 - Daily Writing David’s Newsletter: Overthinking Everything Unfuck Your Habitat 15:47 - Learning to Be Better at Emotions 23:22 - Achievement and Joy as Aspirational Goals [Homeostasis vs Homeorhesis](https://wikidiff.com/homeostasis/homeorhesis#:~:text=is%20that%20homeostasis%20is%20(physiology,to%20a%20trajectory%2C%20as%20opposed) Aspiration: The Agency of Becoming by Agnes Callard Seeing like a State: How Certain Schemes to Improve the Human Condition Have Failed by James C. Scott Philosophical Investigations by Ludwig Wittgenstein Reflections: Jessica: Trying not knowing yourself. Rein: You shouldn’t be the owner of all your desires. Instead, you should measure your life by how well you follow the intentions that arise out of your values. Jacob: Thinking of yourself as the sum of all of the habits you maintain or don’t. David: The [Homeostasis vs Homeorhesis](https://wikidiff.com/homeostasis/homeorhesis#:~:text=is%20that%20homeostasis%20is%20(physiology,to%20a%20trajectory%2C%20as%20opposed) distinction, and cleaning a home as an ongoing process. This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well. Transcript: SPONSORED AD: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started. JACOB: Hello and welcome to Greater Than Code, Episode 223. My name is Jacob Stoebel and I'm joined with my co-host, Rein Henrichs. REIN: Thanks, Jacob and I'm here with my friend and also stranger because we haven't done this together in months, Jessica Kerr. JESSICA: Thank you, Rein! And Iím really excited today because our guest is David MacIver. Twitter handle, @DRMacIver. David MacIver is best known as the developer of Hypothesis, the property-based testing library for Python, and is currently doing a Ph.D. based on some of that work. But he also writes extensively about emotions, life, and society and sometimes coaches people on an eclectic mix of software development, intellectual, and emotional skills. As you can probably tell, David hasn't entirely decided what he wants to do when he grows u and that's the best because if you had decided well, then so few possibilities would be open. David, hello! DAVID: Hi, Jessica! Great to be here. JESSICA: All right. I'm going to ask the obligatory question. What is your superpower and how did you acquire it? DAVID: So as you saw me complaining about on Twitter, this question doesn't translate very well outside of the United States. JESSICA: Yeah, which is fascinating for me. DAVID: I'm a bit too British to say nice things about myself without sounding like I'm being self-deprecating. JESSICA: Self-depreciating it is! DAVID: [laughs] So I thought about this one for a while and I decided that the answer is that I'm really good at being confused and in particular, I have a much more productive response to being confused than it seems like most people do because basically, the world is super confusing and I think I never know what's going on, but then I notice that I know what's going on and I look at it and I'm just like, ìHmm, this is weird, right?î And then I read a book about it, or I sort of poke at it a bit and then I'm not less confused, but I'm less confused about that like, one little facet of the world and have found ten new things to be confused about. [laughter] JESSICA: Nice. DAVID: Usually, I can then turn this into being slightly better at the thing I was previously confused about, or writing about it and making everyone else differently confused than they started with. JESSICA: Definitely confused. That is a win. That's called learning. DAVID: Yeah, exactly. [laughter] This is where a lot of the writing you were talking about comes from and essentially, about 2 years ago, I just started turning these skills less on software development and more just going like, ìLife, it doesn't make sense, right?î [laughter] And noticing a whole bunch of things, I needed to work on and then that a lot of these were shared common problems. So I am, if anything, far more confused about all of it than I was 2 years ago, but I'm less confused about the things I was confused about that and seem to be gradually becoming a more functional human being as a result of the process. So yay, confusion. JESSICA: That superpower, the productive response to confusion, ties in with your reaction to the superpower question in general, which is as Americans, we're supposed to be ñ we want to have power. We want to be special. We want to be unique. We want to make our unique contribution to the world! And as part of that, we're not comfortable being confused because we need to know things! We need to be smart! We need to convey strength and competence and be the best! I hate the superlatives. [laughter] I hate the implied competition there, but instead, we could open our hearts to our own confusion and embrace that. Be comfortable being uncomfortable. DAVID: One of the things that often comes up for me is it's a thing that I think is slightly intentioned with this American tendency youíre pointing at, which is that I kind of want to be the best, but I don't really want to be better than other people. I just want to be better than I am now. I wrote a post a while ago about neuromas of excellence like, what would a community look like, which helped everyone be the best version of themselves and one of the top lists was basically that everyone has to be comfortable with not being good at things, but another is just that you have to not want to be better to the other people. You just need want to be better. Again, this is where a lot of the writing comes from. I've just gone, ìWell, this was helpful to me. It's probably helpful to other people.î That's not as sense of wanting to change the world and wanting to put my own stamp on things and it does require a certain amount to self-importance to go, ìYes, my writing is important and other people will like to read it,î but then other people like to read it so, that's fine and if they don't, that's fine, too. JESSICA: Well, you didn't make anyone read it, but you did start a newsletter and let people read it. JACOB: Is this weird thinking reflect a journey that you took in your life? Because I think about my company and my team and how incredibly generous everybody is and even still, I just find it's natural to compare myself to everyone else and needing to not be on the bottom. Part of me wonders if that's just like a natural human tendency, but just because it's natural doesn't make it so. JESSICA: Way natural American. JACOB: Yeah, basically I'm asking how do I stop doing that? [laughter] DAVID: It's definitely not something I've always been perfectly good at. But I think the thing that helped me figure out how to do this was essentially being simultaneously at the bottom of the social rung, but also super arrogant. So it's your classic nerd kit thing, right? It's completely failing at people, but also going, ìBut I'm better than all of you because I'm smart,î and then essentially, gradually having the rough edges filed off the second part and realizing how much I had to learn off the first part. I think sometimes my attitude is due to a lot of this is basically, to imagine I was a time traveler and basically going back in time and telling little David all the things that it was really frustrating that nobody could explain to me and I sadly haven't yet managed to perfect my time machine, but I can still pay it forward. If nobody was able to explain this to me and I'm able to explain it to other people, then surely, the world is a better place with me freely handing out this information. I don't think it's possible, or even entirely desirable to completely eliminate the comparing yourself to others and in fact, I'd go as far as to say, comparing yourself to others is good, but I think theÖ JESSICA: Itís how do we have a productive response to compare ourselves to others? DAVID: Yeah, absolutely. There's a great section in The Inner Game of Tennis, which is a book that I have very mixed feelings about, but it has some great bits where he talks about competition. If you think of a mountain climber, a mountain climber is basically pitting themselves against the mountain, right? They're trying to climb the mountain because it is hard and you could absolutely take a helicopter to the top of the mountain, but that wouldn't be the point. It's you're improving yourself by trying a hard thing. I mean, you're improving yourself in the sense that you're getting better at climbing mountains. You might not be improving yourself in any sort of fully generalizable way. JESSICA: Okay. [laughter] DAVID: When you are playing tennisóbecause this is a book about tennisóyou are engaged in competition with each other and you're each trying to be better than the other. In this context, essentially, what you are doing is you are being the mountain for each other. So you are creating the obstacles that the other people overcome and improve themselves that way and in doing this, you're not just being a dick about it. You're not doing this in order to crush them. You're doing this in order to provide them with the challenge that lets them grow. When you think about it this way, other people being better than you is great because there's this mountain there and you can climb it and by climbing the mountain, you can improve yourself. The thing that stops everyone becoming great is feeling threatened by the being better rather than treating it as an opportunity for learning. JESSICA: Yeah, trying to dynamite the mountain instead of climbing it. Whereas, when you are the mountain for someone else, you can also provide them footholds. Rein, do you have an example of this? REIN: I sure do, Jess. Thanks for asking. So I was just [laughs] thinking while you were talking about this, about the speed running and speed running communities. Because speed running is about testing yourself against a video game, which in this case, serves the purpose of the mountain, but it's also about competing against other speed runners. If it was purely competitive, you wouldn't see the behaviors, the reciprocity in the communities like sharing speed running strats, being really happy when other people break your record. I think it's really interesting that that community is both competitive, but there's also a lot of reciprocity, a lot of sharing. JACOB: And it's like the way the science community should work. It's like, ìOh, you made this new discovery because of this discovery I shared with you and now I'm proud that my discovery is this foundation for all these other little things that now people can be by themselves in 10 seconds instead of 30.î JESSICA: Yeah. Give other people a head start on the confusion you've already had so that they can start resolving new confusions. DAVID: Yeah, absolutely. Definitely one of my hopes with all of this writing is to encourage other people to do it themselves. Earlier this year, I was getting people very into daily writing practices and just trying to get people to write as much as possible. I now think that was slightly a mistake because I think daily writing is a great thing to do for about a month and then it just gets too much. So I will probably see if I can figure out other ways of encouraging people to notice their confusion, as you say, and share what they've learned from edge. But sadly, can't quite get into do it daily. JESSICA: This morningís newsletter you talked about. Okay, okay, I can do daily writing, but now I want to get better at writing. I've got to go do something I'm worse at. DAVID: Yeah, absolutely. I think daily writing is still a really good transitional stage for most people. To give them more context for this newsletter for people listening. Basically, most of my writing to date, I just write in a 1- or 2-hour sitting from start to finish. I don't really edit it. I just click publish and I've gotten very good at writing like that. I think that most people are ñ I mean, sometimes it's a bit obvious that I haven't edited it because they're obvious typos and the like. But by and large, I think it is a reasonably high standard of writing and I'm not embarrassed to be putting it out in that quality, but the fact that I'm not editing is just starting to be sort of the limiter on growth for me. It's never going to really get better than it currently is. It's certainly not going to allow me to tackle larger projects that I can currently tackle without that editing skill. JESSICA: [laughs] I just pictured you trying to sit down and write a book in one session. [laughter] And then you'd be tired. DAVID: Yeah. I've tried to doing that with papers even and it doesn't really work. I mean, I do edit papers, but Iím very visibly really bad at editing papers and it's one of my weaknesses as a academic is that I still haven't really got the hang of paper writing. JESSICA: Do you edit other people's papers? DAVID: I don't edit other people's papers, but I provide feedback on other people's writing and say, ìThis is what worked for me. This is what didn't work for me. Here are some typos you made.î It's not reading as providing good feedback on things, that is the difficult part of editing for me. It is much more ñ honestly, it's an emotional problem more than anything else. It's not really that I'm bad at editing at a technical level. I'm okay at editing at a technical level. I just hate doing it. [laughs] JESSICA: That is most problems we have, right? DAVID: Yeah. JESSICA: In the end, itís an emotional problem. DAVID: Yeah, absolutely. I think that is definitely one of the interesting things I've been figuring out in my last 2 years of working on learning more about emotions and the various skills around them is just going, ìOh, right. It's not this abstract thing where you are learning to be better at emotions and then nothing will change in your life because you're just going to be happier about everything.î I mean, some people do approach it that way, but for me, it's very much been, ìOh, I'm learning to be good at emotions because this really concrete problem that I don't understand, it turns out that that's just feelings.î [laughter] It's like, for ex…

    Full show notes at the publisher

    221: Cultivating Strength and Change with Wesley Faulkner Feb 10, 2021
    Show notes

    01:59 - Wesley’s Superpower: Connecting With People and Being a Social Chameleon

    11:31 - Sharing Responsibility Based on Strengths; Delegating “Weakness”

    • Strengths Finder 2.0
    • Positions vs Roles

    23:52 - Mission Statements Are Bullsh*t (especially for marginalized people/groups)

    • False Value Systems
    • Veni Kunche: Diversify Tech
      • Greater Than Code Episode 212: Diversify Tech with Veni Kunche

    “The real barrier is individuals who don’t want to lose power.”

    32:16 - Talking Truth to Power: Enacting Change

    • Systems Thinking: A Primer
    • Networking
    • Running For City Council / Learning How Politics Work
    • A Promised Land by Barak Obama
    • User Research
    • Accessing People

    “Strong opinions don’t mean right opinions.”

    Reflections:

    Damien: The decommodification of labor and people.

    John: Finding strengths and leaning into them so you can be the most effective.

    Casey: We are stronger together.

    Wesley: Skills are things you aren’t necessarily born with. You can create and cultivate them.

    This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode

    To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.

    Special Guest: Wesley Faulkner.

    Sponsored By:

    • Linode: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started.

    Support Greater Than Code


    220: Safety Science and Failure As An Opportunity For Growth with Josh Thompson Feb 03, 2021
    Show notes

    01:48 - Josh’s Superpower: Teaching nearly anything he knows to almost anyone

    • Fear Remediation

    05:04 - Safety Science and Staying Safe While Rock Climbing

    • 2020 Accidents in North American Climbing
    • Accidents are the result of normal work
    • How Complex Systems Fail

    17:42 - Transfer of Knowledge from Experts to Non-Experts

    23:07 - Root Cause Analysis & Taking Gambles

    33:00 - Failure As An Opportunity For Growth

    • Why Tacit Knowledge is More Important Than Deliberate Practice by Cedric Chin

    50:07 - Psychological Safety

    • William Khan: Psychological Conditions of Personal Engagement and Disengagement at Work

    Reflections:

    Rein: Operators are always gambling and taking risks.

    • Cognition in Practice by Jean Lave
    • The Reflective Practitioner: How Professionals Think in Action

    Mando: How to properly build systems and teams that are friendly to lesser experienced individuals to bring up folx who are earlier in their careers or other industries.

    Josh: Commemorating team learning experiences.

    This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode

    To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.

    Special Guest: Josh Thompson.

    Sponsored By:

    • Linode: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started.

    Support Greater Than Code


    219: How Are You Doing? with Mando Escamilla Jan 27, 2021
    Show notes

    03:19 - Mando’s Superpower: Willingness to Talk About Anything Personal with Others

    08:39 - Dealing with Life in 2020/2021

    • Rationality vs Non-Rationality
    • Feeling Lost and Unmoored

    18:30 - Finding Anchors

    • Narrative and Story
    • Emotion
    • Song
    • Rhyme
    • Repetition
    • Affiliation

    Ted Lasso
    The Ten Thousand Doors of January by Alix E. Harrow

    34:28 - Being Okay Being Less Productive

    Sea Shanty TikTok

    46:47 - Practicing Gratitude For Communities You Do Have; Talking to Kids About Feelings

    • What do you do with the mad that you feel? – Mr. Rogers
    • Sesame Street: Dave Matthews and Grover Sing about Feelings

    “If it’s mentionable, it’s manageable.” – Fred Rogers

    Reflections:

    Rein: The ability for there to be a higher-level cognitive function that happens after emotional and affective responses and that it is capable of mediating between those responses and action.

    Mando: Giving a specific name to how he’s feeling right now: lost.

    Damien: The value of interrogating feelings.

    “Community is not the sum of its members but the product of their relationships.” – Russell Ackoff

    This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode

    To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.

    Sponsored By:

    • Linode: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started.

    Support Greater Than Code


    218: Building Bridges with Isa Herico-Velasco Jan 20, 2021
    Show notes

    02:12 - Isa’s Superpower: Being a Bridge

    • RailsBridge
    • Bridge Foundry – They’re Hiring !!

    08:56 - Community Learning

    • Asynchronous Communication
      • Discord
    • Cultivating a Leadership Pipeline
    • Transparency
    • “Many hands make light work.”

    19:16 - Pivoting From Rock’n’Roll to Software Engineering: Software + Music

    • Gigwell: Talent Booking
    • Everything Relates to Tech Somehow

    27:57 - Grappling with Impostor Syndrome

    Reflections:

    Damien: Community over architecture.

    Casey: Community and mentorship.

    Isa: Talking to other engineers re: non-code + community and sustainability.

    Laurie: Finding new ways to collaborate in a remote/pandemic world.

    This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode

    To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.

    Special Guest: Isa Herico-Velasco .

    Sponsored By:

    • Linode: Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with $100 in free credit for listeners of Greater Than Code. You can find all the details at linode.com/greaterthancode. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/greaterthancode and click on the "Create Free Account" button to get started.

    Support Greater Than Code


    217: Robots As "Social Entities" with Laura Major Jan 13, 2021
    Show notes

    02:05 - Laura’s Superpower: Problem Solving

    04:07 - What to Expect When You’re Expecting Robots

    • Check out our interview with Laura’s coauthor: Greater Than Code Episode 216: Robot and Human Collaboration with Julie Shah
    • Where is human collaboration with robots heading?

    06:59 - The Human/Robot Partnership

    • Robot Personification
    • Positives and Negatives
    • Robots Will Never Be Perfect
    • Making Our World “Robot Compatible”

    14:34 - Human Behavior Towards Robots; Vice-Versa

    • HitchBOT, the hitchhiking robot, gets beheaded in Philadelphia
    • Marty the grocery store robot is a glimpse into our hell-ish future
    • The robot waiters in this Japanese cafe are controlled by people with paralysis

    20:38 - Robots as “Social Entities”

    • Safety Transcending Competition
    • Contextualization
      • Observable
      • Predictable
      • Directable

    24:43 - How Media Affects The Way People View Robots

    • Science-Fiction Expectations

    26:39 - How Humans Can “Update” Themselves: Experiencing Robotics

    • Direct Exposure

    28:23 - Robots as “Social Entities” (Cont’d)

    • Vigilance Decrement
    • Communication Problems
    • Change Agent by Daniel Suarez
    • What Robots/Humans Will/Should? Expect From Eachother

    39:52 - Will and, if so, when will autonomous cars become the standard?

    • Swiss Cheese Model

    Reflections:

    John: What is the right level of empathy for social entities?

    Jamey: Being in the process of consciously creating new social norms and thinking more thoroughly about who you could be hurting with your actions.

    Push, the talking trash can, makes his final appearance after 19 years at Walt Disney World

    Casey: Treating certain social entities in different ways; i.e. a Roomba and a dishwasher. And, the way you have to think about who is outside autonomous cars: not just the passengers. Also, we should be on the lookout for robotaxis!

    Laura: Not wanting robots in the future to look too much like people.

    This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode

    To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.

    Special Guest: Laura Major.

    Support Greater Than Code


    Previous 1 4 5 6 7 8 29 Next

    Related Podcasts

    Know How… (Video)

    1

    Know How… (Video) Education
    JavaScript Jabber

    2

    JavaScript Jabber Education
    Programming Throwdown

    3

    Programming Throwdown Software How-To
    Software Engineering Radio – the podcast for professional software developers

    4

    Software Engineering Radio – the podcast for professional software developers Software How-To
    The Changelog: Software Development, Open Source

    5

    The Changelog: Software Development, Open Source How To
    Coding Blocks

    6

    Coding Blocks Software How-To
    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