Thoughts on Steve Jobs — Walter Isaacson

I don’t think Steve Jobs, seen as a whole package, holds much of a lesson for us mortals, as Gary Stix argues here. Nonetheless, Steve Jobs the book is as fascinating as one should expect. The broad contours of his life and the book’s contents are well known, so I won’t repeat them here; I will note a few things:

1) As early as 1980, Jobs was “thrashing about for ways to produce something more radically different. At first he flirted with the idea of touchscreens, but he found himself frustrated. At one demonstration of the technology, he arrived late, fidgeted awhile, then abruptly cut off one of the engineers in the middle of their presentation [. . . .]” Notice how early he was thinking about a product that didn’t make it into shipping products until 2007. But I’m not that interested in touchscreens because, at least so far, they’re lousy for typing and other kinds of content creation. More than anything else I’m a writer, and I don’t see much use for iPads beyond checking Facebook, reading e-mails, and watching YouTube videos. Maybe they’d be useful as menus and such too. Charlie Stross gets this, and he a) actually has one and b) explains more about their uses and limitations Why I don’t use the iPad for serious writing.”

2) Not all of the book’s writing is great—phrases and ideas are too often repeated, and Isaacson shies from figurative or hyperbolic language, like a 13-year-old not quite ready to approach the opposite sex. Nonetheless, the books has enough evocative moments to balance its stylistic plodding, as in this moment: “Randy Wigginton, one of the engineers, summed it up: ‘The Apple III was kind of like a baby conceived during a group orgy, and later everybody had this bad headache, and there’s this bastard child, and everyone says, “It’s not mine.”‘”

I have yet to see an “individual orgy,” as opposed to a “group orgy,” but the metaphor nonetheless resonates.

3) Jobs didn’t think the same way most of us do about a wide array of topics. He didn’t think like the idiotic managers who think anything that can’t be measured automatically has no value. One can see non-standard thinking that works all over the book—it would be interesting to look too at people with non-standard thinking who fail—and I noticed this moment, at a Stanford class, where Jobs took business questions for while:

When the business questions tapered off, Jobs turned the tables on the well-groomed students. ‘How many of you are virgins?’ he asked. There were nervous giggles. ‘How many of you have taken LSD?’ More nervous laughter, and only one or two hands went up. Later Jobs would complain about the new generation of kids, who seemed to him more materialistic and careerist than his own. ‘When I went to school, it was right after the sixties and before this general wave of practical purposefulness had set in,’ he said. ‘Now students aren’t even thinking in idealistic terms, or at least nowhere near as much.’

Students are too shocked, and by the time they get to me they’re too often well-behaved in a dull way. I’ve mentioned weed in class, and the students are usually astonished. But I remember being a freshman, and most of the shock is undeserved. I went to school at Clark University, where mentions of pot smoking and LSD seemed fairly normal.

“Practical purposefulness” can be impractical when it blinds one to alternative possibilities that the well mannered simply cannot or will not imagine.

4) The last four paragraphs of the book are perfect.

5) Here’s Steven Berlin Johnson on the book; notice:

After devouring the first two-thirds of the book, I found myself skimming a bit more through the post-iPod years, largely because I knew so many of the stories. (Though Isaacson has extensive new material about the health issues, all of which is riveting and tragic.) At first, I thought that the more recent material was less compelling for just that reason: because it was recent, and thus more fresh in my memory. But it’s not that I once knew all the details about the battle with Sculley or the founding of NeXT and forgot them; it’s that those details were never really part of the public record, because there just weren’t that many outlets covering the technology world then.

This reminded me of a speech I gave a few years ago at SXSW, that began with the somewhat embarrassing story of me waiting outside the College Hill bookstore in 1987, hoping to catch the monthly arrival of MacWorld Magazine, which was just about the only conduit for information about Apple back then. In that talk, I went on to say:

If 19-year-old Steven could fast-forward to the present day, he would no doubt be amazed by all the Apple technology – the iPhones and MacBook Airs – but I think he would be just as amazed by the sheer volume and diversity of the information about Apple available now. In the old days, it might have taken months for details from a John Sculley keynote to make to the College Hill Bookstore; now the lag is seconds, with dozens of people liveblogging every passing phrase from a Jobs speech. There are 8,000-word dissections of each new release of OS X at Ars Technica, written with attention to detail and technical sophistication that far exceeds anything a traditional newspaper would ever attempt. Writers like John Gruber or Don Norman regularly post intricate critiques of user interface issues. (I probably read twenty mini-essays about Safari’s new tab design.) The traditional newspapers have improved their coverage as well: think of David Pogue’s reviews, or Walt Mossberg’s Personal Technology site. And that’s not even mentioning the rumor blogs.

So in a funny way, the few moments at the end of Steve Jobs where my attention flagged turned out to be a reminder of one of the great gifts that the networked personal computer has bestowed upon us: not just more raw information, but more substantive commentary and analysis, in real-time.

Except I’m a native to this environment: by the time I came to be cognizant of the world, this was already, if not a given, then at least very close. The later sections of the book had the feel of stuff I’ve already seen on the Internet, and much of the most interesting work analyzing Steve Jobs’ personality, predilections, and power had been done earlier.

