Developer experience & developer advocacy as a service

Make your API a joy to adopt

I look at your docs, APIs, SDKs and onboarding the way a new developer would, then help you fix what slows them down. Short projects with a fixed scope, a clear finish and a handover your team can run with.

TypeScript & JavaScriptNode.js & DenoFrontend & backendTypstPHP on request

Every project comes with

  • Outcomes agreed before we start
  • A fixed scope and a clear finish date
  • Findings in plain language, prioritised
  • A handover your team can run with

Case studies

Don't take my word for it. Try it.

Projects you can open, install, run or watch yourself.

Case study · WüSpace

Telestion: ground station software in a few lines

Mission control software is about as complex as it gets: live telemetry, many services, real hardware and a mission at stake. The developer experience work on Telestion kept that complexity out of the developer's way. A service that watches telemetry and raises a warning looks like this.

Telestion is an open-source TypeScript framework and a team effort at WüSpace. I led its end-to-end developer experience.

TypeScriptOpen sourceEnd to end
low-altitude-warning.ts
const { messageBus } = await startService();

const telemetry = messageBus.subscribe('telemetry');

for await (let packet of telemetry) {
    const data = telemetrySchema.parse(packet);
    if (data.altitude < 10_000) {
        sendWarning(`Low Altitude: ${data.altitude}`);
    }
}
Zuri wearing a hat, sitting on a grey sofa in an office and gesturing while explaining something
Zuri in the Adobe Munich office, preparing the Partner Days.

About me

Hi, I'm Zuri

I'm a one-person business, and that's on purpose. When you work with me, you work with me: from the first call to the handover, with no account managers and no hand-offs in between.

I was DevEx lead for Telestion at WüSpace. Before that I worked on UXP at Adobe, where I ran developer events, wrote docs and samples, and led initiatives such as the developer office hours format. I also build my own Node.js and Deno libraries, with the same focus on developer experience.

I've seen great developer tools fail far too often. The engineers build a great product, but there's no documentation, or only rudimentary docs, so nobody sees the new features. I want to fix that, even for businesses that can't afford a dedicated developer experience person on the team.

Recommendations

What former colleagues say

Personal recommendations from colleagues I worked with on UXP while I was employed at Adobe, shared with their permission. They speak for themselves, not for Adobe, and aren't an endorsement by Adobe.

Former colleague

Zuri is incredibly passionate about delivering the best possible experience for developers and users alike. … Zuri can wear so many different hats to help a team scale — from running developer events, writing high quality documentation and samples, advocating for changes to the user experience, to raising awareness regarding diversity—I'm always amazed and impressed at the incredible passion and impact Zuri brought to the team.

Kerri ShottsGroup Product Manager, Creative Cloud, AdobeWorked with Zuri on UXP at Adobe · March 2024
Former colleague

Their commitment to best-in-class developer experience has resulted in so many impactful features in the platform. UI/UX improvements to the existing tools, quick start guides for easy onboarding, videos to explain UXP concepts, and constant engagement with the community through Office Hours, forums, and developer events are just the tip of the iceberg.

Padma KrishnamoorthySr. Technical Product Manager, AdobeWorked with Zuri on UXP at Adobe · July 2023

Approach

People first. Your AI tools benefit anyway.

When the app breaks at 2 a.m., an actual person sits in front of a computer and has to understand what's going on. That's who I design for.

AI assistants and agents are part of how developers work today, and ignoring them isn't an option. But they don't need a separate track. What makes docs and APIs great for people is exactly what makes them work well for language models.

Docs that work for a tired human at 2 a.m. also work for your AI assistant.

  • The person comes first

    Audits look at your developer experience through the eyes of someone new to your product.

  • Semantic docs serve both

    Clear structure, real headings, complete examples and explicit types: what helps people is exactly what language models handle well.

  • Intuitive APIs, for anyone

    Consistent naming, predictable behaviour, good types and helpful errors make an API easy to learn and easy to use correctly.

  • No separate AI checklist

    My work focuses on the developer experience. Better results with AI tools follow from that, so I don't treat them as a separate focus.

How it works

From first call to handover

  1. Intro call

    We talk about your product, your developers and where they get stuck. If I'm not the right fit, I'll tell you.

  2. Written scope

    You get a proposal with outcomes, timeline and price. What's included is written down, and so is what isn't.

  3. Work and handover

    I do the work, keep you posted and finish with a handover, so your team can carry on without me.

Contact

Tell me where your developers get stuck

A few lines about your API, docs or event are enough. I'll reply within a week and tell you honestly whether and how I can help.

A link to your docs or repository helps me prepare.