26.04.2015 Views

Founders at Work.pdf

Founders at Work.pdf

Founders at Work.pdf

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

Livingston: Why were you so secretive? Were you nervous about competitors?<br />

Gruner: We were nervous about competitors; we thought we had a very specific<br />

edge. And we also thought it was a good recruiting technique in terms of<br />

having people focus on three things we thought were important. First of all,<br />

“Let’s focus in both directions on the people, on the culture, on the environment,<br />

see if th<strong>at</strong> makes sense to you.” Because we asked them some extraordinary<br />

things. We said, “This project is going to take about 2 years, and it’s going<br />

to be a lot of work. Furthermore, we are going to institutionalize it by saying,<br />

‘We need you to work every other S<strong>at</strong>urday.’”<br />

Livingston: Really?<br />

Gruner: Yeah. “You gotta be here. It’s a regular work day. And the other<br />

S<strong>at</strong>urdays and Sundays you might have to be here too, but every other S<strong>at</strong>urday<br />

is a regular work day, gotta be here on time, full day, no monkey business. And<br />

th<strong>at</strong>’s for 2 years.” We told them th<strong>at</strong> early on. We wanted to get people to focus<br />

on th<strong>at</strong> first, and then get psyched up about the project. We didn’t want to<br />

reverse it, where people got really psyched up, “Oh, I want to work on this sexy<br />

technology.” We held th<strong>at</strong> to the very end.<br />

During th<strong>at</strong> 2-year period, where we were working very hard, we had virtually<br />

no <strong>at</strong>trition. At the time we announced, we had, I think, 40 people in the<br />

company, and I think over the 2 years, the <strong>at</strong>trition was one or two people. It as<br />

very small, because we did a careful job of filtering people. And they didn’t<br />

come in saying, “I feel like there was misrepresent<strong>at</strong>ion here,” or “I<br />

didn’t understand wh<strong>at</strong> was going on.”<br />

Livingston: Do you remember any big turning points as you were building<br />

these parallel processing systems?<br />

Gruner: We were using a technology called g<strong>at</strong>e arrays. These were custom<br />

integr<strong>at</strong>ed circuits. In our case, we were using technology by Fujitsu in Japan.<br />

They were very expensive to design, very expensive to tool. They had a very<br />

long development cycle. So in building the design, the computer th<strong>at</strong> would use<br />

the first revision of g<strong>at</strong>e arrays was really critical. If we had to go through revisions,<br />

we had budgeted th<strong>at</strong>, but th<strong>at</strong> would make things a lot more expensive<br />

and more complic<strong>at</strong>ed. So when our first g<strong>at</strong>e arrays came back, representing a<br />

total investment <strong>at</strong> th<strong>at</strong> point of probably $3 million, and essentially worked<br />

almost completely, th<strong>at</strong> was a huge milestone in the project. Th<strong>at</strong> was a year<br />

before we announced.<br />

So we had hardware th<strong>at</strong> began to work, and then the next step was the<br />

Fortran compiler. Fortran is a computer programming language, and the compiler<br />

is wh<strong>at</strong> took a Fortran program, say, written for a Digital Vax computer,<br />

which <strong>at</strong> the time was a very successful high-end machine, and converted it to<br />

run on our machine. The key question was, “Can we take these off-the-shelf<br />

Vax programs, recompile them for ours, and actually have them (1) run correctly<br />

and (2) significantly speed up as you add more computers?” When we<br />

demonstr<strong>at</strong>ed th<strong>at</strong> to ourselves, th<strong>at</strong> was a huge milestone. At th<strong>at</strong> point we<br />

knew. By early ’85, we knew we’ve got technology th<strong>at</strong> works and is viable. And<br />

if we can execute from th<strong>at</strong>, we’ve got a viable company.

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

Saved successfully!

Ooh no, something went wrong!