Three things I learned at ScreencastCamp

Last week, I had the chance to attend ScreencastCamp, a weekend event put on by Techsmith, Inc. just down M-6 in Okemos, Michigan. What a great experience! Techsmith develops Camtasia, my go-to software for all screencasting needs, as well as several other great products like Jing and SnagIt. I’ve been a fan of their products for a long time, and it was great to spend time getting to know the people behind them.

ScreencastCamp was an unconference, where there is no set agenda beforehand. Participants just come with an idea of what they want to learn, and then either put on a session or request one. There were about 40 of us participating, mostly from education but with a healthy contingent from the corporate (training) world as well. Amazingly, although this is a relatively small number of participants, all the session slots for Saturday and Sunday filled up almost immediately as people pencilled themselves in to give sessions. It was busy. Some of the sessions were like regular conference talks, while others ended up as discussions among four or five like-minded people sitting around on the sofas in a back area of Techsmith headquarters. The hosts were generous, the food (and the beer!) amazing, and the atmosphere of enthusiasm infectious.

I came away with a lot of great ideas about screencasting, but here are the three that stood out the most.

1. Write careful and complete scripts for your screencasts. Back in my series of “How I Do Screencasting” posts, I wrote that a rough script was the way to go. Now I’m a believer in complete, careful, tightly-written and -edited scripts. What’s so great about a complete script? First of all, I have a tendency to talk fast and speed up as I get going in a screencast. Scripting out what I’m going to say not only helps me to edit my thoughts down to just the essential ideas, it also provides a way to talk at a normal, relaxed pace. Second, having a script printed out in front of me will make it easier to caption my videos, which is something that I want to start doing and indeed may eventually have to do. If I have a script, I can copy and paste the text of my screencast into Camtasia for the captions. It’s a little more complicated than that sounds, but at least I wouldn’t have to transcribe the audio.

Techsmith gave us a copy of the template (MS Word, 66 Kb with a bunch of my own stuff on it) they use for their own screencast scripts. I’ve used this simple form for a series of Maple 15 screencasts I’m working on right now, and it’s really made things go a lot more smoothly than when I was reading from a text file, or making it up as I go.

2. Record your audio first, then your video. This was the most radical idea I heard. I had always recorded the audio and the video simultaneously using Camtasia, but that’s not how Techsmith themselves do it. After writing the script, Techsmith screencasters will read the script and record the audio using Audacity. Then the audio file gets exported into Camtasia as an audio track, and the video part is recorded on top of the audio separately. At first I was very skeptical of this (wouldn’t it be a lot more work?) but after trying it myself, I’m a convert. Recording the audio separately reduces cognitive load — you don’t have to worry about getting both the audio and the video right at the same time — and so both pieces turn out better. Audio is much easier to edit when it’s not attached at the hip to video, I think. And you can focus on the quality of the audio as well. As one Techsmith employee put it, viewers will put up with crappy video as long as the audio is good, but not vice versa.

The way I’ve made this work for me is with the following workflow. First, write a good script using the Techsmith template. Then, read the script into Audacity, putting plenty of “white space” in between each box in the template — this gives viewers a little breathing room while they are watching. Next, go back and edit out any mistakes in the audio, either in Audacity or in Camtasia after the audio has been exported. Then, to record the video, turn off all audio inputs (because you’ve already done the audio), start recording the screen, then start the playback of the audio track and just click along with whatever it is you’re saying from the script. After all, this is what your viewers are going to have to do. Once you’re finished, it’s relatively simple to sync up the audio and video (especially if you keep the whole thing short) by just moving the tracks up and down the Camtasia timeline until it looks like they work. Then trim off the beginning and end of the video to make the video and audio the same length.

3. Get a real microphone. I’ve mentioned before that I’m too cheap to buy a USB microphone when the built-in mic on my Macbook works passably well. But after trying some of the higher-end equipment at Techsmith and hearing what it sounds like on playback, I think I might have to be, well, less cheap. When I recorded my practice screencast in the Techsmith studio, the mic captured the full range of my voice without sounding like I was at the bottom of a well, and no other sound made it into the audio. Part of that is because I was in a studio, as opposed to my office, but part of it is the microphone. It really does make a difference.

I also picked up a ton of little tricks and tips from participants — for example, buy a dog clicker to use when you make a mistake on the audio; the spike it makes in the audio waveform is really clear and it makes it easy to find where you need to edit.

ScreencastCamp was a great experience — amazingly, it was totally free too — and I learned a great deal about how to be a better screencaster. Thanks Techsmith!

