Logistics

• Instructor - HilaryHolz
• Grading - Prep, Assignments, & Labs (no exams)
• Collaboration/Plagiarism/Etc. - What is important is to (1) work hard, (2) read others' work, and (3) give credit where credit is due. Make sure that you immediately make a record of where you find information (you'll never remember later!). Then link back to it when you use it.

See also

• PLCLabsSpring08
• MutualDiscovery

Class Notes

• OnBindings
• Chapter2intheWild
• SampleAutoloadCode
• TypeSystems
• ControlAndEvaluation

[edit]

Investigative labs for PlcWinter09

Older Examples to look at

• PLCLabsSpring08 - from back on Blackboard, this is a set of labs that are somewhat 'packaged' for other faculty, administrators, etc., to look at.
• Lab sets from Fall08 on twiki for other classes listed at MutualDiscovery - 'in situ', not processed or modified at all, but you have to click to see each lab, etc.

things we'd like to do differently

• we'd like to get a much richer narrative. NandiniPremmanisakul asked whether investigators should be keeping a journal while doing a lab, and that is the perfect metaphor for the level of richness we want, at least for the moment.
• we're trying to sort out some balance between prep work and involving the classes in the design of the labs

our labs

• YourFirstLab
  • YourFirstLabReports
• BindingsInRuby
  • BindingsInRubyReports
• ExploringLanguagesThroughParallelExamples
  • ExploringLanguagesThroughParallelExamplesRoughDrafts

What you should be doing

• 2/5
  • More on BindingsInRuby, added the RubyBindingKoans page. For Tuesday, should have rough draft mostly done.
  • We will go over 3.4.1 (on CD), 3.4.2 (on CD) and 3.5.1 in class on Tuesday. Make sure you spend some time looking at the sections before class, so that you get the most out of the talk.
  • Rough drafts will be due on Thursday 3/12 to get into the peer eval lottery.
• 2/3
  • We're going to get more formal about the lab process in this class. We discussed this briefly last week, but now we get down to it for real... See the new section on labs.
• 1/27 - 1/29
  • We started on the central theme of Chapter 3, bindings...
  • We focused on integration:
    • discussed Software Engineering (and the books on WebHome)
    • worked some more on integrating Chapter 2 material,
    • looked more at RuBy,
    • on Thursday went to a guest lecture on RisCool.
  • You should be writing a couple of paragraphs about RisCool, your impressions of the language and how it is used, and how it relates to the other languages you know. If you did not get to the guest lecture (there was a sign-in sheet which I have, bwahahah (evil laughter), I will expect a more in-depth report...)
• 1/22/09
  • start exploring RuBy, using the Why's Poignant Guide (see RuBy page). Even if you already have started working with RuBy in the past, read Why's Poignant Guide anyway. Why? You'll see. The lesson here isn't just the syntax (which is tiny, after all), it's about how to learn these languages, how we think in these communities, how to gain access to the geek world and to the geek way of thought.
    1. for Tuesday (duh!), read the book and play with the language,
    2. keep a journal (online or physical, up to you) about the process. your reactions, what you did, what worked, what was new, what you ate for dinner, I don't care which of these or all of them, just keep a journal about the process.
  • in class, we did peer evaluations, see also LabPeerEvaluationTemplate, and PeerEvaluation?
• 1/15/09
  • get JFLAP!
  • play with it
  • use it to start learning Chapter 2
  • YourFirstLab
    • YourFirstLabReports
• 1/8/09
  • (for Tuesday, 1/13/09) read Chapter1 in Scott
  • register for your account on the wiki
  • (for Tuesday, 1/13/09) take notes on Chapter 1 on a page on the wiki - can be your wiki home page or you can create a page in this web, Mutualdiscovery, to keep your notes. Answer some of the 'check your understanding' questions as you go (Hint! don't wait until you are done reading, instead,
    1. read the questions first;
    2. pick out the ones you find interesting/challenging/impossible;
    3. make an entry on your notes page for the question;
    4. keep notes relevant to the question;
    5. finally, rewrite your answer when you are done reading.

required textbook

• Scott, Programming Languages Pragmatics, 2nd Ed.

recommended reading

• the 'Generally wonderful books' from the FreeOpenSrc activity home page

tools

recommended books

• Agile Software Development Ecosystems by Jim Highsmith, ISBN-13:9780201760439
• Agile Project Management Creating Innovative Products by Jim Highsmith, ISBN-13:9780321219770
• Object-Oriented Programming in Python, Goldwasser & Letchser (sp?), more info in Hilary's reading list.

• Set ALLOWTOPICCHANGE = TWikiAdminGroup
• Set ALLOWTOPICRENAME = TWikiAdminGroup

• 01chapter_1._introduction.ppt: 01chapter_1._introduction.ppt

• 02chapter_2._programming_language_syntax.ppt: 02chapter_2._programming_language_syntax.ppt

• 03chapter_3._names_scopes_and_bindings.ppt: 03chapter_3._names_scopes_and_bindings.ppt