Plane parts: The Wingo, partially assembled. The foam plane has a wingspan of 43.25 inches and weighs 20 ounces. Credit: Simson Garfinkel

Jef Raskin is largely remembered as the father of the Macintosh. He started at Apple in January 1978 writing documentation for the Apple II, after a brief stint teaching computer science at the University of California, San Diego. In 1979 Raskin hired his former student Bill Atkinson to work on what was to become the Macintosh Project. But then Raskin left Apple in 1982--many people say he was thrown out--and started a new company that created another breakthrough computer called the Canon Cat. These days practically nobody remembers the Canon Cat, tens of millions of people use Macs, and Steve Jobs is typically given most of the credit. But inside Raskin's home office was the millionth Macintosh to come off Apple's production line. The Macintosh team had given it to Raskin in recognition that it was his creative vision that had brought the Mac into existence.

I met Raskin in the 1990s at a party that Wired magazine threw to celebrate moving into its new offices. Like me, Raskin wrote for the magazine from time to time. We started talking about computers, and about Apple's then-recent decision to purchase NeXT Computer. Raskin thought that putting Unix underneath the Mac was precisely the wrong thing to do, if your professed goal was creating a computer that is easy to use. Alas, he acknowledged that Apple probably didn't have much of an alternative at that point. I said that I had been one of the coeditors of The Unix Hater's Handbook a few years before and, as a result, agreed whole-heartedly.

It turned out that Raskin was a designer of all kinds of things, not just computers and software. He especially loved building and flying radio-controlled aircraft, which he did at his house in Pacifica. He invited me over; I ended up visiting his house a bunch of times over the following years. It was a large two-level house built into the side of a hill, with the kitchen, living room, and other formal rooms upstairs and the bedrooms down below. The hallways were lined with bookshelves. Go down the stairs and into one of the rooms and there was a hidden door in the wall that led to Raskin's office. Although there were a few computers and laptops, the most prominent objects in the office were the aircraft. As I looked at them, I realized that something seemed odd: none of them had any propellers. They were all gliders.

I learned to fly in high school but stopped after a near-death experience between my second and third years of college. Once you learn to fly, though, it's something you never forget. Raskin told me that flying an RC aircraft was harder than flying in the cockpit. I wanted to find out.

Sometime in the spring of 2002 Raskin took me out to a park that was a mile or so from his house. It was typical California: a road, a few parking spaces, and a cliff. He took a glider out of his trunk, took out the RC controller, and then threw the glider in the air. We spent the next two hours talking while he piloted the craft. It was too sensitive, he told me, for a first-time flyer. He told me that I should buy my own craft and crash it a few times before I tried my hand at one of his. The ideal beginner's plane was the Wingo from Hobby Lobby, he said. I told him I would buy one, build it, and come back when I knew how to fly one of those little planes.

Of course, there are a lot of steps between buying a kit plane and flying an aircraft. When the Wingo showed up in its box, I was hard at work on another project, so the Wingo went into the basement. Then I started graduate school. Then I started working on my thesis. I was at a conference in Dominic when I heard on the radio that Raskin had died of cancer--I hadn't even known that he was sick. Apparently the onset had been sudden, and the cancer had been very aggressive.

After I heard about Raskin's death in 2005, the Wingo box in the basement started haunting me--but in a good kind of way. Every time I saw it I felt guilty that I was spending so much time working hard, not spending as much time with my children. Raskin had doted on his children. They all played musical instruments together. He taught his oldest son enough about aeronautics that his son designed a new wing. I wanted to learn to fly the plane and then take it out with my kids. Instead I was putting in long hours in a research lab at MIT and then Harvard.

A few months ago I was in the basement and noticed that the Wingo box had been water-damaged. I wasn't sure if that would matter or not, but I realized that it was time to either build the kit or throw it out. Still, I procrastinated until last weekend, when I took the box out of the basement, showed it to my kids, and started building it.

For a person who is used to working with software, building the Wingo is a completely different experience. The kit came with the precise number of pieces that I needed--no extra. With software, you can always revert to a backup if you make a mistake; that's not the case when working with a physical kit. Another difference was the directions: they were in German first, with a poor English translation underneath. With software, practically everything is in English.

Most of the model is assembled with five-minute epoxy. I was about 60 minutes into the project when I discovered that I had glued on the elevator upside down. Not good. The wings are all made of foam, so I cut it off and put it back on the correct way. After five or six more hours of work (with lots of time spent waiting for the epoxy to dry, then wandering off to tend to other projects), the aircraft was finished, more or less.

Like most beginners, I had used far too much glue. Then I looked at the aircraft and noticed that it wasn't straight: the elevator was a good 20 degrees out of line with the wing. Nevertheless, I thought the thing would fly.

The Wingo's instructions advise taking the plane for a drive around a parking lot before letting it into the air. On the ground you can make sure that the plane's controls all work. Then you can roll to a takeoff. But I had no idea where to fly the thing. I took it to a nearby high school; I wasn't sure if the football field was big enough. My kids and I tried driving it around on the parking lot. That worked, more or less. But I couldn't get the thing to take off from the grass, or from the dirt of the baseball diamond. So finally I just gave the thing a toss and hand-launched it. It flew, then crashed. I tried again. Then a third time. This time it was flying pretty well when the engine quit.

Apparently the battery had run out of juice.

When I got home I went to the Hobby Lobby website. Sure enough, flying time for the kit is listed at 10 minutes. That's a lot of time when you are a first-time RC flyer and you've got an aircraft you are desperately trying to keep in the air. It's not a lot of time when you have an aircraft that you are taxiing around in a parking lot. I had used up my flying time without even realizing it.