Advertisement

How I make screencasts: The whiteboard screencast

In this post, the fifth in a series of posts on how I make screencasts, I’m going to focus on what I call the “whiteboard” screencast. This is a screencast where I am demoing some sort of concept or calculation by writing things down, rather than clicking through a Keynote presentation or typing something on the screen. It’s intended to mimic the live presentation of content on a whiteboard, hence my name for it.

Of course the most well-known examples of “whiteboard” screencasts are the videos at Khan Academy. In the unlikely event you haven’t seen a Khan Academy video before, here’s one:

I do whiteboard screencasts fairly often. I use them sometimes for presenting hand calculations for students to watch and work through before class, and sometimes (probably more frequently) I use them to create additional examples for things I’ve covered in class. This is a really powerful use of screencasts — students often want more examples than there is time for in a class meeting, and whiteboard screencasts give me a way to give students as many examples as they can dream up.

The basic principles of whiteboard screencasts are the same as for other screencasts. You first have to engage in basic planning, which involves defining a tight and coherent scope for your screencast and writing out a script. For whiteboard screencasting, which is more free-form than lecture capture using Keynote or PowerPoint, the scripting process has to be a little more rigorous. Because it’s easy for me to get carried away when talking about something that matters to me, I find it very helpful to work out in advance everything that I am going to do in the screencast, in the order and position on the screen that I intend to do it. I don’t always read words from a script, but in order to make the screencast logical and coherent, I do storyboard what I am going to do and practice with the drawings, erasures, and such. Very little of what I do in a whiteboard screencast is ad-libbed. (If I were better at ad-libbing, that might be different.)

So I will start a whiteboard screencast with something like a mind-map of the topic or topics I intend to address and one, maybe two, examples of that topic. Additional topics go into additional screencasts. I work those examples all the way through to ensure that there are no math or other mistakes and that I don’t get stuck in one of my own calculations. If you think about it, this is just the same kind of planning that goes into a successful whiteboard lecture, so this process is not entirely alien to instructors.

Once the screencast is properly planned, it’s time to put it together. This is where it gets technically somewhat complicated. But a lot of people ask me about the tools I use to make whiteboard screencasts, so hopefully this will be worth it. I use four main tools for doing whiteboard screencasts:

• Keynote; I’ll explain in a minute.
• Camtasia, which we saw in the last post in this series.
• FlySketch, a software app from Flying Meat (they also make the popular personal wiki software VoodooPad). FlySketch puts a transparent overlay on top of any existing objects on your computer screen and allows you to draw freehand, draw geometric shapes, or type text on the overlay. See the link for screenshots and a more detailed description.
• A Wacom pen tablet. I currently a Wacom Graphire tablet purchased with a grant a few years ago. With my upcoming job change, I have to hand that in when I leave, so I plan on picking up a Bamboo Pen & Touch this fall.

With those tools, here is the workflow I follow for making a whiteboard screencast.

First, open up Keynote and make a single, blank white slide. This is going to be the “whiteboard” itself. Of course you could also use a blank MS Word document, or any other blank white window or screen. Keynote is just for convenience’s sake.

Next, open up FlySketch and lay it completely over the blank window so that the controls are showing above the top of the window:

Then, open Camtasia and create a custom region that encompasses the “whiteboard”. When the video rolls, it will record what is happening on the whiteboard:

And finally — start the video, and start writing on the FlySketch overlay using the Wacom tablet. Before you start recording, make sure to select the pen color and size you want. If you need to change color, size, or pen type during the screencast — say, you want to switch from freehand writing to typing, or drawing a straight line for an axis — you can tap on the appropriate FlySketch control and Camtasia won’t record it because it’s off-screen.

Then you simply record what you need, then stop, and process the video as was described in the previous post in this series. This includes editing out any mistakes and splicing together multiple video clips for the same screencast.

Here’s an example of the finished product:

Although Sal Khan has been my inspiration for doing screencasts, I’ve made some conscious decisions here to do things differently than Khan does. First, I prefer the white background to the black; it’s more familiar to learners and seems cleaner. I also tend to use thicker pen “tips” than Khan does; I tend to think his pens look a little spidery. Also, the Wacom tablet pen is pressure-sensitive, and that feature works better if the pen tip is thicker. Finally, from a planning perspective, my whiteboard screencasts are a lot less conversational than Khan’s videos. Khan tends to shoot from the hip in terms of presentation; this is part of what makes his videos so charming, but I think it also tends to make his videos go longer than they need to. I prefer to make things a bit more efficient and focused and take less time. It also cuts down on mistakes.

