Show notes (Technically Working, Episode 146) This week starts with a dramatic voice demo and turns into a practical conversation about TTS quality, accessibility, and the friction that slows down real work.

In this episode, we talk about:

• More expressive on-device voices (and why “emotion” in TTS can be impressive but unpredictable)
• Why some AI voices drift over long reads (like losing low end after a few thousand characters)
• The practical fix: chunking text around 3,000 characters at sentence or paragraph boundaries
• The jarring side of expressive TTS: when the tone suddenly shifts mid-training

• Mac code editor accessibility and workflow:

• VS Code feeling clunky with VoiceOver navigation

• Nova being close, but still having VoiceOver quirks (like wrapped-line re-reading)
• Missing the flexibility and simplicity of TextMate
• A quick audio reality check: room reverb, mic position, and loud breathing in the mic
• Why it’s worth listening back sometimes, even if you usually don’t
• “Personal intelligence” assistants: Gemini connecting deeper with Gmail, Calendar, Photos, and Drive, and what that could enable
• Stream Deck Plus on sale (knobs!) and the bigger question: is the software accessible enough?

• Capture friction and follow-up problems:

• Getting ideas out of your head fast

• Using automation to sort notes into reminders, drafts, and follow-ups
• Why the Apple Watch action button might help reduce steps
• PLAUD recording devices: improved hardware button design, but app accessibility still matters
• Local processing ideas: Raspberry Pi options for local transcription and LLM workflows
• Listener feedback: Squarespace questions and a quick look at support options (tip jar vs Buy Me a Coffee)

Feedback and contact: feedback@technicallyworking.show

Support the show: Visit technicallyworking.show and click “Support Us” to leave a one-time tip or set up a recurring amount.

Mastodon: @payown@dragonscave.space @damashe@technically.social @tw@technically.social

Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working

Find out more at https://technically-working.pinecast.co

Send us your feedback online: https://pinecast.com/feedback/technically-working/1396d590-a7dc-4a88-8455-1b3da1991eb2

Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

Episode 145: Teaching Tech, Tethering Pain, and a Little CES Talk

This week we bounce between real life and real tech: why tethering still makes us want a MacBook with built-in cellular, what passkeys look like in the real world, and how Google Family Link pushes you into creating Gmail accounts for kids. We also talk honestly about teaching tech, why we often prefer working with people who are ready to level up their productivity, and how listener feedback shapes where the show goes next. Plus, a quick CES roundup with a few gadgets and ideas that actually stood out.

• Late-night work limits, and planning so tomorrow doesn’t get wrecked
• Tethering frustration, and the “just give us a MacBook with cellular” wish
• Michael’s living-room recording setup: Vocaster + OWC dock + Zoom, no virtual device chaos
• Google Workspace security alerts: suspicious login emails and what to check
• Passkeys: what’s great, what’s still confusing, and why some services still ask for a code
• Family Link and kids’ Google accounts: why Google requires @gmail.com, and how passkeys fit in
• Shared iCloud Passwords groups so parents can manage kids’ logins
• Password manager friction on Mac: Apple Passwords prompts vs 1Password workflows
• Listener feedback and the point of the show: it’s not a weekly “how-to,” it’s real conversations
• Teaching tech: beginner wins, real frustrations, and why “productivity level” training can be a better fit
• CES notes: mobility tech, batteries, smart locks, and a few other items that caught our attention
• Quick Surf app check-in: progress, but still clunky in places
• Support and contact info, plus Mastodon handles and the show hashtag

Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working

Find out more at https://technically-working.pinecast.co

Send us your feedback online: https://pinecast.com/feedback/technically-working/c074c0cd-6feb-44da-bde8-e4a9321fd9f3

Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.