How Ben Dechrai Became a Developer Relations Advocate

Early Career: From Code to Community

Ben Dechrai's journey into software engineering began in childhood, inspired by his father's work as a forensic scientist with a home laboratory. Programming on an Amstrad CPC6128 in BASIC and assembly language sparked a lifelong fascination with making computers execute his will. After formal education, Dechrai began his professional career in 1999 coding in VB and ASP, later transitioning to PHP development. While these early language choices earned him sympathy from peers, they represented logical market progression at the time. His move to Melbourne, Australia in 2002 marked a pivotal shift as he became deeply involved in the developer community, running meetups, organizing conferences, and speaking at events worldwide.

The Evolution into Developer Advocacy

Around 2010, Dechrai expanded his expertise into consulting and security work, becoming comfortable with a contract-based lifestyle that allowed him to attend conferences regularly. This consulting background provided the foundation for what would eventually become his role as a Developer Relations Advocate—a position that didn't have a formal title when he was already performing its core functions. The transition happened naturally as he discovered his genuine passion for authentic conversations with developers about the problems they faced. Unlike a one-directional support model, Dechrai learned from developers while helping them, finding the bidirectional exchange far more powerful and rewarding than traditional technical support.

The Unique Position of Developer Advocacy

Developer advocacy sits at an interesting intersection within an organization, representing both the company's products and the developer community's interests back to the business. Dechrai describes this positioning as "Best of Both Worlds"—advocates work to raise awareness of products while helping developers use them more effectively. A critical aspect of the role involves identifying where developers struggle with existing products, gathering feedback on desired features, and communicating these insights back to internal product teams. This cusp position allows advocates to improve developer experiences while supporting business objectives, creating a mutually beneficial dynamic.

Clean Code and Developer-Centric Thinking

Dechrai emphasizes that aspiring software engineers must master core fundamentals including data structures and software architecture. However, he advocates for a fundamental mindset shift: prioritize the next person who will read your code over optimizing for computer performance. Modern computing power has made this philosophy not only humane but practically sound—writing readable, comprehensible code that resembles English is far more valuable than micro-optimizations. Clean, readable code makes it easier to identify logic errors, security vulnerabilities, and bugs during development rather than after deployment. Simplified conditionals and readable structures allow developers to understand business logic flow intuitively, catching issues before they reach production.

The Power of Empathetic Leadership

Early in his career, approximately three years into his first job, Dechrai learned a transformative lesson: you can accomplish more for a team by doing less individual coding and supporting colleagues in other ways. Whether ordering lunch, ensuring proper breaks, or organizing late-night food for working developers, these seemingly small acts of care have outsized impacts on team productivity and morale. This philosophy extends naturally into developer advocacy, where genuine engagement and understanding of community challenges creates stronger, more authentic relationships than transactional support ever could.

Key Takeaways

• Developer advocacy requires authentic, bidirectional engagement with communities rather than one-directional support, allowing advocates to learn as much as they teach
• Clean code prioritizing readability and human understanding over pure performance optimization leads to better bug detection, fewer security issues, and improved long-term maintainability
• Developer advocates occupy a unique position representing both company interests and community needs, enabling them to bridge gaps and improve products based on real-world feedback
• Supporting team members through non-coding contributions can paradoxically increase overall productivity and impact
• Core software engineering fundamentals remain essential, but modern development philosophy should emphasize code clarity and the next developer's experience