I think the hardest part of this process, for me, was mastering the art of writing on the Wacom tablet in one place and having the writing appear on the screen. This is harder than it sounds! At first my handwriting was horrible (I think at the time I likened it to somebody with a brain injury) but eventually I got my act together. I suspect people learning to play the drums or the piano have to go through the same process before it sounds any good.

Another challenge is managing the relatively small amount of physical space you are working with. A Keynote slide is just not a very large place, and it’s easy to run out of room when writing. If this happens, it can be dealt with by just starting another slide and creating a new video clip. But it’s better for the learner to see one example per slide if possible, and making sure this happens is part of that all-important planning process. I find it helpful to practice the presentation not on the screen or a piece of paper but on a 3 x 5 inch notecard, which has something much closer the same proportions for writing as the Keynote slide on the screen. But note that it does take practice — if you just sit down and try to bang out a whiteboard screencast, it’s likely not to be as good or as instructional as possible, and it could end up taking more time in terms of edits and re-takes than it would if you just planned and practiced in the first place.

I’d be interested in hearing any alternative approaches for making these kinds of screencasts. I once wrote Sal Khan and asked him what his tools were, but never got a response, so I just reverse-engineered what he was doing. There may be a better way. Let me know!

Next up will be the final installment in this series, touching on what I called a “demo” screencast. It’s probably what I do the most. Stay tuned!

How I make screencasts: Lecture capture, part 2

Now that school’s out, I’m going to pick up where I left off (two months ago!) in my series on how I make screencasts. So far I’ve made three posts in this series. In the first post we talked about what a screencast is, exactly, and why anybody would want to make one. In the second post, we saw how the elements of careful planning make screencasting a successful experience. And in the most recent post, we took a look at using Keynote (or PowerPoint) to create a lecture-capture screencast.

Before I talk about the other kinds of screencasts I make, I’m going to take this post to describe how I use my go-to tool for screencasting: Camtasia for Mac, specifically how I use it to make lecture capture videos when I’m not using Keynote. (Full disclosure: I was on the beta-testing team for Camtasia for Mac and got a free license for the software for my efforts. But I can definitely say that I’d gladly have paid the $99 for the software otherwise — it’s that useful.) There is a Windows version of Camtasia and a server-oriented variant called Camtasia Relay, and they are all very similar, so what I describe in this post can be used if lots of different situations.

Let’s suppose I have a lecture or presentation that I want to turn into a screencast, which basically means I need to record the presentation as it happens on the screen and add a voice-over. I’ve already described how to do this with Keynote or PowerPoint, but what if you’re using Prezi, Beamer, or some other presentation tool? What I need is a tool that will record stuff happening on the screen that’s separate from the presentation tool itself. That’s where Camtasia comes in.

Camtasia is software that records video of anything happening on your screen — all of it, or part of it — along with any audio you choose to add, including voiceovers. You can record multiple segments of video, edit those segments, and put it all together with transitions and effects. The interface is laid out a lot like iMovie, so Mac users will feel right at home using it.

There are a lot — seriously, a lot — of options for working with video in Camtasia, too many to get into here. I’ll just show an example of a simple lecture capture putting Prezi and Camtasia together.

First, bring up the screen that has the Prezi in it. (For Prezis particularly, creating the lecture capture works best if you download the Prezi to your local drive and then run it in a window, rather than trying to run it on the web.)

Now launch Camtasia. When you do, a little floating pane will come up that looks like this:

The dropdown menu on the left lets you specify which part of the screen you’re going to capture. I usually just select “YouTube HD/720p”, which records essentially the entire screen. I can crop out what I don’t need later. And once I put it on YouTube (which is my usual destination for screencasts) it’ll be in glorious 720p HD.

Once you’ve selected your area, just click the Record button and start presenting, just as you would if you were giving the lecture in front of a live audience. Your lecture is being recorded behind the scenes and all you see is your screen. Warning: Presenting for a screencast feels a lot different than doing it for a live audience because, well, the audience isn’t there. There’s no body language or ambience to add to the presentation. So this will feel a little unusual at first. Also, I can’t stress enough that you should probably go from a prepared script the first few times you do this, rather than try to wing it. It’ll keep you on track and prevent lots of mistakes.

When you stop recording, you’re brought into the main editing area of Camtasia:

The bottom part of this screen is called the “timeline”. Right now, the one clip that I have in the timeline is a partial video of the presentation. It appears as a chunk of the timeline outlined in blue. Inside the timeline you can see the audio levels given as waveforms, and there’s a playhead along the top of the timeline showing you where you are in the video as well as the time.

