369
Bane Mask
(lemmy.dbzer0.com)
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
For programming, yes, because the text is formatted, but not for plain English. The average person can easily speak 130 to 150 words per minute, but they certainly can't type that. If you personally can, then alright, that's cool. You're maybe more efficient with a keyboard.
And regardless of your opinion on it (or mine) vibe-coding is plain English, so what they're saying is true for that one use case. Besides, they can use both. The keyboard is still there.
This comment was written using speech-to-text.
Does the 130-150wpm number include thinking? I don't think I ever speak that fast even when I'm retelling material I know very well to my juniors, because even that requires thinking while talking to convey the information logically and consistently.
When you're not thinking, and you know what you're going to say, you can talk at 130 words per minute very easily.
When using a keyboard, you're going to pause just as much to think. The comparison is this: when you are in text entering mode (not thinking mode), are you faster talking on the microphone or the keyboard?
What I think is interesting here is that I regularly give Claude a sentence or four that it then thinks on for 10-15 min. Like, maybe 40 words tops, generally closer to 25-30. I can type that in seconds. And then wait 10-15 min. If it took me 3x as long to type it in, it still wouldn't impact my day or output.
Wait, you wait for individual responses? You're supposed to be giving Claude 15 simultaneous tasks where you dictate one per minute, and loop around when you're done to review the first task's output. What kind of vibe coder gives only one task at a time and then jerks around for 15 minutes? You're fired!
Hey Claude, what does "int open parenthesis asterisk fun closed parenthesis open parenthesis int c comma char asterisk asterisk v closed parenthesis equal get open parenthesis closed parenthesis minus greater sign fun semicolon" means?
"Conversing" with an LLM is a different dialect than speaking to humans if one wants consistent output. Keyboard still wins. LLM is exhausting. Humans are dope.
Oh, you think speech to text is your ally? But you merely adopted the speech to text; I was born in it, molded by it. I didn't see a keyboard until I was already a man. By then, it was nothing to me but key Binding.
It's not really 130-150 words per min though bc mostly the words we say are nonsense, "uhms" and saying the wrong thing and starting over and pausing and such.
Not to mention, when we speak to a computer, it's not like to a person, as others have pointed out. The 130-150 wpm number comes from in context speaking where we already know what we're going to say. That isn't the case when doing things on a computer such as responding to a comment, anything requiring thinking, coding, etc.
Also, speech-to-text systems do not immediately recognize the speech we say, adding further delay.
So it's not actually 130-150 words a minute.
In terms of meaningful day-to-day use, I maintain that it's far slower and less precise than a keyboard, especially if you're a proficient typer.
And this makes sense as everyone I've ever met who likes to use speech-to-text (excluding those who MUST use it for disability reasons) are simply those who are bad at typing. Cope harder. slow-mo. This comment was written using a keyboard
EDIT:
This doesn't follow. Both of us are talking about inputing in english. Vibe-coding with a keyboard is also superior there
You do all of that with a keyboard, too! You stop and think. You erase and try again. You never actually sustain your 80 WMP peak (or whatever),
When it comes time to knowing what they're going to say, however long that takes, the average person can speak much faster than they can type.
You're way overthinking it, and also wrong. Read the research. If you are some super-human typer, good for you! I specifically said "average person".
Please explain.