|
1.
|
Change the test format! The module 5 Test was a good way to do it and the multiple choice was a terrible way to do.
|
|
2.
|
Sometimes it helps to bring in outside knowledge if possible,
specifically with regard to terminology. Sometimes terminology in the
exams might be more common in actual technological conversation than
what will be found in the textbook. That being said, the textbook is a
great resource with a very thorough index, so use it as much as
possible, especially for homeworks.
|
|
3.
|
Make an effort on the projects - any work is better than none.
|
|
4.
|
This class is more conceptual than technical, so keep that in mind when
taking the course. Try to get a grasp of the larger concepts and how
they relate to one another. Otherwise, you'll just get bored with the
class and think it's too easy because there really isn't any coding
involved except for the projects.
|
|
5.
|
Keep up on the reading, the book is interesting and informative.
|
|
6.
|
The book may be the most useful tool you have for tests and projects.
Knowing where information is in your book will prove to be invaluable
during open book tests.
|
|
7.
|
Google for sample code and tutorials for the homework assignments. The
book explains the concepts, but the actual implementations can be odd.
There are some excellent sample programs on the internet that you can
play with.
|
|
8.
|
be sure to allot enough time to finish the projects.
|
|
9.
|
Reading the chapters ahead of time and being familiar with the material would help with paying attention in class.
|
|
10.
|
Don't be afraid to participate. For some reason, our class was silent
and never answered questions and didn't get much out of lectures. Also,
start the homework projects early, and use class time to ask questions
about them. It is very hard to do projects in 1 night, and often you
get stuck on a silly problem that requires a simple question.
|