To some extent, it’s always easier to chart rises than plateaus, and this is certainly true in Jobs’ case. The very end of Steve Jobs described the steps he’s taken to try ensuring the company continues in the mold of a company capable of producing great stuff—unlike most companies, which slowly come to be ruled by bean-counters and salarymen. Japanese companies like Sony are instructive here: Akio Morita‘s departure from the company coincided with its stagnation, which is most evident in its failure to see the iPod coming.

6) There are many subtle lessons that would be easy to miss in Steve Jobs and from Steve Jobs.

Charlie Stross on the Real Reason Steve Jobs hates flash (and how lives change)

Charlie Stross has a typically fascinating post about the real reason Steve Jobs hates flash. The title is deceptive: the post is really about the future of the computing industry, which is to say, the future of our day-to-day lives.

If you read tech blogs, you’ve read a million people in the echo chamber repeating the same things to one another over and over again. Some of that stuff is probably right, but even if Stross is wrong, he’s at least pulling his head more than six inches off the ground, looking around, and saying “what are we going to do when we hit those mountains up ahead?”

And I don’t even own an iPad, or have much desire to be in the cloud for the sake of being in the cloud. But the argument about the importance of always-on networking is a strong one, even if, to me, it also points to the points to the greater importance of being able to disconnect distraction.

In the meantime, however, I’m going back to the story that I’m working on. Stories have the advantage that they’ll probably always be popular, even if the medium through which one experiences them changes. Consequently, I’m turning Mac Freedom on and Internet access off.

Kindle land, with requisite ruminations on the iPad

EDIT: See this comment on my long-term analysis of this generation of Kindle.

James Fallows says that in order to avoid becoming a Kindle bore, you should “Just shut up when tempted to say or write anything about it. Otherwise you’ll be driving people crazy with your enthusing about how useful and convenient it is, and what its potential might be, and how many elegant decisions are evident in its conception and design.” I’m going to violate that right now by enumerating the number of things the Kindle does right and huge, giant thing it does wrong. If this makes me a bore, proceed to the next post.

Things done right: The screen is very, very nice, as is the tactile feel of the device itself. Although notes aren’t as satisfying to write as they are in paper, they work reasonably well and are easily aggregated. Using the “search” feature allows effectively infinite, immediate concordances in realtime. Shopping in the Kindle store is easy, although I think I’ve only bought two books from it because of the DRM.

The most useful thing about the Kindle for me isn’t actually reading books bought from Amazon—I’m reluctant to spend much money on them, knowing there’s a decent chance that in five years I’ll have a different device or won’t be able to transfer the books I buy now. Rather, Marco Arment’s Instapaper makes the Kindle insanely useful. If I find a longish article online, I hit the “Read Later” bookmarklet in Firefox. About once a week, I log into Instapaper and download all those articles on my Kindle. Bingo: I don’t have to keep printing and losing papers and I still get to read everything I want to read.

Things done wrong: The big-time, number one problem with the Kindle is its terrible software for organizing and managing documents. Actually, scratch that: it doesn’t really have software for managing documents.

The Kindle shows up as a generic USB device on OS X. Want to load it with .pdfs? Be prepared to drag them into a folder labeled “documents.” This process reminds me of .mp3 players… before the iPod. This doesn’t bode well for Amazon, especially now that the iPad is out.

The closest third-party app I’ve found so far is Calibre, which is clunky and doesn’t work that well, especially out-of-the-box. It won’t automatically sync to my Kindle at the moment for reasons not abundantly clear to me; it doesn’t have built-in optical character recognition (OCR) for .pdfs; it doesn’t automatically copy things bought off my Kindle to the computer. The list goes on. The difficulty of writing really good, really intuitive software like iTunes is really, really high.

I’m reminded of this post comparing Tumblr and Posterous, which compares those two “reblogging” tools. The basic point: design counts more than technology. At the moment, the Kindle’s technology is impressive. The physical hardware isn’t bad, although the screen should be bigger: there isn’t enough space before I have to scroll. But until iTunes for the Kindle comes along and whisks the searching and sorting problems away, the Kindle is effectively crippled by software.

I’m sure the omission of iTunes-for-the-Kindle is intentional on Amazon’s part: what they really want you to do is pay them money every time you buy a book or convert a .pdf. That’s okay but seems penny-wise and pound-foolish; think of Scott Adams’ complaint about bad user interfaces. At the end he asks, “What is your biggest interface peeve?” I now have one.

In other news, Apple released the iPad not long ago, which virtually every media outlet on the planet has covered. Megan McArdle says of it:

I’m still unsure how the iPad gets around the core problem: it doesn’t replace anything. Buying an iPhone let me take my phone, my camera, and my iPod out of the briefcase. Buying a Kindle let me remove a newspaper, several books, and some documents I have on PDF.

You can see similar comments here.

But if the iPad software is sufficiently better than the Kindle, users might end up chiefly with it.
One should read this article from Paul Buchheit’s blog, in which he notes the three reasons why the original iPod succeeded where others didn’t. It was:

