|
| 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).
___________________
My party schedule:
2009-02-21 - DJ Attention @ I'm So Popular
2009-06-18 - DJ Annoying @ People Need To Know Where I'll Be
2012-11-32 - DJ Insufferable ɸ Or At Least the Stalkers I Complain About
2048-06-66 - Spastic & Whocares ¶ Although I'm Actually Flattered
9999-45-81 - Tweaker Gimp ☼ I Probably Won't Even Go To This But I Have To Make Sure I Fill Up All The Available Space Here
|
