Ten ways to lose marks in your assessed exercise
------------------------------------------------
1. Ignore "How Not To Do It"
   http://www.dcs.gla.ac.uk/~pat/cp4/notes/claireNote02.html
   That is, invent your own really awful coding convention
   and have absolutely lousy variable names (like we expect
   in 1st semester of 1st year). 

2. Forget everything you learned at school about English, spelling,
   grammar, and basic communication with  fellow human beings.
   Hey, you're trying to become a computer scientist. When you graduate
   you will never have to converse with a real human being ever again.

3. Include redundant statements in your code, lines of code
   that do nothing, variables that are not used, print statements
   that nobody wants. Basically, write 1st year 1st semester code.

4. Include crap jokes in your email or put a quote at
   the end of your email so that the marks are awarded to
   a non-existent student, rock star, 19th century poet, whatever

5. Make it nearly impossible to download, decompress and access
   your submission because it goes to some bizarre directory
   with a non-UNIX file name. Basically, make it really awkward
   to download and read.

6. Do not bother to look at the course material, especially course
   material that is to do with CP4.

7. Don't bother to find out what arc-consistency actually means.

8. Do NOT read the manual. Do NOT bother to find out why certain
   functions do not work as you expect them to (hey, if it doesn't
   do what you want it to (not having bothered to read the manual) this
   is evidence of a bad api and a bug on the language developers part!)

9. Put all your code in the one for loop. Hey, even though I post
   the very same constraint 26 times times when once is enough,
   it still works so who cares!

10. Don't bother to hand in your exercise.