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.

Dan Bricklin 81<br />

and how wide are the columns and all this stuff? Is it an integer, is it a flo<strong>at</strong>ing<br />

point number? How do you specify all th<strong>at</strong>? In computerdom in those days,<br />

th<strong>at</strong> was the most yicky stuff of any computer language—the form<strong>at</strong> st<strong>at</strong>ement<br />

in Fortran, and COBOL’s pictures and all th<strong>at</strong>. It was just such a mess. How do<br />

you get the output specific<strong>at</strong>ion of how it looks?<br />

I ended up with WYSIWYG, like people had done in typesetting. How do<br />

you marry th<strong>at</strong> with calcul<strong>at</strong>ing? There I came up with use of the grid as a way<br />

to be able to name things. The big problem for me was, how do you name<br />

things? How do you name the value? In the old days, it’s like, variable name<br />

equals expression, right? Th<strong>at</strong>’s how computers work. Well, this was, “Wh<strong>at</strong>’s<br />

the variable name going to be?”<br />

Today it seems so n<strong>at</strong>ural: you use A1. Well, first of all, it was A1, not 1<br />

comma 1. It is too many keystrokes, it’s not normal for people, and there’s a<br />

whole lot of problems with it. By going to the map coordin<strong>at</strong>e type of thing—<br />

A1, G7, or something like th<strong>at</strong>—th<strong>at</strong> was something I knew regular people<br />

would understand. But it also parsed well: anything th<strong>at</strong> starts with a letter was<br />

obviously a variable name, because numbers always start with a number, or a<br />

plus and a minus or something. So it made it really easy to make it obvious wh<strong>at</strong><br />

you were typing in. So, if you said 1 + A1, I knew exactly wh<strong>at</strong> it was. But, if I<br />

said 1 + 1,1?<br />

So coming up with th<strong>at</strong> idea, coming up with the fact th<strong>at</strong> you’d be editing<br />

the output as the input—you’d basically be inputting into the output; wh<strong>at</strong> you<br />

see is wh<strong>at</strong> you get—with a separ<strong>at</strong>e loc<strong>at</strong>ion th<strong>at</strong> showed the contents and all<br />

the <strong>at</strong>tributes of it <strong>at</strong> the top, with the menu tree being shown <strong>at</strong> the top. We<br />

had very little memory space to give you in the way of help, but if you hit /, it<br />

listed all the letters you could type. If you typed a letter, it would give you the<br />

name of the command th<strong>at</strong> you were doing and any options. So basically, it was<br />

always prompting you with wh<strong>at</strong> you could do next, once you learned to do the<br />

/ key. And, of course, we could use /, because / is an infix oper<strong>at</strong>or, not a prefix<br />

oper<strong>at</strong>or, so you always knew th<strong>at</strong> if something started with a /, it had to be a<br />

command. But, if it started with a +, it’s going to be a number. So it was one of<br />

the few characters around th<strong>at</strong> was good for th<strong>at</strong>. And it was not shifted (I h<strong>at</strong>e<br />

holding control keys down), and computers had used / as commands before, so<br />

it was a n<strong>at</strong>ural thing to use, for me.<br />

So working out those problems was the thing. But then, after th<strong>at</strong>, everything<br />

else was just, “Wh<strong>at</strong> are the required fe<strong>at</strong>ures?” Adding replic<strong>at</strong>ion, the<br />

ability to copy a cell with absolute and rel<strong>at</strong>ive, th<strong>at</strong> was sort of a n<strong>at</strong>ural thing<br />

for me to come up with, and it was not uncommon in other financial forecasting<br />

systems th<strong>at</strong> existed—the time-sharing systems th<strong>at</strong> were not as interactive. So<br />

th<strong>at</strong> just all flowed. And it was just, “Wh<strong>at</strong> can we throw out to make this thing<br />

useful and to fit in memory?”<br />

Livingston: Wh<strong>at</strong> kind of interesting fe<strong>at</strong>ures did it launch with? Any th<strong>at</strong> you<br />

wish you had included?<br />

Bricklin: Well, it would have been nice to have a better help system, but there<br />

was no space to store th<strong>at</strong>.

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

Saved successfully!

Ooh no, something went wrong!