Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
32 | Beginnings<br />
We had a lucky disaster one morning when the entire engi-<br />
neering department—meaning all three <strong>of</strong> us—walked in to<br />
find that the Sun system where we stored our work had died.<br />
We expected to spend the day recovering from backup tapes,<br />
but then we remembered that for testing we had been copying<br />
all <strong>of</strong> our data to a prototype named Maytag. (We named all<br />
<strong>of</strong> our prototypes after household appliances.) Maytag became<br />
our primary storage system from then on, which gave us an<br />
excellent user’s-eye view <strong>of</strong> our product and even more incentive<br />
to make sure that it worked well. In the computer industry,<br />
this is called self-hosting, or more colorfully, eating your own<br />
dog food. Moving onto Maytag probably allowed us to ship to<br />
customers three to six months earlier than we otherwise would<br />
have. Self-hosting was our eventual plan, but doing it early<br />
showed us that our system was more mature than we thought<br />
and helped us quickly identify the problems that really mat-<br />
tered. Eat your own dog food as soon as you can.<br />
We shipped our first test system to Patrick Mulroney at<br />
Tandem Computers in January 1993, barely a year after Mike,<br />
James, and I first began talking about NetApp. Patrick was a<br />
system administrator in an engineering workgroup, and his<br />
boss was Mike’s friend, which got us in the door. Going into<br />
his <strong>of</strong>fice and seeing his setup, I realized that he was our perfect<br />
customer. A Sun workstation sat on top <strong>of</strong> a cardboard box with<br />
three or four disk drives scattered about and strung together<br />
by cables. Our appliance could clean up his mess. He was a<br />
tinkerer and a good system administrator, and he very clearly<br />
saw the coolness <strong>of</strong> what we were doing. Earlier I said we did<br />
less than a regular computer, but we actually developed several