The Berkun Blog

Management, design, and the making of good things.

Archive for the 'Recommended' Category

The best book I read in 2007

December 17th, 2007

I’m nuts about books. I finish a book a week, and abandon many more. Looking back on the year, picking a favorite, #1 book to recommend is easy - that’s how much I enjoyed this book. It’s Over the edge of the world, by Laurence Bergreen.

Over the edge of the world

The book tells the wild, nearly unbelievably difficult tale of Magellan’s expedition to circumnavigate the world. In short, everything goes wrong. Mutiny, starvation, politics, bad project management, and on it goes. There’s also what has to be one of the greatest idea pitches ever (”Yes, I will go all the way around the world, requiring several routes no one has discovered yet, and you will pay for it”). And it’s all told with the perfect balance of tight, thrilling storytelling and historic detail.

I love books like this for their power to humble: they put all of the challenges and complaints people have today in relief. Nothing any entrepreneur or middle manager faces today even approximates the risks, suffering, and significance of what these historic figures did. Finishing this book I felt inspired by the realities of what Magellan and his crew did, rather than the false, simple tale I’d learned as a kid.

It’s a great gift choice for anyone interested in innovation, how progress happens, how myths compare to realities, project management, people management of all kinds, and well told true adventure tales.

Over the edge of the world: Magellan’s Terrifying Circumnavigation of the Globe, by Laurence Bergreen.

Why you should go to the GEL ‘08 conference

December 11th, 2007

Gel logoI’ve been attending or contributing to GEL (Good experience live) for several years now - sadly I can’t make it this year (it’s 4/24-4/25/08), but I have to say, it’s my favorite conference. The early registration deadline is tomorrow, so if you have the budget to attend a conference next year, I want to make my pitch to you to make it GEL.

Why GEL rocks:

  • They pick great speakers. I’m a pro public speaker myself, and GEL has a high bar for the people they let on stage - they all understand experience, tell great stories, and earn their slot on the program. This year they have Bobby C. Martin Jr, Director of Jazz at Lincoln Center, Garrett Oliver, a Brooklyn bar owner, Phoebe Damrosch, author of the bestseller, Service Included, and Alex Lee, CEO of OXO (makers of good grips line of kitchen gadgets), not to mention the day one experiences. The full agenda is here.
  • It’s a NYC conference run by new yorkers. All of the day one experiences, where you get to experience design first hand, are run by local designers, curators and other experience creators. No other conference I know of pays so much attention to locale and teaching experience through places and activities, instead of presentations. Many conferences move every year, like nomads, never taking full advantage of their locale - not GEL.
  • It’s single track. Ok, like, no big deal. But when was the last time you went to a design conference that said “our speakers are so good, and so fun, you can stay in your seats, and we’ll bring the good stuff to you?”. Like a good UI design, a single track shows a high commitment to quality and faith in the program.
  • Until Dec. 12th, It’s $1000 to attend. Hey, why pay less for forgettable generic conferences, when you can pay a little more for a true experience you’ll remember? More info and registration here.

Book review: A whole new mind

December 10th, 2007

If you write about innovation or creativity there are certain books people will continually tell you to read - they’re not necessarily the best books, just popular ones. I’ve kept track, and the top # of mentions have gone to: Malcolm Gladwell, Connections by James Burke, and A Whole new mind, by Daniel Pink. I’d already read Gladwell and much of Burke, and this week finally read A whole new mind.

Short review:

wholenewmind.jpgIt’s a light, positive, inspiring read. It makes strong claims about the value of right-brain, or creative, thinking, and how the economic conditions in the world have created big opportunities for creative people. However the arguments are often one-sided with claims that verge on pollyanna (creative thinkers will rule the world!). If you or people you work with are logic centric thinkers, this book will help you understand the value of a holistic view of what our minds do, and give you ammunition for debates, as well as resources for how to grow the intuitive parts of your brain. But while I’m a fan of the theme, and anyone that defends left-handed people (we are the only people in our right minds, ha ha) I struggled with his arguments despite my agreement with some of his conclusions.

