TL;DR
DevRel should be the first user of your product before it ships. I call this "Dev Zero" - we catch bugs, missing buttons, and confusing flows that developers miss, and then turn those findings into targeted docs and content.
As a developer advocate, I often ponder DevRel’s role in catching bugs and tricky issues before they escalate. I’m sharing my thoughts in this blog post.
DevRel as Dev Zero
DevRel can serve as the “Dev Zero” stage in product development. Like testing code before release, DevRel tests from a user’s perspective, catching overlooked issues. This early feedback loop ensures smoother product releases and reduces the need for last-minute fixes.
DevRel is a superhero, catching bugs before they wreak havoc!
Addressing Tricky Issues
Once, while testing a product, I found the “Create Account” button missing on the sign-up page. It was a design flaw unnoticed by developers. This showed that DevRel can detect issues that developers might miss, improving product user-friendliness. By finding and fixing these problems early, DevRel helps reduce user frustration and improve overall product adoption.
Benefits for Tech Companies
DevRel as Dev Zero has clear benefits, especially for startups:
-
Catching bugs early: Saves time and money otherwise spent on fixes.
-
Building a community: Increases brand recognition and creates a loyal user base.
-
Improving user experience: Ensures that products are user-friendly, leading to higher customer satisfaction.
Content Creation
DevRel can determine content needs for docs and blogs based on user issues. Identifying common problems, we create targeted content to help users maximize the product.
-
If setup is difficult, we create a step-by-step guide.
-
If a feature is confusing, we make a video tutorial.
This targeted content helps users overcome hurdles, leading to better product usage and higher retention rates.
Why This Matters
DevRel as Dev Zero is important in product development. It helps make products user-friendly and saves startups time and money. Using testing insights, DevRel creates targeted content addressing user issues. I wrote more about how the role is evolving in my post on developer advocacy in 2023, and how Dev Zero fits next to search and LLM work in running DevRel in 2026.
Next time you spot a bug, be a superhero and catch it! Reach out to DevRel for help; we’re eager to save the day.
Joe Karlsson
Developer Marketing Engineer at CData, leading developer growth for the managed MCP platform that connects AI agents to live enterprise data. Writing about databases, self-hosting, and the things I build. Runs a 60+ container Proxmox homelab with AI-powered automations.
cat newsletter.md
Works on My Machine is my newsletter: thoughts and reactions on tech writing, AI, homelab builds and open source, plus whatever I'm working on. It goes out when I have something to say.
Free, no spam, unsubscribe anytime. Read past issues.
Related Posts
Apr 21, 2026
Running DevRel in 2026 Means Owning Three Discovery Surfaces
Running DevRel in 2026: developers find you through people, search, and LLMs. What breaks on each surface, how I measure it, and my first 90 days.
Oct 16, 2026
Why I use DOOM to visualize MCP data
MCP data is just rows and JSON, so I built Doom out of it: an AI agent pulls live records through an MCP server, and each one becomes a monster.
Oct 12, 2026
I hate editing video, so I built a screen recorder that edits for me
Screencast Director is an open source macOS screen recorder that drafts the edit: it cuts dead air, speeds up typing and takes edits from the AI model you pick.