At this point, what I usually do is check the sound levels first. A lot of times the built-in microphone on my Macbook doesn’t record very loudly. I’ll listen to a bit of the recorded video to check if that is the case. If so, I go and apply the Dynamics Processor effect to the clip I made:

You apply the clip just by dragging it from the effects area directly onto the clip in the timeline. In fact this is how all the effects, transitions, and other features of Camtasia are applied to video. The Dynamics Processor brings all audio levels up to a uniformly audible setting.

If I have the time, I will watch the whole video from start to finish to see if I’m happy with it. If there’s something I need to edit out — I goofed the script, or sneezed, or the phone rang, etc. — I can go back and edit that part out just by putting the playhead just before the mistake:

Then selecting “Split selected at playhead” from the Edit menu; this splits the video clip in two, right where the blooper is. Then move the playhead until just after the mistake, and selecting “Trim Start to Playhead”. This will crop out the blooper from the second clip. Then you can just drag the second clip over next to the first one, and with that, the blooper is edited out.

The ability to edit in such an easy way really changed screencasting for me. You will make mistakes when you screencast, no matter how good or experienced you get. But you don’t want to have to throw away an entire screencast because of one goof. If I am screencasting and I make a mistake, I just pause for a moment, and then I start again from the point of error. The pause will show up on the audio as a flat spot, and I can go back and edit the error out. You cannot do this with the voiceover features of Keynote and PowerPoint, and it makes a huge difference.

If this is just a straight lecture capture — so there’s no other video coming in from a different source — at this point I’m done. The only thing left to do is add the “credits page” that I always put at the end of my screencasts that lists my email, YouTube channel, Twitter, and so on. I have this saved as a PDF. To bring it into the timeline, I go to Import Media:

and select it from the file finder. It then appears as a clip:

I just drag it into the timeline at the end of the video:

And then, for effect, add a fade-in transition from the video to the credits, which I do by finding it in the transitions menu:

And dragging and dropping it in the little seam between the video clip and the credits page:

Now I’m ready to publish. Camtasia allows me to publish the resulting video directly to my YouTube channel using the Share menu:

As you can see, there are options for iTunes and Screencast.com as well. Or you can just choose “Export…” which exports the video to a file format of your choice, for uploading wherever you want.

After I start the process, Camtasia converts the video to Quicktime and then uploads it with the title I gave it. A 10-minute video will take several minutes to complete this process on a Macbook Pro. Your mileage will vary according to your system hardware and your internet connection. After it’s done uploading, I still have to go to YouTube and add metadata. But otherwise that’s it!

What’s nice about Camtasia is that the tool is separate from the presentation tool you’re using. So if you already have the presentation content made up, you can turn it into a screencast quite easily. It doesn’t matter whether it’s Prezi, Beamer, a text document you’re scrolling down, or anything else. And the more you do this, the easier it gets to convert existing presentation content into a mobile device-friendly screencast.

In the next post, I’ll talk about what I call “whiteboard” screencasts, where I record stuff that I am writing on the screen. This is a lot like what Salman Khan at Khan Academy does. Hopefully it won’t be another two months before I get to that.

Three things I wish Google Documents would let me do

Let me preface this article by saying that I really like Google Documents. It’s a fantastic set of tools that extends basic office functionality to the web in really compelling ways. I’ve been incorporating Google Docs pretty centrally in my courses for the last few years — for example, I no longer hand out paper syllabi on the first day of classes but instead write the syllabi on GDocs and distribute the links; and I’ve given final exams on Google Docs with links to data that are housed in Google Spreadsheets. I love being able to create a document on the web and just leave it there for students (or whoever) to come see, collaborate, and comment — without having to keep track of paper and with virtually zero chance of losing my data. (If Google crashes, we have much bigger problems than the loss of a set of quiz data.)

But like anything, Google Documents isn’t perfect — and in particular, there are at least three things that I wish Google Documents would do that would push my really like-ness to unqualified love:

1. Bring back the old Equation Editor. A couple of years ago, Google rolled out an equation editor for Google Docs that was just beautiful — a small editor that had point-and-click features for adding equations and the ability to parse commands. In other words, it was a mini- editor built right into Google Docs that would implement almost any of the essential functionality of , including matrices, multi-line equations, and more. I remember discovering this editor two years ago and promptly writing up every single one of my linear algebra activities as Google Documents. Then, inexplicably, Google replaced this sweet goodness with a stripped-down equation editor that pales in comparison, supporting only a tiny fraction of ‘s command set, and in particular no matrices or multi-line equations. And the “new” editor is clunky and doesn’t seem to produce very good results. I have yet to hear a satisfactory explanation of why this change to a clearly-inferior editor was made. It can’t be because it was overtaxing Google’s system! This is Google, for goodness’ sake, and it’s 2011 — can’t we have a real editor for Google Docs? There’s already one for GMail, you know.