Long review:

I had major criticisms of both the assumptions he makes, and how he makes them, primarily ignorance of history, unnecessary polarization, and lack of devil’s advocacy. If you don’t care about my gripes, stop reading: I’d generally recommend the book. And since what follows is long, I have to say the book was thought provoking, though not necessarily in the way the author intended.

If you haven’t read it, and don’t want spoilers, go read it before continuing. Ok, you’ve been warned.

Ignorance: Right brains have been dominant at other times: namely, the European Renaissance. What happened? Why didn’t the world change in the ways he describes ours will if we can get better at Right brain thinking? He doesn’t say. The rise of Impressionism, Cubism, Rock music, Surrealism, Punk rock, Free Love, Video Games, Movies, Music videos, the birth of Greek philosophy and drama, and other huge cultural/political contributions driven by R-dominant (his term) behavior aren’t mentioned either. R-dominant thinking is old: it may be so old it’s new again, but to frame the argument as a Whole New Mind, without any hat tip to things pre-1950 is glaring, or as Tom Standage might say, overly chronocentric. The shifts between L to R dominance at the culture level, across time, has been discussed by other authors, from Leonard Shlain’s excellent Art & Physics and to some extent, Daniel Boorstin, but no reference from this line of thought is mentioned.

Polarization: Isn’t the best possible world one where we use all of our talents, as appropriate, to the problems at hand? Wouldn’t it be just as dangerous to have an R-dominant world as it is to have a logic, or L-dominant one? The tag line for the book is Why right-brainers will rule the future. Rule? Is that for the best? I bet he’d agree our rulers should be people who recognize the value of both kinds of thought, and that he’s fighting for a return to some kind of balance, but the book doesn’t say so (If I does, I missed it, despite a careful read). Perhaps I should have read the book as a manifesto, but I found that hard given the attempts at logical arguments and statistics he uses in his arguments.

Devil’s Advocacy (DA) : Every book makes a bet on a core theme and then tries to live up to it. But what should a writer do in chapter 6, when they realize a good point that disagrees with the title? Or several major points? Ideally at least one of them is discussed ( however briefly), hopefully they’re mentioned, and minimally they’re referenced. I didn’t find any kind of refutation or questioning of the core thesis in the text or in the notes. If I’m guilty of this in my books, fine, I’m a hypocrite and I’ll do better next time. But that said, my DA questions included:

  • The book states MFAs are the new MBAs. What? Pages 54-56 discusses the rise of design in business, which is true and good. But if MFA’s are infiltrating the management ranks of GM, GE and McKinsey, it’s to complement the L-Dominant people they have in abundance, not to replace them all. I’m all for R-dominant people, but I doubt they’d be great at doing corporate taxes, remotely managing 1000s of employees (remotely in Asia), or the other dozens of core business functions that will always be core business functions. Or put another way How many R-Dominant people does a company really need? (And footnote: he mentions the low acceptance rates in MFA programs as an indicator of how hot MFAs are in the business world, but likely makes the wrong conclusion. First, there are likely fewer MFA programs than MBA programs, and the class size accepted are generally much smaller (often 20-30) - I bet this has always been true, so it’s not a trend, and likely has more to do with how MFA programs work than anything going on in the rest of the world).
  • The environment. Pages 74-86 explore the increasing value of design, a point I agree with. But the emphasis here is heavy on consumerism, not designing things better for the world. Pink writes “The forces of Abundance… turn goods and services into commodities so quickly that the only way to survive is by constantly developing new innovations, inventing new categories, and… giving the world something it didn’t know it was missing” (pg. 81). Victor Papanek, one of the fathers of Product design, would call this a horribly selfish distortion of the power of design. How is it good for the planet, and our grand-children, if our only solution to problems is to keep making new stuff for people to buy, only to throw them away, despite their perfectly good conditions, replaced by more stuff people really don’t need? How is this sustainable in any way? Not mentioned.
  • Are there tests or skills for helping a person have a balanced mind? Is it possible for a person to not be L-Dominant nor R-Dominant? I kept wondering if this binary kind of thinking is useful, other than as a polemic. I mean, doesn’t the book rely more on L-Dominant thinking in most of it’s arguments? Sure, that’s a side effect of written language, but then doesn’t anyone who works via e-mail, or the web, face the same challenge? Namely, that R-dominant talents are, almost by necessity of how modern communication happens, filtered through L-dominant skills?
  • Do some cultures, perhaps in Europe, Africa or Asia, have more balanced views of the mind (e.g. Yin/Yang)? The United States has a poor view of art and architecture relative to Europe, if not other parts of the world. So is this an American problem? If so, why did we become so L-Dominant when other cultures did not? One argument is the Enlightenment of the 18th century sent Europe, and America, on a logic dominant world view, with Descartes’s “I think therefore I am” (ab)used to overstate the importance of rationality over other modes of mind. Pink doesn’t ask these questions or hint at their possible significance (If these themes are embedded in our history, culture and government, how do we remove/modify them?).

