#dx

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

Designing or marketing an API where an autonomous agent could evaluate, integrate, or transact on a developer's behalf — anything that sells or provisions something programmatically.

Your product ships an MCP server, or "MCP support" appears anywhere in your positioning.

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

Docs served as markdown and OpenAPI with a quickstart that says "hand this spec to your LLM" — and a purchase flow (quote-token, idempotency keys, consent record) an agent can run without over-buying.

A long, honest architecture explainer — WireGuard, NAT traversal, DERP relays — that markets by teaching the mechanism instead of hiding it.

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

"Engineers who write" as the staffing model, with Dell, NVIDIA, Qualcomm, AMD and Stripe named, sold three ways: a scoped sprint, an embedded documentation engineer, or full ownership.

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.

A named devtools practice covering startup advisory, design for CLIs and SDKs, and developer marketing, with bolt.new, Lago and Whop as clients and 100+ open-source projects behind them.

A Y Combinator-backed docs studio for devtools with Supermemory, Greptile, Reducto and Rootly shipped, agents doing the code verification and humans doing the architecture.

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.

GitHub announced on 2026-08-04 that Spark stops accepting new users and new apps immediately, with existing users given until 2026-08-31 to export their work; already-deployed apps keep running, but any app using the `llm()` function needs a new inference provider since GitHub Models (the service behind it) retired 2026-07-30. It is the shortest deprecation window in this site's running comparison — about 27 days' notice against MCP's 12-month offramp, GitHub Models' own six weeks, and HCP Vagrant Registry's 21 months.

Sinch launched Agent Tools on 2026-08-04: VS Code/JetBrains/Open VSX extensions, an MCP server exposing live Sinch API definitions, a Simulator Mode that tests integrations before an account exists, and "Sinch Skills" — structured implementation guidance for AI coding assistants including Claude Code, Cursor, GitHub Copilot and ChatGPT Desktop. It joins a growing roster of vendors making their platforms "agent-safe by design" rather than just documented for humans.

HashiCorp is retiring the HCP Vagrant Registry in three dated phases — new box creation stops 2026-12-14, support ends 2027-03-15, all operations cease 2027-06-07 — with documented S3 export guidance and the open-source community edition kept alive as the fallback. It is the longest migration window on record in this site's deprecation-window comparisons, ahead of MCP's 12-month offramp and well past GitHub Models' six weeks.

Recorded at Heavybit DevGuild, the episode traces how Unikraft went from an academic unikernel project to a cloud platform for efficient workloads, and covers why unikernels can make applications faster, cheaper and more secure. The framing worth noting for a devtools marketer is the demand story: AI agents needing disposable sandboxes is what turns a research-grade technology into a category with buyers.

MCP's biggest spec revision started a twelve-month migration clock under every MCP server the same week GitHub retired Models on a six-week runway with no like-for-like replacement. How you end things is becoming as much of a marketing surface as how you launch them.

GoDaddy and Atlassian both shipped product for the agent-as-user in the same week — the thread graduated from tiny Show HNs to platform roadmaps — while Cerebras showed how quietly sunsetting a free tier burns trust it took years to earn.

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.