“Vibe coding” is having a moment — and for a lot of people it means some combination of:
- a modern AI-first editor (Cursor, etc.)
- fast iteration
- more time describing what you want than writing every character
That last point is why this is relevant for Voice Type: vibe coding is often writing-heavy, and dictation can reduce typing load while keeping your momentum.
TL;DR (fast answer)
- Vibe coding isn’t just coding — it’s requirements, prompts, and review.
- Dictation is most useful for the prose: “what should happen”, “edge cases”, “acceptance criteria”, and “why”.
- A practical workflow: voice → generate → test → review checklist.
What “vibe coding” usually means (without the hype)
Different people use the term differently, but common themes:
- use AI to draft code quickly
- steer via natural language prompts
- iterate until it feels right
If you want a thoughtful critique (and a reminder that “AI-assisted programming” and “vibe coding” aren’t the same thing), Simon Willison’s write-up is a solid reference point (Willison, 2025).
For a general explainer: Cloudflare’s learning page gives a straightforward overview (Cloudflare), and mainstream coverage has picked it up as well (PCMag).
Why vibe coding pairs well with dictation
When you vibe code, you often write more than you expect:
- prompts
- implementation notes
- bug reports
- PR descriptions
- tickets and acceptance criteria
Dictation helps you get the first draft out fast, then you edit for precision.
This is especially helpful if you:
- write lots of tickets (Linear/Jira)
- write lots of PR descriptions (GitHub)
- are managing RSI / wrist pain
A Mac workflow that works (voice → generate → verify)
Step 1: Dictate requirements (not code)
Before you prompt, dictate these:
- what the feature should do (1 paragraph)
- what it should not do (scope)
- edge cases (bullets)
- acceptance criteria (checklist)
On macOS you can start with built-in Dictation (Apple Dictation guide).
If you do this daily, a hold‑to‑dictate hotkey is easier to stick with: /voice-typing-mac
Step 2: Paste into Cursor/VS Code and generate
Use your editor’s AI features to draft code quickly — but treat the output as a first draft.
Related how-tos:
- Cursor: /how-to/cursor-mac-dictation
- VS Code: /how-to/vscode-mac-dictation
Step 3: Run the “vibe coding review checklist”
Dictation makes generation faster. Review makes it safe.
Checklist:
- Does this change have tests?
- Are error cases handled?
- Are inputs validated?
- Is auth/permissions correct?
- Did we leak secrets/log PII?
- Is the code readable and maintainable?
Step 4: Dictate the PR description (so reviewers trust it)
PRs are mostly explanation:
- what changed
- why
- how to test
Dictate the prose, type the identifiers: /how-to/github-pull-request-mac-dictation
Where Voice Type fits (product)
Voice Type is on-device voice typing for macOS. The workflow is simple:
- hold a hotkey
- speak
- release to finalize
It’s not “voice code.” It’s “voice the parts that are prose,” especially when you’re moving between editors, browsers, and ticket tools.
Keep going
- Dictation in GitHub Issues: /how-to/github-issues-mac-dictation
- Dictation in Linear: /how-to/linear-mac-dictation
- Dictation in Jira: /how-to/jira-mac-dictation
- RSI workflow: /solutions/rsi
Sources (definitions + references)
- “Not all AI-assisted programming is vibe coding …” (context + critique): Simon Willison, 2025
- Explainer: Cloudflare: “What is vibe coding?”
- Mainstream overview: PCMag: “Vibe Coding Is Everywhere…”
- Apple Dictation: Use Dictation on Mac