Saltar al contenido ForoHackers

Developer relations: start here

Relaciones con desarrolladores
#2889 · · Citar · Denunciar

Developer relations is the work of helping outside developers succeed with a platform, library or API, and carrying what they say back to the people who build it. It mixes teaching, writing, speaking, sample code and listening. Credibility comes from being a working engineer who respects the audience's time.

Key concepts

  • Developer experience: the whole path from first look to a working result; every friction point is a lost user.
  • Time to first success: how fast a newcomer gets something real running.
  • Content: tutorials, samples, talks and videos, each aimed at a clear audience and goal.
  • Feedback loop: collecting questions and bug reports, finding patterns and getting them fixed.
  • Community: forums, events and maintainers who answer, thank and welcome.

Vocabulary

  • Advocate: someone who speaks for developers inside a company and for the product outside.
  • Sample app: a small working program that shows the right way to use an API.
  • SDK: software development kit, the libraries and tools for building on a platform.
  • Onboarding: the first steps a new developer takes, from signup to a working call.

What to study, in order

  1. Follow another project's getting-started guide with a stopwatch and record every stumble.
  2. Build a small sample app against a public API and write its tutorial.
  3. Give a ten-minute talk or screencast on it, then collect questions.
  4. Triage a project's open questions into themes and propose three fixes.
  5. Learn to write an honest bug report that a maintainer can act on.

Related tags

#technical-writing #api-design #open-source-community #documentation

No has iniciado sesión, así que esto se publica como anónimo: no se guarda con ello ninguna cuenta, nombre ni dirección, y no puede llevar enlaces ni imágenes. Inicia sesión o únete para publicar con tu nombre. Los registros de nuestro servidor web guardan la dirección y la hora de cada petición hasta 14 días; para que la tuya no quede en ellos, usa Tor. Para escribir al equipo de forma confidencial, usa el buzón. Firmar como fuente habitual (una clave guardada solo en este navegador)

Enviar tarda unos segundos aquí: tu navegador resuelve antes una prueba de trabajo contra el spam.

Responder