Book review: Founders at work

February 6th, 2007

Founders at work is a collection of interviews with, surprise, founders of tech-sector companies. The goal is to capture their recollections of the early days of their successful ventures, and share stories that were often overlooked.

The interview list is first rate: founders from Hotmail, Adobe, Excite, Firefox, Yahoo! and more than 20 other well known companies are included.

The upside is that these stories read honest: there’s struggle, failure, fear, mis-steps and changes of direction, all the things often glossed over by high level mainstream interviews of success stories. If you’ve wished you could have a chat with some of these folks, you’ll be happy with this book. Livingston does a good job of staying out of the way and tries to cover similar territory with each interview (however it has the minor effect of making the book more readable in separate sitings, as the repetition of questions tires after 5 interviews in a row).

The other risk for those with dreams of entrepreneurship is that the stories come across as ordinary: there are few magic moments, radical breakthroughs, or amazing coincidences: its mostly hard work, and fantasies of what starting a company is like will fade by the 8th interview.

This book is inspiring at times: mostly because it makes the stories of these startups real. These were human beings doing these things, not omnipotent geniuses. Anyone expecting triumphant, and replicable, vision for why these folks succeed will be forced to look elsewhere, or perhaps more to the value of this book, reconsider what it takes to found a successful company.

Founders at work at Amazon.com.

The author, Jessica Livingston, is a partner at Y Combinator, a venture firm for early startups with some novel ideas on what venture firms should do.

Book review: Designing Interactions

February 2nd, 2007

Disclaimer: I met Bill Moggridge (the author) when he volunteered as a judge, with Brenda Laurel, and Andrew Dillon, in the CHI.

di.jpgDesigning Interactions is a book of stories. It takes the novel view that the people behind the designs can teach us more about design than the designs themselves. Although there are plenty of ID-magazine style photographs, they’re not the centerpiece: the people and their design stories are.

If you’re fond of interviews, and want to hear first person stories about how various famous designs were made, this book is for you. I’m a story guy so I was happy, finishing most of the book in one sitting (More theory-driven readers would be happier elsewhere).

The book’s content is well described on the companion website, including a chapter overview exposing an emphasis for tech-design history: From the mouse, to the PC, to PalmPilot, Moggridge starts at the beginning and works his way, one person at a time, to the Internet, gaming and the future. While there is some predictable designer-self worship, and a shortage of stories of failure, many of the stories are humbling, refreshing and inspiring.

One warning is that the book has a San Francisco & IDEO centricity: more a reflection of the author’s network than an objective history of tech-design. IDEO, which Moggridge co-founded, is mentioned often and if this annoys you either filter it out or look elsewhere.