2. Allow comments and discussion threads on PDF’s uploaded to Google Documents. From a teacher’s perspective, one of the most compelling possibilities for Google Docs is to have students upload their class work on Google Docs and then initiate a running discussion thread on that work. Such a thing would replace the usual system of handing in work and having the teacher write comments on it, thereby turning the grading process into something more like a conversation. You can do this with documents created in Google Docs. But if you want students to create mathematical work — since, as I just noted, the current equation editor for GDocs doesn’t get the job done — students would have to create their work in MS Word or , convert to a PDF, and then upload it. No problem, except that discussion threads and comments aren’t allowed on uploaded documents. The option simply isn’t there in the menu system. Google acknowledges that comments and comment threads are only available on newly-created documents, and functionality is coming for older documents — but no word on uploaded documents. If this could be made to happen, grading student work suddenly gets a whole lot more interesting (and valuable for students).

3. Auto-shorten URL’s of links to documents. OK, this is pretty minor, because all I have to do is copy the URL given to me by Google and run it through bit.ly. But since Google already has its own URL shortener, why not just auto-compress the URL using that shortener at the moment the URL is generated? It saves a few clicks and makes users happier because we don’t have to deal with URL’s that are multiple dozens of characters long. And more practically, it makes Google Docs easier for novices to use — many new users (I’m envisioning a good portion of students in my classes who I’d like to get to use Google Docs) have no idea that URL shorteners exist.

What else would you add to this list? Better yet, are there hacks or workarounds that resolve these issues? (Or, thirdly, am I just mistaken on any of this?)

Technology making a distinction but not a difference?

This article is the second one that I’ve done for Education Debate at Online Schools. It first appeared there on Tuesday this week, and now that it’s fermented a little I’m crossposting it here.

The University of South Florida‘s mathematics department has begun a pilot project to redesign its lower-level mathematics courses, like College Algebra, around a large-scale infusion of technology. This “new way of teaching college math” (to use the article’s language) involves clickers, lecture capture, software-based practice tools, and online homework systems. It’s an ambitious attempt to “teach [students] how to teach themselves”, in the words of professor and project participant Fran Hopf.

It’s a pilot project, so it remains to be seen if this approach makes a difference in improving the pass rates for students in lower-level math courses like College Algebra, which have been at around 60 percent. It’s a good idea. But there’s something unsettling about the description of the algebra class from the article:

Hopf stands in front of an auditorium full of students. Several straggle in 10 to 15 minutes late.

She asks a question involving an equation with x’s, h’s and k’s.

Silence. A few murmurs. After a while, a small voice answers from the back.

“What was that?” Hopf asks. “I think I heard the answer.”

Every now and then, Hopf asks the students to answer with their “clickers,” devices they can use to log responses to multiple-choice questions. A bar graph projected onto a screen at the front of the room shows most students are keeping up, though not all.

[…]

As Hopf walks up and down the aisles, she jots equations on a hand-held digital pad that projects whatever she writes on the screen. It allows her to keep an eye on students and talk to them face-to-face throughout the lesson.

Students start drifting out of the 75-minute class about 15 minutes before it ends. But afterward, Hopf is exuberant that a few students were bold enough to raise their hands and call out answers.

To be fair: This is a very tough audience, and the profs involved have their work cut out for them. The USF faculty are trying with the best of intentions to teach students something that almost assuredly none of them really want to learn, and this is exceedingly hard and often unrewarding work. I used to teach remedial algebra (well short of “college algebra”) at a two-year institution, and I know what this is like. I also know that the technology being employed here can, if used properly, make a real difference.

But if there’s one main criticism to make here, it’s that underneath the technology, what I’m seeing — at least in the snapshot in the article — is a class that is really not that different than that of ten or twenty years ago. Sure, there’s technology present, but all it seems to be doing is supporting the kinds of pedagogy that were already being employed before the technology, and yielded 60% pass rates. The professor is using handheld sketching devices — to write on the board, in a 250-student, 75-minute long lecture. The professor is using clickers to get student responses — but also still casting questions out to the crowd and receiving the de rigeur painful silence following the questions, and the clickers are not being used in support of learner-centered pedagogies like peer instruction. The students have the lectures on video — but they also still have to attend the lectures, and class time is still significantly instructor-centered. (Although apparently there’s no penalty for arriving 15 minutes late and leaving 15 minutes early. That behavior in particular should tell USF something about what really needs to change here.)

