I recently heard an analogy equating DevRel to an iceberg (shoutout to David G. Simmons!). The idea is for every visible activity (talks, blogposts, etc.), there's so much more happening behind the scenes building tools, maintaining a safe and welcoming community, and more. Wassim Chegham recently published a visual that goes along with this idea, including things like collaboration, being "customer zero," and testing out new tactics all in the "below the water" section of the iceberg.
With all of these things on our plates, it's more important than ever to clearly prioritize our work. One of my favorite ways to do this is setting out an impact effort matrix to better understand which projects should be dropped, which ones are a priority, and which ones should be tabled for another time. I know personally just how busy things can be, especially at this time of year. Perhaps pushing pause on your projects just long enough to evaluate your work is exactly what you need in order to make it through this busy period!
Breaking into DevRel
If you're DevRel-curious and looking to break into Developer Relations, it can seem a bit intimidating. Lucky for you, I have a few resources for you today!
- Career Change: How I Became a Developer Advocate by Amruta Ranade
- How to Get Your First Job in Developer Relations by Alex Lakatos
Lastly, if you're looking for a new job, take the time to read through this thread from Noele Flowers. In it, she lists some of the questions she always asks when interviewing. My favorite is this: "What problems throughout the org are you trying to solve with community?"