Effectively the last chapter of the book is chapter nine: Developer Marketing Organization. And there it is. I did it. I referred to it as developer marketing, even though the title says that it doesn't exist. I couldn't think of another way to title this chapter.

So this is about, the roles you need, but also the book is really organized around the skills that are needed in whatever the group is that you call that does developer marketing.

And I think what you need—this part isn't in the book, but we've written about it on the EveryDeveloper blog and I've talked about it in conferences— it might be different depending on where you are on a spectrum of developer-focused to developer-enabled where, really how important is the developer audience to the business as a whole, and it doesn't matter. You can still enable developers, and need to do some of these things that we've talked about. But the more you are developer-focused, the more you're going to need a true developer go-to-market strategy and you'll need a lot more of the skills and roles that I write about in this chapter.

So developer-focused, it's much more likely that a developer relations team would be needed versus if developers are enabling other teams with the tools, then it's less likely that you would need multiple people working directly with your developer community.

I'm sometimes asked what, what is the least that we need to start attracting developers? And you can begin publishing content if you want, but really starting to think about how you want to reach those developers. What are the problems, understanding the problems, understanding the audience.

What type of developer, even down to the, what language or languages do they code in. If you can start to be able to answer some of those questions, you'll have a much better chance of being able to create content that will actually matter to the audience you want to reach.

And so can you just start publishing content and see what happens? Again, yes, you can. But then you are, throwing non-strategic content at the wall and you will learn something from it. And no matter what publishing content is about learning from what resonates with the audience, what does succeed in attracting developers and the right developers to your product. But you really want to take the best swings you can at that. And that's, where taking the time to figure out what those problems are and how you want to reach those developers will help you. That's the sort of stuff that we work on at EveryDeveloper. It's a big part of, why I wrote the book to help people be able to understand that frame of reference that a developer is coming from.

Really that empathy, which is one of the skills that I mentioned in this chapter is a key piece of not only your strategy to reach more developers, but what you look for in the roles that you put together in your marketing organization that happens to be trying to reach more developers. And that is the Organization. chapter of Developer Marketing Does Not Exist.