<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Summary on Tony Andrew Meyer</title><link>http://tonyandrewmeyer.com/tags/summary/</link><description>Recent content in Summary on Tony Andrew Meyer</description><generator>Hugo</generator><language>en-nz</language><lastBuildDate>Thu, 23 Jul 2009 18:00:55 +1200</lastBuildDate><atom:link href="http://tonyandrewmeyer.com/tags/summary/index.xml" rel="self" type="application/rss+xml"/><item><title>D520 Week One</title><link>http://tonyandrewmeyer.com/2009/07/23/d520-week-one/</link><pubDate>Thu, 23 Jul 2009 18:00:55 +1200</pubDate><guid>http://tonyandrewmeyer.com/2009/07/23/d520-week-one/</guid><description>&lt;p>As &lt;a href="http://tonyandrewmeyer.wordpress.com/2009/07/19/ironpython-course-notes-the-plan/">promised&lt;/a>, here&amp;rsquo;s my material from the first week of &amp;ldquo;D520: Programming&amp;rdquo; (in &lt;a href="http://codeplex.com/IronPython">IronPython&lt;/a>).  I gave the students &lt;button type="button" class="deadlink" aria-haspopup="dialog">a set of revision exercises&lt;/button> [PDF] (and &lt;button type="button" class="deadlink" aria-haspopup="dialog">example answers&lt;/button> [zip]), &lt;button type="button" class="deadlink" aria-haspopup="dialog">a course outline&lt;/button> [PDF], and &lt;button type="button" class="deadlink" aria-haspopup="dialog">some brief notes&lt;/button> [PDF].  The notes have four sections (this pattern will continue): which chapters of the &lt;a href="http://ironpythoninaction.com">textbook&lt;/a> are covered this week (and a couple of sentences that summarise them or point out which parts are important to us), the tools that are required this week (since this is the first week, this section is large, covering installation of &lt;a href="http://adobe.com/reader">Adobe Reader&lt;/a>, IronPython itself (including putting it on the PATH), and several IDEs (as &lt;a href="tonyandrewmeyer.wordpress.com/2009/07/12/choosing-an-ironpython-editor-for-teaching/">previously covered&lt;/a>), including configuration), key points, and example code (the examples that I plan to use in class).  For anyone interested (chiefly: me in about nine months time, when I&amp;rsquo;m planning the 2010 course), here&amp;rsquo;s a summary of the first week.  It&amp;rsquo;s rather long (2100+ words) - the summaries of future weeks should be shorter.The students seemed fine with the choice of textbook, and that there was one.  I expected more grumbling about the price, but perhaps they just kept that to themselves.  There did seem to be a moderate amount of interest in the &lt;a href="http://manning.com/foord">ebook version&lt;/a> over the print copy.  The real test of the textbook starts next week, since none of the students were organised enough to buy the text before the first class, and so hadn&amp;rsquo;t seen it or read the first two chapters, which we covered.  They are expected to have at least skimmed through Chapter 3 before next week&amp;rsquo;s class.
The first part of the lesson was the mandatory-but-dull course introduction (who I am, what the assessment is, what they&amp;rsquo;ll be learning, and so forth), which went as normal.  The second part was a small lecture about IronPython and .NET (roughly covering the material from Chapter 1 of the textbook, but improvised at the time).  I doubt much of this will be accessed (I haven&amp;rsquo;t finalised the examination paper yet) - if anything perhaps just low-mark questions like  &amp;ldquo;what is .NET&amp;rdquo;, &amp;ldquo;what is the Framework Class Library&amp;rdquo;, &amp;ldquo;explain what managed code is&amp;rdquo;, or &amp;ldquo;what is one advantage and one disadvantage of IronPython over CPython&amp;rdquo;.  The first lesson of most modules is generally fairly light-weight - it helps those that miss the first class (more than you might think), and leaves room for addressing any problems that arise.  I tried to emphasise the strengths of both .NET and IronPython, as well as reassure them that they would be using their existing skills, rather than starting from scratch (it&amp;rsquo;s possible I made too much of this: since they don&amp;rsquo;t know how difficult students in the previous two years found the Python-&amp;gt;Visual Basic change, they may not have been expecting anything difficult).  I imagine few students were interested in the history, but IMO it&amp;rsquo;s still worth including in the lecture.  We then proceeded to tool installation and I did a few examples in the interactive console.
There were a few IronPython-specific hiccups:&lt;/p></description></item></channel></rss>