Why Developer Relations Matters

ramijames.com

2 pointsramijames4 comments

This is partly just a timely gripe, but as an example of what not to do... There's a certain company whose SaaS product has an API. Parts of the documentation are public, and others are--with no obvious rhyme or reason--locked behind a login page for customers only.

As someone developing client software that their direct customers will use, every once in awhile some feature request or bug comes up, and I'm locked out half the documentation, because they never let the login remain valid for more than a month. I'm sorry guys, but your API docs simply aren't that good, no one even wants to steal them.

With all that, why would I ever have positive things to say about their product to others developers?

Funnily enough, I came across exactly this yesterday. An important part of the docs, which would help me decide if I wanted to recommend this tech up the chain, was "only available for enterprise". I'll never understand the logic behind gating documentation. It should ALL be public.

For me it's always an adverse inference, suggesting one-or-more of:

1. They have bad support or don't see the API as important

2. They have something to hide

3. Their management doesn't understand or prioritize software

All three. It's always all three.

Reply on news.ycombinator.com