Announcements
I have been remiss in the past about updating the site. I'm hoping to remedy that this year, but know it's a habit-change in progress.
- Sept 5, 2011 : Updated website contents for F11 course.
- Sept 14, 2011: Added Lecture 2 and Q2 to the site.
Q & A
I will place salient questions and answers here.
Submission Policy
Concerning submission of homework and quizzes:
- THERE ARE NO LATE DAYS FOR THIS CLASS. There are many, many of you, and one of me. You have more than enough time to complete the given assignments in the time allocated (2 weeks). I will also make an earnest attempt to make the assignments available to you ahead of time, but I reserve the right to edit the assignment without warning until the day it's officially assigned. These will mostly be minor changes, but still, be aware. In terms of the quizzes, they should not take you more than 20-30 minutes, tops. You have 2 days to do them. Don't turn them in late.
- YOUR SUMITTED CODE MUST COMPILE ON THE EDLAB LINUX MACHINES. If the code does not compile without modification on one of these machines, you will receive a zero for the assignment.
- I WILL NOT PROVIDE HELP IN SETTING UP ANY DEVELOPMENT ENVIRONMENTS. You can ace this class writing your code in Notepad (Windows), TextEdit (Mac OS X), or Emacs/Vim (Linux). In fact, if you prove to me that you did, you will receive extra credit because that's hardcore and awesome. Setting up Visual Studio, Xcode, NetBeans, or Eclipse is a waste of your time. I'm not saying you can't use them, but I am saying that I will not help you set them up since you definitely don't need them to pass.
- DO NOT EMAIL YOUR CODE TO ME OR THE GRADER(S). All homework and quiz submissions will be made to the Spark website. This will allow us to securely and efficiently provide you with grades as soon as possible, as well as avoid any confusion concerning submission times. Both assignments and quizzes will be available from this site (see Syllabus). In the case of programs, you will provide the source code files and the Makefile necessary to build the program from your source. In the case of quizzes, just submit a plain text file containing the answers to the questions.
Classroom Behavior
I tend to be a bit flippant in class - I probably do this in order to loosen the atmosphere and hopefully make
a rather dry topic a little less boring. Although I have no problem with in-class or banter in communication (i.e. email),
please remember to be professional and tasteful. Should I find your behavior overly familiar, I will inform you once that you
need to watch yourself and maintain some amount of distance. If you continue to behave in a way that I find unacceptable, I
will escalate the matter to the undergraduate program director, which most likely will then go to the department chair and/or the
dean of students.
Academic Dishonesty
The official university policy on academic dishonesty can be found
here. If you are found cheating (using someone else's work as your own, violating the aforementioned policies, or collaborating without permission),
you will be disciplined pursuant to the university policy on academic dishonesty.
In terms of my response in class, the offending individual(s) will receive a zero for the given assignment,
and their participation contribution in the class is automatically reduced to zero with no negotiation possible.