+* 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.
+-->
+
+* The student session has been scheduled for Wednesdays from 5-6, in Linguistics room 104 (back of the first floor).
+
+ Those of you interested in additional Q&A but who can't make that time, let us know.
+
+ You should see these 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's expected you'll have made at least a serious start on that
+week's homework (due the following day) before the session.
+
+* Here is information about [[How to get the programming languages running on your computer|installing]]. If those instructions seem overwhelming, note that it should be possible to do a lot of this course using only demonstration versions of these languages [[that run in your web browser|browser]].
+
+* 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.
+
+
+
+
+(**Week 1**) Thursday 29 Jan 2015
+
+> Topics:
+[[Order in programming languages and natural language|topics/week1 order]];
+[[Introduction to functional programming|topics/week1 kapulet intro]];
+[[Homework|exercises/assignment1]];
+[[Advanced notes|topics/week1 kapulet advanced]]
+
+(**Intermezzo**)
+> Help on [[learning Scheme]], [[OCaml|learning OCaml]], and [[Haskell|learning Haskell]];
+The [[differences between our made-up language and Scheme, OCaml, and Haskell|rosetta1]];
+[[What do words like "interpreter" and "compiler" mean?|ecosystem]] (in progress)