Need to program faster for tests in class

[Fullmetal Chocobo]

I've been doing basic JavaScript programming for a while, so I know some about programming. I started my first C++ programming class this semester, and I am slow when it comes to writing programs in class. I'm also the only one in class that does pseudocode on scratch paper, then writes code on the test's scratch / notes page, then writes the final code to the final pages.

Any tips or practices for those experienced in programming or that have done written programming tests before?

I wish I could type the test out--I'd probably be a lot better off.

 

[Crusty]

Use simple variable names as often as possible. On tests I only used to give meaningful variable names to ones that were important to the question, otherwise they got a single letter as their name.

Perhaps instead of writing full out pseudocode you could try starting with a flowchart and then go straight to the final code. For me flowcharts were a lot faster to do then pseudocode.

 

[DaveSimmons]

Do a lot of extra coding outside of the required work. If you have a textbook and are given (say) 1 out of 5 of the end-of-chapter exercises as homework, do the other 4 too. Or go to the library and find another C++ book with problems and check it out.

The more you work at it, the more you'll be able to hold in your mind without needing to put it down on paper first.

Like most other work, it gets faster and easier as you practice.

 

[Hyperblaze]

On tests, since you are under time restrictions, avoid trying to complicate things too much (less problem requires said functionality)

you are there to show how to provide a solution to a specific problem.

anything else is just icing on the cake and not required.

 

[Journer]

written programming tests are easily the biggest gripe i have about cs. i can program pretty well and never make less than 90% on my projects, but i cant pass the stupid tests because i forgot a minor syntax; something any compiler would let you know... argh!! /rant

 

[drebo]

Precision is pretty important in programming. Speed isn't really all that important. However, in the swing of things, the person who is precise AND fast is more desirable than the person who is precise OR fast. Thus the higher grade to the person who gets it done right and in the correct amount of time.

 

[mosco]

Originally posted by: Journer
written programming tests are easily the biggest gripe i have about cs. i can program pretty well and never make less than 90% on my projects, but i cant pass the stupid tests because i forgot a minor syntax; something any compiler would let you know... argh!! /rant

I am about to graduate with a BS in comp sci and I can't even remember the last time I had to write code on a test. Once you get done with the first year of CS, you should never have to write code. My classes usually don't even have tests, just homeworks and group projects.

 

[sourceninja]

I'm actually working on developing a php class for the college where I work. One of the things I've decided is no writing code on tests. They will describe principles on tests, answer multiple choice on code snippets, select correct code blocks to complete a program, etc. All programing will be done during labs and a single project they will have to turn in (working in labs or at home) with their final.