Thread: writing code on paper

Learn the language.

Seriously, I can think of 2 reasons you can write code on a compiler properly:
1. You look up everything on the internet, maybe even copy code from others.
2. You compile a lot, the compiler shows you the errors, which you solve.

Well, everybody has "2" more or less. I think it's good practice to compile often, and even experts will make mistakes often enough. But if you use it too much, it will impact your grade.

So you tell use, which of the two is true? Or did you just happen to have a full black-out at the exam? I think you should just learn the language better...

Originally Posted by bernt

-Double space on paper
-Abuse whitespace rules (or lack of them);-You can put all your declarations on one line if it really comes to that
-Does your prof. let you use scratch paper? He probably does. Write out the general structure of the program and list what you need to declare based on that.

actually no he doesn't, I know it seems weird, but he doesn't give any scratch paper and even if you ask him to give one like one of my class mates did he gave nothing, because he said that the space required is enough

i hope he gets the logic right though, I have the logic correct everywhere, I hope he appreciates that

but anyway, thanks guys for your advice, I will try to work it out, so that next year I will have no more problems related to this

it's all practise I guess, I just never had to write code on paper this year, and this was just too much for me, especially when you wait something more that has to do with theory instead of writing code again

I will practise this summer though and try to get better

thanks for your help

I can't imagine having to write 100% syntactically correct code on paper. Man, I don't even require interview candidates to do that on a whiteboard.

I think Salem has it right that your prof. probably just wants to see that you understand the concepts, algorithms, and in general just wants to see your thought process. Syntax is just sugar and I cannot imagine getting graded on pure syntax.

i hope it is like this, i will just wait and see

the problem is that it's not just me, i ve asked many students and all are very dissapointed with the exercises, because we expected to have plain theory, with small coding exercises that require to create simple functions, show what the result is for example you have an exercise with pointers etc functions and show what the results would be

usually this is what he puts in these kind of exams, we already had coded using a compiler and took grades for that, and we were just expecting theory, and this is what we get again

maybe wrong syntax is ok, but at least it would be good if he specified what he really wanted

but nevermind, this has already passed, i will just try to prepare myself better for the next time

Coding on paper is brutal. Sorry, dood

I don't mind coding on the whiteboard for interviews. I think it's better because I can think out loud, and it's usually the thought process that gets me the job.

Just leave lot's of space between lines.

They don't really care about syntax anyways. Everyone knows the syntax. I usually go half C half pseudo-code even. Probably not a good idea on tests, though.