+ 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)
+
+(**[[Lambda Evaluator|code/lambda evaluator]]**) Usable in your browser. It can help you check whether your answer to some of the (upcoming) homework questions works correctly.
+<!--
+ There is also now a [library](/lambda library) of lambda-calculus arithmetical and list operations, some relatively advanced.
+-->
+
+(**Week 2**) Thursday 5 February 2015
+> Topics:
+[[Intro to the Lambda Calculus|topics/week2 lambda intro]];
+[[Advanced notes|topics/week2 lambda advanced]];
+[[Encoding Booleans, Tuples, Lists, and Numbers|topics/week2 encodings]];
+[[Homework|exercises/assignment2]]
+
+> Also, if you're reading the Hankin book, try reading Chapters 1-3. You will most likely need to come back again and read it multiple times; but this would be a good time to make the first attempt.
+
+> We posted [[answers to Week 1's homework|exercises/assignment1_answers]].
+
+(**Week 3**) Thursday 12 February 2015
+*We will continue to develop these notes over the next few days.*
+
+> Topics:
+[[Arithmetic with Church numbers|topics/week3_church_arithmetic]];
+[[More on Lists|topics/week3 lists]] (expanded on Sunday);
+[[What is computation?|topics/week3_what_is_computation]];
+[[Reduction Strategies and Normal Forms|topics/week3_evaluation_order]] (posted on Monday 23 Feb);
+[[Unit and its usefulness|topics/week3 unit]] (posted on Wednesday);
+[[Combinatory Logic|topics/week3 combinatory logic]] (revised on Monday and Tuesday);
+[[Homework|exercises/assignment3]]
+
+> Also, by this point you should be able to handle all of *The Little Schemer* except for Chapters 9 and 10. Chapter 9 covers what is going on under the hood with `letrec`, and that will be our topic for next week. You can also read Chapter 4 of Hankin on Combinatory Logic.
+
+> We posted [[answers to Week 2's homework|exercises/assignment2_answers]].
+
+(**Week 4**) Thursday 19 February 2015
+
+> Topics: [[!img images/tabletop_roleplaying.png size="240x240" alt="Hey, no recursing"]]
+[[Yes, recursing|topics/week4_fixed_point_combinators]];
+[[More about fixed point combinators|topics/week4_more_about_fixed_point_combinators]];
+Towards types (in progress);
+[[Homework|exercises/assignment4]]
+
+> Now you can read Sections 3.1 and 6.1 of Hankin; and browse the rest of Hankin Chapter 6, which should look somewhat familiar.
+
+> If you're reading along in the Pierce book, we've now covered much of the material in his Chapters 1-7.
+
+> We posted [[answers to Week 3's homework|exercises/assignment3_answers]].
+
+(**Week 5**) Thursday 26 February 2015
+
+> *Note*: Jim will be updating and expanding the lecture notes by Tuesday, but doesn't want to delay any longer letting you have access to the drafts we (in part) presented from in seminar. But do come back and re-read the pages when the expanded versions are posted.
+
+> Topics:
+[[Simply-typed lambda calculus|topics/week5 simply typed]];
+[[System F|topics/week5 system F]];
+Types in OCaml and Haskell;
+Practical advice for working with OCaml and/or Haskell (all will be posted soon);
+[[Homework|exercises/assignment5]]