Episode 11: Kim Maida  [music] Welcome to Community and Code, the podcast about the people, the human beings behind the commits. I'm here today with Kim Maida. She is a senior director of developer relations at Fusion Off. uh welcome to the show and tell us a little bit about yourself. >> Hey Chris, thanks uh and thanks for that introduction. Um I guess uh [laughter] where to start? Like you said um I've I've actually been working in identity for a little while. I've also worked at Ozero and Octa um as well as on Devril at various other startups in between um and I kind of had always found myself gravitating back to identity. So I think recently I finally made the decision of this is my career. I will probably be working in identity for the remainder of my career after kind of yo-yoing back and forth a bunch from it. Um >> yeah. What what is it for you about like identity management authentication type stuff that is interesting? I think for me and probably for a lot of developers that's like the thing that we want to think about the least. >> Yeah. Yeah. Well, I like I like being the person who thinks about it so that other people don't have to. >> Um I like there are plenty of things like that for me like DevOps. Like I know enough DevOps to be dangerous because I had to learn it in order to like operate my Digital Ocean VPS. >> But it's it's just really not my thing. Like I'm not good at it. I don't retain the information. Um I had found that with identity and access management like I do actually retain the information. Um and I like being a a part of critical infrastructure because everybody needs it. It's one of those things that no matter what language you use, no matter what stack you're using, at some point you're going to come across a need for O in some way. And so it, you know, some of the other jobs that I've had were very specific to like a certain language or a certain framework and and you know, it was it was a lot of like people love this thing. They want to showcase what they've done with it. And interestingly, like when I I actually started my Devro career in O. So I hadn't kind of experienced things out communities outside of that community before. And then when I did I, you know, initially I had been like, "Oh, it'll be, you know, it'll be awesome because there's, you know, hundreds of thousands of people are really excited about this thing. Um, they want to showcase their knowledge." And I, what I found was I I just didn't find as much um like critical meaning in it for me. Uh, like it was great to help people use things they already loved and already cared about, but that criticality was gone. um the the sort of idea of if you get this wrong, you will be in big trouble. Like you could potentially have a huge disaster on your hands if you get it wrong. And I think that kind of pressure is something that I really enjoy being in a space that has that around it >> because I do not think that everybody should become an off expert. I don't absolutely don't think so. Um I think that >> because I don't want to. [laughter] >> Yeah. most people don't want to be. Um, but that's, you know, that's why tools exist. But also, there's, you know, certain things that you should probably understand in order to be competent. >> And there's a significant difference between like knowing everything and knowing enough that you're confident that what you've done is secure and that you've done things right. Um, and I like kind of trying to find that balance of confidence where people can be sure that they can have faith in what they've done so that they can move on and not have to think about it anymore. Um, versus like here's the oath spec read it from beginning to end like >> right. >> Yeah. taking a a little bit of a step back I think um I want to get dig into your history a little bit more but like just from like a big picture like from the perspective of somebody who maybe isn't a developer who like is listening to this or or who you might just encounter you know wherever at a conference or or even just in person like in in like the line at the coffee shop like when you talk about what you do or what like the practice around uh what what you do and talk about um in your role in developer relations like how would you break it down to like like the the explain it to me like I'm five sort of uh prompt you know like what what is what is the the highlevel like definition of of what what it is that you are trying to get people to do. Um, I guess I think there Let me unpack that a little because I think there were a couple [laughter] questions in there >> probably. I have I often do that is just like slide five or six more questions into one question. Yeah. >> Okay. So, maybe if we back up I think like the initial question was um kind of and explain like I'm five. What do I tell people my job is? >> Yeah. Yeah. >> Yeah. Um, so for people who don't like relatives and family, friends and and people like that, I basically say, you know, when you get online and you need to log in to a website or something, like that's the service that my company provides. >> That's fair. >> And and then I usually get a bunch of questions about like why do why does everybody have MFA? Like why do I need this thing? Um, but it's that usually leads to further interesting conversations because, you know, then you can explain like why >> there are, you know, these additional security precautions for like your bank versus um, you know, I don't know, like making a reservation at a restaurant or something like that, >> right? Yeah. Yeah. Yeah. >> So, >> it's Yeah, that's basically what I tell. And then as far as like I usually don't go as far as like defining authentication, authorization. Most people, like you said, like [laughter] most people aren't really interested in that level, right? >> Um, but, you know, if if I do, then I basically, you know, would say like authentication is proving who you you are who you say you are and then authentication is what can you actually access? >> Yeah. >> What can you access and do? >> Yeah, that makes a lot of sense. Um, and you're at Fusion O and you were formerly at uh Ozero and Octa and those are, you know, from from where I stand in the tech world, like Octa and Ozero are kind of big pretty big players in this space. Um, what was interesting to you about Fusion Off specifically? >> So, I actually joined Ozero when they weren't a huge player in the space. Um, I think I was like employee number 150 or something. uh and I got to experience kind of that startup rocket ship phase and that was really exciting to me. It was it was my first time working at a startup. Um and it was we were moving fast and we were breaking things and we were trying to break into like the IM industry to become what they have become now. you know, which is I I think it's awesome that that they've succeeded to that degree because I remember when nobody knew who we were, [laughter] >> right? >> Uh at while working there. Um, and I think that the thing that really excited me about fusion off, there's a couple of things, but one being the start I like working at startups and I like working at startups that are at, you know, roughly this stage because you everybody makes a huge impact [clears throat] >> and that was kind of one of the things that going to bigger companies and then working at corporations, I I felt like I could probably make an impact, but it was going to take me like two or three years to do it. And at a startup, you can really you can really make and show that impact quite early and everybody can do it. Like anybody from IC all the way up to, you know, like VP um can have that impact and show it and everybody can recognize it and see and you can see what you've done for a company. And I think that that kind of more instant gratification is something that I really like at work about working at smaller companies. Um and then like why Fusion Off uh especially after working for other other id companies. Um, one of the first questions that I asked uh when I was approached about the role was what makes Fusion different because I think after after Ozero got acquired for $6 billion, [laughter] there were a lot of id companies that popped up, right? And there's way more of them now than there were when I was at Ozero, like by far. >> Um, and so they all kind of do the same thing, right? And right >> so you know my first question is why why fusion? Why are we different? >> And really it comes down to we're downloadable. >> Okay. >> And so you can run the fusion authorization server as a part of your core infrastructure. And the advantages you get from this as far as like security and and the ability to own everything and to end are often things that you would like when people care deeply about that um like if fusion didn't exist they'd usually be reaching for like open source solutions like key and that type of thing. Um, and I thought it was really interesting and differentiated that we do onrem for free. Um, if you want to have an on-prem conversation with a lot of these SAS companies, that's, you know, locked behind a big sales call and it will cost a lot of money, >> right? >> Um, >> but yeah, so we also have like a cloud offering, but it's single tenant. So you are the customers who are on the cloud don't share infrastructure with the other customers >> right >> um so it's dedicated instances yeah >> which uh I think is also cool but for myself I'll probably always just download Fusion whenever I need off like into the future >> because it it was one of those things where I didn't realize how much I liked that like owning it >> until I actually had it like running on my machine >> and I could put in like a config file and spin up a new environment like really quickly. I could make changes to the environments and you know do all of this transferring of of configuration and and things like that >> that I just like wouldn't have been able to do with a SAS product. Mhm. >> Um and that that level of ownership like there is a movement out there, you know, in general the local first stuff where people, you know, are really focusing on what can they own and run. Um and I hadn't really been, you know, part of that community. Like it wasn't necessarily something that I thought too hard about. Most of the companies I worked for were SAS companies. Um, so I didn't I think realize how much I would like it >> once I could actually like own and and control this thing that also is being governed by a body of people who know really well and will make sure that you know nothing bad is happening. Whereas you know when you uh implement homegrown you're you're kind of at the mer of your own knowledge. Uh, so you could have it was like you could have the local thing, have your cake and eat it too, which which I definitely appreciated and actually hadn't used an a solution that did that before. Yeah, I was actually just like thinking about how like if you for any SAS product that's that you're integrating into your site or whatever like if it's just if it's hosted somewhere then if you're working locally you have to figure out some way of like either authorizing that local connection or like figure out. So it'd be it'd be a huge benefit to just be able just for local development and local testing uh to be able to stand it up uh on your own thing or like inci like >> just like multiple environments like any anything like that and and like the I think the configuration thing is something that maybe at Fusion we don't talk about enough. >> Um you can have this configuration file called a kickstart and it's basically a JSON file that makes a bunch of calls to the API. um when you run it. So you can put in like a custom theme, you can have it create specific users, you can have it create uh applications with a specific ID. Um it basically anything the API can do you can put into the kickstart and it will do it for you automatically like as soon as you spin up as soon as you like run Docker Compose. >> Um and so you can duplicate environments extremely easily that way. Um, and you know, change things that that make a change, an environmental change that then you can just give everybody that kickstart file and and a bunch of people can can have the same config like in a couple of seconds. >> Yeah. >> Um, and that was something that especially like for me in DevO like creating demos and that type of thing instead of having like this huge long setup where like first you go into apps and then you have to copy and paste this this client ID or whatever. Um, I I can just set all of that up for you and you can like be productive right away. >> Which I love. But it was also funny because when I first started at Fusion, the very first time I used it and it ran a Kickstart and I was like, "Oh my god, a bunch of things just happened magically." [snorts] Like, "How do I have all this stuff set up?" Like, I didn't know where it came from. Um, I think just because we don't talk about the Kickstart very much. Um, but having, you know, done a bunch of things with Fusion off now, I I really like it's it's one of the highlights [laughter] for me of set of the setup process is having the ability to do that. Um >> yeah, >> we give full access to the API. Like developers can access anything in the API >> and that's part of like the role that we play in Devril is is like when a magic thing happens like demystifying the magic part like like like yeah it is magic but also let me tell you let me walk you through all of those uh all of those things that just happened that made the magic that you're seeing so that you don't have to worry about these things. >> Yeah. Yeah. And I think that's that's kind of like the philosophy around how I think about teaching people stuff about Oth. Um I know for me like probably the first example of something that I was like this is a black box and I really don't understand it was Jason Web tokens >> like how they're signed >> and and that part was like every article that I ever read was just like and then you sign it and magic [laughter] and I was like but what's happening like and it was that mean? What does those words mean? >> Yeah, but it was it was interesting. Um because it's not that I wanted to do it myself, like I didn't want to have to write the code that would actually execute all of that. Like I'm totally fine using a library. >> Yeah. >> But it was just this mystery thing that like was a secret. Um, and I like I like exposing those secrets, not so that people can go do it themselves, but so they understand how things work and then they can have that confidence again like that that it's being done right and that they understand what's been done even if they weren't the ones to actually like write the code, stuff like that. >> Yeah. So >> what was your um tell me about your your journey into tech broadly and then transitioning like into like developer relations as a focus? I feel like the the story of how we got we get into Devril is always sort of like uh often a meandering uh sort of journey. >> A lot of people just fall into it or they're doing Devril for a long time and their role doesn't say developer relations. >> Exactly. Recognize that's what they've been doing forever. Um, and that actually wasn't the case for me. So, I uh had um actually gotten my degree in animal behavior neurobiology. >> That is totally lends itself to developer relations. >> Yeah. As a child, I I was like, I'm going to be a doctor. And then I was like, I'm going to be a scientist. And then I went to college for science. And I really enjoyed it. Like I loved it. Um but then as I was you know kind of reaching the end of my degree it be it was you know abundantly apparent to me that if I wanted to continue to build a career in the things that I was interested in most likely it would mean that I would need to get a doctorate and I would also need to teach. >> So I would need to teach college while in the summer I got grants and and did research. And the irony is at the time I was like, "Well, I probably don't want to teach. I don't want to teach people." [laughter] Uh, so, you know, looking back on it now, I probably would have loved it. Maybe I would have become a college professor instead. Um, but at the at the time, I was like, "Oh, well, maybe maybe that's not like the thing that I want to spend the next eight years doing." >> And so, I had taught myself how to code as many people did, right? Um, I think when I was in like fifth grade, I went to summer science camp and they had like an hour or something they spent teaching us HTML. And this was this was even like CSS was not a thing yet. >> Yeah. Right. >> Um, and I had then, you know, gone on to make 500 geo cities sites on every little thing that I was interested in. >> Had the like little under construction gif and guest book and the page counter. >> Um, yeah. So basically anything that interested me I just made a [laughter] city site about it and that whole time like as a kid I it never somehow occurred to me that that could be a career >> right? >> I was just like this is a thing I do for fun and I'm going to be a scientist. [laughter] So, so then it like that perpetuated though all all the way kind of through college because I had decided okay maybe I don't want to be a professor so I'm going to get a second degree in human bio and dietetics >> um because overlaps with a lot of the science that I already had and while I was doing that degree which was going to take a much shorter time because I had a lot of prerex done but while I was doing that I got a job at the university >> doing front-end development and design and IIA and I was doing that like to you know pay the bills and it was at that time I still didn't see it as a viable career [laughter] like I had a job doing it and I was still like and I'm going to be you know a dietitian now. >> Yeah. Um, and I guess it it took a while of me uh suddenly realizing I wasn't getting paid enough, >> right, >> for my work to actually go and start looking at like other real jobs doing that. And I had basically a full-time job before I graduated and it was a full-time job at an digital agency, not in science. Um, and I was, you know, leaving a little bit early to finish like my last classes for this other degree. >> Um, and I think like at at that point I shifted my focus for the degree because I was so deep into getting a second degree. I wanted to still walk away with one. Um, >> so I switched to uh like digital media arts and communications um and knew everything that they were teaching us because you know they're they were teaching beginning code stuff right >> so so it was easy but that that phase I think was when I realized oh okay like this is going to be my career it's not anything like what I thought it was going to be >> you know when I was a kid or when I even when I enter college Um, so then I worked at uh digital agencies for a while. Um, I did more front-end development and then eventually did um engineering management and architecture and that type of thing. And uh then I had a baby and I so I was gone for like 3 months and I came back and I just remember like the designer met me outside the door like in the parking lot when I was coming back and he was like wait until you see this. >> So I got in and immediately basically started working 100 hour worked weeks. >> I was getting home at like 2:00 in the morning. It was it was absolutely ridiculous. >> No. Um so I was missing milestones like for my kid and I I you know had said okay I can't I can't sustain this. Um >> and so I applied for jobs and and I had met some people at a conference that you know I had just attended for work to learn stuff. Um and they said oh we work at a zero like you should you should apply especially if you like to write and teach you know like make tutorials and stuff. And I was like oh yeah that sounds fun. Um, so I joined Ozero on the content team. Um, basically we were developers who could write. So everybody was an engineer, everybody knew how to code. Um, and got to write about pretty much anything that I found interesting as long as I could tie it in some way back to Oth. And even in those in those early days, like we even didn't always write about O at all. like there are old articles on that blog that don't have anything to do with >> O. >> Um but because I later went to a conference and somebody was like where do you work and I was like a zero and they were like oh I love that blog [laughter] like they didn't even know we were an O company they just blog. So, uh, eventually, you know, I I got to a few leadership roles, um, and managing additional teams and had the opportunity to speak at a conference, um, because we had an advocate who was like on his way out, but he had already made this commitment, right? >> He didn't actually work at the company anymore at the time of the conference. So, he said, "Do you want to do you want to speak with me?" >> Because you do actually still work there. Um, and I thought it sounded terrifying and thought I should definitely do it because it sounds terrifying and it seems like something I should do. >> And it was terrifying. >> But I found out that I really really enjoyed it. So I started applying to speak at more conferences. Um, I started traveling and speaking and eventually um ended up leading global devril at Ozero. um having come from doing a ton of devro while I was not on the dev team, >> right? >> Um but yeah, ever since then I I have only had devil roles after that. I mean developers who write is kind of like one of the or two of the qualifications like that I would list under the role of like developer relations anything you know like it's such a small ven diagram because most developers are super just very technical uh very like like sort of focused on their on their area of of interest but not necess necessarily able to make the words good. Um, and it often takes somebody like me, like I I wanted to be a writer or something creative, right? Like when I was a kid, I wanted to be a writer or a rockstar, one of those two things. Um, and uh, and not a rockstar in the tech bro sense. Like a [laughter] literal songwriter. >> I I said that out loud. I'm like, "Wait a second. [laughter] I don't want to be that kind of rockstar. >> Um >> but uh but yeah, so I I you know did a lot of writing and so and and as a developer I did a lot of writing too but it was never part of my job until you know I took the role and I was like yeah I'm doing this because I've been doing it but also because I'm good at it and it's fun and it gets to flex the muscles the creative muscles that I don't get to do in like an engineering role. >> Yeah. [snorts] Yeah. Totally. And and that's what like I found it really refreshing to um coming off of doing all like production production work for external clients um who you know were various levels of difficult to work with. >> Yeah. >> I'm not even sure there was anybody who was like really easy to work with. I think it was all just varying levels of difficult. [laughter] >> But you know I loved it because the work changed all the time, >> right? Um, and so if you had one hellish project, like hopefully in a year, you wouldn't be on that project anymore. Um, but I I really kind of was still able to sort of get that doing the writing because we could basically write what about whatever we wanted, whatever we were interested in. So anything that I wanted to learn, I was just like, okay, I'm going to write an article about this, a tutorial on how to integrate off with, you know, X new thing that came out because I want to learn learn thing. >> Um, so I got farther and farther away from production code. Like I, you know, obviously haven't done client work since then. Um, and once in a while I I kind of miss getting getting some wireframes and getting a design and slicing it up and doing all the things. But uh I I still get to um like write a ton of code in in these types of roles. And that is another thing that just like I really value um about being in Devro is I still get to write code but I also get to teach people and do talks and things like that. So >> and things like this. >> Yeah. Yeah. Um, my brain completely stopped functioning for a second. Uh, there is a thing that I was going to ask. Uh, oh my god. [laughter] >> Um, tell me about making small things. [laughter] >> Uh, yeah. So, I make miniatures as a hobby. It was a pandemic hobby. Um, I had, ever since I was really little, I had a dollhouse that my grandparents made me like handmade and I always loved making little things for the dollhouse, like I'd make the little Play-Doh hot dog in a in a bottle cap or something. Um, and so I always was interested in in little things. And over during the pandemic, I think I was just like looking at stuff on Instagram and stuff and I was like, "Oh, people make this amazing super realistic tiny food and it looks so real and it's so cool." And then I watched a couple tutorials and I was like, "Oh, they're using polymer clay. Anybody can buy polymer clay." Like, it's not a special >> magical thing that you, you know, need to be super experienced in to even get your hands on. Um, and so I started making miniature polymer clay food and got quite into it and then started making other things as well. Um, I've made like a katan board and and stuff like that. um and had gotten kind of I through the course of like the tiny things uh COVID thing, I started getting into mechanical keyboards and uh artisan keycaps. So, I started experimenting with making artisan keycaps with polymer clay. And there's a lot of kind of thought and design that has to go into that because you need to design them in a way they're not going to break. Mhm. >> And then from there I actually started getting into resin casting. So then I now I resin cast uh artisan caps um as well as make the tiny food [snorts] um and game boards. Mhm. Um, oh I remember the thing I was going to say uh that well and it sort of tangentially relates uh because uh the question we were talking about um speaking and you were talking about being terrified uh and developer relations and from from my experience but also from like I've been speaking at events but for long before I was you know a developer advocate um but it involves a lot of like speaking or being in front of people or whatever. Um I like in high school and into college uh a little bit was in really into theater. So like I was in film and so I was like all about being in front of people. Um which is another thing that like most engineers like are very much like very introverted. would much rather just sit in a room that is dark and stare at their computer and just type code for without interacting with another human being for most of the day. Um whereas I definitely, you know, enjoy being around people or being in in spaces where I can, you know, like talk to people and have have conversations and things. Um, and that makes so that makes the speaking thing less slightly less of a uh nightmarish horrifying thing for me because it's just a form of natural being on stage thing. >> Um, >> so uh all that to say um where on the sort of introversion extroversion uh spectrum do you see yourself? Because I I I have a suspicion [laughter] >> I'm I'm an outgoing introvert. Okay. >> So, I I love to speak. I love to interact with people. I love to be out and about and doing these things. And then I need a little bit of time by myself in order to recover. >> Yeah. >> So, I don't you know, the classic, I think, definition of an extrovert is you get energy by doing those things. >> Yeah. >> And then introversion is when you get energy by being by yourself. And I think people often confuse introversion and like shyness or because you can totally be an extremely outgoing introvert. >> It's just that the way you recover from like [clears throat] it drains your energy to do that instead of like giving you more energy. >> Yeah. >> Um so that's definitely uh where where I'd classify myself. But as a child, like I think the words painfully shy would probably be an accurate like like painfully shy like hide behind my parents like in public when somebody talked to me type of shy. >> Um so you know it surprised even me that this was something that I was actually really interested in. >> Yeah. >> Like wrote as an adult. But um I think speaking if you are introverted speaking at conferences is actually an awesome way to to go and um have give people a reason to talk to you. >> Yeah. >> Like it's I've been to conferences alone. It kind of it's hard especially if you're an introvert. Yeah. >> To find people to talk to and stuff like that. But if you apply to speak at an event and you get up and speak, people will come and find you and talk to you. >> Mhm. >> And I think that that doing a lot more of that also helped me to be less shy. Um so yeah. >> Yeah. I I it's definitely a thing like I I remember having a conversation with my father-in-law um who would have uh identified himself as an introvert but also like he was a pastor. He was like very much in front of people a lot of the time and like it was just something that he like he learned to adapt and to be that role even while it's not necessarily like the natural role but like because of social circumstance because he's male because of all sorts of all sorts of other reasons um and and where he was in the sort of organizations and things that he did uh he just sort of gravitated to that thing and just like learned learned how to kind of learned the techniques he needed to kind of muscle through in a way. Um I definitely find when I go to events and I'm I'm around people um all day long um I I definitely need that time to recharge is like super it's like exhausting. But I also I I I I just always find it interesting because like part of the role of developer relations is the relations part, you know, it's it's the interacting with other humans. And so it's it's like built in. Um but I don't think that that necessarily means that we're all super extroverted. Um we are also many of us still kind of coders at heart. >> I I would even say that probably more than half of the people that I know who who are in deval are introverts. Mhm. >> Um because it it's basically a discipline that puts you in a position where you will be pulled out of your shell by external factors and you don't have to force yourself out of it on your own. >> Um and I think that that that really has, you know, obviously I've gotten more comfortable with all of this stuff, but >> um >> I had I had kind of [laughter] an interesting revelation. I went to Cedar Point. I don't know if you're familiar with Cedar Point. Um, it's a massive roller coaster park in the Midwest. And, >> um, I had I love roller coasters and I was riding, you know, like the the biggest ones and and I realized I don't get nervous about going on roller coasters anymore, like at all. And like there's no physical reaction. I'm just like, yay. But [laughter] I and and I realized like how much, you know, people are adrenaline junkies and and you you can get that adrenaline the like couple of moments before you walk on stage in front of like a huge crowd. Um, and I had this kind of revelation about the roller coaster thing is like, oh, like that was part of why I like roller coasters is like feeling that feeling before you get on. And I think that's why I like those few moments before like peak they say peak scary is like you know the moments that you're walking up to the stage. >> Yeah. >> And and I was like >> I haven't spoken in a while because of the pandemic. Um at least not in like out in an actual physical event, right? >> And I'm about to do a couple events and I was kind of like I hope I get nervous [laughter] >> which is kind of funny. But uh yeah. >> Yeah. That's awesome. That's a really interesting insight. Like I wouldn't even have thought about that connection, but like Yeah. Um that like the minute that that the roller coaster isn't doesn't make you nervous, then it becomes less enjoyable. >> Yeah. Cuz like a lot of it is kind of the hype like building yourself up to to do this thing and then >> Well, and a really good example like I remember the the first I think the first roller coaster that I had ever been on was probably Space Mountain at Disneyland. And this was probably um maybe the 80s or early 90s. So, it was they they've done a couple like renovations of it since then and it's it's much less dark and much less scary. Um but at the time it was like you go in and it's pitch black and there's maybe a couple just like tiny little lights that are like stars that that that are going around. Um and there's like a loud whooshing like wind noise. Um and you can't see anything. And I I remember like and so the sound and the sound of people screaming and not being able to see anything and it was I remember being terrified as a kid, but I was like musling through it. And so I [laughter] I did like I I tell my partner this and she's like, "You're weird." Um >> because like I closed my eyes and that made it better somehow. I'm not entirely sure how because you couldn't see anything anyway, but it made it better for me. And then that that's how I got through that that initial sort of terror of like roller coasters was I would just close my eyes. But like now but like I remember that like it was so um there's so much of of that. It wasn't even like >> it wasn't even the ride itself. Like the ride is almost fine. It was like all of the leadup. It's like the the ramp up the hill is like hearing the sounds and hearing all of the other stuff and the sound of the coaster itself and like everything. That was the scary part. Like once you get going it's like it's 30 seconds of your life. Like it doesn't even it's nothing. Yeah. >> Yeah. So I guess like the that like click click up the hill is like what what the walking up to the stage is like >> the anticipation. >> Yeah. Yeah. >> And I I hadn't realized just how big of a component that was in my enjoyment of roller coasters until I went and didn't feel it anymore. >> Yeah. >> And I was like this is actually [laughter] really disappointing. like what what am I gonna I'm gonna have to like do more crazy like or something because I this is like not I I'm not getting nervous. >> Um >> skydiving. >> Yeah. I mean like we've talked about it a bunch of times [laughter] actually like me and my husband. Um so yeah. >> Yeah. I I have a um I've been taking uh aerial classes, aerial arts classes and and so like for me like heights is a thing for me. So, like now, but now I can like climb up a silk or whatever and be up at the top and not feel like super scared. Um, but like one of my instructors recently went skydiving and took lots of pictures and I'm just looking at the pictures like, "Nope, nope. Absolutely not. Nope. I can see." Fun for you. [laughter] >> Yeah. Yeah. Well, that's kind of like where I was lukewarm on it for a while just because I was like, I just I just don't need to do that. >> Yeah. But now now that the [clears throat] roller coaster thing is like not exciting. I was like maybe maybe that now. Um because Yeah. >> What events are you speaking at? You mentioned that you're you have a couple uh speaking uh gigs. >> Yeah. So I'll be speaking at JSCOM and NG comp and they're colllocated. So they're both um in the same place in mid-occtober. So just like a couple of weeks. >> Wow. Yeah. Yeah. Coming right up. Um, and then, uh, where where can people find you on the internet and find your your tiny things? >> Um, my tiny things are on, uh, my so my like art name or whatever is MI. Um, or it's Mihi- Mini.studio. So, it's Mihei Mini Studio is uh what what it's called. But um in general, I think maida.kimconnect is where I is, you know, my equivalent of linkree. >> Uh is is where I'm mostly at. And these days, like I'm social media wise, I spend more time on LinkedIn. >> Yeah. >> Than other platforms. >> Yeah. >> Mostly. >> But not not that that's a bad thing. I'm like [laughter] acting all disappointed or >> Right. No, it's true. You know, I guess it's it's been great, but it's just funny because I never really thought of the platform like that before. >> Right. No, there was a certain point where I where I started using LinkedIn more for for just I just using it more period honestly. Um because there was a long period of time where like okay, when I'm looking for a job, that's when I care about my LinkedIn. But but yeah, now I I sort of >> check it more frequently and possibly more than other things as well. Um well, thanks coming for coming on, Kim. Uh and uh thank you everybody who might be watching this or coming to this later or listening to this on on the audio version. Um and uh yeah, we'll we'll see you on the internet. >> Great. Thanks so much for having me. [music], Episode 11: Kim Maida, YouTube, 01kgjmc4h4f0qbcvp5v801tmkt.