The book is a bargain, coming in at a hefty 800 pages, many amazing color photos (including archival), and a companion DVD (although it overlaps with the published interviews). I can’t think of another book like it.

Interview list includes: Bill Atkinson • Sergey Brin • Stu Card • Gillian Crampton Smith • Jane Fulton Suri • Bill Gaver • Bing Gordon • Rob Haitani • Jeff Hawkins • Matt Hunter • David Kelley • Brenda Laurel • David Liddle • John Maeda • Tim Mott • Joy Mountford • Takeshi Natsuno • Larry Page • Mark Podlaseck • Larry Tesler • Bill Verplank • Terry Winograd • Will Wright

Sample chapter and interviews. Buy from Amazon.

Book review: Dreaming in code

January 8th, 2007

dreaming.jpgI was greatly anticipating Scott Rosenberg’s, co-creator of Salon, new book, Dreaming in code and was happy to get a free copy in the mail.

In short: I enjoyed the book and recommend it - it’s a good, though uneven, book exploring why software is hard to make. I read most of it in one night and finished it off in a second, and despite anything else i say, that’s an endorsement of any book of any kind.

However my take on the book is unavoidably hurt by its lead praise from James Fallows, of The Atlantic, who said ‘The first true successor to Tracy Kidder’s The Soul of a New Machine’, in reference the Pulitzer prize and National book award winner that defined the ‘computer engineering as human narrative’ genre. Kidder’s book was personally seminal and I have respect for Fallows, but it’s misguided praise, and worked to Rosenberg’s disadvantage. I don’t think his intent as an author was to write the same kind of book, and the comparisons in my mind didn’t help. However, as an author I’m ambivalent on the appropriateness, or dangers, of comparing a book based on what it’s blurbs say, so I’ll leave it at that.

Dreaming in code is three books woven into one: one of them is a narrative story of of the Mitch Kapor lead project to create a new PIM application called Chandler. The other threads introduce software concepts (e.g. explaining object oriented programming and how Python differs from C++) and explores why software is hard to make. All big topics, and fun ground for Rosenberg’s curiosity and intelligence to explore. The book struggles however with keeping them together: the 3 threads are uneven, and I was often unsure where he was going, or when we’d get back to the Chandler story, the one I expected to be, based on the cover and Kidder reference, the focus of the book.

For example, the book dances between assuming the reader has tech-interests vs. being a layperson, with side threads into esoterics like Hungarian notation and Literate programming, that made me wonder. Most books in this genre don’t go that far, drawing the line around the depth of what a magazine feature article would explain: even Digital woes, a favorite book on why software fails, nails the topic without getting into construction or showing code samples.

Steven Levy’s Insanely Great, about making the Macintosh computer, or Zachary’s ShowStopper, about Windows NT, are classics in this genre, and unlike them Dreaming in code has a higher degree of difficulty: it doesn’t have a star central project at the book’s core. I would never have heard of Chandler without picking up the book. Mitch Kapor and Andy Hertzfeld, industry pioneers and legends, play leading roles which adds some star power, but they’re not the focus.

And without the natural tension of a big well known project, the players in the book feel light: the drama and passion that are integral parts of good projects aren’t there (and it’s something Kidder went to great lengths to capture). I can’t tell if that’s Rosenberg’s polite reporting, or something missing in the project itself, but the emotional commitments of people to each other, and the project, is critical to making good software, and might be the secret Rosenberg seems to seek in the book, but it’s never mentioned.

That said, Rosenberg is smart and insightful, and the book has its share of gems. Ideas from many luminaries are touched on, from Doug Englebart, Fred Brooks, Alan Kay, Richard Stallman, Don Knuth, Watts Humphrey and more. The result is a good, often charming book, that would be good fodder for a team to read together, discussing their own opinions as each chapter unfolds.

