 I was kind of hoping that there wouldn't be a ton of people, not because I didn't want to speak in front of a lot of people, but I was thinking about this, you know, I got such a positive response, the idea of this talk, and it sort of broke my heart to think that that many people might really be that burned out and I really need this. So you know, I'm not a super experienced speaker, I really hope that I can do this topic justice, because it seems like something that a lot of people need to hear about. The bad news is that I'm not a self-help guru or a motivational speaker, a licensed clinician, any of those things. I don't really have any official capacity to tell you how to relieve your stress. What I do have is some common sense, some stories, a little bit of advice from my own stories that I think might help. But I have this feeling, you know, if you're here and you're already identifying as being burned out, you probably already know what you need to do to change that, but sometimes it just helps to hear it from someone else. So I hope that I can help. If you're here at JangoCon, you're already a part of a really thriving community. It's a very active community. You're already, you know, part of open source, so you used to give me your time and energy very freely. Well, why we do that is probably a topic for another talk at another time. I know that most people that I know outside of open source don't get it at all. You know, we give all of our free time. We work a lot in our free time where we, you know, there was a tweet that I saw from PyTex this weekend about leaving, you know, to go off on your Labor Day holiday weekend to go and write more code. That's what a lot of us do. And maybe it's so that you can improve your programming skills or make some new friends, take part in this community and meet really amazing people. There could be a lot of reasons. Maybe you're just drawn by the energy and excitement of all the knowledge share that we do. Those reasons have really been discussed and discussed and dissected. And, you know, I don't really know. One thing that I do know is that we all have this very common passion. Everyone's very excited and they love what they work on. But that passion has to have limits. I think we've all discovered that at some point. So I'll start by telling my story. A few years ago, probably three, four years ago now, I just moved to Austin. I started and finished one contract job and then started another permanent job. I started a relationship. I was blogging or trying to. I had just begun doing Young Coders, which is the kids' Python class. And we teach at PyCon. I started developing that. I was teaching beginner Python classes here and, you know, and all over at small conferences around the South. I had gotten involved with the local CSTA, that's Computer Science Teachers of America. I was volunteering with them to try and help, you know, work to improve local computer science teachers in class or computer science classes in classrooms here in Austin. I was volunteering with a local program, Central Texas Discover Engineering, that brings technologists into classrooms to speak and to teach and kind of get kids excited about STEM. So I spent a lot of time doing that. In between all of those things, I was doing some technical review. I had a couple of friends that were doing Python and Django books. I was spending a lot of time reading. And I founded the PyLadies chapter here. So I was spending a lot of time doing meetups in classes to try and get that group growing. So as you can imagine, I was stretched to my limits pretty much. I was really exhausted most of the time. My relationships were suffering a little bit. My friends and relatives, I was not seeing very much of them. I started developing some health problems, which I will never go into here. I was traveling, sure, but the only travel that I was doing was for comrises. I used to joke that I was seeing the world, one PyCon and DjangoCon at a time and not much more than that. It started to take time away from my actual job, the day job that pays the bills. I was not getting to do any of the things that I love outside of programming. And so after a while, after a couple of years of this, I started to really dread every meetup, every class. My God, it was like pulling teeth, dragging me out to a meetup two, three nights a week was awful. In short, I was really starting to hate my big open source life. I was very involved, and I didn't want to. I really wanted to run away a lot of days. So it took a couple of years of this before I realized what I had to do, and that was just to scale back. I handed PyLadies over to some other very capable women here in Austin, and Inda's continued to grow to this day. It's been really amazing. I cut my teaching schedule back very dramatically. I stepped back from all of that volunteering, which was heartbreaking. It was a real shame, but I've been able to get some other people involved in my stead, and I started saying no to a lot of requests for my time. And eventually, things got sane. Things calmed down, and I was able to breathe again. So we know that burnout really is a result of long-term exhaustion. And everyone can have a busy day now and then or a busy week. So just when those weeks start turning into months and years, and you're doing the same thing, and you're struggling to get it all done, and you're taking on more over and over, you're being spread too thin for too long, and the result starts to feel a lot like depression. You start to dread what you're doing. It gets hard to get up out of bed some days, knowing what you're going to be facing. So it should surprise no one that that kind of thing can lead to really terrible performance. But what I think a lot of people don't realize is what a serious health toll it can take. Every time I open a browser, I see more news about new stories, new studies that are being done about the effects of overwork on the brain and the body. It's pretty scary stuff. Oh, by the way, the links in these slides. I'm going to post these slides to my blog, mechanicalgirl.com, after this. And there are going to be links. So you can actually read some of these articles in depth, take a look at these studies and see the kinds of things I'm talking about. So when you're juggling your day job and your open source work, and your personal lives, usually the first thing that gets sacrificed is sleep. I know that's true of me. I was at one point sleeping maybe two or three hours a night. It was scary stuff. So I wanted to talk about some of these articles that I found. So this one up here, this UC Berkeley thing that was posted in this episode back in July. This is actually a reference to the study over here from the Journal of Neuroscience. It's a very formal study conducted by UC Berkeley. I just really loved the sensationalist headline. When you're overtired, you perceive friends as enemies. And it kind of got me thinking. I wonder if that's where flame wars come from. People who love each other and respect each other suddenly find themselves at each other's throats when they're under the pressure of trying to get a pull request in. And then also, you guys know the XKCD cartoon. I can't go to sleep yet. Someone's wrong on the internet. Well, what if they're not really that wrong? What if they just seem wrong because you haven't gone to sleep yet? So there's that. And then this one over here, this is an article from mic.com from last year. This actually came accompanied with a really great infographic. It was too large to put in a slide here. I think you would not have been able to read it even up on this big screen. But I can give you some of the highlights. Sleep deprivation can lead to things like hallucinations, cerebral shrinkage, lost memories, false memories, lost focus. I think we're all pretty familiar with that. And ultimately brain damage is something that you can suffer from. But one of the stories that really caught my eyes, this last one here from NPR back in May, it's actually a story about another sleep study that was done by the University of Washington. One of the examples that they cite is the Exxon Valid Ease Crash. Now that happened back in 1989. So I realized some of you actually may be too young to even remember what a huge disaster that was. By some estimates, there were something like 40 million gallons of oil spilled. Hundreds of thousands of animals were killed, including orcas. There were a couple pods of orcas that were decimated. There were seabirds, seals, sea otters. I deliberately did not get any photos from the disaster. They're just too harvenging, especially if you're a hippie environmentalist like me. I just couldn't do it. These are very happy, alive seals, not covered in oil, but in water. I just want to point that out. But yeah, I mean, the fact is this disaster had a lasting impact on Prince William Sound. 26 years later, there are still thousands of gallons of oil in the water, in the sand. Most of the animal populations have not recovered. There was an entire oyster bed, I think, that was wiped out, that has started to come back, but that's about it. And I remember, I was in college at the time, I remember the rumor that was going around was that the captain of the ship was drunk and that he ran the ship aground. What came out later was that the captain wasn't even there. He was not at the helm. It was the third maid who had been up and working steadily for 18 hours at that point. And he was not the only one. The crew was accustomed to that kind of sleep deprivation, working 18-hour shifts and getting a couple of hours of sleep and then going on again with no breaks, no weekends. So they were pretty overworked. And the result of that was this huge environmental disaster. So it kind of made me wonder, I know people who have stayed up as long as 18 hours hacking on a project. It's not that uncommon, especially when you're young and eager and new to the community. It made me wonder, imagine working for that long and that hard and being that tired and your open source project crashing like that, what a disaster that could be. Not on the same scale, obviously. I don't expect that you would kill animals, but really giving your most tired self to a project is not good for that project. The people that you're working with, the people that are working around you deserve better, you deserve better. Your self-care is so much more important than getting that next line of code written. Sometimes you just need to step back and refresh and then come back to it with a new passion and if you're not going to do that for yourself, please do it for the otters. So if you take nothing else away from this talk, remember this phrase. This is probably the most important thing that I can tell you. When it comes time to recover, the first step is to simplify your life. You need to spend some time thinking about what it is that you really want. Do some soul searching. Make a list if you have to. Figure out what are the things that are really important to you? What's fulfilling to you? What's giving you joy? What are you doing that is really bringing you fulfillment? And if the answer is none of these things, well, maybe it's time to start jettisoning those things and look to something new. Or keep the one thing that you find that is really important to you. When I was feeling burned out and I needed to shed all of those projects, the one thing that I held on to was young coders. Because I started out my career as a teacher and teaching kids and teaching them programming is the one thing that I love the best. So that is the only thing that I do these days, aside from occasionally speaking, obviously. I focus on teaching and I develop curriculum and that's it. I say no to everything else. And there's one thing that I wanted to point out to you, another important point. When you are evaluating what's important to you, whatever you do, please do not compare yourself to other people that you know in this community. We all know someone who seems like they have a hand in every project. They're doing all the things. And you can't possibly know what they're going through behind the scenes. You have no idea if they are fulfilled or if they're struggling. So don't judge yourself by other people's contributions and other people's performance. Just focus on yourself and focus on what you want out of life. And I think ultimately you'll be happy. And then once you've made all those decisions and figured out what you want, get ready to start practicing this phrase. If you are overloaded and someone asks you to speak at a meetup, you can always say no or actually better thanks, but no. Be polite about it, firm but polite. If someone asks you to teach a class, same thing, you can say no. Then if people want to contribute to their project, and I know this is hard because everyone wants to be involved in these code projects. But if you're overloaded, you can say no, and it's okay. I'm giving you permission. Maybe you're worried that someone might be upset if you say no. And it's possible, that can happen. But if they are, anyone who's gonna be angry at you for turning down an offer or saying no to something is someone that is not worth your time, trust me on this. I think your mom would agree with me. And sometimes no just means not saying yes. You don't have to respond to every letter or every tweet that comes your way, every email. Sometimes just listening in on the conversation is enough. You don't have to participate. In fact, this is something that I feel really strongly about. I think that it took me a while to realize that any unsolicited email that I get really is just a big ask for my time that I didn't agree to. And it takes a lot of time. We want to be generous, we're conditioned to be generous with our time. But really, at the end of the day, you don't owe anything to anyone. You don't have to answer that email if it wasn't something that you agreed to do. But note that I said unsolicited. I mean, if you're organizing an event or you're leading a project, you've kind of implicitly signed up to deal with those things. And so those emails that come your way, they are for you. But that's something to keep in mind before you make your next commitment. Remember that those are the kinds of things that you're going to be burdened with and so maybe you don't want to commit to that project or that event, just, and also as I check my notes here. Saying no isn't a license to flake either. Do the things that you say you'll do. Just as you go forward, promise less, commit less. And you'll be a happier person, I swear. And those people that all seem to be doing all of the things, there is one thing that you can learn from them. They're very good at delegating and asking for help. The irony is not lost on me that everyone here is at the start of a conference, the start of DjangoCon, you're going to be exposed to a lot of new ideas and projects and you're going to want to get involved in all of them because they are all really cool. And you don't necessarily have to say no to all of them. Just, I think my best advice to you is just to be judicious. Guard your time carefully, be judicious with your commitments, really evaluate whether or not this project is going to be something that you'll enjoy or that you can offer something to you or that will be good for you before you jump in. You don't necessarily have to say no to things, but you might have to relieve yourself of some responsibilities before you take on new ones. And I have a couple of examples. So the first step towards giving yourself a break might be just mentoring someone new. So I have a story. Over this past year, I've been traveling a lot, doing a lot of conferences, and I've talked to lots of other women who are tech speakers. And I found much to my core that there are some of them that are traveling around the country, break next speed, doing as many as 15 to 20 conferences a year. That is no way to live. But right now, there's a big push in the community, in all of open source, really, to increase the visibility of women. And that's a very admirable thing. The problem is that these same 10 to 15 women cannot be doing all of these talks. So I think maybe we need to mentor some new ones, do some teaching, bring some people up and get more people involved and get more people talking about their experiences that are women, specifically. And then the same thing goes for that code library that some of you out there have been maintaining for many, many years. Probably to the point that you are so tired of it and you cringe every time a pull request comes in and maybe you're starting to really hate the language and you just are so sick of emailing people and talking about it. But maybe you've convinced yourself that no one else can do that job. As well as you can. Well, I have some news for you. There are a lot of fresh faces and a lot of developers in our community who just really want a chance to stretch and grow. And they just need that chance to get in there and get started. What's old hat for you is going to be very exciting for them. And they might make a few mistakes and they might stumble a little bit. But they'll be all the better if you spend the time to mentor them. So reach out to your user groups, reach out to mailing lists, find people who might be interested in filling your shoes. If it's something that you really want to get rid of, bring some new blood in. Don't be afraid to do that. And then hand the job over. I think that once you let go of it, the waist's gonna come off your shoulders. You're gonna be able to take a deep breath for the first time in a long time. And it's gonna feel really, really good. No, I have another great anecdote here, this is terrific. So something to remember if you're the one asking for help. Over the summer, I was at a party in Brooklyn hanging out with some other developers. It's pretty much the only people that I hang out with these days. It was a different community, different language altogether. But I was spending some time with some other people who are also very, very sought after speakers. And they had some horror stories to tell me. They get so many requests to come and speak at these conferences that they've had to start making excuses. They have to start lying about having personal commitments or a death in the family or something else that they have to do to avoid saying no. Because just saying no has stopped being enough. Applied, thank you, but no, I just don't have the time. It's not cutting it. There are some organizers out there that are actively hostile. And being like, well, so you'll do so and so's conference, but not mine. Well, nah, nah, nah, nah, nah, you know? And it just, it drove me crazy. I've never experienced that. And I couldn't imagine someone being that mean. But the point that I want to make is that if you're that person doing the asking, just be very careful that you don't cross over the line from being welcoming and encouraging into pressuring and bullying in some cases. Don't do that, please, please don't be mean. And by the same token, if you find that you're in the position where you're being pressured to contribute to talk or contribute to a project, you can push back gently but firmly. Some people may not know that they are putting on that much pressure until you tell them. So finally, we get to the good part. There are actually some things that you can say yes to. Once you're clear your plate, there are a lot of things in life that are out there to enjoy. You can go outside, for example, your inbox can wait. No, no, no, sorry. That outside, that's the one that you want. It really is that beautiful sometimes. The point is though that when you let go of all those things that are weighing you down, you can go out and take on the things that you really love. And this is just a quick sentence cloud that I put together with a handful of things that I enjoy doing that have nothing to do with code. I'm sure you can think of hundreds more. Make a list and work towards that. And then finally, I know, I know, this is probably one of the most annoying acronyms in the history of humankind. It's been used to justify a lot of obnoxious behavior and I felt really bad about including this. But if you think about it, there's a kernel of truth there. You only get one life and you really owe it to yourself to make the best of it. And that is it.