Engineering Computing: CSC160

Procrastination is the grave in which opportunity is buried.

--- Dennis Kimbro.

Any fool can drown; that's the easy bit.

--- Pete Goss, Solo sailor

Grading Policies

Academic Honesty:

Yogi says: "If you can't imitate him, don't copy him!"

This course follows The University Policy on Academic Honesty .

Explicitly for this course: Thinking together about problems or programming projects and assignments is fine, and encouraged. Asking technical questions from your fellow students or anybody else, and getting specific answers, is fine, and you're crazy not to. Going out to the web for better explanations and examples than the text has is fine.

BUT do NOT share your written answers or code, or what you plan to hand in. That is, don't volunteer it, don't ask for it, don't give it, don't receive it, don't show it, don't look at it, don't allow it to be copied, don't copy it. Also do not copy answers or prose from the web, blogs, books, or any other non-human source. When you use any source, either human or non-human, in an answer, credit that source with a reference and say how you "added value" to the content you built on to produce your answer. Such sharing of WORK (not thoughts) we must consider Plagiarism and we must take the necessary steps as mandated by the University.

Unless work is surreptitiously stolen, we both consider parties equally guilty; to dispute this, you can always go tell your story to the BAH.

Notes

• The Reading listed for a day should be done BEFORE that day.
• Topic dates in the tables are approximate and may be shifted.
• Programming exercises are due in Blackboard on the day and time indicated in Blackboard: any dates given in the tables below are approximate. There's a 2-day "late" period on programming assignments where some partial credit may be given.
• In the tables, AX.Y means the Attaway Text, Chapter X, Section Y.

Schedule: Theory and Applications Segment