Rachel Nabors tells us what it takes to reform a large open source project's documentation efforts (React Native), and also about organizing the Women of React conference.
ep-004-rachel-nabors_mixdown
Chris Biscardi: [00:00:00] I'm Chris Biscardi, and this is the party corgi podcast. Today we have Rachel Nabors. Rachel has a long history in web automation, having written for a book apart Animation at Work, cultivated the web animation weekly newsletter and community. Built out a number of courses and given numerous talks on the subject.
She's also worked with Firefox to build devtoolschallenger.com and worked on the motion design guidelines for lightning design system. Rachel is a react core team member and expert award-winning cartoonist. Welcome Rachel. Thanks for coming.
Rachel Nabors: [00:00:33] Hey, thanks so much for having me, Chris. It's good to be here. How are all the party corgis?
Chris Biscardi: [00:00:39] The party corgis seemed to be good as of today.
I have not explicitly checked in with all of them. There's quite a few of them, but they, uh, they seem to be doing well.
Rachel Nabors: [00:00:50] How big is the party corgi community?
Chris Biscardi: [00:00:53] Uh, about 600 people or just over 600 people. Now,
Rachel Nabors: [00:00:57] that's not a bad size. How long have you been around?
Chris Biscardi: [00:01:01] Uh, about three quarters of a year. So yeah, it's exciting.
We're, we're approaching one year in a couple months here.
Rachel Nabors: [00:01:11] You should have a celebration.
Chris Biscardi: [00:01:13] We should, uh, we were thinking about actually doing an in person kind of thing. Uh, but that is probably not going to happen anytime soon. So we are going to do something else.
Rachel Nabors: [00:01:22] How are you doing?
I am far from home on distant shores, locked in my tiny London's studio flat, all of those, um, with my rings and my back porch was the pigeons that like to fight.
We have these really interesting pigeons in the neighborhood that were imported meat braids from the United States, and they're much more aggressive than the local wild European varieties. So the patients are big and bossy, and I've never seen patients have more fights than outside my window. But, and I lived in the Netherlands shirt years.
I have seen
Chris Biscardi: [00:02:07] pictures, I didn't know the Netherlands had a pigeon problems.
Rachel Nabors: [00:02:13] I wouldn't call them problems. I'm just saying like if you're in a European city, there are pigeons. Sure.
Chris Biscardi: [00:02:19] Yes. It sounds like we exported the New York city pigeons to wherever you're living right now.
Rachel Nabors: [00:02:26] So your New York city pigeons,
Chris Biscardi: [00:02:29] New York city pigeons.
I've seen New York city pigeons fight rats, let's put it that way.
Rachel Nabors: [00:02:35] Oh,
communicable diseases. I always say, why do you hate on patients? They're like little winged angel janitors for the city cleaning up your trash. They don't ask for any money to do it all very aside from like the occasional avian flu, which is his own kind of pandemic. Um, most mammalian contracted diseases can't hop between birds and mammals.
So they're pretty safe waste disposal units.
Chris Biscardi: [00:03:06] That's awesome. I actually didn't know that much about pigeons
Rachel Nabors: [00:03:11] make it a bad rap, but they're really sweet. I have one raise a baby out on my back porch, and they were the sweetest soul parents ever that that baby was ugly. They were, they were really sweet. Do you want to talk about tech?
Chris Biscardi: [00:03:29] Uh, I mean, I'm, I'm happy to continue with either, but, um, we are here to talk about the react native documentation. So would you want to start with what react native is for anybody that might be listening and doesn't
Rachel Nabors: [00:03:41] know. Oh, cool. So you may have heard of react, uh, the Java script library for creating and composing user interface, but you might think, Oh, react is only for the web because it's written in JavaScript and you would be encrypted.
That's the game. There's actually a. No other open source library that is Facebook maintained called react native. And basically it lets you compose user interfaces using Java script and the react, the react component structure you've come to know and love, but get this you can use them to build apps for phones, for iOS and for Android.
And actually there are even some, like I think the react VR is built with react native. And react, uh, is also used to build parts of windows so you can build apps for windows is react native using that repo. It's, it's really cool. It's like you can use Java script to write from native platforms. Um, it's JavaScript.
It's not just for the web anymore.
Chris Biscardi: [00:04:51] Sounds great. Sign me up. How do I get started?
Rachel Nabors: [00:04:54] Well, you can mostly on over to react native.dev to check out our official documentation. Uh, if you click on the docs link, it will take you right to our print new scrubbed up introduction, which I totally had a hand in. Um, I came to this company like.
10 years, 10 years, 10 months ago,
10 years.
What day is,
yeah. So Castaway over here. One of the first things I was tasked with when I joined the core team was, Hey, yeah, of course documentation is pretty darn good, but react native has just kinda been doing it some thing for years, like for five years, this documentation was largely contributed to by the react native community out of the goodness of their heart and the occasional core contributor, et cetera.
But then that the. It had grown in its own specific way. Um, and it was sort of like, have you ever read a secret garden?
Chris Biscardi: [00:06:11] I have not. What is the secret garden.
Rachel Nabors: [00:06:14] Uh, it's one of those, I think is by the same author who did a little princess, but it's one of those English books for children that's completely tree and it starts off about a girl character, but it ends up being about a boy character.
Um, I was really jilted by that when I discovered that as a little girl reading this, I was like, why are we suddenly talking about him?
Chris Biscardi: [00:06:37] It's about them. Why is this not about the main
character?
Rachel Nabors: [00:06:40] Exactly. It's got a picture of a little girl at a big hat sneaking into a garden on the cover. This, what have
Chris Biscardi: [00:06:50] you done?
I'm looking at the page right now and I totally agree.
Rachel Nabors: [00:06:55] I know it was called the secret garden and not like the tale of this girl. And these books are fraught with all kinds of colonialism and complications regarding gender representation. But you know, like anyway. The point is she finds this kind of interesting locked garden, and when she gets in it, you can tell that it, it's this huge, magnificent garden.
It's got this great big, beautiful tree with a swing in the middle of it, roses that have grown a lot of control, et cetera. It's just not intended in years. And so she sets about. Cleaning it up and making it nice and making it her own private garden. And there's this mystery about why it's been abandoned.
And, um, anyway, I can keep going, but it's, it's really cute. And I, I'd like to say like, I think like the react native docs. When I got here, we were a bit like that secret garden. We had so many poor requests that hadn't been merged because no one had gotten to them. I mean. Core teams, shipping features, documentation, pull requests, kind of fall, or the, the low end is the priority scale, but it's like on the high end of my priority scale, because I was hired to work on documentation community.
So I would go in in there and it's like, what's up with this information architecture? And. Why is everything written? Assuming I have a web development background, if we also are trying to attract people from mobile app development, they might not understand these words and terms. So I started survey the community and found out all kinds of interesting things, like 7% of the people who come to react, me to stock lamentation to learn, react native.
Actually, that's their first experience programming, and so we really can't take anything for granted. Uh, when it comes to these docs and it's been a big challenge cause I've always written for a web development community and now I'm getting to branch out and meet people from other kinds of development communities and seeing where we have overlap and where we are pretty darn.
Chris Biscardi: [00:09:01] That's pretty wild. 7% of people that show up are like, this is their first time ever doing anything.
Rachel Nabors: [00:09:09] According to the survey, I mean, I, maybe they had something else in mind when they clipped up. Pretty sure. That's the impression I got. And something like 30%, um, like 30%, 30%. There's like 60% of people are actually from platforms like iOS and Android development.
So the number of people who are reading the docs from the perspectives as web development is actually pretty low. And that made me think, well, is this is our first time using react. I, I interviewed a couple of people from his background and I was like, tell me about how you learned react natives. And they were like, well, first I had to go to the ACS website and learn everything about react there.
Uh, before I could understand the react news box, I was like, Whoa, we should probably make fewer assumptions about how much people know about react to refer to the react docs more often. And maybe like start with a mini warm up on react. So I wrote that. That's pretty cool. I used to cat cafe metaphor, um, Israeli, cute little SPG cats there.
So, um, yeah, so it's taking all of my skills from UX, from creative coding, from information architecture and developer advocacy and it just to make a resource that people can really get a lot out of. Um, and also we have a great community. It's not that people don't want to write the docs that people weren't out there managing and proofreading.
And you know, like there's a lot of work that goes into doc. So I don't want to downplay it as why we consider anyone who makes a docs contribution as a core contributor because you have to really understand and care about source code to be adding to the documentation. So our docs were, are running a bit out of date, a couple of versions, and you know, some of the API APIs hadn't been updated.
So I ran a, a big documentation drive and I opened up a get hub issue and I listed all the components that needed updating and 29 people worked for like a month and we ended up getting all of the APIs nicely spruced up and up to date. And it's like the best condition that these docs, uh, have been in perhaps since they were originally launched.
I don't mean that in a bad way. Not like jocks take effort if you're not directly writing him from your code base, but that's not how the, well, even then, like generated docs are no good if nobody's handwriting anything and handwritten docs are no good if people don't go update them. It's a, it's a fine balance district.
Chris Biscardi: [00:11:42] It is like I'm listening to how much work you're describing here and you're like, just casually like, I know I did this and then I wrote that and then we did this. I was just like, that is like a lot of work both for you to do and for like you to organize. How did you start on that? Like what was the first thing you did when you, when you landed in this sort of garden of overgrowth.
Rachel Nabors: [00:12:06] Oh, you have to remember, I didn't know anything about react native and I was only mildly experienced with react. I was kind of a few person before it came to the team, but I wanted to learn, react because I saw a lot of potential in the community to to grow and you know, like include more people from around the world.
So I was really excited about the potential there. He came in and then I find myself in the react native secret garden, and I was like, I don't know what react native is. Uh, so the first thing I did was I set out to talk to you, all the team members, and I was like, well, who's is the biggest advocate for react native in a community?
I write down that person's Twitter ID. I go reach out to them and be like. So talk to me about how do you use react native? Talk to me about how you use the site. And I would just follow these circuits of inquiry and sometimes I would post on my Twitter like, Hey, I've got 30 minutes on my Calendly open.
That's a little little service you can use to let people schedule time with you. Hey, like I want to talk to more people who've been using react native and learning react native. And I think I did for about two weeks to 30 minute interviews with people per day about react native and their learning experience.
And I gained not just information for me, but the internal, um, engineers, like they really want to hear from other people at Facebook who are using react native. Because you know, they're heads down building this thing for their teeniest use so I can come back in and I'd be like, did you know that 7% of the people, they'd be like, yeah,
there's a, there's an element of advocacy there and that I do a lot to bring what's going on outside the react natives, the react native core contribution team. Uh, into the contribution team. I mean, that includes both our internal team and our external team is quite a few numbers of people on core. Also external.
So it's been exciting and it's kind of an exciting sitting right between react and VR natives. Uh, they're two very different teams like react native kind of consumes react, react team thinks about big decisions like concurrent and trends and react. Native is over here. Like how many components do we want to support in core?
Does it make sense that we should support them all or should the community build its own components based on its own needs? So it's built on top of react, but it solves different sets of problems and the community that builds with it is concerned about things. The one development communities. That's
Chris Biscardi: [00:14:48] super interesting.
Um, it's super interesting that sort of the web community is this minority group in the sort of the user base of. React native, whereas it seems like the majority is 60% or so, or like 70 if you conclude the first time programmers are sort of like native programmer, right?
Rachel Nabors: [00:15:08] I don't know if you can split the numbers that well.
I did ask people like, what are the, what are the platforms you're fluent in? Rather than like. You know, like, do you consider yourself or this or that? Um, but I think it's an interesting, actually, I don't remember the terminology I used. It said six months. Um, I don't exactly remember the terminology, but I do remember that it shows that the people who use react native.
Have a diverse background in different platforms. Like sometimes you do meet someone who does Android and iOS, or sometimes you meet people who they are specials, but they also happen to be like the Android specialists. On a react native team where they're working with a bunch of people who came in from the web with Java script skills and don't know anything about Android, and they sort of parcel out their niche, super power knowledge of Android, their team, and allow the team to ship products and features that otherwise, you know, a person with a website in the background might not have any idea of the capabilities of the platform or how to write a custom native module to support
Chris Biscardi: [00:16:18] them.
That's the beta.
Rachel Nabors: [00:16:21] I know, right?
Chris Biscardi: [00:16:25] So I like, you've sort of brought a lot of people from not contributing to the documentation to contributing to the documentation. Now, how do you organize that effort and what does it like to get somebody who maybe hasn't contributed to the doc at all through to the point where they're contributing maybe multiple changes to the doc.
Rachel Nabors: [00:16:46] That's a great question. So early on I realized that because I'm not the expert, I would need to work with people who are experts. Like I had two options. It's spend a year becoming an expert at react native, and I could literally write the book or. With that, that would end up with very sad reviews for Rachel for a year.
Or I could do the cool thing and I could go out and activate my community network and say, Hey, this is an expert at security and that's caddy crime, and I saw her give a great talk at react native summit. EU. Or wait, react native. Eat you. Yeah. React native summit II or the adjacent event at the conference where a bunch of our EU to contributors got together with the core team and we all have gone core for a bit.
I got some really good documentation contributions that part. But, uh, I watch these talks and find one that somebody like, this person's really smart, and then I'd come up to them afterward and I'd be like, would you like to contribute back to your community? Right. Adopt, I will help you. I will be a proofreader and a technical reviewer.
And that's actually really, really reassuring because we have a very diverse audience of users from all over the world. I know this cause I, I spoken a lot in the EU and you'll have people too. You know, might feel a little cautious about just throwing stuff up on medium and they're really happy to have a tech editor or an editor at their side.
You know, I want to see an outline. This outline looks good. Um, why don't we phrase it like this. Don't worry about that. I caught that. You know, it's, it's kind of a back and forth collaboration and it always takes longer than you think it will. Like I'll be like, Oh, this is great. Well, there'll be like, we'll get it done in two weeks and I'll be like, Ooh, like two months and then six months later, because it's an open source contribution.
You can't really, you know, like these people are not paid professional writers just, they give back to the community. And I try to celebrate that gift by adding illustrations that help our visual learners in the community. Remember certain key concepts with a little bit better than if they're just looking at a wall of text.
That is how I get individual contributions, but for the documentation drive, I opened an issue on get hub. I listed all the things. It was a little awkward. I listed all the different components that needed work, and then I asked people to claim them in the comments. There is a little bit of stepping on toes for we all figured out a system that worked for us.
But in the end, um, like I said, 29 people contributed and they, they did a great job and some people would start, start Hale and hearty and make a bunch of contributions and they have to disappear because work or family. But another person would step up to the bat and. There were a couple of really nice first time contributions.
I use this as an opportunity to encourage people you, you know, might want to get more active in Oakland sources is like a really good chance cause I'm right there providing feedback. You know, it's like you're the expert but I'm helping you and this, this was great. It was wonderful getting it done and I can't wait to celebrate everybody in a big blog post.
So
Chris Biscardi: [00:20:13] do you think that, cause there's a lot of other open source projects out there that seem like they are in desperate need of somebody filling this role, right. Do you think that this is a good path for people as long as you like sort of like you have buy in from whatever maintainers of the project that you're intending to work with?
Right. Given that this is a good path for people to try to pursue when contributing to open source.
Rachel Nabors: [00:20:37] Absolutely. Um, like if you're intimidated and I totally feel this, so, and I was thinking about working on this team, I was like. I'm not a software engineer, you're looking at me. I couldn't possibly, I felt really intimidated.
And that's super common, especially if you don't have a computer science background and you, maybe you're a little nervous about that. Um, but if you start with the documentation, it takes an expert to write documentation. So if you're trying to increase your expertise and shooting to documentation, like opening for requests, student feedback on it.
It can be a great way to either proves that you really know your stuff. And, you know, earn credit was the, was the people who are maintaining the core. Or it can be a great opportunity for you to learn even more as people come in and say, this is a great contribution. But, uh, this, this example is a little weird if you explained to me why it's like this.
So that act is conversation on documentation, repose, really healthy for the community. You know, I say this as much to people who are managing their open source projects as I do to people who want to contribute to them. Think of documentation is like the stepping stone to greater involvement with the core
Chris Biscardi: [00:21:50] team.
That's a really awesome way to put it. Um, I've seen plenty of people sort of do their first thing, uh, as a contribution to an open source project. And it's like, I see a typo and it's a small contribution, but it gets you through the entire flow of making a PR, talking to the maintainers, getting it merged, and then everything, like the whole thing.
Right. And then the next change you can make as a slightly bigger one. Maybe maybe you write a documentation page or something like that, et cetera.
Rachel Nabors: [00:22:18] Well, you'd be surprised. But just the act of caching the typos and coming in on other people's PRS and being like, Hey, this doesn't conform to the style guide.
I mean, that is so useful to maintainers. Like I am incredibly grateful, uh, during the documentation drive. One of the contributors who didn't submit as many PRS as the others, but they were coming around and you know, tech checking and spellchecking, all of the other PRS. It was like I had a little, you know, deputy editor.
Then that was so awesome that this person's actually been given extra privileges on the repo because they're so reliable and so helpful for us to make sure that we're keeping this TRS flowing and getting merged in. That's awesome. You might be like, Oh, all I have are some typos, or you know, checking things against the style guide.
But that means so much because so many people refer to the documentation and the reference materials, not just basically, but daily. These little things make a huge difference. A typo can throw off an automatic translator like you wouldn't believe. So this is mission critical for some people's employment.
Chris Biscardi: [00:23:27] Yeah. Having worked with a number of open source projects in the past, I think that this, uh, this person that you're describing, the people who do sort of the in between work, the little work are a lot of little work or a lot of like filing and labeling and things like that are, and critical, especially as projects grow because you just, you can't do it all.
Rachel Nabors: [00:23:48] No. Yeah. And the best part is sometimes those relationships grow. I know that this is a person that I need consult now, but I'm like, well, what do you think we should do with this weird page? It doesn't seem to fit in the hierarchy. I really value their feedback because I know they've been all over the ducks with me.
Chris Biscardi: [00:24:06] That's a great way to get involved. Right? Like I know that sometimes people talk about these alternate paths to get into things, right? And this is like one of those paths
Rachel Nabors: [00:24:15] right? Yeah. Even an artist, I think you could get into 'em you could get in with the crowd just by committing like illustrations of different concepts in the documentation.
You'd be surprised how much a difference that makes. Like you might be thinking, Oh, I don't have any special skills I could offer. I've seen designers submit or request to rearrange sidebars. They're actually legible and that went so well. Everyone has a skill that they can lend to make the learning environment even better.
Chris Biscardi: [00:24:48] So there's a lot of writing that you've described here. Is there any sort of, um, like I know in like if you're writing in word, you have spell checkers and things like that. Is there any sort of automation that you use on the react native documentation that
Rachel Nabors: [00:25:01] helps? So we do have one automation that we've run.
It's a special Java script library, and I always blank on it's name, but it is it like, uh. It checks for exclusive language, like language that could PR people on their back foot, uh, language that that's like, you know, uses like pronouns instead of using gender neutral pronouns or uses something like, it's just easy.
It lends for easy, it's a little Venter really. And, and my laptop is adding up all at me right now and I'm kind of terrified to touch it because I know you're recording, even though I am also recording a quick time, so I can't look up the name of it right now.
Alex J us is awesome. We have our PR, um, our PR contributions. If they fail, Alex, you have to go back and edit your PR in order to make it pass. And this has been really good for just keeping some super, I don't want to say. Anything that would be exclusionary term here, but let's just say yes. A lot of things that even I get tripped up on and miss that, that, uh, that proofreading process that much easier for me cause I don't have to be, you know, on guard for.
Common mistakes that people would be making from, from different standpoints. So that really has helped. Um, otherwise I'm pretty much just rely on the spellchecking that you get from like Google drive or Quip or whatever you're using, and then export that as marked down.
Chris Biscardi: [00:26:53] That's awesome. So you've done all of this work, all of this writing, all of this documentation, all of this community organizing.
Um, you've got a bunch of people over the last six months that have gone from. No contributions to some contributions to maybe being heavier involved in the project. What's
Rachel Nabors: [00:27:11] next. Whoa, I'm glad she got asked. I hope people are listening to this before April 25th because I'm also co organizing an online conference featuring some of the most awesome women in react I've ever had, the honor to meet.
Uh, it's called literally women of react, and you can go to women of react.com to get your free or STP. It's going to be a lot of fun. We've got a lineup from around the world and it's seven talks, a few fireside chats, a streak of lightning talks, and a lot of fun. He'll be on Saturday and hopefully you can come join us.
A little something that I and some colleagues put together because it was just so sad. Know that. We weren't going to be going to any conferences. A lot of us had written talks ready to go. We were really excited and then all of a sudden. All the conferences got canceled. Um, we knew that we weren't going to see, usually you go to a conference and that's where you see like, ah, there are people like me here, and we wouldn't have that kind of visibility to each other.
I realized I wasn't going to see Jen Creighton and I love Jen and Sarah. Oh man, what am I going to see these amazing women again? Oh, no. I love so sad. So we decided he could a big party up and have a, have a conference for everyone. We're going to have a discord that Scott, lots of mob students share.
We're keeping the peace and opposing the code of conduct. So if you sign up, you can join the discord, or you could always just watch tremor, YouTube.
Chris Biscardi: [00:28:59] Awesome. Um, how, like, how much effort is it to, cause you're listed as the instigator here, which I thoroughly enjoy myself. Um, how much effort does it get something like this up off the ground?
Because, uh, for example, like the other day I was tweeting about, well, what is everybody going to do with all of these talks that they now are not going to give places? And, uh, it was super unfortunate to hear that a lot of people were just dropping them. Mmm. Yeah. This seems like a lot of work and it seems like you spun it up really quickly.
Rachel Nabors: [00:29:31] That's because I have a very supportive group of people around me, and also I am lucky enough to know a lot of the organizers of various international communities, um, you know, women in reacts and the globe, so I could reach out and be like, Hey. I'm putting together this conference with some friends who gave a really good talk that you can recommend that we invite to speak at it.
Because I didn't want to ask people to make brand new talks for an online conference. That seems like a lot, but it turns out there are a lot of really great talks that we're just not going to be seen that were like one lady. She couldn't give her talk, a big react conference because she couldn't get a visa to the States, and now she gets to give it both of them.
So yeah, right. Um, so it was exciting. It was needed. I get, I get messages from people being like, I am really looking forward to this. This is the thing that's making my April awesome. And that's really exciting. I think putting on these online events is a great way to bring your community together. And it doesn't have to be a big one.
You know, you can do a small conference just for your people if you want. Yeah. I'm
Chris Biscardi: [00:30:40] super excited to see more people, uh, sort of start streaming and as they start streaming and realizing that they can sort of. Just do this, that they get together in little groups and they're like, okay, we're going to do this as a group here now and get everybody together.
I'm super, super looking forward to that as a, as a thing that happens over the next couple
Rachel Nabors: [00:30:59] of months. Absolutely. I think it's actually been really useful to empower people in their communities because we're so used to like, I'm going to this conference and you know, you see the conference lineup that the organizers put together and you get to meet people, but at the same time.
You don't have to go to a big conference. You could go into a little conference just full of introverts if you wanted, or with like people from around the world to all are into the same niche topic. I originally wanted to make this a 24 seven around the world. Talk around the world's conference. The shifts of.
MCs and hosts, but everyone was like, Rachel, no,
Chris Biscardi: [00:31:51] we will be constantly live for 24 hours. Oh man, that would've been super cool. And I cannot imagine the amount of work that would have went into that.
Rachel Nabors: [00:32:02] So a lot of work just to get the eight hour conference off the ground. I confessed. Some days I'm like, I bit off more than I, yeah, well, I have friends.
It's not more than I could chew. I've got friends.
Chris Biscardi: [00:32:12] I was going to say, it seems like it's happening successfully, so definitely not more than you can chew. .
Rachel Nabors: [00:32:18] Yeah, I think it helps always have at least one co-conspirator. You should always like, don't, don't get into any project. This is a rule that I figured out after many years working for and by myself.
Don't take, take on any new projects unless you can convince one other person to go in with you. Because if you can't come to this other people's, probably not a great
Chris Biscardi: [00:32:38] idea. That is, I will partially agree with that. I think that, yeah, I think that it's very, very useful to have somebody and figuring out how to convince somebody else to work on something with you is very, very good and a very, very good indicator.
But there are things that, uh, you can work on that you might not understand how to convince somebody else to work on yet, and you might just need to work on it a little bit more before you do that. So I'm behind
Rachel Nabors: [00:33:10] it.
Chris Biscardi: [00:33:14] Are you releasing talk titles and things like that? I think I might've seen some murmur of, uh, what kind of talks are going to be here.
Rachel Nabors: [00:33:21] Yeah, we're going to have talks. Okay. So if you visit the site now, it should have a schedule posted. We're tweeting about every different speaker there, talk, uh, all the way up to two, and, uh, the actual event.
But we will have the full schedule on site. So, um. We've got starting with basically a double, a double header about design systems and how they're awesome and also how to use it. I think it's styled component with design system, a design system integration. So that's super exciting. I know that we've got a talk.
This one's one that I'm personally pumped for because I think as the recession becomes more of a thing. It'll be particularly relevant. I talk about preparing for, um, reacts technical interviews. That one's going to be our closers. Super, super, I think relevant, uh, toward the end of, uh, toward the end, toward the end of the conference.
Yeah. Mmm. And Oh my gosh. He for cello is going to be talking about concurrent mode. I'm very Oh, concurrent mode and suspense, so that's going to be amazed.
Chris Biscardi: [00:34:31] That's awesome.
Rachel Nabors: [00:34:32] Yeah. Check out the site for the holistic.
Chris Biscardi: [00:34:35] I'm super excited to hear Eve talk about that. She talks about all the time and I super enjoy it every time she speaks about that, so I'm hyped on that one.
Rachel, thank you so much for spending time with us today. Uh, is there anything that you would like to say before we end the show?
Rachel Nabors: [00:34:54] Well besides, uh, hope. Poke, you'll come to women of react conference, a conference for everybody. I'm going to take the stage, but anyone can be in the audience. And. If you'd like to get into open source, I think of your shame for it.
Open source technology and go ask them if they need some help with their docs.
Chris Biscardi: [00:35:15] And where can people find you on the internet if they're interested in hearing more about what you have to say.
Rachel Nabors: [00:35:21] You can find me on Twitter. Uh, racial neighbors. That's N. a. B. O. R. S. it's a silly spelling, but it works out.
Rachel Negroes on Twitter.
Chris Biscardi: [00:35:32] Thank you very much, Rachel.
Rachel Nabors: [00:35:34] Thank you, Chris.
Chris Biscardi: [00:35:35] That's all we have time for today. Thank you for listening to the party corgi podcast. If you want to come be part of our community of creators and hackers, you can find a link toward discord channel@partycorgi.com. You can also find us on Twitter at party corgi pod.
I hope you have a wonderful day.