Developer Experience (Japan Meetup 2025)

Robinson argues that developer experience starts with a product developers want to use; marketing cannot compensate for product problems. DX teams should talk with developers, surface difficult feedback early, and route it to the people who can improve the product. He describes DX as a cross-section of product, marketing, and sales, and says early hires need to be adaptable and connected to the community.

Robinson says documentation should ship alongside product changes and be maintained like a product, with regular investment in its platform and content. Docs should be accessible on the web, in editors, and through AI tools; he mentions SEO, JSDoc, llms.txt, MCP, and custom search or RAG. At Vercel, an AI-powered GitHub review suggests documentation edits, helping contributors follow the team’s style guide without making every suggestion mandatory.

A DX team should know the community’s main strengths and pain points, which Robinson recommends learning through regular feedback and AMAs. Vercel routes product feedback to relevant engineering, design, and product teams, then follows up with customers when issues are addressed. AI can help filter and find useful social posts, but Robinson says people should respond as humans, with empathy and practical help.

Repeated questions can reveal where education needs to improve: a question asked a few times may call for a guide or doc update, while dozens of repetitions may indicate that the product’s positioning is unclear. Robinson shares open-source Next.js demos as a way to teach patterns and invite community contributions. He also describes making a self-hosting video after hearing that deployment to a VPS was confusing, and using community feedback while developing it to improve the final resource.