I remember that Raskin had told me why he preferred gliders. It isn't just that they are quiet--much more quiet than even an electric aircraft. The real reason, he told me, was that you can spend your time actually flying, rather than charging and changing batteries.

So now I've got a Wingo, an RC remote control, and a bunch of servos. I wonder if I can fit them into a glider.

Click here for images of the Wingo being assembled, completed and in flight.

I buy a lot of used hard drives on eBay. Originally, I bought these drives to demonstrate that people throw away or sell computer equipment without much regard for the so-called residue data. About one-third of the hard drives that I bought had confidential information on them, one-third of the drives had been properly wiped, and one-third were broken. I published and made a big splash with my findings. The research was even part of my PhD thesis.

After I graduated, I turned my attention to other uses for this information. One of the more interesting things you can do is develop new computer-forensics tools. Most academics and other researchers who are developing such tools today base the tools on a very small data sample--but by using my collection of used hard drives, I could develop and validate tools using more than a thousand different drive images.

There is just one problem: ever since I published my research, fewer and fewer of the drives that are sold on eBay actually have data on them. I believe that this is one of the positive results of my research--more people are aware of the need to overwrite their data before tossing (or selling) their drives. But it has also caused a problem for me because I'm still trying to grow the corpus of disk-drive images.

A few months ago I was visiting another computer-forensics specialist when I learned about the freezer trick. This fellow gets a few broken disk drives now and then, and, by putting the drives in a freezer overnight, he's frequently able to recover data that would otherwise be "lost." Well, when I got back to Harvard, where I work, I took a few of my "broken" drives down from the shelf and put them in the freezer overnight with a note: "These hard drives are being used for a research project; please don't eat them."

The next day I took two of the drives back to my desk and plugged them into my computer. How about that: two of the drives that had been "broken" were now giving me their data.

This is a big deal for me. For starters, it means that I can now get data off many of those "broken" drives I've been keeping on my shelf. But it also means that many of the drives being sold on eBay as broken can nevertheless be scavenged for data. This is particularly troublesome because it's unlikely that the previous owners of the drives were able to properly clear them before they were sold.

I don't know why people continue to sell used hard drives online. I mean, there's not a lot of money to be made. And given that more than a third of the drives I buy are broken (even the ones advertised as working), I can't figure out why people are buying them. But I can tell you one thing: when I bid for hard drives on eBay, I lose most of the auctions.

We were invited to a fundraising party on Monday to kick off the Computers, Freedom, and Privacy Conference. Although our host recommended that we take a taxi, my friend Mark had a Garmin Nuvi 360 GPS, and it claimed to know the way. Mark, another journalist friend, and I went for a walk. The other friend had paper directions explaining how to get to our destination, but we decided to ignore that inferior fiber-based technology.

I had my own GPS as well, a cheaper Garmin Venture CX. Although my GPS is designed for hiking and Mark's is for driving, I was astonished at how much better suited the Nuvi was for hiking around the city. Yes, it knew all the streets. It could navigate to where we wanted to go. It even had a "walking" mode whereby it knew that we could do pedestrian bridges and walk the wrong way down one-way streets.

Of course, my GPS cost something like $350 less than Mark's.

The trip was fun, but long. Instead of being the 2.1 miles that the Nuvi claimed at the outset, by the time we reached our destination, my GPS told me that we had walked a good 3.5 miles. And we ended up walking through some very sketchy neighborhoods. We walked by buildings with broken glass, by a building that was either a soup kitchen or a rehab center (with a long line of men standing outside), two clusters of kids just hanging out on the street, and then, near our destination, a group of seven kids walking in the middle of the street, some of them carrying "walking sticks" and the like.

Mark missed most of this, of course, because he was fiddling with the GPS most of the time we were walking. And I kept fiddling with my GPS, trying to convince myself that it was good enough for my needs. Yes, I had a case of GPS inferiority. My GPS had a lousy base map; Mark's GPS had high-quality street-level detail, navigation, and even text-to-speech for speaking the names of the streets as we walked by them. (This is useful when you are driving, to be sure, but not terribly useful when you are trying to outrun a gang of kids in hoodies.) On the other hand, I got a nice dotted map of where we had been and the odometer.

I was also impressed at how sleek and compact the Nuvi is, although it lacks that all-important lanyard, which is so useful when you are on foot. The Nuvi will also charge off USB; my Venture CX takes AAs (but it runs for nearly 24 hours on a charge, rather than just 3 to 5).

Finally, we reached our destination: an intersection by a highway in the middle of a burnt-out industrial zone near a canal. We could hear rushing water through a manhole cover. But we couldn't find the party.

I took out my Treo 700p and pulled up a copy of Google Maps (Google now has a very nice Palm application). I typed in our destination's address, and it gave us the same location. I guess the Navteq data is wrong.

We finally ended up calling our host, who came and got us in his oversized black SUV. Apparently, we were on the opposite side of the block from him--we had walked by his "apartment," which we learned was really a loft in an old industrial building. He told us that Google Maps just didn't know where he lived. Which means that the Nuvi didn't know either, since the data all comes from the same source.

In retrospect, what's really interesting is this: when the technology failed us, we didn't look around to see where we were and search for street signs. Of course, at that point we were standing in the middle of a barren junkyard wasteland. But we were actually on the right street, just at the wrong location. If we had walked back a quarter mile, we would have ended up at the right location. And if we had then looked at the paper directions, we would have been able to find our way to the party.