Jul 09

More on Printers, from Bigelow

A couple of days ago, I posted something about how I’m playing around with @font-face (and since then have also been experimenting with TypeKit, which I use for the headlines you see here). Generated a bit of discussion, but one of the things I mentioned at the end of my post was a class I took at Stanford 15 years ago called Concepts of Text, and taught by Charles Bigelow, a well-known font designer — his foundry did the font family Lucida, for example, and the System 7 city fonts, among many, many others.

One of the classes I remember fondly for being a little wacky (and interesting) was when he gave a talk about typographers who were persecuted for the material they were typesetting.

After I posted the other day, Professor Bigelow somehow found the post and gave us a little primer, which I include below because of the high awesomeness quotient. Really made my day – favorite comment ever. 🙂

Nice to hear, after all these years, that somebody remembers those classes. :-)

Just in case the names and dates have faded from memory, here’s a brief refresher.

Antoine Augereau, Parisian printer and type designer, reputedly the teacher of Garamond. hanged and burned on Christmas Eve, 1534, on (supposedly trumped up) charges of printing heretical placards.

Etienne Dolet, printer of Lyon and Paris, burned at the stake on August 3, 1546, in Paris, on charges of blasphemy, sedition, and selling prohibited books.

Martin l’Homme, hanged in 1560 for printing a pamphlet against a Cardinal.

That all happened a long time ago, but in the 20th century, Sophie Scholl, among others in the White Rose society, was guillotined on charges of treason, on February 22, 1943, for distributing pamphlets against Nazi genocide on the Eastern Front.

I’m sure that somewhere there is good news about printers, too. :-)

Apr 09

Walking in the footsteps of giants

Mike Beltzner and I had a neat experience today — we got to give a talk at Stanford’s CS547 class on how we do design at scale at Mozilla, with Firefox in particular. It was a nostalgic and humbling experience for me — revisiting a set of experiences that significantly changed my life. In the early 90s I was trying to figure out what I really loved; what I wanted to do with my life — and what I wanted to learn while I was at Stanford.

A friend, Sean White, kept telling me I should look at Human Computer Interaction — I eventually did, and got involved with the curriculum that Terry Winograd was creating at Stanford, I helped TA for Bill Verplank, read this article by Mitch Kapor, and just generally found the thing that I really, really loved to do, which was try to build computing systems that made sense to people and made them generally happier and more productive. These people are huge in my history, and in the field — they invented so much of what we think of now as software design — I feel incredibly lucky that Sean encouraged me to follow that path, and incredibly lucky to have been at Stanford at that time.

So when Professor Winograd asked if I’d like to give a talk at 547, I of course said yes. CS547 is a seminar course that has been a who’s who of people doing amazing work in design — the list of speakers over the past 15 is truly unbelievable — people who have made real and massive differences in making computing (and the Internet) more accessible, useful, and joyful for people around the world.

As we got closer to the event, I got more reflective on the path that I’ve taken from there to here; the choices that have led me to be more interested in how to help more people do design — to help more people participate and engage and change their world — and how Mozilla represents such a natural point on that path. And of course that made me more self-conscious than ever about speaking in this forum — it’s a small class, but the history and the implications are not.

I was touched that Bill Verplank came by — and happy to get a chance to talk with him, 15 years after being his teaching assistant. And I have to say that I was shocked as I heard myself talk — how many of the ideas that I use today, in 2009, I realized came out of our interactions back then.

Anyway, I was happy to get the chance to talk, in this storied forum, and extremely humbled. And very proud to give the talk with Mike Beltzner, one of my very favorite collaborators and co-thinkers on design. I’ll put the slides below, and you can see video of the talk as well (link is at the bottom of the page — sorry for the WMV!)

Nov 08

Extraordinary Letter from Stanford’s President

Along with (I think), thousands of Stanford alums, yesterday in my in box I found an extraordinary letter from John Hennessy, Stanford’s President (and a wonderful CS professor and entrepreneur) about the current economic situation and the implications for Stanford. The letter speaks for itself, I think, but I’ll preface it by noting a few things. First, John’s proactive & candid openness is incredible and wonderful to me. Happily, there seems to be a lot of that going around lately. Second, the economic situation is very bad, expanding, and touching everyone. It’s going to get much worse.

Still, I can’t help but feel like we’re all developing ways to talk about challenges like a community of adults, whether they be in commercial terms like we have at Mozilla, in the academy like this note, or in our government with the new administration. That’s something we can build on.

Dear Alumni, Parents and Friends:

Many of you have contacted me over the past few months with questions about the recent shifts in the economy and how the University is affected. I would like to update you on our response to these challenges.

Financial Aid Commitments Still Secure
The questions came to me even before the academic year was under way, from parents moving their sons and daughters into their residences this past fall: Given the state of the economy, would the University be able to meet its commitments to financial aid? Would we be able to help in situations where decreased home equity might preclude a loan they were counting on to help pay tuition? How would we deal with job losses by a family member? Our response: We will stand by our commitments and, yes, we will reconsider the financial aid needs of any family negatively impacted by the economic downturn.

The questions continued through Reunion Homecoming Weekend as the Dow Jones average dropped approximately 25 percent further. How was the University’s endowment affected? What would this mean for financial aid, for operations and for the capital facilities projects already under way?

The Tightest Financial Outlook in Decades

Let’s start with the endowment. We weathered the period through early summer comparatively well, achieving an overall return of 6.2 percent for the year ending June 30, 2008. Since then, the endowment has declined steeply, although somewhat less precipitously than the market indices. In addition, sponsored research, our second largest revenue source, has been declining in real terms over the past several years, and given the challenges in the federal budget is unlikely to improve quickly. Tuition, our third major source of revenue, cannot be raised significantly out of fairness to our students and their families. All of these factors contribute to the tightest financial outlook we have seen in decades.

