# DX Published articles for DX. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How agentic development affects team collaboration DevFeed: [How agentic development affects team collaboration]() Original publisher: [Read original article]() Author: Irina Nazarova (inazarova@evilmartians.com) Published: 2026-09-09T00:00:00Z Content type: opinion Language: en Sources: [Evil Martians]() Topics: [Development](), [Artificial Intelligence](), [Code](), [pull-requests]() Tags: [agentic-development](), [ai](), [code](), [collaboration](), [developer-community](), [development](), [dx](), [teamwork]() ### AI overview This opinion article examines how agentic development can increase individual speed while making collaboration harder. It distinguishes learning work, such as testing hypotheses and building experiments, from other engineering work even when both produce code, and presents practical ideas for working together again. ### Source excerpt Agentic speed turned all of us into super-ICs and broke our ability to collaborate. Two types of work that both produce code, and three recipes for working together again: a safe perimeter for experiments, shared rules everybody pays for, and an intent log your agents write themselves. ## Migrating evilmartians.com from Gatsby to Astro in two weeks with Claude DevFeed: [Migrating evilmartians.com from Gatsby to Astro in two weeks with Claude]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Astro](), [gatsby](), [migration](), [Claude](), [Large Language Model](), [GraphQL](), [React](), [Security](), [build performance]() Tags: [ai](), [astro](), [build](), [claude](), [dx](), [graphql](), [javascript](), [migration](), [react](), [security](), [typescript]() ### AI overview Evil Martians describes migrating evilmartians.com from Gatsby to Astro in two weeks with Claude. The article outlines the site's Gatsby maintenance, security, and build-time costs, and discusses four bugs that could have shipped if the agent had operated without oversight. ### Source excerpt 367 posts, four years on Gatsby, and no dedicated team: here's how we moved evilmartians.com to Astro in two weeks with an LLM. ## Checks for safer review of rapidly generated TypeScript and React frontend code DevFeed: [Checks for safer review of rapidly generated TypeScript and React frontend code]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Front end](), [React](), [TypeScript](), [Artificial Intelligence](), [OpenAPI Specification](), [API](), [mutation-testing](), [Testing](), [Code]() Tags: [agent-experience](), [agentic-development](), [agents](), [ai](), [api](), [code](), [continuous-integration](), [dx](), [frontend](), [llms](), [mutation-testing](), [openapi](), [react](), [testing](), [typescript]() ### AI overview This article presents ten checks for making rapidly generated TypeScript and React frontend code safer to trust and cheaper to review. It covers API contracts, generated types, boundary validation, mutation testing, dead-code detection, and mandatory checks. ### Source excerpt Ten checks that catch what AI-written frontend code hides: contract codegen, boundary linting, mutation testing, and dead-code detectors. ## How to reduce Rails boot time with require-profiler and Bootsnap DevFeed: [How to reduce Rails boot time with require-profiler and Bootsnap]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-08-19T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Rails](), [Optimization](), [Ruby](), [Instrumentation](), [Docker](), [Development]() Tags: [development](), [docker](), [dx](), [instrumentation](), [optimization](), [performance](), [rails](), [ruby]() ### AI overview This guide explains how to profile and reduce Rails application boot time using require-profiler, sampling profilers, and Bootsnap. It describes profiling results from real projects, including a 40% reduction for a 200-component monolith, and covers cache precompilation and verification in Docker-based production builds. ### Source excerpt Rails boot time is a DX metric in the AI age: meet require-profiler, learn to actually read sampling profilers, and see the pit stop that cut a 200-component monolith's boot by 40%. ## Ship agent skills like packages: discovery index, digests, and install sources DevFeed: [Ship agent skills like packages: discovery index, digests, and install sources]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Agent Skills](), [Agent Skill](), [ai-coding](), [Publishing](), [GitHub](), [make](), [rubygems]() Tags: [agent-experience](), [agent-skill](), [agent-skills](), [ai](), [coding](), [coding-agents](), [dx](), [github](), [jamstack](), [json](), [llms](), [npm](), [rubygems](), [sha-256](), [skills]() ### AI overview This tutorial explains how to publish agent skills so AI coding agents can discover and install them. It covers a .well-known/agent-skills/index.json discovery index, SHA-256 integrity digests, single-file, multi-file, and bundle packaging, multiple install commands, and hosting skills from a GitHub repository while re-hosting the served files on the publisher's domain. ### Source excerpt How to publish agent skills so any AI coding agent can find and install them: the .well-known/agent-skills/index.json discovery index, SHA-256 integrity digests, single-file vs multi-file vs bundle packaging, and every install command. Worked from the catalog we just open-sourced. ## How to protect an npm package from supply chain attacks DevFeed: [How to protect an npm package from supply chain attacks]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-07-28T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [npm](), [supply-chain-security](), [Security](), [ci](), [GitHub](), [Open Source]() Tags: [2026](), [ci](), [developer-community](), [dx](), [github](), [how-to](), [javascript](), [monorepo](), [npm](), [npm-packages](), [open-source](), [performance-scale](), [security](), [supply-chain](), [supply-chain-security]() ### AI overview This tutorial explains how to protect npm packages from supply chain attacks. It covers Trusted Publishers, publishing restrictions, organization-wide 2FA, GitHub tag controls, pinned CI actions, CI security linting, cooldowns for new versions, and staged-release approval. ### Source excerpt How to protect your npm package from being stolen in a supply chain attack and improve its position in security ratings ## Which AI actually reads your site? Two months of LLM traffic, measured DevFeed: [Which AI actually reads your site? Two months of LLM traffic, measured]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-07-21T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [Large Language Model](), [Artificial Intelligence](), [Claude Code](), [ChatGPT](), [Google Analytics](), [Netlify](), [Back end]() Tags: [agent-experience](), [agents](), [ai](), [backend](), [chatgpt](), [claude-code](), [dx](), [google-analytics](), [jamstack](), [llm](), [llms](), [logs](), [measurement](), [netlify]() ### AI overview Evil Martians measured two months of server-side LLM traffic to its website. The study found that ChatGPT primarily fetches rendered HTML, while Claude Code requests Markdown most of the time through content negotiation. Most llms.txt requests came from bots other than the intended AI assistants, and a hidden AI hint received no measurable hits. ### Source excerpt We told you to measure. So of course we did it ourselves too: two months of server-side LLM traffic to evilmartians.com. Find out which agents read HTML, which read Markdown, what llms.txt actually does, and the one technique that got zero hits. ## Using Storybook Workbench to audit AI-generated UIs for dead components and accessibility bugs DevFeed: [Using Storybook Workbench to audit AI-generated UIs for dead components and accessibility bugs]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-07-08T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Storybook](), [Agent Skills](), [agentic-coding](), [AI-assisted coding](), [Accessibility](), [Design system]() Tags: [accessibility](), [agent-experience](), [agent-skills](), [agentic-coding](), [agentic-development](), [ai](), [bugs](), [design](), [design-engineering](), [design-for-devtools](), [design-system](), [dx](), [storybook]() ### AI overview The article presents Storybook Workbench, a bundle of Agent Skills that audits AI-generated web applications by rendering components as Storybook stories. It describes finding dead components, coexisting design systems, conditional component states, and accessibility bugs, based on an internal audit of an agent-coded app. ### Source excerpt Storybook Workbench is a bundle of Agent Skills that turn Storybook into an audit layer for AI-generated UIs: find dead components, design-system drift, and hidden accessibility bugs. ## Most MCP servers don't need to exist. Your case might be an exception. DevFeed: [Most MCP servers don't need to exist. Your case might be an exception.]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-06-30T00:00:00Z Content type: opinion Language: en Sources: [Evil Martians]() Topics: [Model Context Protocol](), [API](), [Command-line interface](), [Artificial Intelligence]() Tags: [agent](), [ai](), [analysis](), [api](), [cli](), [dx](), [llms](), [mcp](), [mcp-server]() ### AI overview This article presents a framework for deciding whether a product needs an MCP server or would be better served by a direct API, CLI, or skill. It argues that MCP should be treated as a product interface with stable, narrow, opinionated operations and ongoing maintenance, rather than as an automatic AI feature. ### Source excerpt An MCP server is a product interface for the age of agents, not an AI feature itself. This post presents a framework for deciding between direct API calls, CLI, Skills, and MCP, detailing the architectural signals, the hidden costs, and the failure modes you should know about before embarking on an MCP quest. ## Building a design system specced for engineers and agents DevFeed: [Building a design system specced for engineers and agents]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-06-17T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [Design system](), [User interface design](), [AI-assisted coding](), [cursor](), [Claude]() Tags: [ai](), [ai-assisted-coding](), [claude](), [components](), [cursor](), [design](), [design-system](), [devtools](), [dx](), [figma](), [llms](), [ui-design]() ### AI overview Evil Martians describes how it built a design system for Currents in seven weeks. The system standardized UI decisions and was structured to be readable by engineers and AI-assisted coding tools, including Cursor and Claude, helping the lean team reuse components and maintain a consistent product interface. ### Source excerpt Coding without design guidelines can leave teams with an inconsistent UI design and a complex feature development process. Here's how we built a design system for Currents that's readable by engineers and AI agents. ## How Nx Redesigned Its CLI for AI Agents DevFeed: [How Nx Redesigned Its CLI for AI Agents]() Original publisher: [Read original article]() Author: Max Kless Published: 2026-03-05T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Developer experience](), [Command-line interface](), [Artificial Intelligence](), [code productivity]() Tags: [ai](), [ai-agents](), [cli](), [commands](), [developer-experience](), [dx](), [nx](), [productivity]() ### AI overview Nx describes improvements to commands including nx import, nx init, and create-nx-workspace to make its CLI work more effectively with AI agents. The article explains how missing context, interactive output, retry failures, and overly prescriptive output can hinder agent workflows, while improvements to agentic experience can also improve developer experience. ### Source excerpt How we redesigned Nx CLI commands like nx import, nx init, and create-nx-workspace to work seamlessly with AI agents, and the AX principles behind the changes. ## Dodo Payments 2025:what we built, why it mattered, and what's coming in 2026 DevFeed: [Dodo Payments 2025:what we built, why it mattered, and what's coming in 2026]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-01-05T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Automation](), [AI Agent](), [SDK](), [Tooling]() Tags: [2025](), [2026](), [ai-agent](), [automation](), [code](), [developer-tools](), [developers](), [dx](), [resources](), [sdk]() ### AI overview Dodo Payments reviews its 2025 work, including community growth, billing and payments capabilities for AI-native builders and platform businesses, global expansion, and developer-focused tooling. It also outlines a 2026 roadmap involving credits, stablecoins, and developer experience. ### Source excerpt See what Dodo Payments built in 2025 - billing automation, global rails, and developer tools - plus the 2026 roadmap for credits, stables, and DX. ## Big DX Improvements for Neon Users on Vercel DevFeed: [Big DX Improvements for Neon Users on Vercel]() Original publisher: [Read original article]() Author: Gustavo Salomão Published: 2025-11-18T17:42:20Z Content type: news Language: en Sources: [Blog -- Neon Docs]() Topics: [Vercel](), [Deployment](), [observability](), [Security](), [Databases]() Tags: [deployment](), [dx](), [git](), [improvements](), [integration](), [observability](), [policy](), [product](), [retention](), [security]() ### AI overview Neon announces updates to its Vercel-managed integration, including automatic cleanup of database branches after preview deployments expire. The update also improves reliability and observability, synchronizes Vercel team membership and role changes with Neon organizations, and removes corresponding Neon access when users leave a Vercel team. ### Source excerpt Good news for Neon users on Vercel. We've shipped a few highly requested updates to the integration, plus a round of behind-the-scenes reliability and observability upgrades. Automatic Branch Cleanup Until now, Vercel-managed projects didn't automatically clean up their database... ## Heroku Announces New Hiring as It Invests in Platform, AI, and Developer Experience DevFeed: [Heroku Announces New Hiring as It Invests in Platform, AI, and Developer Experience]() Original publisher: [Read original article]() Author: Andrew Fawcett Published: 2023-08-31T02:04:27Z Content type: opinion Language: en Sources: [Heroku]() Topics: [Heroku](), [Development](), [Artificial Intelligence](), [Tooling]() Tags: [ai](), [developer-tools](), [dx](), [education](), [engineering](), [growth](), [hiring](), [innovation](), [join](), [news](), [operational-excellence](), [operations](), [product-features]() ### AI overview Heroku announces new hiring tied to a new phase of investment in its platform. The company says it plans to expand offerings, improve developer experience and integrations, and incorporate AI into customer applications and developer workflows. ### Source excerpt While it's not our usual approach to announce hiring updates on our product blog, we're pleased to share our ongoing dedication to improving the Heroku experience. Focused Growth and Progress Heroku is entering a new phase of investment, and as a part of this initiative, we are opening up new positions for individuals who would [...] The post Join us for a New Chapter of Growth and Innovation appeared first on Heroku. ## What Developer Experience Engineers can learn from User Experience Engineers DevFeed: [What Developer Experience Engineers can learn from User Experience Engineers]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-05-28T13:15:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [User experience (UX)](), [Usability](), [User interface design](), [Accessibility]() Tags: [accessibility](), [culture-developer-productivity-software-craft](), [developer-experience](), [dx](), [usability](), [user-experience](), [user-experience-design](), [users]() ### AI overview The article reflects on how developer experience engineers can apply established user experience engineering practices. It discusses the UX journey, the why, what, and how of product use, Peter Morville's User Experience Honeycomb, and the importance of understanding developers' needs through research and observation. ### Source excerpt What Developer Experience Engineers can learn from User Experience Engineers While developer experience is a relatively new term, user experience is not. In fact, the term user experience was probably first coined in 1990 by Don Norman: ## New Terminal Output & Performance Improvements in Nx 13.5 DevFeed: [New Terminal Output & Performance Improvements in Nx 13.5]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2022-01-25T00:00:00Z Content type: release Language: en Sources: [Juri Strumpflohner]() Topics: [Terminal](), [Caching](), [Chrome](), [developer tooling](), [Command-line interface](), [Graphs]() Tags: [cache](), [chrome](), [devtools](), [dx](), [feature](), [improvements](), [nx](), [performance](), [profiling](), [terminal](), [visualization]() ### AI overview Nx 13.5 introduces dynamic terminal output that separates completed and running tasks while showing errors immediately. The release also reports performance improvements, continued caching of full terminal output, and Chrome DevTools profiling support for Nx commands. ### Source excerpt Nx 13.5 brings a new dynamic terminal output, 2.3x faster operations, Chrome DevTools profiling support, and improved project graph visualization. ## DX Audits - A Framework for Developer Advocacy DevFeed: [DX Audits - A Framework for Developer Advocacy]() Original publisher: [Read original article]() Author: Kurt Kemple Published: 2021-08-18T09:18:14Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [audit](), [Usability](), [GraphQL](), [Framework]() Tags: [advocacy](), [audit](), [community](), [developer](), [dx](), [framework](), [graphql](), [usability](), [workflow]() ### AI overview This article presents Apollo's DX Audits framework for developer advocacy. The process has developer advocates experience common GraphQL and Apollo platform workflows, document friction in logs, report findings, and track action items to reduce product friction and improve developer success. ### Source excerpt If you ask a developer advocate (DA) what their day-to-day looks like, you'll likely get a very different answer from each person you ask. Interestingly enough, I'd wager that if you asked two DAs on the same team, you'd still get two totally separate answers. As DAs, we're tasked with helping developers be successful, but how we do that is basically up to us.