<Every important cross-cutting concern> should be part of the culture, not a project.<p>Quality, security, devops, performance, observability, you name it. If you have a separate team for it, I know you're not serious about it.
i winced at the part where jason basically talks about john cutler-style feature factories shipping some new beta every few months without follow thru and how it makes you fall behind on messaging despite being first to market compared to competitors. too true. and not fixable at the devrel level; its a product and eng leadership issue but a VP should be able to give that feedback and make change happen.
This was great, and about a lot more than devrel. I enjoyed his comments about messaging and how you should stick with a message for at least 6 months, preferably more.
Is there any company out there that would treat development relationships as a project? If you are a SaaS company targeting developers surely your own developrs know what DevRel is about.