<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Example on Tony Andrew Meyer</title><link>http://tonyandrewmeyer.com/tags/example/</link><description>Recent content in Example on Tony Andrew Meyer</description><generator>Hugo</generator><language>en-nz</language><lastBuildDate>Sat, 15 Aug 2009 16:54:19 +1200</lastBuildDate><atom:link href="http://tonyandrewmeyer.com/tags/example/index.xml" rel="self" type="application/rss+xml"/><item><title>D520 - Week Four</title><link>http://tonyandrewmeyer.com/2009/08/15/d520-week-four/</link><pubDate>Sat, 15 Aug 2009 16:54:19 +1200</pubDate><guid>http://tonyandrewmeyer.com/2009/08/15/d520-week-four/</guid><description>&lt;p>This week continued from &lt;a href="http://tonyandrewmeyer.wordpress.com/2009/08/09/d520-week-three/">the previous one&lt;/a>, covering Chapter 4 of &lt;a href="http://ironpythoninaction.com">IronPython in Action&lt;/a>.  That meant no new notes, and no new lab exercise.  We basically did two things: worked through the MultiDoc example in Chapter 4, and worked on implementing the Airline lab designed in the previous week.
The first recommended reading for the week was &lt;a href="http://www.joelonsoftware.com/items/2007/12/03.html">Part 1 of Joel Spolsky&amp;rsquo;s &amp;ldquo;Talk at Yale&amp;rdquo;&lt;/a>, wherein he tries to relate his study to his career - the part I hoped they would find interesting was the discussion of &amp;ldquo;geeks&amp;rdquo; versus &amp;ldquo;suits&amp;rdquo;.  The second recommended article was &lt;a href="http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html">Steve Yegge&amp;rsquo;s &amp;ldquo;Code&amp;rsquo;s Worst Enemy&amp;rdquo;&lt;/a>, which is mostly about code bloat.  In retrospect, these might not be the best pairing, since Yegge is always long, and this particular Spolsky article is very long (if you read all three parts).  However, I was again pleasantly surprised to hear that students were actually reading these.
I was right to set aside a whole &amp;rsquo;lecture&amp;rsquo; section of a week for introducing MultiDoc - I used all two hours (with breaks and a late start, actually about 90 minutes) going over the code, and didn&amp;rsquo;t quite manage to finish - I got up to the very last section, but didn&amp;rsquo;t have time to go through adding the menubar/menu items (so I did that in the break and showed the working example afterwards).&lt;/p></description></item></channel></rss>