Are Written Computer Science Exams a Fair Measure? 728
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?
simple (Score:0, Funny)
college is overrated.. you'll realize sooner or later
Re:simple (Score:1, Funny)
State-Dependent Memory (Score:2, Funny)
---
Never test for an error condition you don't know how to handle.
-- Steinbach
Re:Writing code (not typing it) is *hard* (Score:2, Funny)
I agree. It's when the start talking cars and lights turning on and off that you want to pay attention.
(sorry,- I'm in my Friday mood...;-))
Re:Agreed (Score:3, Funny)
package dataStructures;
public class FinalExam {
public boolean pass() {
return true;
}
public int grade() {
return 100;
}
}