What USF seems not to have fully apprehended is that something about their remedial math system is fundamentally broken, and technology is neither the culprit nor the panacea. Moving from an instructor-centered model of learning without technology to an instructor-centered model of learning with technology is not going to solve this problem. USF should instead be using this technology to create disruptive change in how it delivers these courses by refocusing to a student-centered model of learning. There are baby steps here — the inclusion of self-paced lab activities is promising — but having 75-minute lectures (on college algebra, no less) with 225 students signals a reluctance to change that USF’s students cannot afford to keep.

Technology FAIL day

This morning as I was driving in to work, I got to thinking: Could I teach my courses without all the technology I use? As in, just me, my students, and a chalk/whiteboard with chalk/markers? As I pulled in to the college, I thought: Sure I could. It just wouldn’t be as good or fun without the tech.

Little did I know, today would be centered around living that theory out:

• I planned a Keynote presentation with clicker questions to teach the section on antiderivatives in Calculus. As soon as I tried to get the clickers going, I realized the little USB receiver wasn’t working. Turns out, updating Mac OS X to v10.6.5 breaks the software that runs the receiver. Clicker questions for this morning: Out the window. Hopefully I’ll find a useable laptop for tomorrow, when I’m using even more clicker questions.
• Also in calculus, the laptop inexplicably went into presenter mode when I tried to give the presentation without clicker questions. Most of the time when I try to get it into presenter mode, I can’t do it. This time I couldn’t make it stop.
• The Twitter client on my laptop got stuck in some kind of strange mode such that clicking on anything made it go to Expose.
• I lost the network connection to our department printer halfway through the day.
• GMail went down.

Fortunately everything I had planned could be done without any technology aside from the whiteboard. But when the technology doesn’t work, I have to improvise, and sometimes that works well and sometimes not. In calculus, I just had to revert back to what is often called the “interactive lecture”, which means just a regular lecture where you hope the students ask questions, and it was about as engaging as that sounds.

I do believe I can teach without all this technology, but the kind of teaching I do with the technology is, I think, more inherently engaging and meaningful for students. I ask better questions, interact more freely with students, and highlight the coherence and the big ideas of the material more adeptly with the technology in place. So when the tech fails on me, things seem odd and out of place and contrived. Students pick up on that. Maybe I’m simply addicted to the tech, but I don’t like teaching without it, and my classes aren’t nearly at the same level without it.

Partying like it’s 1995

Yesterday at the ASEE conference, I attended mostly sessions run by the Liberal Education Division. Today I gravitated toward the Mathematics Division, which is sort of an MAA-within-the-ASEE. In fact, I recognized several faces from past MAA meetings. I would like to say that the outcome of attending these talks has been all positive. Unfortunately it’s not. I should probably explain.

The general impression from the talks I attended is that the discussions, arguments, and crises that the engineering math community is dealing with are exactly the ones that the college mathematics community in general, and the MAA in particular, were having — in 1995. Back then, mathematics instructors were asking questions such as:

• Now that there’s relatively inexpensive technology that will do things like plot graphs and take derivatives, what are we supposed to teach now?
• Won’t all that technology make our students dumb?
• Won’t the calculus reform movement dumb down our curricula with all this nonsense about graphs and multiple representations and so on?
• How can you seriously call a person a mathematician/engineer if they can’t [insert calculation here] by hand? What if they are in a situation where they don’t have access to technology?

And yet, I actually heard all of these questions almost verbatim from mathematics and engineering professors this morning, multiple times. (To the great credit of the speaker who was asked the last question, he replied: If an engineer is ever in a situation where he is without access even to a calculator, we have a lot bigger problems on our hands than just bad education. TRUTH.)  I was having serious third-year-of-grad-school flashbacks.

These questions aren’t bad; they’re moot. In 1995, mathematical technology was just at the level of expense, accessibility, and functionality that these questions needed to be dealt with. Students could conceivably purchase calculators for a couple hundred dollars that were small enough to slip into a backpack and could calculate symbolically. Should we ban the technology, embrace it, regulate it, or what? Should we change what and how we teach? The technology could be controlled, so the question was whether we should, and to what extent, and these were important questions at the time.

