Monday 10:30 a.m.–10:55 a.m.
Things that are tired: Uggs, Segways and YOU! Coming back from burnout
- Not Applicable
Open source communities are fueled by people's participation. With all that activity and responsibility, burnout is inevitable - we're all driven to do the best job we can. But when burnout sets in, it becomes hard to do your best work. The goal of this talk is to help developers recognize when it's time to step back, and to provide some simple tactics for doing so.
Why is burnout such a bad thing?
When I see that question on paper, the answer seems obvious. But in nearly a decade in this community, I've seen people run themselves into the ground without realizing that they can - and should - take the time to rest. Why? Well, the short answer is that, if you don't take a break once in a while, the quality of your work suffers. But the long and more involved answer? Well, as a wise man once said,
"Life moves pretty fast. If you don't stop and look around once in a while, you could miss it."
Burnout leads to exhaustion, and that leads to terrible performance. And no one wants to be known for performing terribly - we all have too much pride for that. History is full of examples of times when exhaustion led to disaster - remember the Exxon Valdez? Imagine your open source project taking a header like that. I'm actually going to get a little science-y here and cite a few studies, in particular a recent one from Washington State University that shows how sleep-deprived people have an impaired ability to take in new information.
Of course, you can get plenty of sleep and still be burned out. If your waking hours are consumed with community work, your relationships can suffer, and your sanity will erode pretty quickly.
After nearly a decade in the Python and Django communities, I've experienced periods of overwork that have made me hate everything I was doing. I have a lot of good anecdotes, stories that will probably sound familiar to everyone in the room. Luckily, I've also learned some tactics for stepping back and recovering. It can be done, and it's easier than people think. What you're going to hear from this talk is just plain common sense. But sometimes when you're mired in work with no obvious way out, you need to hear it from someone else. So I'm giving everyone permission to let go. (And no, I promise, there will be no 'Frozen' references in my slides.)
But how do you let go? And when?
Burnout is pretty easy to recognize if you know what to look for. Are you staying up every night reading pull requests ... and is that your primary method of interaction with other human beings? Your user group may only meet once a month, but is that group still responsible for the bulk of your email? Do you secretly blame them for your inability to get to inbox zero? Is the only travel you're doing for conferences? Have you given up on vacations and just decided to see the world one PyCon or DjangoCon at a time?
The biggest indicator of burnout in the community is how you feel about the community around you. When you find yourself starting to cringe every time you get a new Twitter follower, it may be time to start saying no to things.
The most important piece of advice I have is to stop looking at what other people are doing. We all know that person who seems to have a hand in every project, but you can't judge your own performance by what you imagine theirs to be. You don't know how they may be scrambling behind the scenes.
And remember that just because you're invited into a conversation doesn't mean that you have to contribute to it - sometimes listening is enough. Emails can sometimes go unanswered - so can phone calls! Think about what's most important in your life, and start directing your energy towards those things instead.
Don't write so much code in your free time. Take a few nights off, go outside - there's a lot to see out there!
Your collaborators WILL understand. Especially if you announce your intentions to the world. Send an email, tweet it out, let people know you need some time off. You'll be surprised how much understanding you'll get and how well people will respect your boundaries (you just need to set them).