Eat a bag of dicks.Originally Posted by BerringerX
Last edited by Nei; 06 Nov 2006 at 10:07 PM.
true dat.
i was taught to write well-documented and easy-to-read code with good variable and function names and all that crap. and the thing that really helped me when i coded was testing everything as i created it. it takes more time to do, but it really helped me figure out exactly where errors were occurring. plus, you can't get help from the TA's if you wait 'till the night before to write the program.
it always drove me nuts to see my friends spit out the entire program without testing it and then get more error messages than the machine could handle.
"I am government man, come from the government. The government has sent me."
IP, you still need C++ pointers and stuff? I'm about to finish up my advanced C++ class...
http://www.ammosart.com/~iidx/images...OS-TNL-Sig.jpg
Der Wille zur Macht
Jenseits von Gut und Böse
Also Sprach Zarathustra
I think i took a class just like this, i was even in the electrical section. In our class the prof would write out a big this of code, and basically erase random things, and large chunks, we had to fill it in. Also we had to write lots of loops, and at one point code a program that would invert any matrix properly... We didnt touch a computer once, even on the assignments, it was pen and paper.
My suggestion is write it all out in pen and paper, from memory (after trying to memorize all you can) then type it in and go through to check your errors.
If its on paper, study it on paper. It will help. Also when you do assignments try doing as much as you can without using any aids, just do them from what you remember, it may help on the tests, since those test what you can remember as well.
Cheers!
You can never be one of the dead, because something that has no existence can have no community.
Frontiers
Bookmarks