#activation

Choosing the litmus-test persona for onboarding, defaults, and install-path decisions in a developer tool.

Planning a launch, an onboarding overhaul, or deciding where the next quarter's developer-marketing budget goes.

A three-pane API reference with runnable, copy-once code that carries your own test key — the docs are the product tour.

The team wrote *Developer Relations* (Apress), created the Developer Journey Map that the field now uses as standard, and publishes the State of Developer Relations report.

Thirty-four skills covering audience context, content, distribution, developer experience, growth and retention — every one reads a shared developer-audience file first.

Anthropic's own four-phase guide to building an MCP server — research, implement, review, then generate ten evaluations that test whether a model can actually use it.

Scores SDK docs across the six sections integration actually fails in — installation, quick start, error handling, troubleshooting, examples, best practices — as an HTML report.

OpenAI's Akshay Nathan discusses building ChatGPT Work and the growth of Codex, around the claim that there are roughly 100x more people who use code than can write it — the bet being that this larger group is the real prize if the agentic interface is right. The episode notes say Codex monthly actives are up more than 10x this year, a figure quoted from the show's own tracking rather than a published OpenAI number.

Five sunsets landed in six weeks — on clocks of 27 days, 29 days, a month, ten months, and twelve months. The window is what gets quoted, but the mechanics decide who gets burned. A working anatomy of the clean deprecation, and the checklist for running one as the campaign it is.

For a developer product, the minutes between install and first success predict adoption better than almost any campaign. Here's how to find that path, measure it, and pave it.