Are Written Computer Science Exams a Fair Measure?

me! asks: "I seem to have this inability to write substantial chunks of code (500+) in exam conditions (for uni). I have been writing code for years for open source and commercial applications, so I know a thing or two. There is just something about exams and code that does not work for me. I find that I need to be sitting in front of a computer to get a problem out, to get in the 'vibe', have you will. I have done exams on computers (closed environment) that involve coding, and it work so much better for me. So what I am asking is...how do people tackle exams that involve solving problems on the fly, on paper, in exams?" I have this exact same problem, and I've never thought written tests were a fair way to measure someone's knowledge of coding. It's fine when you are asking questions about design and structure, but when you need to write code it falls way short. How do you feel about it?

Comments

ABSOLUTE BULLSHIT!!!

[crovira]

Utter crap. Saying "programming is very individual and specific to the programmer" is spewing TOTAL stupidity!

The problem and the object model created to define it will provide the solution. That's the ONLY way to code it.

The data structure falls out of the object model. The algorighm likewise falls out of the model after performing appropriate optimizations.

Write code so the machine will NEVER do ANYTHING it doesn't need to. Not a extra disk hit, not an extra byte fetched, not a uselessly continued loop, not an instruction executed twice. Code the algorithm to deal with sub-optimal structure for the process that needs to be executed.

Cache every execution result that you will need again. RAM is cheap. Time is not. Not even Bill Gates can buy the user another second.

But RAM is not so cheap that you need to waste money and time filling it unnecessarily. Only cache what you absolutely need again.

If you don't know what the fuck you're dealing with. Don't start writing the fucking code. It'll just be garbage. Worse, it'll be "almost" working and become a sump for development time.

I loathe moron who keep saying that software development is an individual's preference. That a total crock spewed by ignorant ass-holes.

Learn your job and write properly optimized algorithms or sell shoes for a living. I loathe debugging code written by dilletantes and "artistes."