Each week, I will ask you to read something about an aspect of Javascript and/or Web Programming.

I will give you “required” readings. These are a minimal set – it’s enough, but I encourage you to find more.

Beyond the Minimum: One aspect of web programming is that the web really is the best resource for it (usually). Books and traditional media don’t evolve as quickly, don’t provide the diversity of viewpoints, and often aren’t the preferred venues of the "real experts." (If you’re an expert programmer, you might be too busy to write a book, but willing to share your expertise). There are downsides to getting information from the web (how do you know you can trust it?), but to be honest books have this issue too. Except that if its a blog and its wrong, a lot of commenters will point out the problems and the author can update it.

For this class, I want to encourage you to seek information on the web. Part of learning to web program is to learn what the good resources are and how to find what you need. I want this to be a collaborative experience where everyone shares the things they find. What I have found is just that: what I have found. Each student in class will find more. Together, as a large team, we’ll find a lot.

Even if you know the topic, you can always find something new to learn about it. So do some reading. If you’re already an expert on a topic, find some more advanced reading about it. Or read a less advanced thing so you can contrast the author’s point of view with your own.

If you find a great resource on a topic that you think others should read, there will be a separate “recommended resources” discussion forum for listing it (this is not the same as the place for you to put your reading discussion). If you list something, please put an URL so we can find it, and tell us a little bit about it (including why you like it so much).

Discussion: With each reading, there will be a required discussion. You will be asked a question to guide your response. You have to make your initial posting before you can see anyone else’s, but after that, you can read and respond to your classmates’ postings. (You will be divided into groups online, so you won’t see the whole class). Making an initial posting that addresses the prompt question is required each week. Reading other people’s responses (and having a discussion) is optional – but you will get a lot more out of class by participating this way.

There are a bunch of reasons why I am asking you to do these reading discussions:

1. You will learn more from the readings if you are forced to think about them, and to articulate things from them.
2. Discussing things is a good way to help solidify the concepts.
3. It’s a way for me to check that you’re doing the work.

Grading: Check/No Check. The minimal thing is to provide a list of what you read, and a sentence or two of assessment and overview of what you read. And, to be honest, given that this class has no grading resources, my checking of this will be minimal. I may spot check them from time to time, but overall, if you decide to "cheat" by just making a garbage post, you will probably get away with it from a grading perspective. However, taking the reading, reflection, and conversation part seriously will greatly enhance the amount that you’ll learn. (really! writing and discussing will help you internalize what you’ve read) And, since these are forums seen by your classmates, hopefully there is some peer pressure to not say silly things

There is no official reward for doing a better than minimal job (this is a pass-fail class). But if you take the effort to write, think and discuss, your reward will be better learning outcomes. And probably the appreciation of your classmates who see what you’ve written.

Overall Grading: To pass (this is a pass/fail class) you need to have completed at least 75% of the readings (which means making a non-bogus posting to the forum for that assignment). And your initial postings should be on-time, most of the time. (so you can’t just go back and write 12 postings the last week of class). Note: you must also get a passing score in other parts of the class as well.

On-Time Policy: Officially, the deadline is hard (see grading above). I want you to do the reading (and the initial posting) by the date required. This is always a Monday (before Tuesday) so you’ll have read the material for class. Of course, I’d rather you do the reading late than not at all, but its really best if you keep up with the reading.

I will leave the  Don’t wait too long to make your first posting, because I might close a discussion without notice.

Programming is (usually) a team sport. In fact, learning programming (and, arguably, learning in general) is best done in collaboration with others. Unfortunately, in a university class setting, we have the unfortunate constraint that we must grade individuals independently, so we need to have people work independently on graded assignments so that we can assess them. Therefore, there is a fine line between "collaboration" and "academic misconduct".

For this class, we want to encourage collaboration. However, we also need to make sure that each individual gets appropriate credit for their work.

Students are encouraged to discuss class topics and assignments with other students, subject to the following rules.

1. If you are unsure if something is collaboration or academic misconduct, please ask the instructor for clarification.
2. No collaboration is allowed on the exams.
3. Assignments and projects must be substantively from the person claiming to have done it. It’s OK to ask for help, but most of the work should be your own.
4. Ultimately, each student is responsible for the material. Projects, assignments and exams will require you to understand the assignments, so be careful not to rely on help since at some point you might need to do it your self.
5. Collaboration must be a two way street. The person giving help must OK it. (e.g. don’t look at someone else’s work without their permission).
6. Every student must turn in their own assignment, and is responsible for it, unless it is explicitly a group project. For group projects, specific instructions will be given (generally it is turned in once, and other group members give pointers).
7. Projects must be "substantially" written by the student handing it in. In particular, the "meat" of the project must be completed by the student handing in the project.
8. Any code that you didn’t write must be given proper attribution. If you grab a piece of code from the web (including the class sample code!), another student, some book, … – YOU MUST SAY SO! It is OK to use pieces of sample code – providing that you give proper credit to the author.
9. We will give you large amounts of example code to work with for various assignments and projects. Be sure to give it proper attribution.
10. If you use an external library as part of an assignment or project, make it clear (in a README file or the notes with your submission) what it is, and where you got it from. You must write key parts of the assignment yourself.
11. With JavaScript, you can do “View Source” in the web browser to see how programs you find (including our sample solutions) work. While we encourage you to use this to learn, we discourage you from just copying too much stuff. We urge you not to snoop to find answers to things we want you to figure out yourself, or to steal large pieces of code. Again, this is a fine line: use your judgment, or ask.

So…

• It is OK to ask a classmate for help on one of the questions on a written assignment. It is not OK to "borrow" their assignment and copy it without their permission. It is not OK to just copy it without understanding it (since you won’t learn the material).
• It is OK to ask a classmate for help looking over your code to find a bug. It is not OK to use a piece of their code without giving them proper attribution, or if its an important part of a project.
• It is OK to use the provided example code, or a data structure implementation you find on the web PROVIDED THAT YOU GIVE PROPER ATTRIBUTION. It is not OK to use a piece of code on the web for a central piece of an assignment (like a required image processing routine)
• If you ever have a question, ask.