---
title: Lessons from two weeks in voice AI
description: "Two weeks in voice AI on the text-to-speech side: a new community, a new set of constraints, and a definition of quality nobody quite agrees on."
canonical: https://lukeocodes.dev/lessons-from-my-first-two-weeks-in-voice-ai
type: article
locale: en_GB
published: 2026-06-22T00:00:00.000Z
modified: 2026-07-05T00: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/lessons-from-my-first-two-weeks-in-voice-ai#article
        headline: Lessons from two weeks in voice AI
        alternativeHeadline: Lessons from my first two weeks in a new corner of AI
        description: "Two weeks in voice AI on the text-to-speech side: a new community, a new set of constraints, and a definition of quality nobody quite agrees on."
        datePublished: 2026-06-22T00:00:00.000Z
        dateModified: 2026-07-05T00:00:00.000Z
        url: https://lukeocodes.dev/lessons-from-my-first-two-weeks-in-voice-ai
        mainEntityOfPage: https://lukeocodes.dev/lessons-from-my-first-two-weeks-in-voice-ai
        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: Two weeks into a new role on the text-to-speech side of voice AI and I keep bumping into assumptions I didn't know I was carrying.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=Lessons+from+two+weeks+in+voice+AI&d=Two+weeks+in+voice+AI+on+the+text-to-speech+side%3A+a+new+community%2C+a+new+set+of+constraints%2C+and+a+definition+of+quality+nobody+quite+agrees+on.&e=Writing
        wordCount: 541
        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: Lessons from two weeks in voice AI
            item: https://lukeocodes.dev/lessons-from-my-first-two-weeks-in-voice-ai
---

[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)

# Lessons from my first two weeks in a new corner of AI

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

Two weeks into a new role on the text-to-speech side of voice AI and I keep bumping into assumptions I didn't know I was carrying.

### The switch cost

I came from speech-to-text, where the community conversation is about word error rate, language coverage, and realtime latency. The problems are about getting audio in and text out, fast and clean. Benchmarks are well established. Everyone agrees on what good looks like.

Text-to-speech is a different world. The community talks about voice quality, naturalness, emotion control, pricing per character. The benchmarks exist but they're more subjective because quality is harder to measure than accuracy. Two people can listen to the same TTS sample and disagree on which sounds better. That barely happens with STT.

I keep reaching for the wrong mental model. I'll think about a problem in terms of transcription accuracy when the actual question is about prosody or speech mark alignment. It's like learning to drive on the other side of the road.

### What surprised me about the community

TTS developers are more opinionated than STT developers. That makes sense when you think about it. STT is a utility - you want the lowest error rate at the lowest latency. TTS is creative. Developers care about which voice they use, how they control emphasis and pacing, what the output sounds like at different bitrates. They have preferences, not just requirements.

The questions I get are different too. With STT, the questions were about edge cases: accents, background noise, domain-specific vocabulary. With TTS, the questions are about craft: how do I make this sentence sound more natural, how do I control the emotional tone, what sample rate works best for telephony. It's a more nuanced conversation and I like that.

### What surprised me about the market

TTS pricing is more varied than I expected. Some providers charge per character, some per second, some per token. Some have tiers based on quality. Some charge extra for voice cloning or emotion control. Comparing costs across providers requires a spreadsheet and a calculator.

A few years ago, the premium providers charged a significant premium because the quality gap was visible. That gap has narrowed. The top models converged on similar quality, so price has become a bigger factor in buying decisions. That's good for developers but it means the market is more competitive than the STT side, where a few providers dominate the top tier and everyone else fills niches.

### What I'm still figuring out

How to write about a domain where quality is subjective. With STT, I could point to a word error rate and say "this is better." With TTS, I have to say "this sounds better to most listeners in blind tests" which is a weaker claim. I'm learning to lean on concrete comparisons - pricing tables, latency measurements, language coverage - and let the quality aspect speak for itself through demos and examples.

Also figuring out how deep to go on technical detail. TTS has a lot of parameters: sample rate, bitrate, SSML tags, speech marks, voice cloning settings. Too much detail loses people. Too little leaves them without useful information. Finding the line is taking longer than I expected.

Two weeks in. Still plenty to learn.

[← Newer: Inference costs are dropping and that changes everything](/inference-costs-dropping-changes-everything)

[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)
