SpeechPrompts, at the length they need to be
A good prompt is three paragraphs of context. Typing that is why people send a bad one instead. Hold the key and say it.
For developers
The prompt is
longer than
the code.
Most of what a developer types now is prose: prompts, commit messages, review comments, the paragraph explaining why. Prose is faster spoken.
Why it fits
Six things that
matter here.
Everything below is shipped today. Nothing on this page is a roadmap.
Commits and reviews that say why
"Fix bug" happens because the real message takes a minute to type. Dictating it takes ten seconds, and the next person gets the reason.
In the app you already have open
Speech types into whatever is focused, so it works the same in your editor, your terminal, the browser and the chat window.
A dictionary that knows your stack
Library names, service names, the internal acronym nobody outside the team has heard. Add them once and they stop coming back wrong.
Hands stay where they were
Hold the shortcut, speak, let go. Nothing to click, no window to switch to, no waiting for a panel to open.
It does not read your screen
The accessibility permission places text at your cursor and reads the few characters before it. Screen capture is a separate feature and it is off.
The point of it
Speaking is a different bandwidth
Typing caps you at your fingers. Speaking runs at about 130 words a minute and the thinking is the bottleneck again, which is where it should be.
Why Roman HinglishWorks in every appEditor, terminal, browser, chat.
Your own dictionarySo the library name is right the first time.
Try it on today's
actual work.
Not on a test sentence. Open the thing you were about to type and say it instead.