|
How many words per minute do you type??? (A test is involved) (pg. 4)
|
View this Thread in Original format
| Theresa |
| quote: | Originally posted by nusty
so much I never knew about you Theresa.... |
Being an old man isn't something I am terribly proud of. :( |
|
|
| Cosmic Fur |
| quote: | Originally posted by DigiNut
[FONT=Tahoma][COLOR=#99CCEE]Hah, you guys suck. Especially saying you're in comp sci and not data entry - it's even more important for you guys to be able to crank it out quickly, you'll usually have about 20 minutes to fix some bug (which requires totally rewriting a module, of course) before a customer gives up or gets really pissed off.
|
Puhleeze buddy. I usually agree with you on a lot of things, but here you're waaayy off. 5 minutes of thinking saves you an hour of coding. I laugh at you even suggesting that typing speed has any bearing on your skills as a programmer. Most of coding comes from thinking, looking at the existing code, analyzing, visualizing what's going on, etc etc, not typing. Bug fixes especially. Those are literally just 1 or 2-line fixes. All 20 minutes of typing at 100wpm accomplishes is way too much code for something that could have been done in 5 lines. |
|
|
| kotsy |
| 67WPM with 3 mistakes.. and that's on a keyboard I'm not completely fond of. |
|
|
| DigiNut |
| quote: | Originally posted by Cosmic Fur
Puhleeze buddy. I usually agree with you on a lot of things, but here you're waaayy off. 5 minutes of thinking saves you an hour of coding. I laugh at you even suggesting that typing speed has any bearing on your skills as a programmer. Most of coding comes from thinking, looking at the existing code, analyzing, visualizing what's going on, etc etc, not typing. Bug fixes especially. Those are literally just 1 or 2-line fixes. All 20 minutes of typing at 100wpm accomplishes is way too much code for something that could have been done in 5 lines. |
Do you do this for a living? Sorry, but production code isn't like academic code. It starts out 5 lines long until you start having to deal with all of the disgusting edge cases from interactions with other features that weren't in the original scope (you never get to stick to the original scope).
As an example - we did a production push after everything had been QAed and by the end of the night we had a bunch of weird error reports about a web service call failing, which was in turn because a SQL query was failing. After about 20 or 30 minutes of analyzing the problem, it turned out that one of the Microsoft data access components was doing datetime conversions to milliseconds and causing arithmetic overflows in the database.
So what does one do? Well there was only one thing I could do. Rewrite all of those SQL queries by hand as stored procedures, write all the calling code for those procedures (mostly a bunch of attributes), and change all the references to use the hand-coded sprocs. I didn't count, but I'd estimate it was a couple of hundred LOC.
Or another fun problem we had was a chart component that was throwing an exception whenever there were multiple stacked series and one of them had a different number of points. You'd think this wouldn't matter - just treat it as a zero, right? You tell that to the component designers. All we could do was write a really ugly hack to go through all of the series and put in zeros where the point was "missing". It's not easy to write simple and elegant code for when you have 3 or 4 series with several hundred points each, and a few of these graphs have to be loaded every page access. There are performance constraints here.
You think fixing a bug is just correcting a typo. Not in the real world buddy.
You're right in the sense that a developer does spend most of his time thinking, reading and analyzing code as opposed to writing new code, but in the profession you have to deal with crunches, and when you're dealing with a crunch, you really don't want to be a slow typist (although being a slow thinker is obviously worse). |
|
|
| The Highroller |
Your speed was: 101wpm.
You made 4 mistakes, your mistakes are shown in bold text:
Muthengi was fourteen years old when he first saw a column of shining-skinned young Kikuyu warriors swinging along the forsest's edge towards the plains, like a ripple of wind across a field of ripening grain, on the way to war. Afterwards he could ont remember the names of the warriors, nor the boating words that they shouted to his father as the loped past, nor even the designs painted boldly in black and red on their long shields; but from that moment he became a warrior' his spirit marched with theirs, and dreams of battle filled his waking mind.
That's me typing normally (ie not trying to type as quickly as possible). |
|
|
| zokissima |
| quote: | Originally posted by Cosmic Fur
In all seriousness, I average about 40 words per minute. That's why i'm in computer science and not data entry. |
I'm in Computer Science...and I average 85wpm... |
|
|
| Cosmic Fur |
| quote: | Originally posted by zokissima
I'm in Computer Science...and I average 85wpm... |
Okay, seriously, I have a job where I code right now, and I'm almost done my degree, and typing speed has NEVER been an issue yet. I'm very happy that you can type fast, but it has absolutely no bearing on your ability to program. |
|
|
| FunkyCrew |
| quote: | Originally posted by Cosmic Fur
Okay, seriously, I have a job where I code right now, and I'm almost done my degree, and typing speed has NEVER been an issue yet. I'm very happy that you can type fast, but it has absolutely no bearing on your ability to program. |
I have a friend who was IT major is Seneca, and boy, was he a slow typer:) |
|
|
| DigiNut |
| quote: | Originally posted by Cosmic Fur
Okay, seriously, I have a job where I code right now, and I'm almost done my degree, and typing speed has NEVER been an issue yet. I'm very happy that you can type fast, but it has absolutely no bearing on your ability to program. |
Key word is "yet". It's a shot in the dark but I have an inkling that as an intern you're probably not personally responsible for architecture-wide hotfixes or new features with a delivery date of last month.
If you're limited by your brain, and not your hands, then fine, faster typing might not help you. But honestly, if you have to think that hard about everything you code then you're going to be in trouble. Sometimes you sit around mulling things over, other times you have to churn it out. That's the way it goes.
I'm not trying to put you down, but if you honestly believe that anything non-trivial can be accomplished in 5 lines, you've still got a lot to learn. There's a legitimate argument to be made that some of these things *should* be doable in 5 lines, but the tools just aren't there yet and probably won't get there within our generation or even the next. |
|
|
| Silky Johnson |
| Goddamn, Diginut...you're an expert on EVERYthing! :eyespop: |
|
|
|
|