But that was 1995. What the TI-92 could do in 1995 can now be done in 2010 using Wolfram|Alpha at no expense, using any device with an internet connection, and with functionality that is already vast and expands every other week. (This says nothing about W|A’s use of natural language input.) The technology is all around us; students are using it; there is no argument against expense, accessibility, or functionality that can reasonably be made. It’s going to affect what our students do and how they accept what we present to them regardless of what we think about it.  So I’d suggest that questions such as What do students need to know how to do in an engineering calculus course? and How do we ensure they can do those things? are better questions for now (and might even have been better then).

Some of the conceptions of innovative teaching and learning strategies I saw also seemed stuck in 1995. I won’t name names or give specific descriptions in order not to offend people who probably simply don’t know the full scope of what’s gone on in mathematics education in the last 15 years. (Although I must call out the one talk that highlighted the use of MS Excel, and claimed that there were no other tools available for hands-on work in mathematics. Augh! You should know better than that!)

I will simply say that people who concern themselves with the mathematical preparation of engineers simply must look around them and get up to speed with what is happening in technology, in the cultures and lives of our students, and in what we know now about student learning that we didn’t know then. Read some seminal MAA articles about active learning. Talk to other people. Read some blogs. Something! We can’t stay stuck in time forever.

MATLAB as a handout creator

One of the fringe benefits of having immersed myself in MATLAB for the last year (in preparation for teaching the Computer Tools for Problem Solving course) is that I’ve learned that MATLAB is an excellent all-purpose tool for preparing materials for my math classes. Here’s an example of something I just finished for a class tomorrow that I’m really pleased with.

I was needing to create a sequence of scatterplots of data for a handout in my Functions and Models class. The data are supposed to have varying degrees of linearity — some perfect/almost perfectly linear, some less so, some totally nonlinear — and having different directions, and the students are supposed to look at the data and rank the correlation coefficients in order of smallest to largest. (This is a standard activity in a statistics class as well.)

I could have just made up data with the right shape on Excel or hand-drawn the scatter plots, but whenever I do that, it looks made it up — not with the randomness that a real set of data, even if it’s strongly linear, would have. So instead, I thought I would take a basic linear function and throw varying degrees of noise into it to make it less linear.

I wrote this little function to generate noise:

function n = noise(degree, size)
n = degree*cos(2*pi*rand(1,size));

This just creates a vector of specified length (“size”) centered roughly around 0, and the bigger “degree” is the more wildly the numbers vary. (I’m sure there’s some built-in way to do this in MATLAB, but it probably took less time to write the function than it would have taken for me, the MATLAB neophyte, to look it up.)

Then I just made four linear functions and literally added in the noise for each, as well as a fifth function that was just spitting out 25 random numbers and a sixth that was a pure linear function with no noise. Then plot all of those in a 2×3 subplot. Here’s the code:

x = 1:25;
y_bigneg = -3*x+90 + noise(5,25);
y_smallneg = -5*x + 100 + noise(30,25);
y_bigpos = 3*x + 3 + noise(3,25);
y_smallpos = 3*x + 3 + noise(10,25);
subplot(2,3,1), scatter(x, y_bigpos)
subplot(2,3,2), scatter(x, y_smallneg)
subplot(2,3,3), scatter(x, y_smallpos)
subplot(2,3,4), scatter(x, y_bigneg)
subplot(2,3,5), scatter(x, rand(1,25))
subplot(2,3,6), scatter(x, 90-4*x)

Here’s the result, after going in and adding titles and removing the legends in the Plot Tools window:

That can then be saved as a PDF and embedded into a document or just posted directly to Moodle for students to play with. All of that code above could easily be compacted into one big M-file with some modifications to let the user control the number of points and whatever else.

This is basic stuff, but it’s awfully handy for creating professional-looking documents and graphics for teaching mathematics. That’s an area where I’m finding MATLAB is highly underrated.

Is the iPad really what students need?

Dave Caolo believes that students are one of the four groups of people who will make the iPad huge, because:

Students are on a fixed budget, and e-books are typically cheaper than their paper-based counterparts. Also, consider all of the money publishers lose when students buy used books from the campus bookstores. Additionally, Apple can distribute textbooks through iTunes U — an established and proven system that students, faculty and staff already know how to use.

Suddenly the iPad is a device that follows a student from his/her freshman year of high school all the way through graduate school. Why buy a laptop when every student has a device that can be a textbook, reference tool, Internet appliance and whatever else the imaginations of developers can dream up?

