How do you handle code syntax and file paths when voice coding?
by•
I started dictating my prompts recently because typing out long paragraphs of context during debugging gets exhausting. The upside is huge you naturally explain the why behind a bug instead of just throwing a short command like "fix error" at the LLM. But the friction comes when you have to say exact file names or variable paths out loud. I end up sounding ridiculous trying to spell out camelCase names or special symbols.
For those using voice tools regularly in tools like Cursor how do you split what you dictate versus what you still manually type?
3 views
Replies
Not a voice coder, but I have a similar split: I talk to my coding agent in Russian while the code and the notes are all in English. What makes that work is describing behaviour instead of naming things. "The switch on the create form that makes a song instrumental" finds the right file as well as the path does, because the agent can search. I would keep exact names for the rare case where two candidates exist, and type those. Saying the why out loud is the real win you found, the names matter less than they seem.