But with the rickety management example of Chandler at the book’s core, software management, as a discipline, is portrayed as an immature, misguided, geeky business: perhaps an accurate snapshot of the average team today, but not of the best. Rosenfeld doesn’t give serious context until the last 1/3rd of the book, when Joel Spolsky, 37 Signals, and Google’s theories surface as cautious remedies to the challenges Chandler faced, but the vibe is cynical, and I found myself, especially with Chandler as the example, defensively optimistic about what a good project manager could have done.

As a sweet side note, Rosenberg did uncover thought provokers I hadn’t heard before:

  • Alan Kay’s wonderful software as a doghouse metaphor
  • Linus Torvalds on how you should start large projects
  • Richard Gabriel’s passionate criticism of programming education

Rosenberg’s perspective cuts both ways: his outsider view is an advantage as he asks questions veterans and gurus have forgotten or are scared of, which paves new ground on old topics. But it you want guidance, harder critiques, or expert analysis of what to learn from Chandler, you’ll need to discuss the book with someone else, or look elsewhere.

A Chapter is available online, and it’s worth a look. Also check out the Dreaming in code website or Pre-order at Amazon.com (Out Jan 17th).

Book reviews: Engines of ingenuity & How Invention begins

October 31st, 2006

Sometimes good books sneak up on you - you enjoy reading them, but their full value doesn’t surface until afterwards, when in the days and weeks that follow you find yourself thinking back on how the book changed your mind. Engines of ingenuity by Historian and NPR host John Lienhard, fits this profile.

The book is comprised of short essays on the history of technology and invention, largely from his NPR show by the same title (transcripts onlne). These essays read well, cover many famous bits of technology history and offer insights and fresh perspectives on some stories I thought I knew well. Highly recommended.

Lienhard’s new book, How invention begins picks up where EOI leaves off. This time he looks deeper into how inventions develop, exploring how often desire, and not true necessity, led to many of the major technoligical innovations of our past.

It’s written in a more challenging style than EOI: longer pieces, more rigorous history, and covers less well known territory. For that reason I recommend EOI or Leinhard’s short NPR pieces first, and if you enjoy those, they’re excellent introductions for How invention begins.

Review: 37signal’s Getting real, the book

April 17th, 2006

The folks at 37 signals have well earned their reputation for making great web applications. They’ve established a strong identity for with a line of web tools for project management (Basecamp), To-do lists (Backpack) and simple collaboration (Whiteboard).

They recently published a short book called “Getting real” about how to build web apps - and here’s my review.

The book is short - 170 pages with lots of whitespace and heavy quoting. If you’ve used any of their apps you’ll feel right at home as they do a fine job maintaining the same voice and style.

The highlight is their passion for making good things. They are most effective when they boldly express their ideals, using them to slash through common assumptions about features, big planning, organization and customers. It’s a brisk and optomistic read. At turns clever and confident, but ocassionally nieve, this book will generate strong opinions and can spark healthy debate even if you don’t like or agree with what they say.

The lowlights are the how - While I’m philosophically aligned with these guys, this book is more mantra than guidance or instruction. I imagine it working as a boost for people who believed some of these things prior to reading the book who, now reaffirmed, can point others to it as an external and respected source. There are obvious counter examples to some mantras, but they’re beyond the point, as the questions raised are worthwhile.

But for those in old-school organizations or with dysfunctional teams, this book doesn’t give the tools needed to turn things around nor provide individual readers with “Real” practices they can employ on their own. Most of “Getting real” is about approach and attitude, and it requires your co-workers to share it with you to work.

The book’s strength and weakness is the experience of the authors: they started 37 signals on their own, and advise largely from that context. While they don’t try to direct readers for how to convert older, larger, slower, less talented teams of people into “Real” teams, there is the vibe througout the book that the world would be a better place if everyone did.

