Articles

One of the things the other developer relations advocates here at New Relic and I often hear from customers is, « Even though I understand why observability is important, I’m having a dickens* of a time getting leadership to buy in (literally). »

Let me begin by pointing out how important it is for us — IT practitioners — to be willing and able to speak to management and leaders of the business about the work we do, and to do so in a way that is understandable and meaningful to the audience. I’m not implying you have to explain observability in a patronizing « explain it like they’re five » kind of way. I mean you need to explain the WHY of observability in the context of what the audience feels is important.

Source de l’article sur DZONE

As more companies realize the benefits of an API-first mindset and treating their APIs as products, there is a growing need for good API product management practices to make a company’s API strategy a reality. However, API product management is a relatively new field with little established knowledge on what is API product management and what a PM should be doing to ensure their API platform is successful.

Many of the current practices of API product management have carried over from other products and platforms like web and mobile, but API products have their own unique set of challenges due to the way they are marketed and used by customers. While it would be rare for a consumer mobile app to have detailed developer docs and a developer relations team, you’ll find these items common among API product-focused companies. A second unique challenge is that APIs are very developer-centric and many times API PMs are engineers themselves. Yet, this can cause an API or developer program to lose empathy for what their customers actually want if good processes are not in place. Just because you’re an engineer, don’t assume your customers will want the same features and use cases that you want.

Source de l’article sur DZONE

With the recent downturn on public stock markets due to COVID-19, a recession or depression is almost inevitable. It’s likely we see mass failures across retail, travel, entertainment, and other industry sectors. The spillover from coronavirus disease and the following shelter-in-place can have drastic consequences in the startup world. Small brick and mortar businesses that were shuttered due to shelter-in-place rules will no longer are spending money on Facebook or Yelp to promote their business nor will they maintain their SaaS subscriptions. Large enterprises will pull back spending in sales and marketing in anticipation of a recession. This could cause reduction in seat counts or usage for SaaS contract.s Similarly, sales teams may find CFOs and financial controllers are blocking many more purchases than before forcing deals to be stuck in procurement or legal review.

The good news is that many developer platforms and APIs have tricks that make them more resilient to a recession. However, if you’re not doing these items today, now is the time to reconsider to ensure the longevity of your product and/pr company.

Source de l’article sur DZONE

I’ve worked with Developer Relations for many years now, and I think it’s a fascinating topic with many takes on what it is and how to do it! I wanted to share my view on it here, and what I think it encompasses.

Last year I gave a presentation called "Have you tried listening?" at the DevRel Summit which I think outlines a number of the main DevRel concepts and areas, and examples from my personal experiences with them.

Source de l’article sur DZONE