From: Jim <jim.pryor@nyu.edu>
Date: Sat, 31 Jan 2015 01:08:15 +0000 (-0500)
Subject: note about refreshing page, notes for us to add later
X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=commitdiff_plain;h=8f7941443b7dd7d1619b6de90f7b33fa78814d14

note about refreshing page, notes for us to add later
---

diff --git a/index.mdwn b/index.mdwn
index eafcf6d7..50d1c03b 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -7,15 +7,14 @@ The seminar meets in spring 2015 on Thursdays from 4 until a bit before 7 (with
 the Linguistics building at 10 Washington Place, in room 103 (front of the first floor).
 
 <!--
-One student session will be held every Wednesday from 3-4 on the
-fourth floor at 10 Washington Place.
+One student session will be held every Wednesday from XX-YY at WHERE.
 -->
 
 
 ## Announcements ##
 
 This wiki will be undergoing lots of changes throughout the semester, and particularly in these first few days as we get it set up, migrate over some of the content from the previous time
-we taught this course, and iron out various technical wrinkles. Please be patient.
+we taught this course, and iron out various technical wrinkles. Please be patient. When you sit down to read the wiki, it's a good idea to always hit "Refresh" in your browser to make sure you're reading the latest additions and refinements of the website. (Sometimes these will be tweaks, other times very substantial. Updates will happen at miscellaneous hours, sometimes many times in a given day.)
 
 If you've eager to learn, though, you don't have to wait on us to be ready to serve you. You can go look at the [archived first version](http://lambda1.jimpryor.net) of this course. Just keep in mind that
 the text and links there haven't been updated. And/or you can get started on installing the software and ordering some of the books.
@@ -24,12 +23,58 @@ As we mentioned in class, if you're following the course and would like to be em
 
 As we mentioned in class, we're also going to schedule a session to discuss the weekly homeworks. If you'd like to participate in this, please complete [this Doodle poll](http://doodle.com/7xrf4w8xq4i9e5za). It asks when you are available on Tuesdays and Wednesdays.
 
+<!--
+One student session will be held every Wednesday from XX-YY at WHERE.
+
+For those who'd like to attend the section but can't make the
+Wednesday time: If you're one of the students who
+wants to meet for Q&A at some other time in the week, let us know.
+
+You should see the student sessions as opportunities to clear up lingering
+issues from material we've discussed, and help get a better footing for what
+we'll be doing the next week. It would be smart to make a serious start on that
+week's homework, for instance, before the session.
+-->
+
 Here is information about [[How to get the programming languages running on your computer]].
 
 Here are Lecture notes for [[Week1]]; [[Assignment1]]. (*These will be posted soon.*)
 
 >	Topics: Basics of Functional Programming
 
+<!--
+*	Henceforth, unless we say otherwise, every homework will be "due" by
+Wednesday morning after the Thursday seminar in which we refer to it.
+(Usually we'll post the assignment shortly before the seminar, but don't
+rely on this.) However, for every assignment there will be a "grace
+period" of one further week for you to continue working on it if you
+have trouble and aren't able to complete the assignment to your
+satisfaction by the due date. You shouldn't hesitate to talk to us---or
+each other!---about the assignments when you do have trouble. We don't
+mind so much if you come across answers to the assignment when browsing
+the web, or the Little Schemer book, or anywhere. So long as you can
+reason yourself through the solutions and experience for yourself the
+insights they embody.
+
+	We reserve the privilege to ruthlessly require you to
+explain your solutions in conversations at any point, in section or in
+class.
+
+	You should always *aim* to complete the assignments by the "due" date,
+as this will fit best with the progress of the seminar.
+
+	The assignments will tend to be quite challenging. Again, you should by
+all means talk amongst yourselves, and to us, about strategies and
+questions that come up when working through them.
+
+	We will not always be able to predict accurately which problems are
+easy and which are hard.  If we misjudge, and choose a problem that is
+too hard for you to complete to your own satisfaction, it is still
+very much worthwhile (and very much appreciated) if you would explain
+what is difficult, what you tried, why what you tried didn't work, and
+what you think you need in order to solve the problem.
+-->
+
 
 ## Course Overview ##