Summary: I recommend this book - it’s a fast and opinionated read. It’s most valuable to small self directed teams, as a reference for how one small, talented, self directed team has successfully built quality software or as a hand grenade for teams that have been doing things the same way for too long. However it doesn’t quite justify the $19 price: there are tragically no references and no links to other sources, something I hope they’ll remidy in a 1.1 book update. (For reference: McConnell’s Rapid Development, with a 5 star average over 100 reviews at amazon, covers similiar ground with near opposite highlights/lowlights, for $22, with thorough links to other sources to go deeper than the text. These two books make a fine pairing).

The Book: Getting real by 37 signals ($19, online PDF only)
Free Excerpts: Scale later, Meetings are toxic, and more

The GEL Conference (May 4/5) - Why you should go

March 29th, 2006

Gel 2006 The early registration deadline for GEL 2006 ends next week, so it’s a good time to make a pitch for why you should go.

Good Experience live is the only conference I’ve been to that is self-reflective: many of the principles of design and good user experience espoused during the day can be found in the way the conference itself is run. Day one of the conference is out in the field, spending time with experts in their domain: an inside tour of the experience design of NYC landmarks like Natural history museum, MoMa and the Hall of Science. Participate in an improv experiment on the midtown streets or a learn how to apply tmusic techniques to your work. There’s also a food experience tour of my home burrough of Queens, NYC.

Day 2 are talks from Craig Newmark (Craigslist), Jason Fried (37 Signals), Seth Godin, Douglas Rushkoff, Photographers, Urban pranksters, Game designers and other interesting perspectives on making great things for people. There’s no formalized boundries here - instead you get great cross-discipline stimulation that will stay with you long after you leave.

The conference rates are still discounted Before April 5th, it’$1200 for both days, and $1500 afterwards. (Price was $900 before December 1st, but that’s behind us now).

I’ll be running a Day one tour on NYC’s sacred places. We’ll be walking around the city and exploring magical and special places, discussing how they were designed to have the effects they have. You can sign up for this or other Day 1 tours when you register.

Hope to see you there.

Book Review: Management of the absurd

October 5th, 2005

Book coverI found this book in the discount rack at a used bookstore in Fremont. Having found much of what people call management quite ridiculous I laughed at the title and flipped it open. Inside I found validation for many of the pet theories and uncorrelated observations I’ve had over the years, written in clear, short, insightful chapters. It’s a gem. You’ll have many deep sighs when you read it and will feel relieved about the insanity at work that, until reading the book, you though only you felt.

The book does offer advice but is not a a how to guide. I found it more of a catalog of the inherent paradoxes of managing teams of people, things that impact everyone but are rarely mentioned.

The management of the absurd, Richard Farson. 172 pages.

Book review: Deep Survival

September 20th, 2005

I read about a book a week and most don’t stay in the front of my mind long. I finished this one a month ago and still find myself thinking about it.

Deep survival book coverThe book Deep Survival: who lives, who dies and why, by Laurence Gonzales, asks the question: why do some people survive dangerous situations and other people don’t? The author spends most of his time telling riveting survival stories: plane crashes, mountain climbing accidents, people lost in the woods - they’re all page turners, but Gonzales also pulls out details to offer theories and hypotheses, most of which are relevant to daily life.

I finished the book in two sittings, enjoying the stories and his thoughts on psychology, training, intelligence and stoicism.

The nugget that I can’t get out of my head is this: people that survive abandon their mental models of the world and open their eyes. They don’t try to force the world to be a certain way: instead they respond to the world like a child, taking it to be what it is, and working within the real world to try and survive (or thrive).

Every day since i’ve read the book I’ve caught myself trying to force something and stopped myself, asking: am I seeing how I want the world to be, or I am I working within the world trying to make it how I want to be?

If you enjoyed Into thin air, or the film Touching the void, this book will add another level to your appreciation of those stories.


You're reading scottberkun.com, home of tasty essays. All rights reserved unless noted. You can subscribe here (RSS ).
If you're not sure how to feel now that you're at the footer, joy is free and recommended.