360
Bane Mask (lemmy.dbzer0.com)
submitted 6 days ago by to c/programmer_humor@programming.dev
106 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 6 days ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 days ago* (last edited 6 days ago) (1 child)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 12 points 6 days ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 5 days ago

    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!

  • permalink
  • fedilink
  • source
  • parent