Evolving DevRel Strategy: Understanding Developer Needs and Communicating Value
TL;DR
- Feedback, even when critical, is a valuable gift for professional growth, requiring careful unpacking to derive its underlying value for improvement.
- Developer Relations (DevRel) is evolving from broad content creation to a more strategic approach focused on understanding developer needs and communicating company value.
- Companies should prioritize hiring DevRel professionals based on their understanding of developer mindsets and problem-solving abilities, not just follower counts.
- Effective DevRel involves a dual strategy of listening to developers to identify their problems and then communicating solutions in a way that resonates with their skepticism.
- Human problems in technology, such as communication gaps and understanding user needs, are often more complex and impactful than coding challenges.
- Content creation in DevRel requires a strategic balance between reactive responses to immediate developer queries and long-term sustainable narratives that convey company value.
- The ideal "dream computer" for developers would combine a distraction-free, aesthetically pleasing interface with a mechanical keyboard and a high-refresh-rate screen, merging functionality with user experience.
Deep Dive
Cassidy Williams' career in Developer Relations (DevRel) demonstrates that success in tech advocacy is built on genuine connection and a commitment to uplifting others, not just on follower counts. This approach has evolved significantly, shifting from in-person events to a more strategic, content-driven model that requires deep understanding of developer needs and iterative communication, thereby impacting how companies should approach hiring and how individuals can build impactful careers.
The core of Williams' philosophy, "lifting as you climb," is a powerful driver for both personal career growth and community development. This principle, learned from mentors, emphasizes the importance of sharing knowledge and guidance to help others advance, creating a virtuous cycle of support. This is directly applicable to the DevRel space, where understanding developer mindsets and problems is paramount. Companies looking to hire in DevRel should prioritize individuals with a strong grasp of developer challenges and communication skills over superficial popularity metrics like follower counts. Williams notes that the ability to code or deeply understand coding principles is crucial, as is the capacity to tailor strategies to specific developer audiences, whether they are open-source contributors, enterprise CTOs, or security professionals.
The evolution of DevRel itself highlights a shift from broad, in-person engagement to more targeted, content-centric strategies. The pandemic accelerated the move towards digital content creation, but the current landscape demands a more nuanced approach. Instead of mass content production, effective DevRel now involves identifying developer pain points through feedback channels and translating those into valuable tutorials, talks, and live streams. This requires a strategic understanding of SEO, community forums, and the underlying narrative companies wish to convey. The challenges in DevRel, including recent layoffs and subsequent resurgence, underscore its value as a bridge between companies and developers, necessitating roles that can listen, communicate, and advocate effectively.
Williams' personal content creation philosophy centers on listening to developers and meeting them where they are. This means acknowledging skepticism, addressing specific concerns about new technologies like AI, and providing practical guidance rather than simply pushing a company's agenda. The goal is to facilitate conversations and solve problems, recognizing that not all developers will respond to the same message. This principle extends beyond DevRel, offering valuable insights for any professional aiming to communicate effectively across teams or with leadership. The preferred medium for communication varies, with Williams favoring written content for its asynchronous nature and live streaming for its direct engagement, while acknowledging the challenges of video editing and the uncanny experience of hearing one's own voice. Ultimately, success in DevRel, and indeed in many tech roles, hinges on translating technical understanding into human connection and fostering a supportive ecosystem.
Action Items
- Audit content strategy: Identify 3-5 developer feedback channels to analyze trends and inform content creation.
- Create runbook template: Define 5 required sections (setup, common failures, rollback, monitoring) to prevent knowledge silos for new DevRel hires.
- Implement mentorship program: Establish a structured process for reviewing resumes and conducting mock interviews for 3-5 junior engineers per quarter.
- Measure DevRel impact: Track correlation between content engagement (e.g., tutorial views, forum participation) and product adoption for 2-3 key features.
- Design developer community guidelines: Draft 5 core principles for fostering constructive feedback and knowledge sharing within 1-2 online communities.
Key Quotes
"The previous indicator was like there are a certain number of questions on stack overflow about a certain topic and if there's not that many questions oh no you're early which is good but also rough and now it's like where are the resources if it's not like very explicitly defined in docs people aren't writing blog posts it's not trained in like the llms you might be asking questions to."
Cassidy Williams explains that a lack of readily available resources, such as Stack Overflow questions or blog posts, indicates that one is working with bleeding-edge technology. This situation, while good for being an early adopter, presents challenges due to the absence of established documentation or community knowledge. Williams highlights that this is a common experience with new technologies where users must navigate and discover solutions independently.
"And so i ended up there's a whole other backstory of how things ended up happening i'm gonna do a very speedy thing i did a hackathon on an airplane that was a flight from san francisco to london my team ended up winning and i ended up speaking at the united nations and on that united nations trip i also interviewed at venmo and i got the job."
Cassidy Williams recounts an unusual path into her developer advocacy role at Venmo, involving winning a hackathon on an airplane, speaking at the United Nations, and subsequently interviewing for the position. Williams uses this anecdote to illustrate that career paths can be unconventional and that significant opportunities can arise from unexpected circumstances. This story demonstrates her ability to connect diverse experiences into a cohesive career narrative.
"I feel like the mentors I've had throughout my career and just advice and stuff that I've been given have have I wouldn't be here today if it weren't for people who were able to give me those tips where yes I have worked hard I've done the interviews I've I've I've built the things but I've gotten a lot of guidance and direction by people who were willing to lend that hand and be just like hey you're not doing this right why don't why don't you go in this direction."
Cassidy Williams emphasizes the critical role of mentors and advice in her career progression, stating she would not be where she is without their guidance. Williams explains that while hard work and skill are essential, mentorship provides crucial direction and helps correct missteps. She highlights that mentors offer advice on career paths, compensation, and strategic decisions, significantly impacting professional development.
"I mean even since last year I would imagine how things changed since then it's it's such a weird like I don't even want to call it a pendulum because I don't think we're going back to anything but first of all devrel like when I first entered it in the in the venmo years over a decade ago it was going to going to events and and just like being a present and a a a a a present person a presence at all kinds of different events constantly and it was a very in person thing and then the pandemic happened and so many things started changing in terms of like okay now dev advocates are content creators they're they're making youtube channels and podcasts and live streams and they're they're posting as much as they can they're they're getting lots of eyeballs."
Cassidy Williams describes the significant evolution of Developer Relations (DevRel), noting its shift from primarily in-person event presence to a strong focus on content creation, including YouTube channels, podcasts, and live streams, especially accelerated by the pandemic. Williams indicates that the DevRel landscape is not returning to its previous state but is undergoing continuous adaptation. She points out the increased emphasis on content creation as a primary mode of engagement for DevRel professionals.
"So that's such a great question because that's one where I've actually told companies saying like you have to stop looking at follower count because that doesn't mean anything and there's once like I it was I felt so like petty and smug or a company came to me once like tail between their legs and they were saying you are right we hired someone because they were super popular on youtube but they didn't actually know what the job was and I was like exactly so satisfying I love being right."
Cassidy Williams advises companies against prioritizing follower count when hiring for Developer Relations (DevRel) roles, citing an instance where a company learned this lesson the hard way. Williams explains that high follower counts do not necessarily translate to job competency in DevRel. She stresses that understanding the developer mindset and the specific needs of the role are far more important than superficial popularity metrics.
"For me because I've been in it for so long so much of it is driven by my gut which is not something that you can pitch to a manager or where you're just like I just know that devs will like this okay just trust me sometimes that works but that doesn't always work I feel like when I approach advocacy I try to figure out like once again who am I talking to what do they care about and stuff I really try to regularly go through like feedback of what developers are saying."
Cassidy Williams discusses her content creation philosophy, acknowledging that while intuition plays a role due to her extensive experience, she prioritizes understanding the target audience and their needs. Williams explains that she actively reviews developer feedback from various channels to identify trends and inform content strategy. She emphasizes that this data-driven approach, rather than solely relying on gut feeling, is crucial for effective advocacy and pitching ideas to management.
Resources
External Resources
Books
- "The Pragmatic Engineer" - Mentioned in relation to a quote about feedback being a gift.
Articles & Papers
- Microjournal Blog Post (cassidoo.co) - Mentioned as an example of a digital typewriter project.
Tools & Software
- GitHub - Mentioned as Cassidy Williams' employer and a platform for developer tools and community.
- Vim - Mentioned in relation to a keycap set design.
- Game Boy - Mentioned in relation to a keycap design.
- Google Drive - Mentioned as a destination for exporting written content from the microjournal project.
- Daylight Computer - Mentioned as an example of a distraction-free computer with an e-paper screen.
People
- Cassidy Williams - Guest, Senior Director of Developer Advocacy at GitHub.
- Bethany Janos - Host of the Overcommitted podcast.
- Brittany Ellich - Host of the Overcommitted podcast.
- Erika - Host of the Overcommitted podcast.
- Sailorhg - Mentioned in relation to designing keycaps.
Organizations & Institutions
- Overcommitted Podcast - The podcast hosting the discussion.
- GitHub - Cassidy Williams' employer, a platform for developer tools and community.
- Venmo - Mentioned as Cassidy Williams' first employer in a dev advocacy role.
- Amazon - Mentioned as a previous employer of Cassidy Williams.
- Netlify - Mentioned as a previous employer of Cassidy Williams.
- Stack Overflow - Mentioned as a resource for gauging the maturity of a technology topic.
- Twilio - Mentioned for a past program to help people communicate tech better.
- National Football League (NFL) - Mentioned in the context of a hypothetical scenario for keyboard protection.
- Pro Football Focus (PFF) - Mentioned in the context of a hypothetical scenario for keyboard protection.
- New England Patriots - Mentioned in the context of a hypothetical scenario for keyboard protection.
- Logitech - Mentioned as the brand of a silent keyboard.
- Razer - Mentioned as the brand of a previous keyboard.
Websites & Online Resources
- cassidoo.co - Cassidy Williams' personal website and blog.
- github.com/cassidoo/ama?tab=readme-ov-file#what-mechanical-keyboard-should-i-buy - A link to Cassidy Williams' mechanical keyboard recommendations.
- drop.com/buy/drop-dsa-astrolokeys-keycaps-by-sailorhg-and-cassidoo?defaultSelectionIds=966968 - A link to a keycap set designed by Cassidy Williams.
- overcommitted.dev - The website for the Overcommitted podcast.
- github.com/bethanyj28 - Bethany Janos' GitHub profile.
- brittanyellich.com - Brittany Ellich's personal website.
- github.com/eggyhead - Erika's GitHub profile.
Other Resources
- Developer Relations (DevRel) - A field discussed extensively, focusing on its evolution and hiring practices.
- Desktop Apps with Local LLMs - A current area of interest and challenge for Cassidy Williams.
- Blogvent - A personal challenge by Cassidy Williams to blog every day in December.
- Keyboards - A personal interest and hobby of Cassidy Williams, with detailed discussion of types, switches, and custom builds.
- Mechanical Keyboard Switches - Discussed in detail, including specific types like creams, gateron black inks, and zealios.
- Keycaps - Discussed in relation to custom keyboard designs, including specific sets like GMK Oblivion and a Game Boy escape key.
- Typewriter - Mentioned in relation to Cassidy Williams' microjournal project.
- Plank Keyboard - Mentioned as a type of keyboard with a specific layout.
- Moonlander Keyboard - Mentioned as a type of keyboard with a specific layout.
- Think 6.5 Keyboard - The keyboard Cassidy Williams is currently using.
- Huntsman Mini Razer Keyboard - A previous keyboard used by one of the hosts.
- Logitech Silent Keyboard - A current keyboard used by one of the hosts.
- Ibook G2/G3 - Mentioned as an aesthetic inspiration for a dream computer.
- E Ink Screen - Discussed in the context of distraction-free computing.
- 60 Frames Per Second E Paper Screen - Mentioned as a desired feature for a distraction-free computer.