Added citation for the importance of documentation. I think the second point from there is self evident. If documentation is important, typing speed is important because slower typing means more time spent on documentation.

Your added link shows comments and documentation exist? Link something that shows people typing fast are also accurate. Link something that shows typing speed has something to do with reading and compression speed.

"Typing fast" clearly means "typing fast and being accurate." Anyone can type quickly, if they don't give a damn about accuracy. Also, compression speed?

Comprehension* sorry I was typing faster

And that would have resulted in an error in your code and you would have had to go back and find that error, taking up a lot of time. Your error gets to part of my point. The better you are at typing, the better you are at programming, and especially the better you are at documenting.

@DanielGoldman Your point sucks, if you linked some other people saying the same stuff you are I might change my mind. Let me try to think of a high profile case where typing 100 wpm instead of 50 wpm would not be helpful oh wait here's ten raygun.com/blog/10-costly-software-errors-history

I did specifically link to a discussion on the importance of documentation. From there, it is a matter of accepting that producing documentation would go faster if someone can type more proficiently.

If your one point that you were making was "documentation was also important" I would agree. But then mods would swoop in and say its a bit short for an answer. back up with links your points!

If you accept it, and I did provide citation to justify it, then we're done. Producing documentation takes less time if you can type more proficient.

You have one link in your answer that shows that documentation exists, everything else might as well be your opinion. If I posted an answer and said "no it actually makes programmers worse to learn to type faster here is a diagram of the waterfall method" my answer would be as good as yours. upload.wikimedia.org/wikipedia/commons/thumb/e/e2/…

You would have to do some amazing logical gymnastics even to dismiss my position let alone state the opposite. You accept that documentation is important. Well, there you go. If you are a poor typer, you're going to avoid documentation or it is, at the very least, going to take a lot more time to add reasonable documentation.

Oh and I say this as a programmer who really should have documented a lot of his material better, because without extensive documentation, it is very difficult to look at a program a few years later and figure out what the hell is going on.

you have made points that arent backed up

so yes yoiu have brung to the table "documentation is also important"

thats not an answer, thats a comment

everything else you said is just what you think

but i shouldn't put it as an answer

You admit that documentation is a very important component of software engineering, yes?

you admit that the rest of your answer doesn't have anything backing it up yes?