“
What can explain this difference? On the surface, much appears to hinge on Richard’s programming feat, his software shim. Otherwise, his effort with Konqueror seems much like my struggles with Mozilla. Perhaps he was just a better programmer than me, and without his coding cleverness, there would be no story. That explanation is too simple. Richard made his shim only after determining he needed one last link in a chain of inspiration, intuition, reasoning, and estimation. His shim was a consequence of his overall plan. To show what I mean, here’s an accounting of what Richard did in his first couple of days at Apple. He began by quizzing us on the browser analysis we had done before his arrival, and after hearing it, he quickly discarded our effort with Mozilla as unlikely to bear fruit. By doing so, he demonstrated the self-confidence to skip any ingratiating display of deference to his new manager, a person who had years of experience in the technical field he was newly entering. Next, Richard resolved to produce a result on the shortest possible schedule. He downloaded an open source project that held genuine promise, the Konqueror code from KDE, a browser that might well serve as the basis for our long-term effort. In getting this code running on a Mac, he decided to make the closest possible approximation of a real browser that was feasible on his short schedule. He identified three features—loading web pages, clicking links, and going back to previous pages. He reasoned these alone would be sufficiently compelling proofs of concept. He then made his shortcuts, and these simplifying choices defined a set of nongoals: Perfect font rendering would be cast aside, as would full integration with the Mac’s native graphics system, same for using only the minimum source code from KDE. He reasoned that these shortcuts, while significant, would not substantially detract from the impact of seeing a browser surf web pages. He resolved to draw together these strands into a single demo that would show the potential of Konqueror. Then, finally, he worked through the technical details, which led him to develop his software shim, since that was the only thing standing between him and the realization of his plan. His thought process amplified his technical acumen. In contrast, Don and I were hoping Mozilla would pan out somehow. I was trying to get the open source behemoth to build on the Mac, with little thought beyond that. I had no comparable plan, goals, nongoals, tight schedule, or technical shortcuts.
”
”
Ken Kocienda (Creative Selection: Inside Apple's Design Process During the Golden Age of Steve Jobs)