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:
    237: Empathy is Critical with Andrea Goulet Jun 02, 2021
    Show notes

    01:13 - Andrea’s Superpower: Distilling Complexity Approaching Copywriting in a Programmatic Way Word-land vs Abstract-land 09:00 - “Technical” vs “Non-Technical” This or That Thinking 16:20 - Empathy is Critical Communication Artifacts Audience/User Impact Programmer Aptitude Test (PAT) 33:00 - Reforming Hiring Practices and Systems Core Values Exercism.io Retrospectives 39:28 - Performance Reviews Continuous Feedback Brave New Work by Aaron Dignan Team of Teams: New Rules of Engagement for a Complex World Continuous Improvement & Marginal Gains “Start where you are. Use what you have. Do what you can.” ~ Arthur Ashe Empathy In TechCorgibytes Reflections: Mando: Empathy is being able to view and identify other perspectives. Jess: Help happens when you have empathy for individuals who aren’t the great majority of people using the software. Casey: The best way to develop empathy for someone else is to get their feedback. Do it during an interview! Andrea: Diving deeper than code is valuable! 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: JESSICA: Good morning and welcome to Greater Than Code, Episode 237. I'm Jessica Kerr and I'm happy to be here today with my friend, Mando Escamilla! MANDO: Hey, Jess. Thanks. I am happy to be here with my friend, Casey Watts. CASEY: Hi, I'm Casey and we're all here with Andrea Goulet. Andrea is a sought-after keynote speaker for conferences around the world, empowering audiences to deepen their technical skills for understanding and communicating with others. She is best known for her work defining Empathy-Driven Development, a framework that helps software engineers anchor their decisions and deliverables on the perspectives of the people who will be impacted by what they create. Andrea is a co-founder of Corgibytes, a software consultancy that helps organizations pay down technical debt and modernize legacy systems. You can recognize her by the JavaScript tattoo on her wrist. Welcome, Andrea. ANDREA: Hi, welcome! Nice to be here. CASEY: We always like to start with a question, which I think you’re prepared for, that is what is your superpower, Andrea, and how did you acquire it? ANDREA: Yeah! First of all, I just love that y'all ask this. I think it's just such a nice way to get to know different people. I was thinking about this because you sent it a little bit ago and I was thinking maybe empathy, given the work I do. But I don't actually think that's it. I feel like I'm constantly trying to learn more about empathy, but I do think that what my superpower is, is distilling complexity. So I went back and looked at what the thread is of all the recommendations I've got on LinkedIn and things like that. It's not something that I would necessarily say that I noticed, but it's something that other people have noticed about me. The idea of taking a really abstract and big, gnarly, complex topic, and being able to distill it down to its essence and then communicate either what the importance is, or what the impact is to other people. I think that's why I've gravitated towards big, gnarly things like legacy code. [chuckles] Because what motivates me is impact and how do we have the work that we do make as big of an impact as possible? So the way I got into software was really a twisty and windy road. I started out as a copywriter and I think that's where the distilling complexity comes down because I would sit with clients and learn all about their businesses. And then I would write typically, a website, or some kind of marketing material and they would say, “You said what was in my head and I couldn't say it.” JESSICA: Wow. ANDREA: And when I got into software, I had a friend of mine from high school, Scott, who's my co-founder at Corgibytes, he came up to me because I had been writing about my writing and he said, “You're not a writer, you're actually a programmer because the way that your brain works, you’re thinking in terms of inputs and manipulating data and outputs, and that's exactly what a programmer does.” So then, he wanted to fix legacy code for a living. I didn't even know what that was at that point, thought it was a good thing and I found that my ability to both walk in and understand not just the syntax of what's going on, but the business challenges and how everything links together. With that, you can create a sense of cohesion on a team and getting different people to work together and different people to see each other's points of view, because when you're able to distill a perspective over here and say, “Okay, well, this is what this person's trying to say,” and still, this over here. “Okay, I think this is what this person's trying to say.” I feel like a lot of times I am kind of like a translator, but it's taken me a long time. I've been in software 12 years now and I still have massive imposter syndrome like, I don't belong because I'm not the fastest person on the keyboard. I really struggle with working memory. My visualization is really a struggle, but I do really great in an ensemble. When I started ensemble programming—sometimes it's referred to as mob programming—I was like, “I can do this. Oh my gosh, this makes sense and I belong.” I think just over the years, little things like hearing the joke – I was at a conference, Jess, I think this may have been ETE when you and I connected, but I heard a joke and it was, I think Phil Carlton had first said it and it was like, “There's only two hard problems in computer science, cache invalidation and naming things,” and then somebody else said, “Off-by-1 errors.” I remember I was like, “Y'all think naming things is hard?” Like, help me understand how that's hard because that’s – JESSICA: [inaudible]? Oh my gosh, that's hard. ANDREA: Yeah, and to me, it just comes so naturally. I think that's kind of the thing is figuring out where is your trait, where's your skillset. I remember when I first started doing open source contributions, I haven't done those in a long time, but just going in and modifying the language on help messages and turning them from passive to active voice. They got accepted, it was on some high-profile projects, and it was like, I didn't really feel like I was even doing much and I still feel like, “Is that even a big deal?” But I think that's kind of the definition of a superpower a little bit is that – JESSICA: Yeah, it’s easy for you. [laughs] ANDREA: You don't recognize that it's hard for other people. Yeah, and so it's neat now that it's like I'm starting to come into my own and leaning into that, and then helping other people see that the way that I approach naming things, the way I approach copywriting is actually in a very programmatic way. It's leaning on frameworks. It's leaning on patterns that I use over time. I know, Casey, you and I have talked last week about like when I first go to a conference like using open-ended questions versus closed-ended questions and these little kind of communication hacks that I've developed over the years. So now putting those together in a framework to help other people remember that when we're coding, we're not coding for a computer, we're coding through a computer for other people. The computer is just like a code is just a tool. It's a powerful tool. But a lot of times – CASEY: I have a question for you, Andrea. ANDREA: Yeah. CASEY: About that, I find myself switching gears between word land and abstract land. So if I'm coding and I'm not thinking of words, the naming is hard, but sometimes I can switch gears in a different head space. It's like a different me and then I'm naming things really well. Especially if I'm looking at someone else's code, I don't have to be an abstract land; they did that part already. Do you find yourself switching between the two? ANDREA: Oh, all the time. Yeah, and especially, too, when you're writing prose. There's two different kind of aspects of your brain. There's the creative conceptual side and then there's the analytical rational side and everybody has both. So it does require you to come out of the abstract side in that and then move into more of the analytical space, which is why I love pairing. I love coding as a group because then that way, it's like the mental model is shared and so, I can stay in my world of naming things really well, or I don't know that we need to be that precise if we try to – like, when I was in one group and they were trying to have a timing thing and it was like down to the millisecond and I was like, “Y'all, we don't need to be that precise. We just need to have this check once every 10 minutes,” and that saved like 6 hours of work. Just being able to say that thing and be the checkpoint. JESSICA: Yeah. Someone has to be super down in the details of what to type next and it helps to have someone else thinking about it at the broader perspective of why are we doing this? ANDREA: Yeah, and that's me, typically and I love that role, but it's very different than I think what goes through people's minds when they envision a software developer. JESSICA: Yeah, maybe they envisioned the things that software developers do that other people don't. Typing curly braces. ANDREA: Yeah. MANDO: I still think of that when I'm doing it. When I think of myself as a software developer, I think of myself as the person who hasn't gotten up from their desk in 5 hours and just hunched over, just blazing fast hacking on something that probably is kind of dumb. [laughter] But when I don't spend my day like that, I don't really feel exactly like I've been doing my job and it's something that I struggle with because I know that's not the job in its totality by any means and it doesn't mean that I'm not getting good work done. JESSICA: Not even close to most of the job. MANDO: Not even close to most of the job, you're exactly right. JESSICA: Like you said, if you're sitting there for 5 hours by yourself, hunched over your computer, you're probably hacking on something dumb. MANDO: Right. [laughter] JESSICA: We had gotten off on a tangent somewhere without someone to be like, “Why are we doing this again?” MANDO: Exactly, exactly. Yeah. ANDREA: Well, and I think that that has been a personal challenge of mine as well. I know there was a really flashbulb moment for me. Scott and I have been running our business together for a couple of years. We had gotten on our first podcast and he was telling our origin story and he used the phrase, “Andrea, she's the non-technical founder.” When I heard it, I was like, “How dare you? I have for 2 years been sitting right next to you,” and then he said, “Well, that's the term you use to describe yourself all the time. We had been in a sales meeting right before I recorded that podcast and that's literally the words you use to introduce yourself. So once you start calling yourself technical, I'll follow suit.” JESSICA: Wow. ANDREA: It really made me think and I think some of it is because whenever I go to conferences, I don't look like other people who code especially 12 years ago. I don't talk like the people who are typically stereotypical developers and the first question I would get asked, probably 25 to 40% of the time from people I met were, “Hi! Are you technical, or non-technical?” JESSICA: Really? ANDREA: Yeah. MANDO: Ugh. JESSICA: Huh. ANDREA: And that would be the first thing out of the gate. At the time, I didn't have the kind of mental awareness to go, “I'm at a technical conference. I think you can assume I'm technical.” The fact is I was scared to call myself technical and over the years, I'm just like, “What does that mean to be technical and why do we define people by you are either technical, or you have nothing?” Non-technical, you have zero technical skills, you don't belong. JESSICA: So after you had that conversation with Scott, did you switch to calling yourself technical? Did you change your language? ANDREA: It has been a journey. I became very conscious of not using non-technical. I'll sometimes then say like, “I struggle with syntax and I'm really, really good at these things.” When I phrase things that way, or “I have engineers who are so much better and have much deeper expertise in Docker and Kubernetes than I do. I'm really good at explaining the big picture and why this happens.” So it becomes, I think what we do in software is that because we're so used to thinking in binaries, because that's the way we need to make our code work—true/false, if/else, yes/no—and that pattern naturally extends itself into human relationships, too. Because I know that every single person who asked me that question in no way was trying to be rude, or shut me out. I know that the intention behind it was kind and trying to be inclusive. But from my perspective, when half the people walk up to you and go, “Do you belong here?” Then it's like, “I don't know. Do I belong here?” JESSICA: Yeah. ANDREA: So that's an example of how, if you're at a conference saying, “What brings you here?” That's very open-ended and then it gives everybody the chance to say what brings them here and there's no predefined, “Do you fit in this bucket, or that bucket? Are you part of us, or are you part of them?” JESSICA: It's open to surprise. ANDREA: Mm hm and I think that's something that I am really good at. That's my superpower is let's see the complexity and then let's see the patterns and let's figure out how we can all get good work done together. But you can't see the complexity unless you take a step back. JESSICA: Yeah, and yet Scott noticed that when you are thinking that way, you are thinking like a programmer. Because while software starts by getting us used to thinking in binaries—I should say programming. ANDREA: Yeah. JESSICA: It’s just thinking of binaries, as soon as you get up to software and software systems, you have to think in complexity. ANDREA: Yeah. MANDO: And like you were saying, Andrea, I find myself nowadays better recognizing when I'm falling into that trap when I'm not talking about work stuff. When I find myself saying, “Well, it's this, or it's this.” It's like, “Is it really this, or this?” JESSICA: Are these the only options? ANDREA: Yeah. MANDO: Yeah. Do I have to eat Thai food, or pizza tonight, or could I just eat ice cream, or a salad, or…? [laughs] ANDREA: Yeah. MANDO: You know what I mean? It's a silly example, but I don't know, there's something about doing this for a while that I find that kind of this, or that thinking wiring itself into my brain. JESSICA: Yeah. ANDREA: Yeah. Well, and I think that that's normal and that's human. We operate on heuristics. There's the whole neurons that fire together wire together and if you're spending the majority of your time in this thought pattern, adopting something else can be a challenge. So to me, it's like trying to describe how the way I navigate the world in being able to name things well and being able to talk to new people, connect dots, see patterns that I rely on frameworks just as much as I do when I code and trying to figur…

    Full show notes at the publisher

    236: Connecting Arts and Technology – The Power of Print with Marlena Compton May 26, 2021
    Show notes

    01:07 - Marlena’s Superpower: Bringing the Arts to Tech Coming Into Tech as a Creative 04:42 - Parallels Between Art and Computer Science/Software Engineering System Architecture Spatial Thinking & Representation Mind in Motion: How Action Shapes Thought by Barbara Tversky Metaphors We Live By by George Lakoff & Mark Johnson 09:33 - Sketchnoting and Zines The Sketchnote Handbook: The Illustrated Guide to Visual Note Taking by Mike Rohde 14:19 - DIY Publishing and Physicality – The Power of Print The Pamphlet Wars 20:33 - Zines at Work & Zines in Professional Settings Slowing Down Our Thought Processes Using Diagrams to Ask Questions & For Exploration Graphic Facilitators 31:11 - Target Audiences, Codeswitching, & People Are Not Robots 37:58 - How We View, Study, and Treat Liberal Arts – (Not Well!) Formulating Thoughts In A Way That’s Available For Consumption 43:01 - Using Diagrams and Images UML (Unified Modeling Language) Collaborative Whiteboarding Software and Shared Visual Language (Drawing Together) 50:41 - Handwriting Advice: Decolonize Your Mind! SLOW DOWN Write Larger Practice How to Do Nothing: Resisting the Attention Economy by Jenny Odell 59:45 - The “Let’s Sketch Tech!” Conference Patreon Podcast Newsletter Reflections: Damien: Decolonize your mind. Jamey: Zine fairs at work and valuing yourself by taking up space. Rein: Creativity is good for individuals to explore, but when we share it with people it’s a way we can become closer. Marlena: Connecting arts and technology. 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: JAMEY: Hello, everyone and welcome to Episode 236 of Greater Than Code. I’m one of your hosts, Jamey Hampton, and I’m here with my friend, Rein Henrichs. REIN: Thanks, Jamey. And I’m another one of your hosts and I’m here with my friend, Damien Burke DAMIEN: Thanks, Rein. And I'm here in addition to with the host, our guest today, Marlena Compton. Marlena Compton is a tech community organizer, designer, and collaboration artist who has worked in the tech industry for 18 years. She grows tech communities and organizes conferences such as “Pear Conf” and “Let’s Sketch Tech!” Marlena has worked for companies like IBM and Atlassian. This has left her with a life-long appreciation for quality code, empathy, and working together as a team. When she isn’t working, Marlena enjoys lettering, calligraphy, and walking her dog. Welcome to the show, Marlena. MARLENA: Hi, thank you so much. DAMIEN: So I know you're prepared for this. Same thing we do for all of our guests, we're going to start with the first question. What is your superpower and how did you acquire it? MARLENA: Yeah, so my superpower is bringing the arts to tech and that is teaching people the value of creative arts—such as writing, sketching, music, and more—and how this relates to the tech industry, helping creative types feel more at home in tech, and helping folks who are mostly in the science track in school learn why they need the creative arts for critical thinking and thinking through problems. So it's like, you have to give people a space to do this learning from a peer perspective versus top-down perspective. This includes building community for folks to explore these things. JAMEY: So you came to tech from art previously, is that right? MARLENA: I have a wild academic background of interdisciplinary studies, which will not get you a job for anything but like, renting a car. [laughter] Or whatever and also, later I did computer science, but while I was getting my liberal arts degree, I did a lot of art history, a lot of painting, and a lot of theater. JAMEY: I wonder if you could speak to coming into the tech industry as someone who is already an artist and considers themselves an artist, like, how that translated for you. Like, what skills from being an artist, do you think were helpful to you as you were starting in tech? MARLENA: Sure. So I think that if you know that you're an artistic type, like I knew how important arts were for me. But I think for children often they get a lot of pressure to find something that will get them a job and it's not like this isn't for good reason, it's like we’ve got to be able to pay our bills. On the other hand, when you're a creative type, it's such a core part of your personality. You can't really separate it from anything and if you try to just tamp it down, it's going to come out somehow. So I was this college graduate and I was having a really hard time getting a job and figuring out what I wanted to do that would make enough money to support me. Computer science was literally the last thing I tried and I seem to do okay at it so I kept doing it. [laughs] And that's how I got into it. I wish that we had bootcamps when I started learning computer science, but there weren't any and so, all I could do was go back to community college. So I went to community college. I had to take every single math class over again. Calculus, I had to take three times, but I stuck with it. I didn't know if I could do it, but I kept taking the classes and eventually, it worked. So [laughs] that's how I got into the tech industry and it's like, it's totally okay to do this just to make money. That's why I did it. DAMIEN: So then coming in with this art background, which seems really broad and you didn't talk about anything specific, what insights and connections were you able to make between art and computer science, and art and software engineering? MARLENA: Sure. So for me, building software is a creative process. In fact, this is something I've believed for a very long time, because as soon as I got out with my newly-minted CS degree and I knew that I needed to create, draw, write, and do all of those things. Eventually, I started looking around for okay, what in computer science is kind of more visual place and it used to be people would think of diagramming software, HoloVizio, Rational Rose, which is that is quite a throwback. Who here –? DAMIEN: UML. MARLENA: [laughs] That UML, yes! I would look at these things, like system architect, where it's like the idea was that you could literally draw out pieces and then it would make your code, which was [laughs] I think an epic fail if you look at it from, did it actually ever write successful code? I have never – REIN: There's another option, which was the expense of architects draw the boxes and then the chief engineer put the code in the boxes. MARLENA: Well, but see, you need a brain in there and this is all about the brain. [laughter] MARLENA: Yeah. I think one transformation that my thinking had to go through so, I had to go from this computer science perspective of find a way to chop up all your thoughts into little, discreet, logical pieces so that you can make classes, objects, and things like that and instead look at the brain as an organ in your body. We take more of a holistic perspective where it is your brain is connected to your thoughts is connected to like your internal axes, GPS system, and mapping system and how all of that comes together to problem solve. REIN: Yeah. I love it. Without bodies, we couldn't think about things MARLENA: Indeed. This past year, I've spent a lot of time specifically investigating this connection. One of the things I did was read Barbara Tversky's book, Mind in Motion, and the premise of her book is that spatial thinking is the foundation of abstract thought. That is how you orient yourself in the world and how you perceive a space around you and yourself in that space is what allows you to organize ideas, take perspectives that are based in imagination, and things like that. REIN: Yeah, and this ties into Wyckoff's work on basic metaphors because basic metaphors are how we structure our thought, but they're all about the world. So thinking about the metaphor of containment, you have a thing, it has an inside and an outside, there may be a portal that gets you from the inside to the outside. So this is how houses work, right? This is how we think about houses. This is also how we think about relationships. It's how we think about code. And then there's you combine that basic metaphor with the metaphor of traveling; starting at a place, traveling along a path, ending up at another place. You put those two metaphors together, you can have complex thoughts about achieving goals. But these are all metaphors based on, like you're saying, our perception of living in a world that has 3D space. Yes, and maps are such a big part of that. So when I was reading through this particular book, she goes into things like maps, how we map ideas, and things like that and there is quite a bit of science behind it. And even for metaphor, she writes that metaphor is what happens when our thoughts overflow our brains and we need to put them out into the world. DAMIEN: So putting these thoughts, these ideas back out into the world and into some sort of spatial representation, is that how you view the tech notetaking, or diagramming sort of thing? MARLENA: Absolutely. So I guess, for listeners, I want to back up a little bit because I think something that Damien knows about me and also Jamey and Rein from looking at the biography is that I'm very into sketch notes. Just to bring us out of the depth [laughs] a little bit, I can tell you about why I turned to sketchnoting and why I started doing it. It was because I was trying to learn JavaScript and yes, Damien, I know how you feel about JavaScript, some of us like it. [laughs] DAMIEN: I don't want to show my cards too much here, but I will say the fact that you had difficulty with it is telling. MARLENA: Well, but I also had difficulty learning C, Java, Erlang. DAMIEN: So how did [inaudible]? MARLENA: Well, so I went to CascadiaJS and this was my first – well, it wasn't my first, but it was the language conference and I was just learning JavaScript and I didn't understand half of it. It just went over my head. So to try and create some memory of that, or try to figure it out, I started drawing. I had seen sketch notes on the web. They were experiencing a bump in popularity at the time. I think my Mike Rohde’s book had just come out and it helped. That was what introduced me to this whole world and eventually, we're talking about when thoughts overflow and you turn to metaphor, this is exactly what was happening for me was Barbara Tyversky refers to these pictures we draw as glyphs. They can be more complicated than language and that is why when we're really trying to figure something out, we're not going to be writing an essay, maybe sometimes, but for the most part, we'll start diagramming. JAMEY: I also wanted to talk about zines while you were on. I was thinking about zines when you were talking about this because I feel like there's a few different mediums of art that I do and some of them are more intentional than others. To me, zines are about like, “I'm thinking this and it needs to exist in physical space and then it will be done and I can stop thinking about it,” because it exists. MARLENA: I love that so much and it's exactly what zines are there for. So zines are DIY publishing and zines are the publishing that happens for topics that, I think it happens a lot for people who are underrepresented in some way. Because you're not going to have access to a publisher and it's going to be harder for you to get any official book out. But then sometimes it's also just, maybe you don't want that. Maybe you want your zine to be a more informal publication. I love zines how kind of – they are all so super niche like, you can put anything. Define the word zine, ha! [laughs] JAMEY: It's so hard. People will argue about this in the zine community for like days and days. Hard to define the word. MARLENA: And that's actually part of the power of zines because it means it can be whatever you want, which means whatever you want to create is okay. I think that's really what we're trying to get down into here is having different ways of expressing and problem solving be okay and accepted. REIN: Just something to point out that containment is a metaphor we use for categories. So we're talking about what is inside the zine category? DAMIEN: I want to go back to the well, Marlena, you said zines were do-it-yourself publishing, DIY publishing, but blogs are also do-it-yourself publishing. So zines have a physicality to them and feels like that's an important aspect. Can you talk about that, or why that is? MARLENA: Well, there are also digital zines, so yeah. [laughs] But. DAMIEN: Maybe five containerization and categories. MARLENA: [laughs] Well, if we wanted to talk a little bit about physical zines, that even is interesting and Jamey, maybe you have a few thoughts about this that you can share, too because there are just so many different ways to format a zine. JAMEY: Well, I know that digital zines are a thing and I've read some digital zines that I've very much enjoyed. To me, the physicality of zines is a big part of them and a lot of what's appealing about them for me. I think that part of the reason for that is that, as you were getting at, people can write whatever they want, people who might not have a chance to write in other formats and most importantly about that, you can't censor a zine. It's impossible because someone makes it themselves and then they give it to whoever they want to have. It's a very personal experience and there's no middleman who can like tell you what you can, or can't say. So I think that having that physical piece of paper that you then hand directly to someone is what makes that possible and not putting it on the internet is also what makes that possible. Like, you have this thing, nobody can edit what's in it. It's all up to you. Nobody can search for it on a search engine. If you don't want someone to see it, then you don't give them one and it's just a holdover from what a lot of media was more like before the internet and I appreciate that about them. [chuckles] DAMIEN: Yeah. To me, it sounds so much like the Federalist Papers, like Thomas Paine's Common Sense. JAMEY: Oh, those were zines for sure. DAMIEN: I wrote this thing, [inaudible] about, I'm hazing him out of here, read this. [chuckles] Those are zines, okay. JAMEY: And political zines are a huge subsection of pamphlets and all sorts of political ideology. REIN: And that's where printing started was with the publishing of zines, that's my argument. MARLENA: This is the power of print. It's the power of print and that power, it's something that you don't necessarily get with the internet. Zines are an archive as well and I don't think we can just say – So when I did the first Let’s Sketch Tech! conference, I had an editor from Chronicle Books come and she talked about publishing. When I was talking to her about doing this talk, what I thought was most interesting about our conversation was she said, “Books aren't going away. Books are never going away because we are so connected to our hands and our eyes.” Books are always going to be there. Printed, words printed, pamphlets, zines, I think they're going to outlast computers. [chuckles] Think about how long a CD, or magnetic tape is going to last for versus the oldest book in the world. DAMIEN: Yeah. REI…

    Full show notes at the publisher

    235: RailsConf Scholars: 2021 Remote Edition May 19, 2021
    Show notes

    The RailsConf Scholarship Program 03:12 - Tram’s Superpower: Getting 8 Hours of Sleep Per Night! 04:08 - Leah’s Superpower: Being a Companion to Long-Distance Runners 04:55 - Stefanni’s Superpower: Doing Things She’s Terrified of Doing 05:34 - Being Afraid and Grappling with Self-Doubt Asking Questions and Being Vulnerable Call-Out Bad Behavior 12:34 - Team Psychological Safety 17:20 - Education & Learning Environments; Tech Journeys Ada Developers Academy The Turing School 27:52 - Making & Noticing Progress; Comparing Yourself to Others The Confidence Code: The Science and Art of Self-Assurance---What Women Should Know Reflections: John: Finding new ways to be of service to other people. Leah: What can we proactively do to make our space safer and more conducive to diverse thought? Mando: It’s okay to make mistakes and not be perfect. Steffani: How common it is to openly talk about these things in the Rails Community ❤️ Tram: Representation matters! Humanization and inclusivity. Calling people out. Lending Privilege -- Anjuan Simmons Transcript: JOHN: Hello and welcome to Greater Than Code, Episode 235. I’m John Sawers and I’m here with Mando Escamilla. MANDO: Thanks, John. And I'm here with three RailsConf scholars who are going to be joining us today, which I'll like to take turns introducing yourself, maybe starting with Leah? LEAH: My name is Leah Miller and I’m a Platform Engineer at Highwing, which is an insurtech startup based out of Denver. Before making over the switch to tech, I spent almost a decade in the insurance industry primarily working as a production underwriter. In my spare time, I enjoy running and craft beer and frequently, the careful combination of the two. I’m also a new dog mom to a rescue pup named Orla. MANDO: Great. Tram, you want to go next, please? TRAM: Yeah. So hi, everyone. I'm Tram Bui. I’m currently attending Ada Developers Academy, which is a tuition-free coding program for women and gender-diverse folks in Seattle. The program includes an internship match with a Seattle tech company. So currently, for my internship, I work as a Developer Relations engineer and what this means is that I try to make it easier for Rails developers to deploy their apps to the cloud. Outside of coding, I try to maintain it and improve my high school tennis skills. I also like to read books and also, thinking about my next great public transportation adventure and volunteering for local nonprofits. And then Stephanie, I can pass it on to you. STEPHANIE: Hi, I'm happy to be here. I'm Stephanie and I've been working with Rails for the past 4 years, but now I'm trying to transition from dev full-time to having my own projects. And besides software, I also like to talk about plant-based diet, financial independence, and mental health. Also, if you have noticed my accent, I'm from Brazil, but I live in Vancouver, BC and yeah, I'm really happy to be here. JOHN: Awesome. Welcome to the show, everyone. So this is just a little setup here. Not every year at RailsConf, but most years at RailsConf, we do have a special episode where sometimes, we've got many of the panelists are together and so, we can record in the same room, which is obviously very novel for us. This year of course, it's all online. One of the things we’ve also done is bringing in some of the people who are part of the RailsConf Scholar Program, which is the program to expand access to tech conferences to people that are underrepresented and to give them some guidance on how to make the most of their experience at the conference. We always think it's great to get the opinions of people that are brand new to this industry and see what their perspective is on everything. So we're going to start off with our usual question which is what is your superpower and how did you acquire it? We can go really in any order. Who would like to go first? TRAM: I can go first. So my superpower would be the ability to get 8 hours of sleep a night [chuckles] and I think I acquired this power – I think I was very just like, I loved nap time as a kid and I grew up knowing the importance of a good night's rest. I think for me to be my best self, that’s one of the big things that I need to have. I think growing up and going to college, it was very like, “Oh, sleep is not important,” but I always had noticed the importance of sleep and I think it does hustle economy, too. People are very fast to just cast aside and was like, “You can sleep when you're dead,” but I'm like, “No, if you don't sleep, you will die faster.” So I'm going to take every opportunity that I can do at least get a full night's rest. LEAH: I am so jealous of that superpower. [laughs] I think mine feeds into a little bit of the opposite of that, but my superpower is the ability to keep people company when they're running through the night during a 100-mile races, or ultra-marathons. So people running it 3:00 AM, 4:00 AM, getting really down, needing someone to lift them up, I can run alongside them and sing, or just be a companion to keep them motivated. I think I acquired this skill from being a middle child. I spent a lot of time just entertaining myself and being pretty independent and if you can entertain yourself, it's pretty easy to extrapolate that to others, keep people going, so. [chuckles] STEPHANIE: I would say that my superpower currently is a work in progress actually, but it's doing things even if I'm terrified of the way I always struggled a little bit with self-confidence. How I acquired that, I actually had to go to therapy first to build the foundation, but now I think I've been getting pretty good at it and the feeling of doing the things that you're scared at the end is a really good feeling. You feel like a superwoman. [chuckles] JOHN: Oh, those are all such great answers. I want to dive into each of them, I think oh, my thoughts are jumbling up because I want to ask questions to all of you. Well, I think I'll start with Stephanie. That's an amazing superpower and it's definitely going to serve you well. It's something that I've had to learn as I develop my speaking career at the same time. Even just thinking that it was possible for me to get up on stage and do that, that took a while to get there and then actually doing it also took a lot of practice. So certainly, that's going to be awesome. MANDO: Yeah. It's so easy to just keep doing the things that you're good at and try to ignore, or maybe push off the things that you're not so good at, or you don't have that confidence in, Stephanie, like you were saying. It's funny, I keep relearning this lesson over and over again, there's this project at work that I've been putting off and pushing the JIRA ticket over just because I kept telling myself that it wasn't important and that I could do – other things were higher priority. It's just because I was kind of scared, but I wasn't going to be able to do it as well as I could do the other things. I just had to sit down and do it and then I pushed up the PR and it got ripped to shreds by the other wonderful, [laughs] amazing engineers that I work with. But it's good. I didn't die. [laughs] So it’s funny how we have to keep learning these lessons over and over again sometimes, I think. JOHN: Yeah, that reminds me that there's a related skill in there also, which is realizing when you were afraid of something. Sometimes you think, “Oh, it's just not important that happened right now.” MANDO: Yeah. JOHN: As an excuse, but once you realize, “Oh, I'm actually afraid of how this is going to go.” It allows you to approach it differently. You can be like, “Oh, okay, well that's what this is. All right, then now I know how to like face it, head on rather than pretending it's some other reasons.” So I think that that's really important as well. MANDO: Absolutely. Yeah, and it took me a couple of days to [laughs] realize that that's what I was doing and it wasn't until that was the last thing I had to work on for the sprint after I had reshuffled and moved everything over and then looked at my other teammates, JIRA boards to see if they had any stuff that I could help out with [laughs] that finally I was like, “Well, okay, I guess I'll just do this one.” TRAM: Yeah. I think sometimes for me, the anticipation, or the thought of it is even scarier than actually doing the task itself. I've had this happen to me so many different times. For instance, with the podcast, I'm like, “Yeah, this is something that I want to do because I like listening to podcasts,” but I was like, the nervousness and the scariness of putting myself out there and just thinking about it leading up to this moment, it's so much scarier than actually being in the moment and talking with y'all. So yeah. LEAH: I think part of it, too is recognizing that your feelings are not existing in a vacuum. There's other people that experience the same insecurities, or just going through what you're going through. We were interviewing someone a couple weeks ago at my company and just talking about the stressors of being from a bootcamp and being hired into an engineering organization as either a junior developer, or a mid-level developer, or whatever level, but just knowing that your background isn't a CS degree, or it's just a little bit different than what other people have. And then having that insecurity of I'm pushing up a PR and then are 20 people going to make comments on this and then that gets pushed to Slack and everyone sees all 20 comments. Am I going to be laughed at, or looked at as less than? So it's just nice to express that to someone else and have them regurgitate the same feelings, or just reflect back to you that you're not the only one who's having self-doubt in that way. MANDO: Yeah, and it's tough for me at least to remember sometimes that I come from a very different place privilege wise than other folks on the team. So it can be a lot easier for me to do stuff like, just push this PR up and ask for comments because my experience may be very different than someone who doesn't have my same background, or the amount of experience that I have, or the kinds of relationships that I may have with other folks on the team. I strive to help create spaces whether at work, or wherever where people can feel comfortable asking questions and not worrying about people coming in and being overly critical, or negative, or whatever. But my lived experience is very different than others. That's something that I need to keep in mind that you can't always just assume good faith that everyone's going to treat you the way that you would maybe treat them and I have to actively work and actively communicate to people that this is that kind of place. JOHN: Do you find that there are specific things that you do to communicate that, or at least to make that ambiently knowledgeable to the other people in the team? MANDO: That's a good question. I think the easiest thing you can do is make sure that you're modeling both sides of that behavior like, asking a lot of questions, putting yourself in vulnerable situations, and then also, making sure that you always jump in and respond positively when others do that so that you can help set a baseline. I think of what the behavior should be and what behavior is expected, and then the second thing is always making sure to call out behavior that doesn't hit the bar. I can't remember where I first heard this, but my buddy, Jerry, he's the one who always drops the phrase to remind me, he says, “It's as simple as saying, ‘We don't do that here.’” It doesn't have to be a big deal. It doesn't have to be a huge problem, or anything. Just when there's behavior that you don't do here, you say, “We don't do that – [laughs] we don't do that here.” It's as simple as that. LEAH: I love that. MANDO: Yeah, Jerry's awesome. JOHN: I think this is a really interesting topic because I'm always looking for examples of ways to make that easily communicated in a team environment. So have any of you had experiences where maybe someone else on the team was able to communicate some thoughts of psychological safety, or things that made you more comfortable being who you were on the team? LEAH: So I can speak to the team where I work. We're a startup. We have about 15, I think maybe officially 16 people now and we have, I think just hired our fifth female to join the team, or a fifth non-male to join the team. We have created just a private channel for all non-males on the team in Slack where we can communicate with each other and we've set up a happy hour once a month where we can meet. You don't have to drink alcohol. You can just sit and chat and we just have an hour set aside where no conversation topic is off limits. It's just really helpful to just set aside that time where there's no outside influence and it's just the five, or six of us, or however many there are right now [chuckles] who can join and just chat through what's a win for the week, or what's a struggle for the week. I think part of it is giving each other the space to express what's going well and also, express what's going wrong, and then see if others of us on the team can be a champion for the other person and just offer support where possible, or step in when something's happening that we need to maybe put a stop to. Our private channel is lovingly called The Thundercats, [laughs] which I'm pretty fond of. MANDO: [laughs] That's fantastic. You make it almost sound like a union kind of [laughs] where y'all can have this place where you have this ability to do collective action, if necessary. I think that's just fantastic. That's amazing. LEAH: And I should say that the men on our team are fantastic. So this is not like a – [laughs] [overtalk] MANDO: Of course, yeah. LEAH: Escape hatch like, we're all upset about stuff, but it's just nice. Regardless of how wonderful the men on the team are, it's nice to have a space for not men. [chuckles] STEPHANIE: Yeah. I think that for me, from my experience, the one that I was more comfortable with was at my first Rails job. It was still in Brazil and the team was totally remote and they did lots of peer programming. They did a great job in onboarding people, but peer programming was way more than onboarding. It was a common practice and I was just like, “Wow, this is so cool.” You could learn so much more beyond just a code and besides that, I felt really comfortable in seeing that no one was scared of doing anything wrong like, there was a really good communication. So I think that the main thing that needs to be worked at, when you're working in a team, is to make sure that everyone feels safe to do their stuff and they don't feel like, “Oh, I'm going to be judged,” or “I don't want to try this because I don't want to have to handle with anything from management,” or whatever. So maybe having that feeling, “Oh, we make mistakes here. We are humans, but we try to make the best to learn from them.” That's a good way to improve this team behavior, I guess. [chuckles] JOHN: So you were able to see the other people on the team, that you were paired with, making mistakes and being okay with it and just that became obvious to you that that was the thing that happened all the time and it was fine. Right? STEPHANIE: Yeah, and especially because I was also self-taught. I actually went for computer science for one year, but I dropped out. I always had…

    Full show notes at the publisher

    234: Civil Society and Community Relationships with Michael Garfield May 12, 2021
    Show notes

    02:13 - Michael’s Superpower: Being Able to Creatively Digest and Reconstruct Categories Integral Theory Creative Deconstruction – Michael Schwartz Creating Truly Novel Categories – Recognizing Novelty as Novelty 09:39 - Recognizing Economic Value of Talents & Abilities Invisible Labor Ecosystem Services Biodiversity; The Diversity Bonus by Scott Page 18:49 - The Edge of Chaos; Chaos Theory “Life exists at the edge of chaos.” 23:23 - Reproducibility Crisis and Context-Dependent Insight 28:49 - What constitutes a scientific experiment? Missed Externalities Scholarly articles for Michelle Girvan "reservoir computing" Non-conformity 38:03 - The Return of Civil Society and Community Relationships; Scale Theory Legitimation Crisis by Juergen Habermas Scale: The Universal Laws of Life and Death in Organisms, Cities and Companies by Geoffrey West 49:28 - Fractal Geometry More amazing resources from Michael to check out: Michael Garfield: Improvising Out of Algorithmic Isolation Michael Garfield: We Will Fight Diseases of Our Networks By Realizing We Are Networks Reflections: Jacob: Some of the best ideas, tv shows, music, etc. are the kinds of things that there’s not going to be an established container. Rein: “Act always so as to increase the number of choices.” ~ Heinz von Foerster Jessica: Externality. Recognize that there’s going to be surprises and find them. Michael: Adaptability is efficiency aggregated over a longer timescale. 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: JACOB: Hello and welcome to Episode 234 of Greater Than Code. My name is Jacob Stoebel and I’m joined with my co-panelist, Rein Henrichs. REIN: Thanks, Jacob and I’m here with my friend and co-panelist, Jessica Kerr. JESSICA: Thanks, Rein and today, I’m excited to introduce our guest, Michael Garfield. He’s an artist and philosopher and he helps people navigate our age of accelerating weirdness and cultivate the curiosity and play we need to thrive. He hosts and produces two podcasts, The Future Fossils Podcast & The Santa Fe Institute's Complexity Podcast. Yay, complexity! Michael acts as interlocutor for a worldwide community of artists, scientists, and philosophers—a practice that feeds his synthetic and transdisciplinary “mind-jazz” performances in the form of essay, avant-guitar music, and painting! You can find him on Bandcamp, it’s pretty cool. Refusing to be enslaved by a single perspective, creative medium, or intellectual community, Michael walks through the walls between academia and festival culture, theory and practice. Michael, welcome to Greater Than Code! MICHAEL: Thanks! I’m glad to be here and I hope that I provide a refreshingly different guest experience for listeners being not a coder in any kind of traditional sense. JESSICA: Yet you’re definitely involved in technology. MICHAEL: Yeah, and I think the epistemic framing of programming and algorithms is something that can be applied with no understanding of programming languages as they are currently widely understood. It’s just like design is coding, design of the built environment, so. JESSICA: And coding is a design. MICHAEL: Indeed. JESSICA: Okay, before we go anywhere else, I did not prepare you for this, but we have one question that we ask all of our guests. What is your superpower and how did you acquire it? MICHAEL: I would like believe that I have a superpower in being able to creatively digest and reconstruct categories so as to drive new associations between them for people and I feel like I developed that studying integral theory in grad school. I did some work under Sean Esbjörn-Hargens at John F. Kennedy University looking at the work of and work adjacent to Ken Wilber, who was trying to come up with a metatheoretical framework to integrate all different domains of human knowledge. All different types of inquiry into a single framework that doesn't attempt to reduce any one of them to any other and then in that process, I learned what one of my professors, Michael Schwartz, called creative deconstruction. So showing how art can be science and science can be art and that these aren't ontologically fixed categories that exist external to us. Looking at the relationship between science as a practice and spiritual inquiry as a practice and that kind of thing. So it's an irreverent attitude toward the categories that we've constructed that takes in a way a cynical and pragmatic approach to the way that we define things in our world. You know. REIN: Kant was wrong. [laughs] MICHAEL: It's good to get out of the rut. Obviously, you’ve got to be careful because all of these ideas have histories and so you have to decide whether it's worth trying to redefine something for people in order to open up new possibilities in the way that these ideas can be understood and manipulated. It's not, for example, an easy task to try and get people to change their idea about what religion is. [laughs] JESSICA: Yeah. More than redefined. It's almost like undefined. MICHAEL: Hm. Like Paul Tillich, for example. Theologian Paul Tillich said that religion is ultimate concern. So someone can have a religion of money, or a religion of sex, but if you get into these, if you try to interpose that in a debate on intelligent design versus evolutionary theory, you'll get attacked by both sides. JESSICA: [chuckles] That’s cosmology. MICHAEL: Yeah. So it's like – [overtalk] JESSICA: Which is hard to [inaudible] of money, or sex. MICHAEL: Yeah, but people do it anyhow. JESSICA: [laughs] Yeah. So deconstructing categories and seeing in-between things that fits through your walking through walls, what categories are you deconstructing and seeing between lately? MICHAEL: Well, I don't know, lately I've been paying more attention to the not so much tilting after the windmills of this metamorphic attitude towards categories, but looking at the way that when the opportunity comes to create a truly novel category, what are the forces in play that prevent that, that prevent recognizing novelty as novelty that I just – JESSICA: Do you have any examples? MICHAEL: Yeah, well, I just saw a really excellent talk by UC Berkeley Professor Doug Guilbeault, I think is how you say his name. I am happy to link his work to you all in the chat here so that you can share it. JESSICA: Yeah, we’ll link that in the show notes. MICHAEL: He studies category formation and he was explaining how most of the research that's been done on convergent categorization is done on established categories. But what happens when you discover something truly new? What his research shows is that basically the larger the population, the more likely it is that these categories will converge on something that's an existing category and he compared it to island versus mainland population biogeography. So there's a known dynamic in evolutionary science where genetic drift, which is just this random component of the change in allele frequencies in a population, the larger the population, the less likely it is that a genetic mutation that is otherwise neutral is going to actually percolate out into the population. On an island, you might get these otherwise neutral mutations that actually take root and saturate an entire community, but on the mainland, they get lost in the noise. You can look at this in terms of how easy it is for an innovative, artistic, or musical act to actually find any purchase. Like Spotify bought the data analysis company, The Echo Nest, back in 2015 and they ran this study on where emergent musical talent comes from. It comes from places like Australia, the UK, and Iceland, because the networks are small enough. This is a finding that's repeated endlessly through studies of how to create a viral meme that basically, or another way – JESSICA: You mean a small enough pool to take hold? MICHAEL: Yeah. That basically big science and large social networks online and these other attempts, anywhere we look at this economies of scale, growing a given system, what happens is—and we were talking about this a little before we got on the call—as a system scales, it becomes less innovative. There's less energy is allocated to – JESSICA: In America? MICHAEL: Yeah. Bureaucratic overhead, latencies in the network that prevent the large networks from adapting, with the same agility to novel challenges. There's a lot of different ways to think about this and talk about this, but it basically amounts to, if you want to, you can't do it from the conservative core of an organization. You can't do it from the board of directors. JESSICA: Oh. MICHAEL: You have to go out onto – like why did they call it fringe physics? It's like, it is because it's on the fringe and so there's a kind of – JESSICA: So this would be like if you have like one remarkably lowercase agile team inside your enterprise, one team is innovating and development practices. They're going to get mushed out. Whereas, if you have one team innovating like that in a small company, it might spread and it might become dominant. MICHAEL: Yeah. I think it's certainly the case that this speaks to something I've been wondering about it in a broader sense, which is how do we recognize the economic value of talents and abilities that are like, how do we recognize a singular individual for their incompressible knowledge and expertise when they don't go through established systems of accreditation like getting a PhD? Because the academic system is such that basically, if you have an innovative contribution, but you don't have the credentials that are required to participate in the community of peer review, then people can't even – your contribution is just invisible. The same is true for how long it took, if you look at economic models, it took so long for economic models to even begin to start addressing the invisible labor of women in at home like domestic labor, or what we're now calling ecosystem services. So there's this question of – I should add that I'm ambivalent about this question because I'm afraid that answering it in an effective way, how do we make all of these things economically visible would just accelerate the rate at which the capitalist machine is capable of co-opting and exploiting all of these. [chuckles] REIN: Yeah. You also have this Scott Seeing Like a State thing where in order to be able to even perceive that that stuff is going on, it has to become standardized and you can't dissect the bird to observe its song, right? MICHAEL: Totally. So obviously, it took almost no time at all for consumer culture to commodify the psychedelic experience and start using to co-opt this psychedelic aesthetic and start using it in advertising campaigns for Levi's Jeans and Campbell Soup and that kind of thing. So it’s this question of a moving frontier that as soon as you have the language to talk about it, it's not the ineffable anymore. REIN: Yeah. MICHAEL: There's a value to the ineffable and there's a value to – it's related to this question of the exploitation of indigenous peoples by large pharmaceutical companies like, their ethnobotanical knowledge. How do you make the potential value of biodiversity, something that can be manufactured into medicine at scale, without destroying the rainforest and the people who live in it? Everywhere I look, I see this question. So for me, lately, it's been less about how do we creatively deconstruct the categories we have so much as it is, what is the utility of not knowing how to categorize something at all and then how do we fix the skewed incentive structures in society so as to value that which we currently do not know how to value. JESSICA: Because you don’t have a category for it. MICHAEL: Right. Like right now, maybe one of the best examples, even though this is the worst example in another way, is that a large fraction of the human genome has been patented by Monsanto, even though it has no known current biomedical utility. This is what Lewis Hyde in his book, Common as Air, called “the third enclosure” of the common. So you have the enclosure of the land that everyone used to be able to hunt on and then you have the enclosure of intellectual property in terms of patents for known utilities, known applications, and then over the last few decades, you're starting to see large companies buy their way into and defend patents for the things that actually don't – it's speculative. They're just gambling on the idea that eventually we'll have some use for this and that it's worth lawyering up to defend that potential future use. But it's akin to recognizing that we need to fund translational work. We need to fund synthesis. We need to fund blue sky interdisciplinary research for which we don't have an expected return on investment here because there's – JESSICA: It's one of those things that it’s going to help; you're going to get tremendous benefits out of it, but you can't say which ones. MICHAEL: Right. It's a shift perhaps akin to the move that I'm seeing conservation biology make right now from “let's preserve this charismatic species” to “let's do everything we can to restore biodiversity” rather than that biodiversity itself is generative and should be valued in its own regard so diverse research teams, diverse workplace teams. We know that there is what University of Michigan Professor Scott Page calls the diversity bonus and you don't need to know and in fact, you cannot know what the bonus is upfront. JESSICA: Yeah. You can't draw the line of causality forward to the benefit because the point of diversity is that you get benefits you never thought of. MICHAEL: Exactly. Again, this gets into this question of as a science communications staffer in a position where I'm constantly in this weird dissonant enters zone between the elite researchers at the Santa Fe Institute where I work and the community of complex systems enthusiasts that have grown up around this organization. It's a complete mismatch in scale between this org that has basically insulated itself so as to preserve the island of innovation that is required for really groundbreaking research, but then also, they have this reputation that far outstrips their ability to actually respond to people that are one step further out on the fringe from them. So I find myself asking, historically SFI was founded by Los Alamos National Laboratory physicists mostly that were disenchanted with the idea that they were going to have to research science, that their science was limited to that which could be basically argued as a national defense initiative and they just wanted to think about the deepest mysteries of the cosmos. So what is to SFI as SFI as to Los Alamos? Even in really radical organizations, there's a point at which they've matured and there are questions that are beyond the horizon of that which a particular community is willing to indulge. I find, in general, I'm really fascinated by questions about the nonlinearity of time, or about weird ontology. I'm currently talking to about a dozen other academics and para-academics about how to try and – I'm working, or helping to organize a working group of people that can apply rigorous academic approaches to asking questions that are completely taboo inside of academia. Questions that challenge some of the most fundamental assum…

    Full show notes at the publisher

    233: Diversity, Equity, and Inclusion Matter with Jess Szmajda May 05, 2021
    Show notes

    01:22 - Jess’s Superpower: Playing ANY Instrument Music & Technology Cultural Expoloration 06:03 - Language Community Ethos (MINASWAN) Human-Centered Design The Joy of Programming Meetup Sapir-Whorf Hypothesis 13:24 - Inclusive Language: Language Matters Valheim 17:19 - Active Listening and Expressing Point-of-View, and Using Loudness Vocally For Vocally Against Quiet For Quiet Against 21:51 - Shining Light on Marginalized People & Voices BULQ Metacognition: Asking ourselves, “What are we not thinking about?” Leadership Changing Mental Patterns; Take a Different Path 31:30 - Benefits of Having Diverse Teams (Resources) & Risks of Homogeneity Diversity wins: How inclusion matters Why diversity matters The Chevy Nova That Wouldn't Go Google Photos labeled black people 'gorillas' From transparent staircases to faraway restrooms, why these benign design details can be a nuisance for some women 37:29 - Storytelling Representation Matters Normalization Reflections: Jess: We are feeling beings that rationalize. Damien: How technology impacts culture. Casey: Taking loudness for diversity, equity, and inclusion with people who don’t always talk about it. Who is more open to it or not? 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:: DAMIEN: Welcome to Episode 233 of Greater Than Code. I’m Damien Burke and I’m joined here with Casey Watts. CASEY: Hi, I’m Casey! And I’m here with our guest today, Jess Szmajda. Jess is currently a senior leader at AWS in the EC2 Networking organization. Previously, she was the first female CTO of a major media organization, Axios, and before that, the co-founder and CTO at Optoro, which helps top tier retailers nationwide handle their returned and excess goods. Jess got her start in tech in the 90s writing Perl to configure Solaris machines. Over the years, she’s contributed to Open Source and organized a number of communities. These days, focusing on the DC Tech Slack and the DC-based Joy of Programming Meetup. Outside of the tech world, Jess is a singer-songwriter, an improviser, a gamer, a proud member of the LGBTQ+ community, and a Mom to the most wonderful, Minecraft-obsessed 6-year-old imaginable. Welcome Jess. DAMIEN: Welcome to Greater Than Code, Jess. JESS: Thank you! It's nice to be here. DAMIEN: So I know someone has prepped you with our first question. What is your superpower and how did you acquire it? JESS: My superpower is that I can play any instrument you hand me and I – DAMIEN: Oh. JESS: [laughs] I acquired it by being a giant nerd. [laughs] I went to a special music high school here in the DC area called Suitland High School and I played all kinds of different instruments. I was the principal bassoonist of the DC Youth Orchestra for a while. Music's always been a lifelong love of mine and it's been a mission to find every strange instrument I can find to figure out how it works. So it's challenge [chuckles] to find something that I can't play. [laughs] DAMIEN: Oh, I'm so tempted and of course, the first thing I would have gone with is the double reed bassoon and oboe, but that's too easy. JESS: That’s right. DAMIEN: Banjo, of course, you’ve got steel drum. JESS: Steel drum and plate, yeah. DAMIEN: Cajon. JESS: Cajon. Oh, I have heard of it. DAMIEN: Aha! JESS: I haven't actually touched one. I'll figure it out. [laughs] DAMIEN: It's particularly easy. JESS: Nice. [laughs] CASEY: I don't know very many people who play more than just an instrument, or two. I think it might be like you and I are the two that come to mind for me, honestly. [laughter] I have an instrument in every color, by the way. That's the way I collect them. [laughter] JESS: Nice. CASEY: I’ve got a white accordion. How do you feel like this breadth of instrument ability has affected your life in other ways? JESS: I don't know. That's an interesting question. How has it affected my life in other ways? I mean, there's the obvious tie into music and technology. There's such an incredible confluence of musicians who are engineers and vice versa. I was actually talking to someone at the office earlier about that and she was theorizing it's because all of the patterns and rhythms that we think about and how that ties into a regular patterns and systems that we think about as engineers and I think it's a really interesting way to think about it, for sure. I do think that there's a certain element of cross-culturalism that you get from learning other cultures instruments. Certainly, the berimbau, the Brazilian martial art? [laughs] DAMIEN: Capoeira? JESS: Capoeira, yeah. The capoeira, the berimbau instrument that has the long string and you have the little – I think you learn a lot about what led to developing an instrument so relatively simple, but creating such an incredible art form in the culture where people just wanted to dance and share their heritage with each other and picked up whatever they could find that would make interesting and fun sounds and created an entire culture around that. So for me, it's as much cultural exploration and understanding as it is anything. I think it's wonderful. DAMIEN: Yeah. That's really amazing. I had a tiny insight on this recently. I saw an amazing video about a Jimmy Hendrix song with the basic premise being, what key is this song in? It's a really difficult question because—and I'm going to go a little bit music nerd here—the tonic is e, but the chord progressions and the melodic signature doesn't really fit that. Amazing 20-minute video, but the end conclusion is that using Western art music tonality to describe blues music, American blues music, it's a different tonality. So it doesn't really make sense to say what major key is this in, or what minor key is this in. JESS: Yeah, totally. My partner and I, this morning, we were watching a video about Coltrane's classic—my favorite thing is interpretation in the 60s—and how he's basically playing between these major and minor tonalities constantly. It's not necessarily tonal from the Western sense, but it’s certainly beautiful and I think it's certainly approachable and understandable to any ear regardless of how you decompose it. Anyway, giant music nerd, sorry. [laughs] DAMIEN: Yeah, but it ties so closely to what you were talking about as an instrument being cultural. The guitar, the five-string guitar, is tuned for American music, which is a slightly different tonality from Western European music. So when you think about “Okay, well, that's very slightly different. Now, what is it like in Africa, in Australia, in Asia?” Then it gets all, it's got to be very, very different. JESS: Oh, yeah. I saw this guy in Turkey, he's modified a guitar to add quarter tones to it because a lot of Turkish music uses quarter tones and so, it's just like the fretboard is wild. It has all of these extra frets on it and he plays it. It's absolutely incredible, but it's wild. It's amazing. DAMIEN: So I want to tie this into different cultures, frameworks, and technology. How about that? JESS: Yeah, you bet, let's do it. [laughs] CASEY: Good segue. JESS: So actually, that's something that's been on my mind is this Ruby community diaspora in a way. I know Greater Than Code has a lot of Ruby folks on it and I'm not sure about the latest incarnation, but definitely a lot of Ruby roots. I think that we've seen this incredible mixing of culture in the Ruby community that I haven't seen in other places that drives this – well, I think [inaudible], it's a really fantastic way to sum it up like, math is nice and so we are nice. As much as that might be a justification to be nice, be nice anyway, but it's still this ethos of we are nice to each other, we care, and that is baked into the community and my journeys and other language communities, I think haven't shared that perspective that it is good to be nice in general and some of them even are, I think are focused on it's good to fight. [laughs] So I've been really curious about this movement, Rubius’s movement into other language areas, like Go, Rust, and Alexa, et cetera, et cetera, how much of that carries forward and what really can we do to drive that? DAMIEN: Yeah. So my question is how does a technological community, what is it about the community? What is about the technology? Why is it different? You and I both wrote Pearl in the 90s and so, that is a very different community. I look at Ruby and I write mostly Ruby now and I go, “Why is it different? What's different about it?” JESS: Yeah, no, it's a good question. A lot of the early conversation that I remember in the Ruby community was—and just contextually, I've been using Ruby since 2006, or so, so that era. A lot of the early conversation I remember was about develop the language to optimize for developer happiness. I think that's a really unique take and I haven't heard of that in any other place. So I'm wondering how much that might've been the beginnings of this. I don't know. DAMIEN: Something came up in a Twitter conversation, I saw a while back where they compared Ruby and Pearl, I'm pretty sure it was Pearl and well, one of the defining features of Pearl was that there's more than one way to do it and Ruby has that same ethos. Literally, in the standard lib, there’s a lot of aliases and synonyms. It's like, you can call pop, or drop and I can't keep it straight. [chuckles] But anyway, then I thought to myself, “Well, in Pearl, that's an absolute disaster.” I pull up a profile and I'm like, “I don't know what this is because I don't know what's going on.” Whereas, in Ruby, I've loved it so much and so, what's the difference and the difference pointed out to me was that in Ruby, it was for expressiveness. Things have different names so that they can properly express, or better express the intention and in Pearl, that wasn't the case. JESS: Yeah, no, totally. I think actually looking at Ruby and Python, I think were both heavily influenced by Pearl and I think Python definitely took the path of well, all of this nonsense is just nonsense. Let's just have one way to do it. [laughs] Having worked with some Python developers, I think that perspective on there is one correct path really drives that community in a lot of ways. I think some people find that releasing really simplifying for them because they're like, “I got it. I know the answer.” Like it's a math problem almost. As a Rubyist going into the Python community, I was like, “Oh, I'm so stifled.” [laughs] Where is my expressiveness?! I want to write inject, or oh, I can't even think of the opposite of inject. Collect. [laughs] Those are two different words for me. I want to be able to write both, depending on what I'm doing so. It's also interesting, like I see a lot more DSL development in Ruby than I see in any other language and maybe Alexa also. But I think that also comes from the same perspective of there is not one right way to do it. There's the best way for this problem and there's the best way for this kind of communication you're trying to drive. It's interesting, as I'm talking myself into a corner here a bit, Ruby almost emphasizes the communication of code more than the solving of the problem and I think that might actually help drive this community where we care about the other humans we're working with, because we're always thinking about how we communicate with them in a way. CASEY: I think about the term human-centered design a lot lately and that's becoming more and more popular term, a way to describe this thing. Ruby totally did that. Ruby looked at how can we make this easy for humans to use and work with and I think that's beautiful. I keep thinking about a paper I read a long time ago that a professor made-up programming language and varied features of it like, white space matters, or not, and a whole bunch of those and measured which ones were easier for new people to learn and which ones were harder for new people to learn. As a teacher, I want to use whatever is easy for the students to learn so they can get their feet wet, so they can start learning and building and doing things and get excited about it, not get hung up on the syntax. So human-centered design baked into Ruby is, I think partly why the community is so human-centered. I think you're exactly right. JESS: Yeah. That's really interesting. That's a large part of why the Joy of Programming Meetup, I think has been really fun is we get to learn from how different language communities build things. I think it was founded on that kind of thinking is the Sapir–Whorf hypothesis for better, or worse theorizes language shapes thought and I think that that is to some degree, at least true in how we think about writing code and solving problems. So the kinds of solutions that you see from different language communities, I think very incredibly. I don't know, even just as simple as from like J2EE, which is the ivory tower of purity in XML [laughs] to obviously, I don't want to pick on Rails, but Rails is an open system. [laughs] An interpretive dance, perhaps. I think it's really interesting, the web frameworks even I see in Haskell almost feel like I'm solving a math problem more than I'm creating an API, or delivering content into somebody. So it's hard for me to separate, is this a community of thought of people who are attracted to a certain way of solving problems? Is this driven by the structure and format of the language? I don't know. DAMIEN: I know you mentioned the Sapir–Whorf hypothesis and their research has been shown to be problematic. JESS: Yeah, for sure. DAMIEN: [laughs] But I will say that the hypothesis is that language shapes thought and I would say that the correct state – correct [chuckles] a better description for me is that language is thoughts and so, the language you use is the sort of things you're thinking about. So if you say inject when you mean collect, those are different things, you're going to get different things out of them. This is why we use get annotate instead of get playing. JESS: For sure. Exactly. So at AWS, this is big drive and I'm not speaking for AWS on this, I'm just speaking for me. But I'm noticing this drive for inclusive language and I think it's really beautiful. Connecting that drive, frankly, in the broader tech community to everything that's been going on in this last year in how we interact with each other as humans from different backgrounds, et cetera. It's like, what kinds of dominant culture paradigms have we baked into our code beyond even the very obviously problematic statements, but just the way that we think about, I don't know. Part of me is like, “Well, is object-oriented design driven by certain cultural expectations that we have, or functional?” I don't know. What paradigms would we get if we'd have had a different dominant culture developing technology? I don't know. It's fascinating. DAMIEN: Yeah, and [inaudible] is an excellent example of that. It's a punishment. This is wrong. I did a whole talk several years ago about specifications versus tests. I don't want you to write tests for your code; tests ar…

    Full show notes at the publisher

    232: Outside The Charmed Circle with Tamsin Davis-Langley Apr 28, 2021
    Show notes

    01:17 - Tamsin’s Superpower: Recognizing Songs Within Seconds 05:08 - Outside the Charmed Circle (Tamsin’s book about gender, sexuality, and spirituality) The Pagan Community “Necessarily Brief” 09:09 - Consent in the Mentor/Mentee Relationship (Master/Apprentice) The Universal Attribution Fallacy Access Power Dynamics Conflicts of Interest The Word “Politics” - how we negotiate power between groups of greater than one 16:57 - Using Certain Phrases (i.e. “Identity Politics,” “Cancel Culture”) and Divisiveness Obfuscation We Hate You Now: The Hardest Problem of The Aftertimes Social Contracts 23:46 - What Is A Person? Individuality & Personhood Plato & Aristotle Women, Fire and Dangerous Things: What Categories Reveal About the Mind by George Lakoff Hegemonic Norms, Privilege & Power 30:01 - “Fringe Communities”; Subcultures and Intersection How Buildings Learn: Edge Cities The Queer Community Using the Word “Queer” Gatekeeping Fear of Powerlessness The Relationship Between Radicals and Reactionaries “Outside The Charmed Circle” Gayle S. Rubin: Thinking Sex: Notes for a Radical Theory of the Politics of Sexuality 44:30 - Individual Experiences Are Not Universally Applicable Getting People to Care About Other People Teaching Empathy Less Hubris, Gatekeeping, and Self-Reinforcing Superiority Reflections: Jamey: Conceptualizing that other people are having a different experience than you. Rein: What are the interactions in a community that empathy leads to and how can we promote those? Helping. Helping by Edgar H. Schein Tamsin: The dynamics at the heart of any subculture you care to name really aren’t that dissimilar from one group to another. 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: JAMEY: Hello and welcome to Episode 232 of Greater Than Code. I’m one of your hosts, Jamey Hampton, and I’m here with my friend, Rein Henrichs. REIN: Thanks, Jamey. That is a lot of episodes. I’m here with our guest, Tamsin Davis-Langley who is a white, queer, nonbinary trans femme from a multiethnic family who grew up poor. They spent most of their adult work life as the tech-savvy person in a non-technical office, and are now pursuing a career in digital communications. Their academic path began in liberal arts, detoured through computer science, and ended with a degree in Gender, Women, and Sexuality Studies from the University of Washington. Their work explores the ways subcultural communities intersect with non-normative expressions of gender and sexuality. They've written about how the problems of abuse and predation in subcultures are linked to the power dynamics inherent in those groups. Under their nom de plume, Misha Magdalene, they're the author of Outside the Charmed Circle, a book about gender, sexuality, and spirituality. Tamsin, welcome to the show. TAMSIN: Thank you so much! It’s a delight to be here. REIN: So you know what we’re going to ask you. [laughter] What is your superpower and how did you acquire it? TAMSIN: My superpower is that I can, with a relatively high degree of accuracy, listen to the radio and identify the song that's playing within 5 seconds, or so if it was recorded within a specific window of time and basically falls under the very broad umbrella of Western pop music. This happened because I was bitten by a radioactive record store employee back in the 80s and since then, I've been able to go, “Oh yeah, that's Won't Get Fooled Again by The Who. It's on Who's Next released 1972. Produced by Glen's Johns,” blah, blah, blah, blah, blah, and this is a delightful party trick for getting people to suddenly realize they want to talk to someone else at the party. JAMEY: I was about to ask – [overtalk] REIN: How do you remember all of that? TAMSIN: How do I remember all of that? I have no idea. I literally could not tell you what I had for dinner last night and I'm in the midst of training sessions for a position that I'm pursuing in digital communications and half the time I'm going, “What was the command to do the things so that I can function?” But I can literally tell you the brand of bass guitar that Paul McCartney played in The Beatles, or the kind of keyboard that Kate Bush used when she was recording her albums in the late 70s and early 80s was a Hohner, a violin-shaped bass, and a Fairlight synthesizer, respectively. [chuckles] JAMEY: I can relate to this because I often think about how many other things I could know if I freed up all of the space in my brain where I kept the names of all the Pokémon. TAMSIN: Right, right. I want to defrag my own brain and just throw out huge chunks of permanent storage, but no. JAMEY: Do you use your superpower for good, or for evil? TAMSIN: In finest, strong, bad tradition, I try to use my powers only for good, or for awesome. I have actually used it to further my career. I did work for a little while at a Musicland, back when those existed, and later at a Tower Records, back when those existed. For younger listeners, those were both brick and mortar stores where you could go in and buy music on physical media and occasionally, accessories that were associated with bands, or musicians that you liked and people would walk in and say things like, “I'm trying to find a CD by this band and I don't know the name of the band, or the name of the song, or any of the lyrics, but it's got this bit in it that goes “Duh, duh, duh, duh, duh, duh, duh, duh” and I went, “Bad to the Bone, George Thurogood & the Delaware Destroyers. Here's their Best Of. Thank you.” So that's the extent to which my superpower operates for good, or for awesome. REIN: That reminds me, there was a librarian who worked at The London Library, which has about a million books, for 40 years and could do a very similar thing where they knew what book someone was looking for better than that person did. TAMSIN: Yeah. That kind of talent always delights me when I find it out in the wild where I'm like, “Yeah, I was looking for this book. It kind of was about this thing and I remember it had sort of a teal cover. Oh, here you go.” Yeah, it's kind of an amazing and wonderful thing to see, but then I do it and I feel really self-conscious, so. [laughs] REIN: So, speaking of books, graceful segue. TAMSIN: Yes. Speaking of books. REIN: Tell us a little bit about the book that you wrote. TAMSIN: I can, yes. So when I was finishing up my degree at the University of Washington in Gender, Women, and Sexuality Studies, I spent a lot of time thinking about how to apply the concepts and the tools that I was learning in my degree program to my actual day-to-day life. It's all well and good when you're in the ivory tower of academia to talk about intersectionality and hegemonic norms of sexuality, or gender, but how does that actually play out in your work life, or in your family dynamic? Or if you are a person who practices some form of spirituality, how does that play out in your spiritual communities, or really, in any subcultural communities that you're a part of? As it happens, one of the subcultural communities that I'm part of is what's generally referred to as “the pagan community,” I'm going to throw a lot of quotes around that because pagan is not a commonly agreed upon term and we could get into a great argument about how much of a community it is. But all of that to the side, one day I was sitting there probably having coffee at the coffee shop on campus and I thought, “Hmm, I wonder what would happen if you took this intersectional feminist lens and turned it on the pagan community?” I thought about it a moment and then I think I literally said, “Oh no,” out loud because I realized that was a book and 2 and a half years later, 3 years later, it was published by Llewellyn worldwide as Outside the Charmed Circle. It's a book about how gender and sexuality are expressed, explored, repressed denied, or whatever other ways engaged within the subculture of modern pagan polytheist, or magical “practice.” It's a book I had a lot of fun writing, which is really strange to hear myself say out loud because there were moments when I absolutely wanted to bang my head on the keyboard, or just fold the laptop up and smack myself in the face with it like the monks in Monty Python. But it's a book that I really enjoyed writing because I got to spend long hours researching and talking about a bunch of my favorite stuff: gender, sexuality, embodiment, philosophy, Van Halen and their impact on Western culture and I say that, and people are like, “Oh, that's really funny,” and I'm like, “No, no, I'm being really serious.” As far as the question that just came up in the chat here: is there something I cut from the book that I wish I could have put in? One of the things that I said in the very last chapter is that the book I wrote is necessarily brief. Each chapter in that book could have been its own book. There's a chapter on embodiment. A chapter on gender and theory – I believe the chapter is actually called Gender and Theory in Practice. There's a chapter, or a couple of chapters on consent and how consent works in these communities. There's so much more that can be said about these topics. There's so much more that I could have said about any of these topics. But 300 pages, I felt like I'd run on quite long enough. Consent in the mentor-mentee relationship also just came up in chat. That's actually a topic that I touch on in the book and it's something I have really strong feelings about. Especially in the pagan and polytheists communities, there's often a lot of stress on the teacher-student relationship, sort of master-apprentice, if you want to get all scythe about it and well, there's a lot of unspoken disagreement about what the appropriate dynamic between those two parties should be. There are people who will cheerfully say, “Oh, well, teachers and students should always have this kind of relationship and should never have that kind of relationship.” Yeah, and by that kind of relationship, we're usually talking about a sexual and/or romantic relationship. And then there are people who are perfectly happy to say, “Well, that's true in most cases, but this situation is different,” and often what they mean is, “my situation is different.” So when I was writing the book, I had the less than enviable of saying, “Dear sweet summer child, no, your situation isn't different. It's not any different. It is never any different. Teachers and students just shouldn't have those kinds of relationships while they are ensconced in that power dynamic of teacher-student, or mentor-mentee.” REIN: Of course, thinking that your own situation is different is quite common. Common enough that we have a name for it and that is the universal attribution fallacy. TAMSIN: Yeah. Not to be super political, but it goes back to the phenomenon that you see quite often in modern sociopolitical discourse where people will say, “X is always immoral and wrong, except when I do it,” and X could be getting an abortion, being in a same-sex relationship, any number of things. “Well, that's always bad and wrong, but my circumstances are different.” JAMEY: One thing I think is interesting about what you're talking about with teachers and students is that the concept of a teacher-student relationship is nebulous in a lot of ways. Like, how would you draw the line here between this is an actual teacher and student relationship and therefore, inappropriate as opposed to “I have this relationship with someone and I'm learning something from them,” which I learn from all people all the time, including my partner and other people? Where is the line between “This is a great person in my life that I'm learning” from versus “I'm in this hierarchical relationship with them”? TAMSIN: The short answer would be access—access to knowledge, access, to experience, access to opportunity. If you are a teacher and I am coming to you saying, “I want to learn this thing,” and your response is not “Okay, sure, I can take you on as a student and teach you this thing,” but instead, “I can take you on and teach you this thing if X, Y, or Z,” that becomes a really sketchy kind of dynamic where if I want whatever it is that you have the ability to give me the knowledge, the opportunity, the access, I am essentially being required to behave in ways that I might not otherwise. REIN: It seems like there are maybe two important things here. One is power dynamics—which always exist; they never don't exist—and the other is more narrowly conflicts of interest. TAMSIN: Right, and one of the things that I ran into, with talking modern practitioners of pagan and polytheistic spirituality, is that a lot of people want to talk about power, very few people are comfortable talking about power dynamics. In part, because in my experience, a lot of people don't want to see themselves as being people who have power to impact others in a negative way. Will they, or nil they? There becomes this attitude of deniability where it's like, “Well, I can't possibly be in an oppressive position. I can't possibly be an abuser because I'm coming to this from just as much a place of powerlessness as the next person,” and that's not always true, of course. REIN: I think sometimes talking about groups in that way is vulnerable to that counterargument and I try to talk about the dynamics as being every relationship between two people has an element of power. TAMSIN: Absolutely, and one of the arguments I often get into with people is about the word politics because people, especially in our current social climate, tend to think that politics means a turf war between these two groups, or parties. My response is that politics is just the word to describe how we negotiate power between groups of greater than one. Politics is how we talk about the policies. There's the whole word police meaning city, politics, policy. It's a thing. Politics is how we arrange policies and laws and agreements so that we can all basically move forward doing the same kind of thing. Yes, from the chat: “framing politics between two groups is very American.” It really is. So I have often been criticized for bringing politics into spirituality and I'm going, “We're sitting around talking about power all day long, pretending that politics isn't a part of that is a way of getting out of having to be accountable for the politics that's actually going on.” That maneuver is as present in any subculture you care to name as it is in the pagan community. I mean, that's certainly not unique to witches, Druids, modern polytheists, and whomever. JAMEY: Yeah. Everything we've been talking about in the pagan has made me think of the tech community, too. My question earlier about mentorship, I was thinking that and when you were talking about “Don't bring politics into” – such a common thing that we talk about in tech, also. TAMSIN: Oh yeah. Why do you have to bring politics into this? Why do you have to bring identity politics, or diversity politics into this argument? We work in tech; this is a meritocracy and the sound of a thousand palms slapping into a thousand foreheads echoes across the land. JAMEY: I know you said it to illustrate that point, the phrase, identity politics, I just have such a visceral physical reaction to. [laughs] TAMSIN: Oh, it's grea…

    Full show notes at the publisher

    231: Deserted Island Safety and Expectations with Austin Parker Apr 21, 2021
    Show notes

    01:04 - Austin’s Superpower: Pain Tolerance 02:06 - Deserted Island DevOps (Running an Online/Virtual Conference in Animal Crossing or Other Mediums) Deserted Island DevOps 2020 on YouTube Software Circus The Great Cloud Native Bakeoff Making Real-Time Audience/Human Connection Streaming Watch Parties Austin Parker: Virtual Events Suck. 24:09 - Failure; Making it Safe to Fail Technical Failure Psychological Failure Underpromise, Overdeliver 32:51 - Safety and Setting Expectations (The Problem with More is Better) OKRs Open Source Principles Reflections: John: The creativity of new ways to experience a conference. Coraline: The importance of moderation. Austin: How to communicate feelings of failure and setting expectations about it to people you’re working with. Jacob: Find a conference that has been thoughtful about interaction when not in person and go. 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: CORALINE: Hello and welcome to Episode 231 of Greater Than Code podcast. I’m so happy to be here with you today. My name is Coraline Ada Ehmke and I’m joined by my friend, John Sawers. JOHN: Thanks, Coraline. And I’m here with Jacob Stoebel. JACOB: Thanks. John! It’s my pleasure to introduce our guest this week, Austin Parker. Austin makes problems with computers and sometimes solves them. He’s an open-source maintainer, observability nerd, DevOps junkie, and poster. You can find him ignoring Hacker News threads and making dumb jokes on Twitter. He wrote a book about distributed tracing, taught some college courses, streams on Twitch, and also ran a DevOps conference in Animal Crossing. Such a nice pleasure to have you on the show. AUSTIN: It's fantastic to be here. JACOB: We can start the show like we always do by asking you a question. What's your superpower and how did you develop it? AUSTIN: Right now, my superpower is I'm 50% through a COVID-19 vaccine and I developed it by staying indoors for the past year, but more hilariously I guess, I developed a strong resistance to burns by working as a gas station cook for quite a while, back in my younger days. So I ran the fryer and you get really good at ignoring hot oil spattering on you. So I'd like to think that that level of pain tolerance is what helped me get through a lot of DevOps stuff and getting used to computers. [laughter] CORALINE: Yeah. I hate Kubernetes and it's hot oil splashing. They should do something about that. It's open source. I guess, I could open my PR, but . AUSTIN: Yeah. Well, they say PR is welcome, but that's the open-source maintainers. Bless your heart, right? CORALINE: Yeah, exactly. So Austin, I want to know more about this DevOps conference that you ran in Animal Crossing. AUSTIN: So let's start at the beginning, let's take everyone back to just about a year ago now where we were all kind of settling in for our wonderful pandemic that has been extremely not wonderful for most people, but I think everyone was coming to grips with how long it would take at first. My day job, I work as in developer relations. I'm a marketer, effectively. But I remember a lot of people were talking, the marketing team and certainly, the entire events space like, “Oh, what's this going to do about the summer events, what's this going to do about the fall events?” and I'm sitting here like, “Hey, I think this is going to last a little longer than till June.” So the conversation kind of pivots as everything gets progressively worse and people are starting to come to grips like, “Well, can we do a virtual event?” I don't think anyone at the time really had a good idea of what a virtual event would be. We all know video conferencing certainly is something that we've come to rely on in our day-to-day lives over the past year. Even if you weren't already in tech, or weren't already working remotely, Zoom is – it’s been Q-tip. It's been Kleenex. It's a no matter what you're using, you're Zooming someone. So they have that going for them, I guess. People, I think there was a lot of possibility and not a lot of real, strong ideas about what does this actually mean? So I wanted to try something different. I was joking around on Twitter and I had just gotten a copy of Animal Crossing: New Horizons, and I was staging with screenshots with like, “Oh look, this is funny. It's like a conference booth.” It's like ha, ha, we're all giving out t-shirts and laughing. And the code people picked up on and they were like, “Oh, that's funny. I bet you could actually do a conference in Animal Crossing and stream it out” because you can actually have people like join you, come over to your island and stand around. I was like, “Well, actually, you could just composite that video from the output of the game over some slides and what's the difference?” Someone's talking, someone's clicking through slides, and it spiraled from a joke. I put up a page, a landing page on April 1st, which is the best time to announce anything thing. Because if people don't go for it, you can always be like, “Ha, ha, April fools. Got you!” [laughter] But I put up a landing page and we had a 100 people register for more information that first day, I messaged them on Slack, and I'm like, “Well, I’ve got to do it now; a 100 people one day. That's great.” CORALINE: Yeah. AUSTIN: So long story short, over the next 30 days, we basically put together, myself and then my co-organizer, Katie @thekatertot on Twitter, or Katie Farmer, a virtual conference inside of Animal Crossing. It's called Deserted Island DevOps. You can go watch it on YouTube, the one from last year. We're doing another one this year on April 30th. It's just a one-day live stream. If you're watching it, you're just watching it on Twitch. We have a Discord that you can talk and do the hallway track stuff and ask questions and network. But the gimmick is basically, everyone's presenting has a Switch and they are in Animal Crossing. They're on this island, they're dressing up their little Animal Crossing character and we overlay their slides with the video coming out of the Switch so they can emote and react and it's cute experience to watch. But I think it's also interesting because what I saw, last year at least, is that it solves a lot of the problems, I think most virtual conferences don't quite nail, which is, I think a good event is something that takes you out of your day-to-day. It takes you out of where you are and put you somewhere else. Now, if you go into KubeCon, or re:Invent, or even devopdays, if you're doing this physically like, you're not at your office, you're not at home, you're somewhere else talking to people, literally, you have changed the physical location you're in. But most virtual events, it still boils down to, “Hey, I'm watching a Zoom effectively and I'm talking to people in Slack.” If I wanted to do that, I could just do my actual job. So I think one of the things that people appreciated about Deserted Island and continue to is the idea that this is produced differently. There's a couple other people that are doing stuff like this. I think Software Circus out of the UK, they've done a lot of themed events, themed virtual events like this, where the presenters are wearing costumes. Or there was The Great Kubernetes Bake-Off, I want to say where it’s a cloud kitchen theme so everyone has their chefs’ hats. I think having that concept also gives presenters a lot of mileage in terms of hey, you can theme what you're talking about. Here is an analogy in a box, here is a world that you can put your talk in and you have an idea that everyone can use those shared experiences, that shared language to develop your talk and give people an anchor for it, which I think is one of the good ways you help people learn. If you give them something they know about and then you tie your concept into that concept, then they're going to get more out of it. The other thing is that it's a great way to be expressive. In Animal Crossing, you are who you are, you are whoever your avatar is. So you don't get any of the – I hate being on camera a lot. It gets exhausting because you feel like you're performing for the camera. It’s not the same, but in this, nobody's seeing your actual face; they're hearing your voice and then you can dress your Animal Crossing your avatar whatever. So you can be creative. You can be who you are without having that weird performance pressure of a bunch of people that you can't see staring at your face JOHN: This is an important topic these days because there's still everything's online and will be for a while and I think so many people are still learning how to do online events and those skills are going to need to keep happening over the next coming years. I think because you can do now online events, which are more accessible to more people all over the world, you don't have to be the sort of person who can fly places in order to attend certain events. Having them online is a great accessibility option. So finding new modalities for making that interesting and not just sitting on Zoom all day, I think is a worthy endeavor. AUSTIN: Yeah, and it's super challenging. I don't want to sound like I'm like dragging people's work because I know CNCF has had to move a lot of stuff virtual. I know of the entire devopsdays community has had to move a lot of stuff virtual. This is super hard to do. It's not easy. It requires a lot of intentionality; a lot of planning and I think we will all get better at it over time. The future is not necessarily going to be like the past, I don't know if there's ever going to be a day where we just kind of flip a switch and it's all like, “Oh, we're back to how we were before March of 2020,” I think. So there's still going to be a desire for virtual events and there's still going to be a desire for figuring out ways to be more inclusive and to bring people in, especially because of climate change and everything like that. At some point, we have to come to a reckoning about the actual cost of a global travel-based society but that's maybe a slightly different topic. I don't know. CORALINE: I actually think a good side effect of all this is a focus on accessibility and like you said, a lot of people aren't people to travel. It's expensive. I know conferences, typically in-person conferences, used to spend quite a bit of money with programs to bring in marginalized folks who maybe couldn't afford the travel. But one thing I do miss is getting that audience reaction. Especially as a storyteller, I tend to tell a lot of stories in my talk and I like to be able to see, is the audience with me, is the audience getting what I'm saying? I can tune my presentation in real-time based on audience reactions and I really miss that. I really missed that aspect of it, that feedback aspect of it, because at the end of people are like, “Oh, great talk.” I'm like, “Yeah, but did it get to you?” AUSTIN: Yeah, did you connect with it? CORALINE: Yeah, and that's so hard. AUSTIN: It's challenging, especially because so many of – on the production side, there's a bias, I think in virtual events to prerecord, due to a lot of factors and this is not a diss on prerecording. I personally hate it. I basically have stopped doing any event that's like, “Oh, we want you to prerecord.” I'm just like, “Eh, I'd rather not” because that’s the style, that's the way I talk. I agree with this idea of storytelling like, you're not just reading slides. If I just want someone to read slides, I could just hand them a book. But what's weird to me is one of the things that I think that we did, that I haven't seen anyone else really do, is there's already a way that people do this. If you watch Twitch, if you watch twitch.tv, or live streams like the kids do these days, there is a real-time chat and people are reacting in real-time. It's a little bit delayed. It's a couple seconds delayed, but I don't know why you haven't seen other virtual event platforms take that idea and really try to have even just a button like a clap button, or a sparkle fingers button, or something to kind of let people know that there's people out there watching you and that they're reacting positively and maybe not negatively, but they're reacting. That they are cognizant of what you're saying. It's really surprising to me that we haven't seen more like that and I would love if some of these event platforms thought about that. How do you make that actual, immediate real-time, or near real-time audience connection with the speaker? CORALINE: The Twitch thing is really interesting. Back in October, I started streaming in addition to everything else I do in my life—I'm a musician—and I started streaming, recording, and music production and I have a weekly show. You're right, the audience interaction is great and I incorporate that into my show. I'll stop what I'm doing after I finish laying down one track and I'll ask the people in chat, “What instrument should I pick up next?” Or, “What sound would you like to hear there?” Things like that. It does make that more interactive and it brings some of that human connection back and I think you're right. That's what's missing from a lot of these online conferences is that connection. CORALINE: Yeah, and I actually think you've hit on it right there with streaming. There's been a big question – I don't know how much you follow the CNCF, KubeCon EU talk acceptance drama that kind of popped off a week, or so ago. But the short version is obviously, KubeCon is a very prominent conference in the Cloud Native world and it gets a lot of submissions and because it gets a lot of submissions, a lot of talks get dropped, a lot of things get cut. That's every event; there's always more submissions than there are slots for people to speak, but it turned into a bit of a blow up on Twitter and they actually wrote a blog post that's very explicitly described again hey, this is how we pick these talks. There's a lot of factors that go into it. The thing that occurred to me and I've seen some people talk about, especially people that have been in the industry for a while is, what really is the benefit of a conference at all? When you have things like Twitch and you can build an audience for yourself and it's easier than it's ever been to get a platform. Some people in the world have used that for good ends and some people in the world have used that for ill ends, but regardless, I could go out and just say, “I'm not doing talks and I'm not doing conferences anymore. I'm just going to stream. I'm going to produce things and put them on YouTube.” The only reason you would be at a conference at that point is as like okay, this is a quality filter. These are some people saying, or suggesting that these talks, or these individuals have a higher value to the community because we got a bunch of people, smart people to look at it and say like, “Yeah, we think this one's better than that one.” But I really wonder if all of this with COVID, with the pandemic, with the change in…

    Full show notes at the publisher

    230: Using Tech + Policy For Good with Corey Ponder Apr 14, 2021
    Show notes

    01:55 - Corey’s Superpower: Empathy Finding Voice: You Are Not a Statistic What does it mean to support Black lives? Authentic Self Having Conversations Around Allyship Owning Vulnerability 09:06 - Having People Hear Your Stories “How are you doing?” “Me Too” Movement – learned something about self and blind spots in the process and the feedback was helpful 13:01 - Allyship Best Practices Growth Mindset Trusted Sidekicks; Augmenting Journies Invisible Knapsack: How to recognize your white privilege — and use it to fight inequality (Peggy McIntosh) 19:04 - Developing Empathy Watch Hamilton! When it comes to leadership, Aaron Burr was right — “Talk less, smile more” (Being Able to Hear vs Being Able to Listen) Deep Canvassing – How to talk someone out of bigotry: These scientists keep proving that reducing prejudice is possible. It’s just not easy. Google Assistant Research; Inclusive Design Empathy Mapping (From UX Design) – Building For Everyone: Expand Your Market With Design Practices From Google's Product Inclusion Team Empathy Can Combat Mis/Disinformation Fearing What We Don’t Understand: Nas - Hate Me Now ft. Puff Daddy (song) | Lyrics Active Processing (psychology) 36:03 - Using Tech + Policy For Good Educating & Empowering People Online Company and Community Values Pipeline Investment and Early Exposure Diversifying the Tech Policy Space / Manifestos? Algorithmic Justice League Virility Clubhouse Is Worth $1 Billion Off the Backs of Black Folks. Now What? Reflections: Arty: Centering around empowerment + asking, “How ARE you?” with the intention of listening. Chanté: We can’t outsource empathy. Corey: How the model of technology has shifted away from interest-based to follower-based and influencing. 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: ARTY: Hi, everyone. Welcome to Episode 230 of Greater Than Code. I am Artemis Starr and I'm here with my fabulous co-host, Chanté Thurmond. CHANTÉ: Hey, everyone and I had the great pleasure of introducing our guest of honor today, Corey Ponder. Welcome, Corey. COREY: Thank you. Thank you. Glad to be here. CHANTÉ: We're so glad to have you. If you don't mind, I'd love to read your bio so everyone knows who you are. COREY: Sounds great. CHANTÉ: Corey has over 10 years of work experience, he has had several roles across two industries and has also served in community organizations and nonprofits. At the core of each of these experiences is a passionate commitment to building community and developing people and programs. Corey most recently worked at Google serving as a senior policy advisor focused on privacy, advising product teams on best practices and approaches to inspire user trust. He also owns and manages his own business, em|PACT Strategies, a consulting firm that helps organizations build inclusive communities by prioritizing empathy as a skillset. Corey serves on boards of InnovatorsBox, a firm focused on creativity, and Youth Speaks, a nonprofit focused on youth arts and education. Great background. Corey, did we forget anything else? COREY: Well, I have to just because I am a lifetime SEC, Southeastern Conference, person, that I have to shout out Vanderbilt University, where I went for undergrad and then also, because I'm in California, I have to shout out University of California, Berkeley, where I went for my Master's in public policy. So those two things I would add. CHANTÉ: Those are great institutions for education. So good. Let's start off with the first question that we give everyone and that is: what is your superpower and how did you acquire it? COREY: Yes. I love this question. It gives me a chance to really nerd out. So I would say the first thing that comes up for me is empathy. When I think about empathy, I think about how superheroes, oftentimes exhibit qualities around being empathetic that we might look at as healing abilities, or the ability to regenerate themselves, or regenerate others, the stamina, or the fortitude, last, or survive in a space where there's a lot of things attacking them mentally and emotionally and able to persevere in spite of all of that. So I would say empathy is definitely the superpower that I have. I think when I step into spaces, I'm always thinking about what can I do to make other people feel more welcome, or feel more authentically themselves, which I feel like is the healing part. I feel like the regeneration piece is often me putting myself into positions where I don't like conflict, or seek it out, but I definitely feel like I put myself into spaces where I'm like, I want to support you and it might come at some risk to me, but I think I can bounce back from this. And then the stamina piece. I mean, none of this work, showing up for others even is not just a one-time thing and so, the consistency piece, I think, is something that I've really over time become more comfortable with just knowing that things might be protracted. People might need you for long periods of time and I'm here for it. CHANTÉ: So you said a few things here that really, I think, demonstrate the skillset for somebody who is in the diversity, equity, and inclusion space and I will bet that you probably didn't see that 10 years ago, or whenever you started down this journey. So if you wouldn't mind, I'd love to know how you got to this space now and I'll also add in, before you answer that question, that a lot of folks, BIPOC folks like us, we know what it's like to be othered. We know what it's like to be excluded. So I know for myself, I'm in the DEI space, but I'm just really curious. I did peek at your background, but just for folks who haven't or who don't have those quick fingers right now, they just want to hear your background, walk us through how you got here. COREY: Yeah, absolutely. So there are two inflection points. The first is I am a Black man so there are moments that I think about as a part of my growth as a Black boy and feeling like I had to grow up very fast to be taken seriously in whatever space that I was interested in to see the world from a perspective of hey, you really have to make sure that you're showing up and representing the person that you want to be because people will quickly ascribe something to you. This was a conversation that was permeating all around me so that when I got to college, there was an inflection point. The first one where I remember I was like, “I want to be a biologist and I might also go to medical school.” When I took lab for the first time, it was a moment where I realized like, oh man, despite all of the things that I have done, all of the things that are within my control, I studied hard. I was getting great grades. I was just woefully unprepared for that space of even just being in a lab and doing a titration. I was like, “What the heck is a titration? What is an Erlenmeyer flask?” I realized that in a lot of ways it was because I didn't have access to the resources, or the conversations, or nobody had even told me that I could do those things. I wasn't seen as somebody that could do those things and so it's like, I didn't know what I didn't know and I think that I really started doubting in many ways from that moment who I could be, what I felt like I needed to thrive in the spaces, what I felt like I was capable of in these spaces. It took me throughout college—great relationships and friendships, but also investment and resources around me to really find that voice that said, “Hey, actually, here's your story,” You're not this other narrative, this person that can't do it and you're not a statistic in a sense of a Black man that is x as opposed to a successful Black man. That was the first inflection point for me. Then I think the second was just having been at this point, maybe like 6, or 7 years working. I was at a moment at Facebook actually, where there was an increased conversation around what does it mean to support Black lives? Why are people talking about Black Lives Matter? In particular, during 2015, 2016, I forget specifically when, but Philando Castile and Alton Sterling were two Black men who were killed by police officers in different instances, in different cities, in different places, but within the same week. It was one of the first times that from a technology perspective, we were discussing this in an international way because it had been captured on Facebook Live. So there was this conversation around who are we as a part of this broader conversation? It was the second inflection point because it reminded me that was man, I am a Black man so even as I've done all of these things, I've been in careers, I've had these jobs and these opportunities where I've done things that I can be proud of, I'm still walking into this space the next day, after hearing about these instances and really feeling like I'm carrying something that I don't know how to speak to. I don't know how – I've never really talked to anybody about how it impacts the way that I am showing up in this space. So from there, I just made the commitment where I said, “I'm going to start trying to be more authentically myself. I'm going to start talking about all the parts of me that make me who I am.” I didn't have a plan for it; I just knew that I wanted to have those conversations. The interesting thing was I started having those conversations and people naturally, after I would talk to people, would say, “Well, what's next? What can I do to support you?” It really just made me think about the broader conversation around allyship. There's a broader conversation around what does it actually mean to show up for somebody and then I realized retroactively that there have been many examples, not only in my life, that people who have shown up for me that now I can pinpoint and look at as case studies, as data points, but also that I have naturally gravitated to doing that because of what I said earlier about the superpower of empathy. It has been something that I had always valued, even if I didn't know what it was, or what I was doing, or what it meant, but it was really important for me to see other people's stories because I knew how important it was for people to see mine. So those two inflection points really shaped how I viewed diversity, equity, and inclusion in my role, in the broader conversation. One, my own vulnerability with myself, but also two, how valuable it is to have people hear your story and validate who you are and your experience and how it's a part of a whole and how they see you. CHANTÉ: Yeah. ARTY: With stories like you mentioned being able to have this experience where you really understood what it meant to show up for someone. COREY: Yeah, absolutely. I'll give two stories. One was actually when someone showed up for me and I remember it was my boss actually shortly after the conversations, or at least what I mentioned earlier about Philando Castile and Alton Sterling. I just was having a really rough, it was a rough day. I mean, I was trying to show up business as usual was very much like, well, I have a job, I have meetings I have to go, and my boss asked me, “How are you doing?” That's a question you hear maybe a hundred times a day and it's also a question that feels like a rhetorical. I mean, you're supposed to say, “Good,” and keep it moving. I said that, but she really stopped me, told me like, “Hey, I'm asking because I really want to know and I have time. How are you doing?” I think just in that simple moment of making the space, creating an avenue for me to actually express a real truth, it just made me feel like wow, you didn't have to listen to my story. You didn't have to consider that I was something more than this a meeting I had to go to, or that I was more than this deliverable, or this project that I was working on. And you did. That meeting was, I, even years later, still to think about it because it was just like, wow, that meeting didn't have to happen that way. But I felt like this wasn't just my burden to bear after that question, or that conversation. The question that she asked and the conversation that followed. I think for me, showing up for others actually has been in this work—working through impact strategies and thinking through how do you actually show up as an ally. I've had a number of experiences. But in particular, there was one right around the decree, I would say the resurfacing of the Me Too movement and that conversation around sexual harassment in the workplace. There was an event, or a town hall, or an opportunity where I had a chance to really show up. I initially—and this is also a part of the failures piece—showed up to that very equally with the best of intentions and said, “Hey, what can I do to move this conversation forward?” Along the way, I remember realizing that oh man, in all of my eagerness to show up to this, I actually have silenced, or not included the voices that were probably most important to actually have this conversation. Women in particular, but also just thinking about in general, people who are survivors, or have been a victim of assault. So it was one of those moments where I took on feedback from people, some of my coworkers, colleagues, friends, I figured out a way to revamp the event, postponed the event so that I could do it the right way. And then I remember in the aftermath of that, seeing I learned something through that process about myself and also, the feedback that I received about the event afterwards was like, all right, this was a conversation where it really prompted people to think about a story that they haven’t thought about before—people who showed up to the event. Because I was helping organize it, showed up, and got something else out of it because I wasn't the only voice in the room. It was another moment where it was like, wow, this isn't necessarily my story, but I leaned in a little bit, or leaned in a lot in the beginning, learned a lot in the process about myself and even where my blind spots were within that entire process of learning in some ways helped tell a story that other people realized like, oh, wow, thanks for helping me see this narrative. CHANTÉ: That is so helpful. I feel like the times where I've had to show up as an ally and lean in to something that I didn't necessarily understand, really helped me to better articulate the needs I had as a Black identified woman, or as a Latino woman to say, “Hey, friend or colleague, you want to show up and help me. This is how you can help me,” Because I've learned from my own ouch moments like, oops, I shouldn't have done that and thankfully, somebody was gracious enough to share feedback in that moment, but many times, they're not. Do you have any best practices in terms of folks who want to show up, especially right now in this year, as an ally, they're very well-intentioned, well-meaning people, but they don't necessarily have somebody like an insider to give them the lay of the land, or to tell them where the real pain points are? COREY: Yeah, absolutely. Two things. The first thing is that to your point about the feedback, I think feedback is so critical and also, we have to recognize that for many communities, like you said, we're in the intersect. We are at the intersection of a lot of identities. I recognize that…

    Full show notes at the publisher

    229: Union Organization with Melissa McEwen Apr 07, 2021
    Show notes

    02:21 - Melissa’s Superpower: Being Extremely Online 03:06 - Unionizing Glitch Glitch workers sign tech’s first collective bargaining agreement Misconceptions re: Unions Engineer Salary Discrepancies Middle Management, Product Management Unionization Minority Unions (i.e. Google) What is a Minority Union? [The Rise of Minority Unions: How Social Movements and Tech Giants Could Be Showing Signs of Things To Come](The Rise of Minority Unions: How Social Movements and Tech Giants Could Be Showing Signs of Things To Come) 14:58 - Melissa’s Previous Experience with Working w/ Unions Communications Workers of America (CWA) Civic Technology (What Is Civic Technology?) Chi Hack Night 17:13 - Positive Skills Union Organizers Should Have 18:32 - Thoughts on Leading with Petitions We are Frank — a platform for worker voice 2018 Google Walkouts 26:58 - Writing Online; Dismantling Publications and the Fracturing of the Media World The Rise Of Substack—And What’s Behind It Melissa McEwen: The best JavaScript date libraries in 2021 29:41 - Evaluating Human Performance PSA: DevRel isn’t fake !! How to Hire A-Players: Finding the Top People for Your Team- Even If You Don't Have a Recruiting Department People Skills 43:21 - Getting Started with Organizing a Union Use Signal, Not Slack Be Harder to Fire Reflections: Casey: Hearing success stories re: unionizing. Jacob: How people skills can be a function of your individual team. Melissa: Studying more about unions in other countries. Rein: Looking more into co-ops and collectivisations. An injury to one is an injury to all. 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: JACOB: Hello, and welcome to Greater Than Code, Episode 229. My name is Jacob Stoebel and I’m here with my co-panelist, Casey Watts. CASEY: Hi, I'm Casey. I'm here today with Melissa McEwen. Melissa is a web developer, working in content now. She often writes about the JavaScript ecosystem. She helped unionize Glitch, which recently signed their first Collective Bargaining Agreement in late February. Welcome, Melissa. So glad to have you. MELISSA: Hi, everyone. CASEY: We like to start each show by asking you a certain question. Melissa, what is your superpower and how did you acquire it? MELISSA: My superpower is being extremely online and I acquired it by being given computers way too young and having nothing to do, but play with computers. CASEY: I like that phrase “extremely online.” What does that look like today for you? MELISSA: It means, I know way too much about what's going on in Twitter and the internet in general and sometimes, I'll make references that you only know if you're extremely online and it's kind of embarrassing. I don't even know what it's like to not be extremely online, but I'm trying to stop being extremely online because it's overwhelming trying not to check Twitter every 5 seconds. CASEY: Oh, yeah. I did that a lot, too. I don't know if I would describe myself as extremely online, but I might have seen some of the same memes as you and I think that would [chuckles] give me a little bit of that. MELISSA: Yeah. I mean, memes, what's the latest drama on Twitter today, that kind of stuff. JACOB: Is there a way to turn that superpower and help people around you or, how do you leverage that? MELISSA: Yeah, the only thing that's good about it, I would say is that you know a lot. I try to write about things and provide my knowledge to other people. I mean, you know a lot, but on a surface level, that's the problem so, you have to always be aware of that. I'm not an expert on unions and for the Glitch union, I was one of the original organizing committee folks, but I was laid off last year in March and there were 18 people, I think laid off. So the union has been going on without me and that's just great. Me and some other externally online people, when we started the union, we leveraged our externally onliness because we were connected to a lot of people who helped us like the CWA, which is the Communications Workers of America. We found them online, for example and they were critical in getting the union actually started because we'd been talking about it, but they were the people that pushed us and they're one of the bigger unions. They've been around for a long time. They have an organized telecommunications workers, primarily and now they're doing some tech stuff. So very interesting. JACOB: Well, as someone who is moderately online at best, I have been reading a little bit about recent union news with Glitch, but I would love to hear your story about how it started and how it brought us to today. MELISSA: Yeah, I mean there's only so much I can say, but the stuff that really was – building a union is about connecting with your coworkers and a lot of people have said, “How are we going to build a union to the remote workplace?” Well, I was remote and half the company was remote. That's one good thing about being extremely online is you’re probably used to talking to people online. I connected to people in my workplace and people on my team. At first, it was mainly people on my own team and then what CWA teaches you to do is to build connections in your workplace. It's almost like you map it out and you talk to other people in your workplace and you try to leverage those connections. I wasn't connected to everybody in the workplace, but I was connected to some other people who were connected to people I wasn't connected to. So it was challenging in that this was not an office where I could go see these people every day. I had to kind of – you can't just sneakily invite someone to a call unionizing. You have to actually build social capital and build relationships and then turn those into those connections you need to build a union. A lot of us had been following union stuff in tech. I was a member of Tech Workers Co, I think others were and we thought since Glitch is a very diverse workplace, we want to make sure that workers have a seat at the table and can actually help each other and to help the company do right by the workers. We had some bumps along the road. It is hard to organize people remotely and a lot of people have misconceptions about unions. They think unions are only for certain workers like people working in a mine, or they have bad impressions of unions. Like, I don't know. I grew up and my parents were like, they told me that unions were bad. We watched On the Waterfront and they were like, “Oh, look, unions, they’re so corrupt.” But a union is just like an organization. It's a big organization and they have a history and they have a context and a union is just like anything. Like a company. It can be bad; it can be good. It's based on the people and once you join a union, you can help guide that union by being part of it. JACOB: I would think an extremely online person would be very good at that. MELISSA: Yeah, it did help to be constantly on Slack and on Twitter. JACOB: And good at really just making those connections. That would not come naturally to make all those personal connections, what you just said. MELISSA: Yeah, but also, it was. I do think people who had those real life – who were at the office did have an advantage in forming those connections because not everybody at Glitch was extremely online, for example. Also, meeting each other in real life, occasionally like, we'd go to the conferences and stuff, that really helped. It's complicated about how much organizing you can do in the workplace and at what times. You don't want to ever do it on times are supposed to be working, for example, so. CASEY: What were some of the things that made this unionization effort successful and possible and what were some of the things that got in the way? I think we've covered some already. MELISSA: Yeah. I think having a pretty social workplace, that was social online, but that doesn't include everybody. There’s some people who were more online than others, for example and the fact that we relied so much on online organizing, it was harder to reach those people. So it was very crucial that we have people in the New York City office who were able to do some on the ground in-person organizing and getting those people on board was like, once we got those people on board, that was a very important thing that we did. Because originally, it was all remote people and then we added in the New York City office people. Yeah, the bumps along the road are just misconceptions about unions, what they mean. People can union bust themselves just by having these misconceptions like, “Oh, union is a third-party. It'll affect my relationship with my manager. I can't be friends with my manager anymore.” It's not true at all. So some of the organizing committee had been in unions before. Like, there was one woman, who was a social worker, who had been a social worker union and I had been in a Civil Workers Union before. So I knew that I was friends with my managers in these unions and I mean, not that being friends with the manager is the priority, but the idea that if you're friends with a manager, you can't do a union. That's just not true. But some people thought that. CASEY: The biggest misconception I can think of is why do you well-compensated professionals need a union and I'm sure you've heard this all the time. MELISSA: Oh yeah, that’s a big one. CASEY: Yeah. Fill us in for that. Like what do you say to that? MELISSA: I think so. Online, someone was like, “Oh, it's cultural appropriation of blue-collar workers.” I do not agree with that. I think all workers benefit from a union and it is just an organization that allows workers to negotiate with their bosses and on a fair playing field. It's not a culture. You don't have to be in the movie, The Irishman, or On the Waterfront, or even know people like that. It's just a way of organizing a workplace and having a seat at the table, so. JACOB: You mentioned earlier that I think, or maybe you implied that this union joins multiple disciplines, too. Is that true? MELISSA: Yeah, like we had engineers and then we also had a media department. That's where things would be hard because a lot of workplaces are quite siloed and I've always been against that. Like, I hate the term non-technical for example, like video production people, those are the most technical people I know they're literally working with like technical equipment every day and they know so much about it. Those people are tactical. And then another big obstacle is who is eligible for a union? Who can join? It's not clear because tech has roles that aren't very traditional, like product manager. Is that a manager, or is that an individual contributor and often, that’s hashed out on the negotiating table. It's based on all these laws and I've read some of the laws, I'm not an expert, but it's good to read a little bit of the labor law just to understand. But even if you know it, it's interpreted differently by different courts and stuff. There's a National Labor Review Board that reviews labor disputes and stuff and that was Trump's appointed board. So we wanted to make sure we got a voluntary recognition because we didn't want anything to do with that board at that time because they were very hostile towards workers. JACOB: The reason I was curious about joining together all kinds of different people from different roles, I was just curious if that diverse workforce came with a diversity of priorities and goals for a union and if those presented any challenges. MELISSA: Yeah. There's a big class difference between engineers and people outside of engineering. Engineers are overwhelmingly paid higher than people outside of engineering, for example and I totally understand the resentment towards engineers. We need to acknowledge that if you're organizing multiple people and outside of engineering. I mean, the fact that engineering is so well-compensated. I don't understand why, for example, a video producer isn't compensated the same as an engineer. It's just an accident of history, how culturally valued, supply and demand, all these things mixed up together. So you have to realize that and when it comes down to money, paying dues. For an engineer, it might be like, “Oh, you're taking 1%, or 2% for the union,” and that's like, “Oh, that’d take you away from being able to go on vacation.” Whereas, for someone who is making a lot less, that's taking away from their ability to pay rent. So that is really, really hard and I don't have a good solution for that. I wish unions would offer things like maybe peg it to your income, maybe not, maybe at a lower percentage, but it tends to not be that high of a percentage; it's 1 to 3%. But acknowledging that that can be the difference between someone being able to afford or not. Especially the salary ranges were quite extreme in our case so, that was really hard. CASEY: I'm listening to this conversation based on my background as a product manager who happened to have managed engineers, designers, and product managers, I don't know how that structure came into play. But even that tier, I wanted to be part of a union, but I think it's US law maybe that gets in the way that says managers at any level can't be unionizing in any form, not even like—let's use a synonym for a union—collective people who tell each other, “Yes, you deserve more money,” or something like that. It's not we're not incentivized to work together in any way and we pretend that the HR department of the company does that for us, which they do the opposite often. What do you think about that middle management kind of thing and how it plays into product management? Your thought process? MELISSA: Yeah. That really sucks because then it becomes like some people feel left out who wanted to be part of the union and at that point, they feel like, “Oh, am I part of –?” Like, they're obviously not C-suite so that's really hard. Other countries have other types of unions like sectoral bargaining that get around that. I don't know that much about that, but we weren't sure if a product manager fit under the definition of qualify, or not. It just depends on if you make decisions on employment, if you tell people what to do, there's a lot of criteria. We did find that product managers were not going to be part of the union. So what does the product manager do? Well, they can't organize themselves, but they're just not legally protected under this bargaining thing under a labor law. So that really sucks and I don't know what the solution is. I guess, getting involved in bigger organizations that work for unionization. The Google union is very interesting and that is a different form of union. It's called a minority union and I don't know that much about those, but I know that people who are managers can join that one, but it has fewer legal protections. So I assume when CWA decided to organize Google under a minority union, it was because they felt they were not capable of doing the traditional union because there are so many obstacles to doing so in Google—Google’s size and multiple locations. It's very difficult. You can organize however you want, it's just what is legally protected and that kind of goe…

    Full show notes at the publisher

    228: Career Snarkiness – Words Hold Weight with Corey Quinn Mar 31, 2021
    Show notes

    02:21 - Corey’s Superpower: Reading 3,400 WPM Increasing Reading Speed 05:35 - Keeping Up w/ AWS Last Week in AWS AWS Morning Brief Screaming in the Cloud 08:45 - Delivering Corey Quinn – Personal Evolution Speaking Truth to Power (Kindly, but Snarkily) Privilege Sonia Gupta and Corey Quinn - Embarrassingly Large Numbers: Salary Negotiation for Humans Holding Yourself Accountable Defensiveness This Cloud Computing Billing Expert Is Very Funny. Seriously. (NYT Article) Intentionality 25:51 - Career Snarkiness @SimpsonsOps @killedbygoogle 28:05 - Approaching and Handling D&I as a Business Owner Discussing Salary Compensation 43:44 - Making and Delivering Jokes 45:08 - The Prospect of Being a Public Figure 50:03 - Recognizing Your Own Failure Mode The Art of Delegation 54:32 - Approachability Admitting Mistakes What’s the point? Reflections: Rein: Systems derive their purpose from how they relate to larger systems. Tim: Iterating on oneself to become a better person. Becoming a human optimized. Arty: Holding yourself accountable. Taking responsibility for how other people see you in a public context. Mando: There’s a power in not hiding who you are. Apologizing for not letting people know what’s going on. Corey: Words are loud. Words are heavy. Words carry weight. Words carry impact. There is a balance. 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. ARTY: Hi, everyone. Welcome to Episode 228 of Greater Than Code. I am Artemis Starr and I am here with my fabulous co-host, Mando Escamilla. MANDO: Thank you, Artemis. I'm delighted to be here with my good friend, Rein Henrichs. REIN: Thanks, Mando and I'm here with my friend and brand-new co-host, Tim Banks. TIM: Thanks, Rein. I am Tim Banks and I am delighted to have our guest for this show, Corey Quinn. COREY: Thank you. It's an absolute pleasure to be here to once again, indulge my ongoing love affair with the sound of my own voice. TIM: Just so everyone knows, Corey is the Chief Cloud Economist at The Duckbill Group, where he specializes in helping companies improve their AWS bills by making them smaller and somewhat less horrifying. He also hosts the Screaming in the Cloud and AWS Morning Brief podcasts; and curates Last Week in AWS, a weekly newsletter summarizing the latest in AWS news, blogs, and tools, sprinkled with snark and thoughtful analysis in roughly equal measure. COREY: I would agree that that is a fair characterization of what I do. Excellent work. Thank you. MANDO: Corey, we like to start off every podcast with asking our guests kind of the same question and that question is what do you consider your superpower to be and how did you get it? COREY: I would consider my superpower to be the fact that as tested and certified by some random site on the internet, I read 3,400 words a minute and the way that I got there was growing up, most people have friends, I had books because of the wonderful thing that happens in my world namely, having a personality that is pretty obvious to anyone who's spoken for more than 30 seconds. In my early phases of my life, this didn't resonate super well so I turned to escapism in the form of reading. Later in life, this turned into something of a superpower when you're trying to do something like, I don't know, read every release that comes out of AWS in a given afternoon. MANDO: Yeah, that'll do it. [laughs] REIN: There are so many. MANDO: I went to a private elementary school for a year and one of the less weird things that they had us do was do speed reading training. They had this little cylinder and you would feed in a piece of paper and the cylinder had room for, I don't know, 8 to 10 lines of the paper and it would scroll automatically at a certain rate and you would read the story and then take a test afterwards and then as you pass the tests, they would both speed up the cylinder and then also shrink the amount you could see at one time to point where it got to just reading line by line and this thing's scrolling superfast. It was really weird and really struck my competitive juices like, I really wanted to show the teachers that I could read as fast as possible. So that's the one thing from that weird private school that I went to that I think has had any sort of payoff in my adult life. COREY: There are a bunch of tools and techniques that people can use to increase reading speed, and I've never done any of them. I don't know how I do it, I just do it. It's easy to sit here and think that, “Oh, I'm going to read super quickly. That's a superpower. That's something I can use and leverage, too,” and then what? The skill, or the talent is necessary, but not sufficient the way that I do things and you have to refine it and apply it in different ways. Sitting here and doing it as a spectacle or sport on a conference panel or something and look at how fast I can consume information, not much of a party trick. Using that and applying it to something that for, in my case, distilling vast quantities information down in an understandable and meaningful way, that was the outcome. It was never about just “being smart,” which is how I often hear other folks talking about various superpowers. “Oh, I have a natural innate intelligence.” Great, what do you do with it? How do you apply that? That's the thing that often gets overlooked; at least by folks in a somewhat early stage of the development that they're dealing with professionally. REIN: So let me ask, you do the Last Week in AWS podcast, why do you give a shit about that stuff? COREY: Functionally, what I do and what I started doing when I started The Duckbill Group, it was understanding the AWS bill so that I can reduce it. Sure, it's easy to do that from a pure numerical analysis perspective and figure out oh, what reservations, or commitments you can use. But a lot of it required insight into what the application was doing because the worst consultants in the world are the ones that walk in, look around, have no idea what they're looking at, and then start telling you that you screwed everything up. That's not helpful, it's not compelling, and it's the sign of a terrifically awful consultant, in most cases. I see something that looks like it's ridiculous, my first question is: great, can you help me understand this? I don't tend to, by default, assume the person I'm talking to is a moron and similarly, I had to understand the various economic impacts of different capabilities, features, and services. They're changing all the time. I had to keep up with this stuff so I shoved a bunch of things into my RSS feed and I was tracking this because there was nowhere else to do it. That got me 80% of the way there to being able to share this with the rest of the world. I figured, ah, I can make other people do my work for me. I figured I would launch a newsletter, run it for a few weeks, someone would chime in, “Well, why don't you just read, insert other thing here?” and then great. I can turn off the newsletter. I found the thing that does this for me and I can focus on other things. Instead, 550 people signed up for the first issue and it's been growing ever since and it turns out that thing that people should read to solve this problem is the thing that I built. It still surprises me and the reason I care about it all is because my customers need to know these are the things, but they don't want to read all of it. They don't want to know all of these things. They want to solve their problem. REIN: It seems relatively easy for a consultant to go in and say, cut here, trim there, and then you'll get 20, 50% off of your AWS bill. But isn't the thing that you want for the people who will be there long after you're gone to be able to make better decisions about their own spend? COREY: One of the nuanced areas of what I do is this idea that, “Oh, I'm going to come in and lower your bill,” That virtually always happens, but that's not the actual goal. The goal is to inform the business so that they can make decisions around managing spend, managing capability, and managing risk. In some cases, we suggest spending more on certain areas such as, “Huh, you claim that that thing is an incredibly critical to your business set of data and you're not backing it up anywhere. Perhaps, you should consider doing that.” It's the idea of doing the right thing, not the cheap thing. It's we don't ever charge for example, by percentage of savings, or percentage of bill, it's flat rate only because once that's done and we agree on what that rate is, there's no other conflict of interest. I'm not trying to rack up savings to claim a percentage of it. I have no partnerships with any vendor in the space, so I'm not getting a kickback if I say, “Oh, use this tool or that tool or that service.” Instead, it purely reduces me down to, “This is what I would do if I were in your position, take it or leave it.” TIM: So I think Corey, it's fair to say that people recognize your expertise, both in optimizing of costs and optimizing the practice. Writing good tools, adopting best practices, having sound resilient architectures, and saving money. But it's also fair to say that that's not why people follow you. You have a voice and a particular way of analyzing things that appeals to people. Snark has its place and it's very well-placed in your commentary, but what it mostly involves is true insight. So can you give me the story behind what really empowered you and made you comfortable in delivering your full Corey Quinn to people in an industry where maybe people aren't really supposed to be their whole selves? COREY: My entire career, I had a core competency that I was always the absolute best in the room at, across the board and no one could step to me as far as being good at that thing and that thing was getting myself fired because of the things that I said. My entire career, every boss, every mentor, every teacher, every family member, every vague acquaintance that I pass on the street has given me the same advice: “Your sense of humor/personality is going to hold you back in your career.” When I started this place, I was so tired and beaten down from hearing that, that I figured that either everyone I've ever spoken to is right and I'm wrong, or I'm right and they're all wrong. And with the confidence born of being a mediocre white man in tech, I figured let's try it and see. Because worst-case, if the whole thing blows up in my face, well, I can go back to using my maiden name professionally. I can effectively shove the Corey Quinn identity as it is down the memory hole and I can go back to being an unhappy employee somewhere else. It started to resonate and it took on a life of its own and for the first time in my entire career, I don't feel like I have to hide who and what I am and that is a powerful thing. TIM: So one of the things that I think people appreciate, especially in your very active and humorous Twitter feed, is saying the things that everyone is thinking about the Giants. You speak truth to power, but you do so in a manner that does not insult nor mischaracterize the people who make the technology, who make the decisions. Can you talk to us a little bit about how being kind while still being somewhat snarky guides – what's your thought processes and how does that guide your commentary? COREY: You say this like it's a done deal, but it's very much not. Earlier, the week that we're having this recording, I wound up doing a snarky, sarcastic rebuttal of the profile of me that appeared in the New York Times in the voice of AWS. I made some snarky offhanded comments that implied basically that AWS marketing was crap and I heard from several people inside that team that, that they thought that hurt them and to be very direct, I got that wrong. If people are hearing what I have to say and feeling bad about themselves, about their work, then I've gone in a wrong direction. It's a very fine line to walk, given who and what I am, but when people see what I have to say and hear it and they walk away hurt, I failed. I don't always get it right, clearly. All I can strive to do is be better and not make the same mistake twice. It's a constant process of evolution and learning. And to be very direct, I am incredibly grateful by people feeling that they have the psychological safety to reach out to me and say, “That hurt my feelings.” MANDO: One thing that I've seen you do, Corey, as an accessory to that is be on the lookout for people who maybe don't feel that same kind of psychological security, but also feel some, or have some negative impact, or connotation with what you said. I've seen this a couple of times. I saw it once this week, when you were talking about – you had a Twitter thread talking about how to find a job in tech, how to negotiate salaries and stuff like that. And then there was a Slack group that we're both involved in and someone made a comment saying that they felt put out a little bit by the tone of what you had said and I personally found it impressive and a little bit inspirin, the way that you responded to that individual. Would you mind building on that a little bit, why you think that's so important and then how you address and maybe manage those kinds of situations? COREY: Sure. Privilege is a funny thing because we all swim in it in various ways, no matter who you are or what you do, there are elements of privilege that are inherent to you based upon aspects of your life and to you. That's not something that you're generally aware of in a conscious sense. Instead, it's very much a part of the background of your own lived experience and it's difficult, at times, to put yourself in the shoes of people who have different stories. The natural response, in some cases, when being told about privilege is to push back, “Excuse me, nothing was handed to me. I had to work and build this thing and sure, maybe that's true on some level, but you did not have to deal with a headwinds against you that a lot of other people did.” And there is an element of, “Well, I was born on third base. I didn't hit a triple.” Yes, that's true. It absolutely is. But you still got to go from third base to home on some level. It's easier than someone who's starting off on home and having to round all of the bases and there's still work that has to be put in. But…

    Full show notes at the publisher

    Previous 1 3 4 5 6 7 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