Coding at a rate of 240 words per minute

[app103]

An interesting use case for Stenotype.

https://www.youtube.com/watch?v=Wpv-Qb-dB6g

[app103]

I am not entirely sure I could code at 240 words per minute, even if my brain were directly connected to my computer via a thought to text engine, unless it could translate visual thought concepts.

But that would be in the realm of sci-fi, where you could create a UI and make it work, by just imagining yourself using it. 

Currently, I'd have to say the bulk of my development time is not spent on actual typing of code, but rather testing, debugging, and research, and I don't see learning stenotype shortening the time spent doing that, by very much, even at double that rate (480 WPM).

[MilesAhead]

I've never worked in a room full of coders.  But I would tend to think sessions where they just type in a flurry of working code are routines they've done so many times they could just paste them in from their code snippets.  But they want to show off. 

There was a guy in my analyst group who was also a concert pianist.  He liked to type at top speed to show off this finger dexterity.  But he never let anyone time him that I know of.  He just liked to see the text fill up the screen.  Also he didn't care about typos. 

[Stoic Joker]

What was the old saying, '4 bugs for every 1,000 lines of code' ... But we can hit 5-7 if we try real hard.

Speed is not always the solution.

[wraith808]

What was the old saying, '4 bugs for every 1,000 lines of code' ... But we can hit 5-7 if we try real hard.

Speed is not always the solution.

That, and typing rate isn't the big limiter in coding for the most part.  I find that the largest asset in coding isn't speed, but the ability to identify problems and create appropriate solutions.

[Edvard]

240 words per minute?!?! 

Maybe y'all need to ease up a bit:
http://jaxenter.com/slow-programming-112923.html

Because programmers don’t just type out code. The act of engineering software is more than just hammering line after line of software into a computer, like laying bricks.

I wrote about it here:
http://www.donationcoder.com/forum/index.php?topic=39720.0

Geez folks, grab a hammock and code easy...

[app103]

Geez folks, grab a hammock and code easy...

But if you have the skills, the equipment, and the software, what reason can you give not to use stenotype? Isn't that like advocating hunt & peck over touch typing?

[wraith808]

But if you have the skills, the equipment, and the software, what reason can you give not to use stenotype? Isn't that like advocating hunt & peck over touch typing?

Does phonetics cover everything that you would need in a programming environment... really?  Especially with the use of templates and snippets and shortcuts.

[app103]

But if you have the skills, the equipment, and the software, what reason can you give not to use stenotype? Isn't that like advocating hunt & peck over touch typing?

Does phonetics cover everything that you would need in a programming environment... really?  Especially with the use of templates and snippets and shortcuts.

She did go into that in the video, explaining the concept and usage of a personal dictionary.

[wraith808]

I will admit... it's 34 minutes, so I didn't watch the whole thing.  If someone wants to use it... more power to them.  But it doesn't look like something I'd use nor advocate.

[MilesAhead]

I will admit... it's 34 minutes, so I didn't watch the whole thing.  If someone wants to use it... more power to them.  But it doesn't look like something I'd use nor advocate.

I suppose if someone made a career switch from stenographer to developer it would only be natural.  On the downside there's enough metrics already without being expected to "type" 200+ wpm of bug free code. 

[kwacky1]

As the old saying goes

Speed, Price, Quality... Pick 2