Developer Relations - The Book.
How To Build And Grow A Successful Developer Program
For many years, we knew that the practice of Developer Relations needed a book. One that could codify this practice by putting a stake in the ground of what Developer Relations is, and a guide to work by. We also had frameworks, processes, and a whole lot of experience built out over fifteen years that we wanted to share. So we combined our knowledge to write this DevRel Book. Two years later, in the fall of 2021, it was published.
Our intent with our book was also to contribute to the growing recognition and professionalization of Developer Relations as a practice and Developer Relations achieving C level authority within companies.
Who the book is for:
The book is for current or aspiring Developer Relations leaders and their stakeholders within a wider organization.
Questions that are answered:
How do we convince stakeholders to support a program?
How do we go about creating a program?
How do we make developers aware of our offer?
How do we stand out from the crowd?
How do we get developers to use our products?
How do we ensure developers are successful using our products?
How do we measure success?
How do we maintain the support of our stakeholders?
What will you learn?
What Developer Relations is and how it contributes to a company's success.
How to launch a DevRel program.
How to operate a successful DevRel program.
How to measure the success of your program.
How to manage your stakeholders.
Who is the book for?
Those interested in starting a new DevRel program.
Those looking to increase the impact of an existing DevRel program.
Those interested in learning more about DevRel.
For DevRel professionals, executives, investors, engineers, product managers, marketers, and students.
It's for you!
I just started reading it as well. It's chalked full of great insights and provides a good foundation for the history of DevRel and the core responsibilities. I highly recommend it to anyone working or thinking about working in the field.
This book provides a comprehensive overview of what is Developer Relations, why it matters, and how to build a Developer Relations program. I have used this book as a reference in building several DevRel programs from the start - from creating the initial strategy and mission, evaluating various resource needs, setting up those resources as a program, to measuring the success... and everything in between. As far as I know, this is the first book that attempts to formalize the discipline of Developer Relations.
"Developer Relations" by Caroline Lewko and James Parton: highly recommended if your company (has) or is starting a new Developer program.
I have only read half of the book so far but I cannot deny that it has already answered questions I had as to how software developers are recognized as decision makers and why companies are increasingly improving programs and processes to get in touch with the developers.
If you're looking for a good intro-to-everything guide with good references to supporting and extension materials, then this has hit the spot for me.As a software engineer and product manager, this book covers many of the things I've been doing ad-hoc for many years, and shed new light on many activities that I should start doing or could do better. It is a reasonably quick read, with a logical flow if you're reading cover to cover like I was. The frameworks are simple and useful. All-in-all it was
Currently reading @jamesparton and @CarolineLewko's Developer Relations book and screaming that it wasn't around in Feb when I started.
If you're working in, setting up or running any kind of dev or design advocacy stuff, this is crucial reading. https://link.springer.com/book/10.1007/978-1-4842-7164-3…
I regularly use this comprehensive guide to DevRel to jumpstart my team's understanding of this fast-growing discipline. The Developer Journey framework is a great reference shaping how we build products for "developer-first" businesses. I also appreciated the extensive 3rd party market analysis assembled in a coherent narrative - it saved me hours of research.