Course Standards

These apply in every course I teach, at the university and at the community college, whether or not the subject has anything to do with the web. They are about how you work, not what you build. The rules for what you build live under Web Standards.

Where these standards and your course syllabus disagree, the syllabus wins - and tell me, because one of them needs fixing.

Your LMS Has the Real Dates

What's due, and when, is in your course's learning management system. This site explains how to do the work and what "done" means; it doesn't have the schedule, because two copies of a schedule means one of them is wrong. If your LMS and a page here disagree about a date, the LMS is right.

Submit What the Assignment Asks For

Name Things so the Name Answers the Question

Files, folders, images, and submissions. A grader looking at a list of names should know what each one is without opening it. This is the same habit whether you're naming an image or a variable, and it's the cheapest professional skill you'll ever pick up.

Do Your Own Work, and Say What Helped

Ask Early, in Public Where You Can

Most questions aren't unique to you. Use the course discussion space so the answer helps everyone, and save email for matters that are about you alone. A question asked two days before the deadline gets a much better answer than the same question asked two hours before.

Accessibility and Accommodations

If you've an approved accommodation, send me the letter through your institution's process as early in the term as you can, and let's talk about how it applies to this course specifically. If something about how this course is run is getting in the way of your learning and you don't have a formal accommodation, tell me anyway.

Back up Your Work

A lost file isn't an extension. Keep your work somewhere that survives a dead laptop - version control, cloud storage, a second copy, anything but one folder on one machine.