Typing challege for developers

[semaphore]

Probably (there probably are a few exceptional cases), but in my experienced I have yet to find anyone who boasts about typing speed producing code that didn't require substantial rework in maintenance.

Well then the developers you surround yourself with are substandard.

 

[MrGray]

Well then the developers you surround yourself with are substandard.

No, he's spot on. Any developer I know who's every boasted about his/her typing speed is generally a tonsil who can't do much more than type fast.

 

[[)roi(]]

Well then the developers you surround yourself with are substandard.

Taking this personally are we? Ps... Never a good idea; stay on topic.

Historically the principle I tended to adopt is 40-20-40; time spent in design / planning, coding and QA. However more recent trends with TDD have shifted me to 50-30-20; with extra time being allotted to both design and coding in order to incorporate testing throughout the build cycle.

 

[semaphore]

No, he's spot on. Any developer I know who's every boasted about his/her typing speed is generally a tonsil who can't do much more than type fast.

No actually hes not, hes using a blanket statement and placing anyone who types fast cant code(efficiently) in it. Which is the most retarded thing i've heard. FYI i type a normal speed when i code (so im not boasting about speed).

But his remarks are only supported by his experience, which does not encompass the entire planet. There are people on github that churn out projects by the bucket load because of their sheer speed(typing) and efficiency in their code.

Not taking it personally, but your comments are totally unfounded. You seem to think that your experience takes precedence of everyone in the world.

 

[MrGray]

No actually hes not, hes using a blanket statement and placing anyone who types fast cant code(efficiently) in it. Which is the most retarded thing i've heard. FYI i type a normal speed when i code (so im not boasting about speed).

But his remarks are only supported by his experience, which does not encompass the entire planet. There are people on github that churn out projects by the bucket load because of their sheer speed(typing) and efficiency in their code.

Typing speed (beyond basic proficiency) is largely irrelevant to how much code you churn out, IMHO. Efficiency, though, is the key and again has nothing to do with the speed you can type. Re-factoring, structuring your code properly, thinking out elegant structures - these make the difference, not how fast you can bash out algorithms.

 

[semaphore]

Typing speed (beyond basic proficiency) is largely irrelevant to how much code you churn out, IMHO. Efficiency, though, is the key and again has nothing to do with the speed you can type. Re-factoring, structuring your code properly, thinking out elegant structures - these make the difference, not how fast you can bash out algorithms.

Really and how do you think those things are going to materialize hey? By thought? Or by typing them out on a keyboard. You come up with this novel parser that you gotta type.

You have two people of equal intelligence, person a types slow, person b types fast. You both type this class out. And for sake of this argument you both do it 100% accurately. Who is going to go on to the next task person a or b? Lets think here... Once code is designed the person who types faster will be the more efficient one. I am not saying everyone who types fast is more productive, that is never the case. But to say oh it doesnt happen is utter bull****.

 

[[)roi(]]

No actually hes not, hes using a blanket statement and placing anyone who types fast cant code(efficiently) in it. Which is the most retarded thing i've heard. FYI i type a normal speed when i code (so im not boasting about speed).

But his remarks are only supported by his experience, which does not encompass the entire planet. There are people on github that churn out projects by the bucket load because of their sheer speed(typing) and efficiency in their code.

Not taking it personally, but your comments are totally unfounded. You seem to think that your experience takes precedence of everyone in the world.

Apparently you're reading far too much into my paragraphs that I ever had the notion to express. To reiterate; coding speed is rarely indicative of a good programmer and certainly never on it's own a good measure for productivity.

I like many others can often churn out decent code far faster than others who follow a similar strong design ethos; however we are certainly to be much slower in wpm than a junior developer who prides themselves on typing speed alone.

Basically my measure of productivity is not on the number of lines I wrote, but rather on the number of lines I didn't have to write.

 

[semaphore]

Apparently you're reading far too more into my paragraphs that I ever had the notion to express. To reiterate; coding speed is rarely indicative of a good programmer and certainly never on it's own a good measure for productivity.

I like many others can often churn out decent code far faster than other who follow a similar strong design ethos; however we are certainly to be much slower in wpm than a junior developer who prides themselves on typing speed alone.

Basically my measure of productivity is not on the number of lines I wrote, but rather on the number of lines I didn't have to write.

I agree with you 100% and i have all along to a certain point. I also write tight compact code, purely because i hate having to scroll more than required. But you can read my response to garp.

 

[MrGray]

You have two people of equal intelligence, person a types slow, person b types fast. You both type this class out. And for sake of this argument you both do it 100% accurately. Who is going to go on to the next task person a or b? Lets think here... Once code is designed the person who types faster will be the more efficient one. I am not saying everyone who types fast is more productive, that is never the case. But to say oh it doesnt happen is utter bull****.

In my experience, given your scenario, person a will just about always produce better designed, more reliable code. Person b may move on to the next task first, but will be back three times to fix the bugs.

 

[semaphore]

In my experience, given your scenario, person a will just about always produce better designed, more reliable code. Person b may move on to the next task first, but will be back three times to fix the bugs.

Never mind you missed the point. As you where. But again its your experience not everyone's.

 

[[)roi(]]

I agree with you 100% and i have all along to a certain point. I also write tight compact code, purely because i hate having to scroll more than required. But you can read my response to garp.

Ok at least there's some progress on both sides; again with your comments to @garp I'd have to say I haven't found an occasion with two highly skilled developers where typing speed was ever the problem.

 

[semaphore]

Ok at least there's some progress on both sides; again with your comments to @garp I'd have to say I haven't found an occasion with two highly skilled developers where typing speed was ever the problem.

Cool. I've grown bored of this argument now

 

[[)roi(]]

Cool. I've grown bored of this argument now

Again we agree... (On both counts )

Btw thanks @semaphore + @garp for the healthy debate.

 

[MrGray]

Never mind you missed the point. As you where. But again its your experience not everyone's.

I didn't miss the point. I just disagree with you. Coding is not just typing, and developers who type very fast almost always haven't thought out what they're doing. So, while they might produce "accurate" code, they tend to write junk. For this reason, developers who make a big thing out of their typing speed are generally not that great.

In any event, with today's tools and IDE's you're seldom going to be using a pure typing only text based editor so this is increasingly irrelevant. The amount you actually have to type is surprisingly negligible so it makes very little difference how fast you type anyway.

 

[[)roi(]]

I didn't miss the point. I just disagree with you. Coding is not just typing, and developers who type very fast almost always haven't thought out what they're doing. So, while they might produce "accurate" code, they tend to write junk. For this reason, developers who make a big thing out of their typing speed are generally not that great.

In any event, with today's tools and IDE's you're seldom going to be using a pure typing only text based editor so this is increasingly irrelevant. The amount you actually have to type is surprisingly negligible so it makes very little difference how fast you type anyway.

Yip and... probably a factor!

 

[Necuno]

Coding 101

A) Think, think good about what you are going to do
B) Type

Of course typing fast will fsckup B

 

[noob_saibot]

We had the Java flame-war the other day and today it is the typing-speed flame-war

 

[gkm]

Basically my measure of productivity is not on the number of lines I wrote, but rather on the number of lines I didn't have to write.

I usually measure my productivity in the number of lines of code I delete. I am annoyed if a change I make cause a net gain.

Edit: That being said, I do wish I could touch type.