Fortunately, Stanford entered this period in a relatively healthy financial position, bolstered by several years of revenue increases, generous gifts from alumni, parents and friends, and remarkable growth in the endowment, which for the first time ever became the University’s largest source of revenue.

To manage our finances going forward, we anticipate reducing the $800 million general funds budget – which pays for most of our faculty and staff salaries, central administrative operations and non-research expenses – by 10 to 12 percent over the next few years. Declining federal research dollars could double the total revenue loss across the University. We cannot achieve these reductions without some significant and permanent cutbacks.

Cutting Costs Wisely
As we implement these budget cuts, we will do so with several principles in mind. First, we will focus on preserving the investments we have made in our faculty over the past decade. Likewise, we will maintain our commitment to both undergraduate and graduate students. The excellence of the University depends on its people, and we will do our best to maintain the quality of our faculty, staff and students as we make adjustments.

Second, we will review our capital projects. We are in the midst of a major capital program that includes some vital construction projects. Halting projects in mid-construction, even temporarily, would cost us more money in the long run. But not all our projects will be built according to the original schedule. We will reexamine projects that incur significant amounts of debt.

Third, through support from The Stanford Challenge we have launched a variety of efforts to address the most challenging problems facing humankind: sustaining our planet for future generations, enhancing peace and stability around the world, exploring the potential of stem cells for autoimmune diseases, improving K-12 education in the United States, and finding new ways to generate energy that will not increase greenhouse gases. These are critical initiatives, and while we must adapt our efforts to present circumstances, we will not shy away from our long-term responsibility to lead in finding solutions for these problems.

Trust in Our Stanford Community
We know we are not alone in dealing with this financial shockwave; some of you will experience situations far more difficult than we see on our campus. My sincere wish is that those whose lives have been disrupted will find firmer footing in coming months. In any crisis, we look to the people and places whose connections sustain and strengthen us. I hope that your place in the Stanford community provides such nourishment for you.

As always, I am happy to hear from you. Send your comment, suggestion or question to me at or to Howard E. Wolf, ’80, vice president for alumni affairs and president of Stanford Alumni Association, at


John L. Hennessy

Nov 08


I’ve had the good fortune to visit the Stanford CS department twice this week — on Monday I visited with some of the current section leaders to talk about Mozilla some, and last night I was on a CS careers panel with my very good friends Schrep & Mauria and got to see Mehran & Jay as an added bonus.

It’s been interesting to be back — both incredibly familiar and pretty foreign to me. [As an aside, I have different feelings when I engage with the — I think maybe it’s because I’ve gotten more involved with Diego & Bob & George and design later in my life, and am increasingly interested in those sorts of problems — so I associate undergraduate CS education at Stanford with some exceptionally strong (and fond) emotions that come along with growing up in college.]

On the incredibly familiar side, I understood all the language; I recognized section leaders pulling a huge stack of papers out of their bags; using the time before the class to grade those programs; talking about whether something deserved a “check” or a “check plus.” I recognized the tiredness that comes from going all the time, but also the common fun & shared interest of the section leaders. And while I guess my time at Stanford pre-dated Joss Whedon, I even recognized the feeling when they all started talking about how much they love Dr. Horrible. And of course, of course, I remember looking forward and wondering what life in the world was going to look like, how I was gonna convince someone to give me a job I probably wasn’t really qualified for, and, really, what the hell people at work did with all their time.

On the unfamiliar side, holy cow these students know so much today, about so many things that are important. In 1995 when Bryan and I were both getting ready to start at Trilogy, I think we had a pretty good idea of what companies like Apple and Intel and HP did, but beyond that, not so much. But the students I talked with yesterday & Monday are incredibly informed. They understand the differences between Firefox & Chrome & Safari & IE, and even the implications of those differences. They understand how the Facebook platform works — many have written Facebook apps or web apps that are already in the world. And they understand more than I would have imagined about open source, which makes me hugely optimistic.

They asked lots of great questions. Some were super-specific, about things like what we’re going to do with Ubiquity over the next year, how we think about competition with Chrome, what it is, exactly that product managers do. (That last question I told them they’ll be asking for a pretty long time.)

But also things like how to decide what job to take? How to measure success? How much risk should I take right now? Does it matter if I do systems or AI or HCI?

And, of course, all of us older folks on the panel found ourselves saying things like “well, you won’t really get this now, but…” or “it took me 3 jobs to really figure out anything about that”. But the coolest thing, really, was that everyone on the panel agreed that the single most important thing was to not over-think it, to do what makes you engaged and interested — to do, in Tom Kosnik’s words, “things that make your soul sing.” And more importantly, to do things that matter to people, that change the world, that make things better. And even with all the economic doom around (more on that in my next post), that message of small groups of people getting together to change the world really resonated and made sense.

So with distance now, some things are clearer, some things not so much — that’s a characteristic of being human, I suppose. But I’m excited about this next group of people who are ready to change the world.

Sep 08

mozilla talk at stanford

I gave a talk yesterday morning at Stanford to a set of folks — slides below. Much inspiration and actual material taken from Mike Beltzner’s earlier talks. Sometime when I have time I’ll do a voice-over in order to include my lame jokes. 🙂

Mostly it’s about how Mozilla is organized, and how we push decision-making to the edges of any organization we have — it’s really an organizational design & behavior talk. It’s been fun to do diferent flavors of this over the last few months — people get really engaged.