Year: 2009

Total 161 Posts

Habits Of Two Outstanding Teachers

Rhett Allain

Rhett Allain is on a tear lately. His summer thing is to apply skeptical physics to YouTube clips of highly improbable projectile motion – a rare jumping elephant, the longest waterslide ever, etc. He runs them through Tracker, his Swiss Army knife for video analysis, and subjects them to lengthy scrutiny with models and diagrams. I can only skim his posts but I have a stupid grin on my face the entire time because here’s the thing:

He has to know.

It’s impossible not to see his insatiable curiosity between the lines. Physics isn’t his day job. It’s how he understands life and resolves its questions. You can ask Rhett to stop wondering about the elephant’s parabolic fit as easily as you can ask him to stop eating.

Students pick up on that vibe. They buzz to it like bugs to a glowing lamppost. The teacher and the student listen to different music and wear different clothes and worry about different problems but curiosity unites them. That shared curiosity transcends their differences and goes a long way to define a classroom culture. It also has a funny way of assassinating the question, “how much credit is this worth?”

To whatever extent our personality traits should motivate student learning, Rhett has something to which we should all aspire.

Mike Konczal

Let me get it straight that, vocationally speaking, Mike Konczal isn’t a teacher. He is a financial engineer in San Francisco and at one point during the recession I subscribed to his blog. Some of his writing gets into quantitative models that are too far above my dusty mathematics bachelor’s degree but I never miss a post. He is an expert after David Foster Wallace’s own definition, which is the only kind of expertise that matters to me as a classroom teacher:

DFW: Think of the thrill of finding a smart, competent IT technician who can also explain what she’s doing in such a way that you feel like you understand what went wrong with your computer and how you might even fix the problem yourself if it comes up again. Or an oncologist who can communicate clearly and humanly with you and your wife about what the available treatments for her stage-two neoplasm are, and about how the different treatments actually work, and exactly what the plusses and minuses of each one are. If you’re like me, you practically drop and hug the ankles of technical specialists like this, when you find them. As of now, of course, they’re rare. What they have is a particular kind of genius that’s not really part of their specific area of expertise as such areas are usually defined and taught. There’s not really even a good univocal word for this kind of genius–which might be significant. Maybe there should be a word; maybe being able to communicate with people outside one’s area of expertise should be taught, and talked about, and considered as a requirement for genuine expertise.

Konczal wrote a post at The Atlantic called How Health Insurance Is Like Zombie Insurance that contextualized both a) rescission and b) credit default swaps – two complicated, nuanced, easily misunderstood concepts – within a hypothetical zombie apocalypse. It’s awesome, clear, expert-level writing.

Allain and Konczal approach the same masterful teaching technique from opposite angles. Allain uses the simple and the fun to motivate the complicated – waterslides and elephants inspiring pages of physical analysis. Konczal uses the simple and the fun – his zombie apocalypse – to explain the complicated. You get the sense from his writing that if zombies didn’t work for you he could dip into his sack of metaphors and pull out something from pop culture, athletics, cooking, or whatever you needed.

Both teachers are dazzling in their own ways. I would buy a ticket to their live shows, easy.

Teach Like An Elective

Jerram Froese, taking offense that anyone would walk out of a conference session after it started:

Damn. If only our students could stand up and walk out of class at any time. Wow, people.

That’s a mixed metaphor right there, but an essential hypothetical for any classroom teacher and especially for core subject teachers who are (overall enrollment notwithstanding) guaranteed an audience year after year.

OSCON 2009: Antifeatures

I picked “Antifeatures” from a crowded slate of good-looking sessions strictly because one of the speaker’s blogs, Revealing Errorsh/t Tom., which aims to teach basic computer science through images of basic computer science failing spectacularly, is awesome, and feels like a close cousin to What Can You Do With This?.

Benjamin Mako Hill didn’t waste time getting to his premise: our usual cost-benefit analysis w/r/t free and open source software is flawed. We often evaluate software on the basis of cost per feature. On that analysis, Hill’s 1990 Linux machine fared poorly, supporting 20 CD drives, none of which was stocked by the computer hardware store. Hill suggested, instead, we evaluate software and hardware not simply on which has more features but also on which has fewer antifeatures.

An antifeature, as defined by Hill, is like a feature. It requires effort and adds functionality. It’s just functionality that no consumer would ever want. It’s functionality a consumer might pay to have removed, if possible.

Bugs are not antifeatures, just mistakes. The lack of a feature is not an antifeature, it’s just a missing feature. Poor implementation is not an antifeature.

He set up four classes of anti-feature, disclaiming that they aren’t definitive and they aren’t without overlap:

1. Features that extract money from the user.

  • You had to pay to get your name unlisted from the phone book. Arguably, it required more work and more material for phone companies to include you than remove you, but your phone number was worth money to them packaged in lists for advertisers, so they passed that cost on to youI’m referring to phone books in the past tense here and I don’t really know why except I can’t remember how many years it’s been since I used one..
  • Spyware / Adware. The basic version of Kazaa (and also the video encoding software, DIVX) came bundled with spyware called Gator which reported your browsing activity, recorded parts of your credit card number, and issued pop-up advertising. Byte-for-byte, Kazaa contained ten times more spyware than useful software. Both DIVX and Kazaa charged users for professional versions of their software which were functionally the same except they didn’t include the spyware/adware.
  • Sony VAIO. A terrible laptop, pre-installed with so much junk trial software, VAIO applications, and games that some users reported crashes from the very first boot. Sony offered a “Fresh Start” program at point-of-sale which would remove all of the junk to (in their words) “conserve memory and processing power while maximizing overall system performance right from the start.” For fifty freaking dollars. Stay classy, Sony.

2. Features that segment the market.

  • Airline price points. Airlines have priced their tickets in order to determine exactly how much a given customer is willing to pay and then extract it.
  • Microsoft Windows NT Workstation / Server. Microsoft made several appearance throughout Hill’s talk. In this case, Workstation cost $200 and Server cost $800.00 but were byte-for-byte the same except that Workstation contained code that would update one bit in the registry to limit incoming TCP/IP connections to ten.
  • Six editions of Microsoft Vista. Vista Starter only allows three GUI applications open at a time. Hill wondered here (paraphrased) how the engineer tasked with writing this antifeature code lives with herself.
  • The Canon G7. The Canon G6 could shoot RAW files. The Canon G7 had better hardware and better software but could only shoot JPEG. This was to push customers toward Canon’s line of digital SLRs. Users had no trouble hacking the firmware and re-installing that functionality. In a world where there is any freedom for users, Hill noted, antifeatures are very hard to sustain.

3. Features that create or extend monopolies.

  • Panasonic Lumix. A firmware upgrade “protected” you from third-party batteries, turning off power management in order to leave users scratching their heads wondering why third-party batteries are so terrible.
  • Dr. Dos 6.0. Microsoft detected its installation and threw up all kinds of error messages, leading users to believe it was incompatible with their systems. This one went to court.
  • The battery authentication market. Hill said that this is the dystopian future: software companies waging war on each other inside your computer, a war where the user is collateral damage.

4. Features that protect copyright.

  • SimCity’s list of high scores. Printed with extremely low contrast in order to deter photocopying. This measure also made it impossible to read.
  • Dongles that prevent software copying. Hill: “How do they sleep at night? No one has ever purchased some software and said [disappointed] ‘I got the new version of the software and there wasn’t a dongle!'”. Billions of dollars are poured into making computers less good at what they’re naturally good at.
  • DVDs & DRM. “Basically every kind of antifeature.” Encryption, watermarking, region control, licensing, can’t skip the first track, etc.

He concluded that freedom has practical benefits. It may not be a methodology toward faster software, better software, that crashes less. But even when proprietary software works perfectly, exactly the way proprietary software engineers want them to, they don’t work perfectly the way the users want them to.

OSCON 2009: What Are Your Session Dealbreakers?

The 4:30PM Wednesday slot was packed at OSCON. I’m talking about three sessions I was either “eager” or “very eager” to attend at a conference where 95% of the conference titles were outright inscrutable. (eg. “Sun GlassFish (OpenSolaris) Web Stack – The Next Generation Open Web Infrastructure” – see what I mean?) One session concerned graphic design. Another risk models. The third session listed as “Antifeatures,” a title which was tough to resist in its own right.

I told myself I’d pick one and sit through the first five minutes. If, at that point, it had met certain criteria, I’d bail on it for one of the other sessions.

If you are loathe to leave a session under any circumstances, consider yourself exempt from this writing prompt. Otherwise, if you value your time and you vote with your feet, how do you judge a session by its first five minutes? Again, it’s possible the session turned into a winner exactly six minutes in. Under these constraints, though, we don’t have the luxury of patience.

I’ll post my own criteria to the comments shortly.

OSCON 2009: My Ignite Presentation

I was constrained by twenty slides at fifteen seconds apiece for a lean five minutes to talk about whateva to a crowd of open source software-types. I talked about a) teaching, b) why my first two years were miserable, c) the difference between teaching math and teaching citizenry, and d) what excites me lately.

[Click through to view embedded content.]

If any other pecha kucha survivors want to commiserate over the format, which required (for me) 400% more rehearsal and 90% less slidework than I’m accustomed to, the comments are all yours.

BTW: A couple of people have asked for a YouTube embed. I tried, but the audio stopped tracking with the video. Here, instead, is a link to a high-quality file.