I just posted on gatekeeping. I kept out one argument because I think it's the most controversial, and specific, and didn't want it to detract from the others: Passion isn't necessary for developer relations #devrel 1/

You can be good at something, even devrel, without a passion for it. Don't get me wrong, passion can help. Passion for a topic can get you through the slog, it can keep you engaged with something. And being able to engage with what you are doing is necessary for devrel 2/

But requiring people to be passionate about their jobs, about what they do for their livelihoods, it's another form of gatekeeping. Knowledge, engagement, talent, skill, ability, interest, these are all other words that you can use, other approaches that get you there. 3/

That's not to say that passion is bad, it's just not a requirement. And passion isn't something that is a constant for most people. I'm not passionate about the same things I was in 2010. And I can be passionate about things that I then don't do for money. 4/

Caring about your job, caring about what you're doing is important but too much emphasis is placed on "passion". Passion can burn you out, use you up. What I care about long term with someone is can they keep doing the job?Can it be fulfilling for them? Or can I make it? 5/

I talk to people who work for me about career goals. Big companies often translate "career goals" into "how do I get a good rating?" and "how do I get promoted?" and that's valid. but also valid "How do I learn about x,y,z?" and "How do I get to work on something meaningful?" 6/

And "How do I get to earn more money for my family?" 7/7