26.04.2015 Views

Founders at Work.pdf

Founders at Work.pdf

Founders at Work.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

94 <strong>Founders</strong> <strong>at</strong> <strong>Work</strong><br />

So we decided to bet on doing something for the IBM PC, which proved to<br />

be one of the reasons why we were successful. They had decided to outsource a<br />

lot of the key elements of wh<strong>at</strong> they were doing, right to the distribution.<br />

R<strong>at</strong>her than selling it just through their own sales force, they were selling it<br />

through retail stores like Computer-Land and Sears, which <strong>at</strong> the time was a<br />

very radical idea. They had gone to Intel for the microprocessor; they had gone<br />

to Microsoft for the principal oper<strong>at</strong>ing system. And I said, “They’re smart.<br />

They realize they don’t understand this business, so they’ll go to the best<br />

people. They’re not going to have a lot of ego, and this is the way things are<br />

going to work.” Also, they had put a 16-bit chip in the machine with gre<strong>at</strong>er<br />

memory capacity. And memory capacity was an enormous issue.<br />

The Apple II had 64K—not megabytes, kilobytes—of memory. It was tiny.<br />

And not all of th<strong>at</strong> was available. Actually, if you wrote programs on the<br />

Apple II, you started with a 48K memory space. So the programs were tiny and<br />

the user d<strong>at</strong>a was tiny and people were building spreadsheets th<strong>at</strong> exceeded<br />

memory. It was a fundamental limit of the Apple II, because it was an 8-bit<br />

microprocessor. IBM used a 16-bit microprocessor and I said, “Ah, this will<br />

permit people to build bigger spreadsheets.” The memory space of the IBM PC<br />

when it came out was 640K, 10 times the size. So I said, “16-bit, faster processor,<br />

more memory says IBM. We should target it. We should build a product<br />

th<strong>at</strong> is optimized for it.”<br />

Now, the IBM PC came out day one, August ’81, with a version of VisiCalc,<br />

and with a version of MultiPlan, which was Microsoft’s spreadsheet, but neither<br />

of them took advantage of the full capabilities of the IBM PC. In particular,<br />

because they had been put under a lot of pressure to get a product out, they had<br />

taken the code for the 8080/Z80 Intel/Zilog processors—8-bit code—and<br />

tweaked it a little bit. The point is th<strong>at</strong> VisiCalc on an IBM PC still ran in 64K<br />

of memory. You had 640K available, but you couldn’t address it in a spreadsheet,<br />

so it was as if it wasn’t there. And I said, “This is really an opportunity<br />

here.”<br />

Plus another factor: because I knew all of the individuals, I knew th<strong>at</strong><br />

Software Arts and Personal Software were fighting with each other over the<br />

royalty r<strong>at</strong>e. And I knew th<strong>at</strong> they were essentially distracted and they were not<br />

working together, and I knew th<strong>at</strong> Personal Software was hiring its own developers.<br />

I felt guilt-ridden about coming out with a product th<strong>at</strong> was going to be<br />

competitive with VisiCalc, so I did my best to pretend to myself th<strong>at</strong> it wasn’t<br />

going to be competitive. I ultim<strong>at</strong>ely said to myself th<strong>at</strong> the fact of the m<strong>at</strong>ter is<br />

th<strong>at</strong> I didn’t cre<strong>at</strong>e this opportunity, they did. If they had been on the job, I<br />

would have gone and done something else because the opportunity wouldn’t<br />

have been there. But I saw a gap in the marketplace and I said, “We should do<br />

something th<strong>at</strong> lets you do bigger spreadsheets, th<strong>at</strong>’s faster, th<strong>at</strong> takes full<br />

advantage of the IBM PC, th<strong>at</strong> integr<strong>at</strong>es the graphing, so you could hit one<br />

button to get a graph”—because I knew people wanted th<strong>at</strong>—“and have a<br />

better user interface for non-expert users”—which we did—“and allow user<br />

customiz<strong>at</strong>ion and user programming”—which we did in the macro language.<br />

So there was a set of ideas th<strong>at</strong> gave 1-2-3 its character, th<strong>at</strong> really made it a

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!