1) small enough to fit in your pocket, 2) had enough storage to hold many hours of music and 3) easy to sync with your Mac (most hardware companies can’t make software, so I bet the others got this wrong).

Emphasis added. The weird thing is that Amazon is getting this wrong right now. Syncing the Kindle to my computer is cumbersome; there isn’t a good program for organizing my books and .pdfs. Charlie Stross writes about why he, a self-described UNIX bigot, uses a couple of Macs, instead of cheaper Linux boxes:

The reason I choose to pay through the nose for my computers is very simple: unlike just about every other manufacturer in the business, Apple appreciate the importance of good industrial design.

(Note: he’s British, which explains the “Apple appreciate” rather than “Apple appreciates.” The Brits think of corporations as plural, we think of them as singular. What would Steven Pinker say?)

I would also add that Apple has fewer and different hassles than running Linux boxes, which I say as someone who had periodic problems with audio drivers and other things in the ~2001 – 2003 range before I gave up. But the Kindle’s hassles are reminiscent of a product that should be better than it is. I’ve drifted somewhat from the main point regarding the Kindle, but the device is one of these “close, but still wrong” items that is somewhat frustrating, much like Linux, the last Volvo I drove, the Ikea desks I’ve seen, and chairs that unsuccessfully mimic the Aeron.

The Kindle is very, very good for English majors who get assigned a lot of pre-1923 fiction (which they can get free online) or for people who like reading from that era and do so voluminously. For the rest of us, it lacks, especially in the nonfiction department, where it’s hard to skip from section to section quickly.

Reading fiction on it is a substantially better experience because I seldom skip long sections in novels—it’s pretty hard to decide an entire chapter should be skipped, since that chapter will usually contribute something important to the story (and, if it doesn’t, the novel isn’t very good). In addition, novels are relatively unlikely to have research citations, which are sometimes important in evaluating nonfiction, especially if that nonfiction makes extensive or dubious claims. Right now, the small amount of nonfiction I’ve got doesn’t come with footnote hyperlinks. It shouldn’t be all that hard to create a style named, say, footnote with an automated number linking it to a later number so that one can jump freely back and forth between them. But that’s rare in the books I’ve read.

Amazon has released a kindle Software Development Kit (SDK), which might improve some of its current problems. But until it solves the “organizing home” problem that iTunes does so well, it’s not going to be a tremendously useful device for me and many other heavy readers who need some way of getting articles to and from the device. That’s a huge missing feature that Instapaper (somewhat) solves, but not well enough. The Kindle is an “almost” device, like many of the “almost” mp3 players before the iPod. But I don’t think almost is enough.

What's Going on With Amazon and Macmillan?

The book blagosphere has been buzzing with the news that Amazon, a big website to which I link in most of my posts, isn’t selling any titles published by Macmillan, the smallest of the big publishers in the U.S. The dominant question in all this is “why?” There’s been lots of speculation, much of it not worth linking to, but Charlie Stross has written a handy outsider’s guide to the fight, which is actually about how the publishing industry will shake out as a book makes its way from an author to you, a reader.

The bad news is that Stross’ post is almost impossible to excerpt effectively, but I’ll try:

Publishing is made out of pipes. Traditionally the supply chain ran: author -> publisher -> wholesaler -> bookstore -> consumer.

Then the internet came along, a communications medium the main effect of which is to disintermediate indirect relationships, for example by collapsing supply chains with lots of middle-men.

From the point of view of the public, to whom they sell, Amazon is a bookstore.

From the point of view of the publishers, from whom they buy, Amazon is a wholesaler.

From the point of view of Jeff Bezos’ bank account, Amazon is the entire supply chain and should take that share of the cake that formerly went to both wholesalers and booksellers. They do this by buying wholesale and selling retail, taking up to a 70% discount from the publishers and selling for whatever they can get. Their stalking horse for this is the Kindle publishing platform; they’re trying to in-source the publisher by asserting contractual terms that mean the publisher isn’t merely selling them books wholesale, but is sublicencing the works to be republished via the Kindle publishing platform. Publishers sublicensing rights is SOP in the industry, but not normally handled this way — and it allows Amazon to grab another chunk of the supply chain if they get away with it, turning the traditional publishers into vestigial editing/marketing appendages.

The agency model Apple proposed — and that publishers like Macmillan enthusiastically endorse — collapses the supply chain in a different direction, so it looks like: author -> publisher -> fixed-price distributor -> reader. In this model Amazon is shoved back into the box labelled ‘fixed-price distributor’ and get to take the retail cut only. Meanwhile: fewer supply chain links mean lower overheads and, ultimately, cheaper books without cutting into the authors or publishers profits.

Read the rest on Stross’ blog.

This makes me feel slightly dirty for having bought a Kindle recently. On the other hand, this… thing… is between giant corporations, both of which are working to extract as much money from me as possible. If I had to root for either Macmillan or Amazon, I’d chose the former, since the prospect of Amazon as the middleman between virtually every reader and every author is unpalatable. But with the iPad en route, the Barnes and Noble Nook at least in existence, and other eReaders on the way, the prospect of Amazon’s dominance looks far less likely than it did. That’s probably why the company is so desperate at the time.

%d bloggers like this: