---
title: Finding the rhythm
description: "Finding the rhythm four weeks into a new DevRel role: what surprised me about text-to-speech, what I was right about, and what I am still figuring out."
canonical: https://lukeocodes.dev/finding-the-rhythm-first-impressions
type: article
locale: en_GB
published: 2026-07-05T00:00:00.000Z
modified: 2026-11-02T00:00:00.000Z
authors:
  - Luke Oliff
section: Developer Experience
tags:
  - Developer Experience
  - Opinion
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/finding-the-rhythm-first-impressions#article
        headline: Finding the rhythm
        alternativeHeadline: "Finding the rhythm: first impressions of a new role in a new corner of AI"
        description: "Finding the rhythm four weeks into a new DevRel role: what surprised me about text-to-speech, what I was right about, and what I am still figuring out."
        datePublished: 2026-07-05T00:00:00.000Z
        dateModified: 2026-11-02T00:00:00.000Z
        url: https://lukeocodes.dev/finding-the-rhythm-first-impressions
        mainEntityOfPage: https://lukeocodes.dev/finding-the-rhythm-first-impressions
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Developer Experience, Opinion
        articleSection: Developer Experience
        about:
          - "@type": Thing
            name: Developer Experience
        abstract: Four weeks into a new DevRel role and I've learned more about what I don't know than what I do. That's probably the point.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=Finding+the+rhythm&d=Finding+the+rhythm+four+weeks+into+a+new+DevRel+role%3A+what+surprised+me+about+text-to-speech%2C+what+I+was+right+about%2C+and+what+I+am+still+figuring+out.&e=Writing
        wordCount: 403
        timeRequired: PT3M
        publisher:
          "@id": https://ably.com/#organization
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: Finding the rhythm
            item: https://lukeocodes.dev/finding-the-rhythm-first-impressions
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# Finding the rhythm: first impressions of a new role in a new corner of AI

Jul 2026 · Updated Nov 2026 · [Developer Experience](/blog/category/developer-experience) · 3 min read · [Luke Oliff](/authors/luke)

Four weeks into a new DevRel role and I've learned more about what I don't know than what I do. That's probably the point.

### The surprise

I spent the last few years in speech-to-text. The developer community there talks about accuracy rates, language coverage, realtime latency. The problems are about getting audio in and text out, fast and clean.

The new role is on the text-to-speech side. Same voice industry, completely different conversation. The community here talks about voice quality, emotion control, pricing per character, streaming audio boundaries. I keep catching myself framing problems from the old angle and having to flip my perspective. It's humbling in a good way.

### What I was right about

Content cadence matters more than content volume. Publishing one solid piece that takes real time beats three rushed roundups. The posts that got the best response were the ones with working code, clear explanations, and something useful at the end. The changelog-style summaries got polite nods. The difference is measurable.

Also right: data wins arguments. A pricing comparison table with real numbers at the top of a public leaderboard generated more real conversation than any opinion piece I've written. Developers trust numbers they can verify.

### What I'm still figuring out

How to balance the two audiences. There are people building on the platform I work for who need reference docs and migration guides. And there's the broader AI community that wants industry analysis and comparisons. They overlap but they're not the same group, and serving both without watering either one down is harder than I expected.

Also figuring out how fast to react to market moves. Google changed pricing mid-week. A Chinese lab shipped a new model variant. A competitor restructured their tiers. Each one is a story but reacting the same day every time is a treadmill. I'm experimenting with a weekly roundup that groups them into context rather than chasing each one individually.

### The thing I keep coming back to

Voice AI quality has converged enough that the decision factors are moving to price, latency, languages, and ecosystem. That makes DevRel work different from two years ago, when part of the job was convincing people the tech was ready. Now the tech is ready and the job is helping people choose wisely and build well. I like that version of the job better.

Still plenty to figure out. That's the fun part.

[← Newer: Building a writing routine that actually sticks](/building-a-writing-routine-that-works)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
