Monday, August 13, 2007

Sergey's Story, in Chinese

A few months ago, Moment Magazine published an article written by Mark Malseed telling the story of Sergey Brin (Google co-founder).

My wife Oriana, in addition to being a lawyer, is quite a skilled English-Chinese translator (that's an understatement, believe me). She translated the article (under the obvious assumption that anything that is interesting to Jews would be interesting to the Chinese). And in fact, her translation was recently published in the Sunday Weekly Magazine editions of the SingTao Daily, the most widely circulated Chinese language newspaper in North America.

You can get the full translation here.

As with any Chinese-related content on this blog, the usual disclaimer applies: it's all Chinese to me.

Wednesday, August 8, 2007

Two Zodiacs Away

I feel like I should have something to blog about on my birthday. Next year, it won't be a problem -- the Chinese have scheduled the opening ceremony of the olympics for that day.

Generally, I'm a guy who feels pretty comfortable with his age. That's an important survival skill when you work for Google. Every now and then, however, I realize that even though I'm not feeling any older, time is passing.

Today the poignant moment was when I was standing and talking with my group members and interns (all very nice, organized a nice birthday celebration. Special thanks to Bijun who ordered a chocolate babka from Zabars in NYC!). I was chatting with my youngest intern (a graduate student) who mentioned she was also born on the year of the rabbit, like me.

Then there was a pause. It took us both a mere 5 seconds to realize that she's *2* zodiacs away from me. Not one. There is an entire unrepresented rabbit in between us.

While it should be said that she is the youngest graduate student I ever worked with, I still found it startling that I'm working with a rabbit two zodiacs away. I'm sure I'll get over it.

Wednesday, August 1, 2007

Notes from Ed Tufte

Sorry for being silent in the last while. Blame it on the book I'm writing (on data integration). I had to finish a chapter before I could write anything else.

After several years of getting the brochures in the mail, and watching Tufte's book on envisioning information sit happily on my shelf, I decided to go for his 1-day course in SF and learn a thing or two about effective visualization.

If you want the full experience, I recommend sitting next to someone who worked on Microsoft Powerpoint at some point in their career. I did that, and it added quite a bit to the entertainment factor of the course. Tufte's powerpoint rant starts about 5 minutes into the course and he makes his last jab in his closing remarks. But more on that in a bit.

The course was interesting, even if it mostly gets you thinking about issues relating to effective visualization. I jotted down a few notes that I'm repeating here mostly so I don't forget next time I'm preparing a presentation. Most of them are obvious, but that doesn't mean they're not often forgotten.


  • more detail in your presentation increases your credibility
  • more detail does not necessarily imply clutter (if done right)

  • annotate anything you can in a visualization. For example, annotate links (otherwise you're implying that they all mean the same)
  • don't try to be too fancy. Focus on the content not on the design. For example, tables are a very effective, yet simple presentation. Order the rows in the table according to some performance measure you're trying to emphasize.

  • don't focus on being original in your visualizations, focus on getting it right (don't innovate, steal).
  • get users out of the decoding business (i.e., remove legends where possible)



The deeper point made in the course is that principles underlying creating effective visualizations mirror the principles that underly thinking processes. Hence, for example:

  • Make and show comparisons between different aspects of the data
  • Make sure causality of effects is emphasized in the presentation
  • Build credibility -- make sure you show all the data rather than just cherry-picking what's convenient for you.
  • Enable the audience to drill down and see more data.
  • Integrate evidence from multiple sources (aha, a plug for data integration!)
  • Always give the source of your data (yes, lineage, folks!)


Following the principle that good presentation should support critical audience thinkers, Tufte also points out what audience members should keep in mind as they listen to a presentation (surprisingly, reading your email on the blackberry is not one of them)
  • What is their story?
  • Can you believe them? Do they have a any conflicts of interest affecting their perspective? What's their track record? What's their reason for bias?
  • What precisely does their argument apply to? What are its limits?
  • What do I really need to know when I leave the room?


Ok, back to the powerpoint issue. I actually found myself a bit confused throughout the main point of his powerpoint rant, but I think I get it now. His basic point is that powerpoint forces you into a very low resolution presentation mode. He argues that people can read 3 times faster than you can talk. In addition, powerpoint encourages you to leave quite a bit of detail out and summarize everything in bullets. The human brain can take in much more than what you can convey with a powerpoint presentation. Hence, you're not really using your time with your audience very effectively, since there are better methods of conveying information that make much better use of the audience's mental capabilities. For example, he argues that you should come into a meeting with a 3-4 text summary of your points, have your audience read it, and then have a discussion and answer questions.

The latter suggestion makes it pretty clear when his methods are effective and when not. For example, it's a non starter for large audiences (e.g., conference presentations). On the other hand, there are cases where we do this by default (e.g., hiring meetings don't typically involve slide presentations). So, don't dump powerpoint just yet.

Interestingly, Tufte was not following his own advice very carefully during the day. I felt that the principles he espoused could have been communicated more efficiently (but then, perhaps he assumed that some of the audience also had blackberries to attend to).