This article originally appeared in TidBITS on 1999-07-05 at 12:00 p.m.
The permanent URL for this article is: http://db.tidbits.com/article/5463
Include images: Off

MacHack: The Ultimate Macintosh Event

by Adam C. Engst

Every so often, I feel like a total idiot. I've been reporting on the Macintosh industry for over nine years, and for the first few years, I vaguely knew there was a developer event called MacHack. At some point, MacHack was explained to me, and as I made more contacts in the industry, an ever-increasing number of people invited me to attend. I always demurred, begging off on the grounds that I wasn't a programmer, or that I couldn't justify travelling to yet another conference, especially one in Detroit, which holds no external attractions like relatives in the area. Last year, I even helped in a small way to find loaner machines for the conference's public machine room; this increased the pressure to attend this year's conference, and I finally gave in.

What a mistake I've been making! MacHack is, quite simply, the most fun a serious Macintosh geek can have legally.

<http://www.machack.com/>

Identification -- Describing MacHack is like summarizing a zany movie - no retelling can capture the essence of the event. Still, let me attempt it.

A defining characteristic of a geek is the confluence of personal and professional interests. The Mac geek lives and breathes the Macintosh, checking email first thing in the morning, using a Macintosh at work all day, debating recent industry events with friends at dinner, playing games, making Web pages, or even writing programs at night. The details vary by individual, of course, but many people fall squarely into this category. For those folks, it's tremendously enjoyable to be surrounded by peers, Macintosh geeks of roughly equivalent experience and knowledge. Conversations amongst Mac geeks range widely and hop nimbly between Macintosh topics, unhindered by any need to differentiate between RAM and hard disk space or explain every Internet reference.

Many of us have had a taste of such an event, though it's usually limited to an evening user group meeting or a brief dinner party. But if a user group meeting is a taste, then Macworld Expo ranks as a light supper - the thousands of attendees make significant interaction with other Macintosh users difficult. There's also a sense at Macworld that someone else is cooking, and we're all guests who must maintain a certain distance and formality. In comparison, MacHack is a ten-course feast prepared in front of the several hundred diners by talented volunteer chefs who then remove their chef's hats and join in the exuberant gastronomic celebration.

In short, MacHack is a conference of the geeks, by the geeks, and for the geeks. Started 14 years ago by Gavin Eadie and some colleagues at the University of Michigan, MacHack became independent in its second year and continues to be organized by a volunteer committee made up of members of the Macintosh community, ably aided by the staff of Expotech, who handle the logistical details. The committee finds a keynote speaker, organizes sessions, designs the t-shirts, and generally ensures that MacHack will happen yet again, while Expotech handles registration, conference materials, coordination with the hotel, and ordering hundreds of boxes of pizza.

MacHack is a developer conference, and there's little question that developers find it tremendously useful. Where else can you ask a question of the best Macintosh programmers in the industry and get an immediate answer or spark a debate between the hotshot programmers and wizards from Apple's Developer Technical Support division, some of whom also attend? That said, I'm not a programmer at all, and I enjoyed myself tremendously. Pondering why, I realized that for non-programmers, two things must be true. You must be a serious and outgoing Mac geek conversant with current technologies, issues, and events, and you must be willing to participate.

In my case, participation came in the form of giving a session entitled "Hacking the Press" (which I plan to convert to a TidBITS article). I also let myself be rooked into offering a technical journalist's perspective in a session on industry terminology, and spent time helping a 12-year-old girl find the necessary software to use an old Connectix QuickCam to create her hack for the Hack Contest.

Education -- My brief donation of time and expertise finding software on the Internet was nothing compared to what many others at MacHack did for the younger attendees. Collectively referred to as "yoots," the student attendees ranged from a seven-year-old girl to a college student interning at Apple. Everyone encourages and helps the students, 50 of whom attended this year and 19 of whom worked on hacks for the Hack Contest. For instance, AppleScript was a popular language for many of the yoot hacks, and AppleScript guru (and author of the AppleScript editor Scripter) Cal Simone lent his expertise to a number of the students.

<http://www.mainevent.com/>

This emphasis on education is one of the most attractive traits of MacHack, because it spreads expertise among the community and also to future generations of programmers. Perhaps even more important is the example set by the generosity of the older programmers - these kids are seeing people helping one another regardless of age or knowledge. All that's required is a desire to learn and participate.

Hacks -- I've referred to "hacks" several times already, and the hacks are an important aspect of MacHack. A hack, for the purposes of the conference, is a program that makes the Mac act in previously inconceivable ways. Hacks may modify standard Macintosh windows, replace the Mac's graphics with ASCII characters, or, in the case of one that didn't succeed this year, attempt to coerce the Mac OS to run on a 240 by 240 pixel monitor. Occasionally a hack may even become a commercial product, as with Leonard Rosenthol's Finder-based Web bookmark utility CyberFinder. Hacks are seldom polished, since they're usually created in the 72 hours before the Hack Contest, and they generally aren't useful. The goal with a hack is to perform a technical feat that will impress the other programmers, not to write finished code with a sophisticated interface. This year's entries in the Hack Contest were innovative and entertaining, and I'll cover them in detail in a separate article.

<http://www.hax.com/HackContest>

Thoughts -- Of all the conferences I've attended over the years, MacHack stands out as the most unusual. A few examples:

<http://devworld.apple.com/mkt/informed/ appledirections/oct96/machack96.html>

Emulation -- It would be easy to recommend that everyone should go to MacHack, but that would ruin MacHack because the conference can't get much larger without losing its charm. Recognizing this, the conference organizers put a cap on attendance and, although they didn't quite hit it, they came close with 289 attendees this year. So for next year, when MacHack will once again be held near Detroit, from 22-Jun-00 to 24-Jun-00, I would encourage developers and serious Mac geeks with technical bents and outgoing personalities to attend.

The people who have organized MacHack have created something truly special, but I don't think it's necessarily unique. Other niche groups, from desktop publishers to database developers to independent consultants, could all learn from MacHack's example and create their own conferences that focus on letting the attendees interact with one another, rather than trying to shuttle them around between sessions like high school students. The best way to understand the secrets of what makes MacHack special would be to experience it firsthand, especially as a volunteer helping behind the scenes.