I do believe that the iPad’s success will be closely tied to its success in the EDU sector, but Caolo’s analysis misses some important points about students and their educational computing needs.

1. The argument about used books explains precisely why students, and conscientious faculty, will resist textbooks on an iPad. Already textbook companies charge full (and overly high) price for products that are speciously “revised” every couple of years, even though the revisions are virtually identical to the prior versions. If using the iPad as a sort of universal textbook locks students in to using only the most recent version at the highest possible price, then how is this a step forward? Students would be better off purchasing used versions of textbooks.  (One way to ameliorate this problem is for textbook companies to take my advice and give away previous versions of their textbooks whenever a new revision comes out.)
2. Students need more from their computers than just email clients, ebook readers, and web access. They need to be able to run spreadsheets and word processors simultaneously. They need to be able to run sophisticated scientific computing software. They need to be able to install and run legacy software that their universities may have purchased — or even developed in-house — decades ago. (For example, in our math courses alone at my college, we use Minitab, Winplot, and even Derive. The chances of these being ported to the iPad are basically zero.) They need to be able to do video chats with Skype. These are just a few of the things that the iPad cannot do right now.
3. The above argument assumes that textbooks are the center of a student’s education. I would argue that the best thing about an iPad in education is that it provides a great platform for getting away from textbooks as the center and focusing on existing, web-based information sources instead. Why invent a whole new class of technology only to have it perpetuate a rapidly-outmoded means of instruction?

I think the iPad is a neat-looking device, and it does have the capacity to change the entire landscape of computing from a user interface point of view. The next time I’m up for an upgrade to my work machine (in 2014, sadly) I fully expect to be getting an Apple device that has all the guts and power of my new Macbook Pro but with a sleek form factor and intuitive touch interface like the iPad (apparently) has. This kind of device is probably what students need. The first-generation iPad, not so much, not right now at least. Although I am sure students will buy it.

Spreadsheets vs. online gradebooks

One of the things my students like the most about learning managment systems (LMS’s) such as Blackboard, Angel, or Moodle (I’ve used all of these at some point in my career) is the online gradebook feature. I enter their grades online, and students can check in on the web at any time and see their grades and get the info. These things are useful to be sure. But I’ve been wondering if they are the best implement for managing grades. I’ve been wondering if it wouldn’t be better to simply hand back graded work and then have students keep their grades on their own using a simple spreadsheet. Some reasons why I think this way:

1. Spreadsheets have functionality. I can enter, view, and edit grades in an online gradebook; students can view them; but nobody can perform any meaningful analysis on the data that have been entered. The gradebook is just a two-dimensional list. But of course in a spreadsheet I can not only store and view data but also manipulate it any way I want and play the many what-if scenarios that profs and students alike play. Of course this is not a big deal because most LMS’s allow you to download gradebook data in some kind of spreadsheet-compatible form, but why not just start with a spreadsheet to begin with?
2. Spreadsheets allow greater choice of implementation of other LMS features. Online gradebooks are often the only redeeming feature of LMS’s, and profs tend to stick with LMS’s they don’t like just to have the gradebook. This often hurts the students, who have to put up with substandard email clients (see this post for more) and file-sharing systems that LMS’s provide rather than use something easier and better-implemented. Or else, profs end up using only the gradebook feature of an LMS and use other software (class blogs, wikis, Netvibes, etc.) for the remainder of what an LMS does (such as posting files and announcements), which can get confusing for students, who then expect the prof to use the features of the LMS.
3. Having students keep track of their grades with a spreadsheet encourages them to learn about spreadsheets. If you take the approach of expecting students to manage their own grades, and teach them how to use spreadsheets to do this, my experience is that students will be motivated to learn the basics of spreadsheets simply because they care about their grades and because they can now answer on their own all those questions such as “What do I need on the final to get a B- in the class?” One can learn a lot about spreadsheets just by using it as a personal gradebook for one class in one semester. And since spreadsheets are an increasingly important tool for data management in general both in and after school, the more students can learn about them, and the earlier they can do so, the better for them.
4. Using spreadsheets encourages students to take responsibility for their learning. One of the detriments of online gradebooks is that it removes an important responsibility of learning — managing the outcomes of your assessments — from the student and makes it the instructor’s job. I don’t mind the work of entering grades into a gradebook, but I do think it would be better for students to learn that responsible record-keeping is important and that they should practice it, and I like the idea of students  being closer to their grade data than they are with instructor-managed online gradebooks.

I don’t know if I’m quite ready to completely give up using an online gradebook for these reasons, but I find them to be pretty compelling. What do you think?