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.

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

Th<strong>at</strong> took us a while to figure out. You don’t want to ignore all of those lessons,<br />

because th<strong>at</strong> would be a big mistake, but <strong>at</strong> the same time, sometimes you<br />

really are just solving a different problem. For example, the upd<strong>at</strong>e issue: we<br />

needed to be able to upd<strong>at</strong>e instantly. Something like search, you can have a<br />

little l<strong>at</strong>ency. If a document doesn’t get added for a few minutes, it’s not a big<br />

deal. So <strong>at</strong> a system design level, th<strong>at</strong> actually makes a huge difference, even<br />

though it’s a seemingly small difference when you describe it.<br />

Livingston: It seems like one advantage of having a startup-like project within a<br />

big company is th<strong>at</strong> you have access to all its resources. Tell me about some<br />

other valuable things.<br />

Buchheit: I think the people are the biggest resource. There are really smart<br />

people around, so you could just go talk to them and say, “How are we going to<br />

do this?” and brainstorm solutions. You can just go talk to people, whether it’s<br />

the engineers . . . and Larry and Sergey are actually really smart.<br />

Yesterday, I heard someone making a comment like, “These guys get lucky<br />

and now they think they’re smart.” But in fact, they really are smart and have<br />

good ideas. Sometimes people think th<strong>at</strong> these guys just got lucky, and luck is<br />

always a factor in everything, but it isn’t sufficient. It takes more than luck to<br />

build something th<strong>at</strong> successful.<br />

So there are lots of good resources, in the people and also systems. We get<br />

machines—we don’t have to build the machines ourselves—so it’s nice to have<br />

th<strong>at</strong> infrastructure.<br />

Storage turns out to be a surprisingly difficult problem. It’s not solved.<br />

There are network <strong>at</strong>tached storage (NAS) appliances, but they tend to be<br />

expensive and they have some other problems. Then you have wh<strong>at</strong> we do with<br />

PCs, and th<strong>at</strong>’s technically pretty challenging—to take this big network of<br />

machines th<strong>at</strong> are unreliable and build a big, reliable storage system out of it.<br />

We’re getting a lot closer, but it probably isn’t something th<strong>at</strong> some startup<br />

could pull off the shelf, <strong>at</strong> least not without paying for it.<br />

Livingston: Was there anyone else <strong>at</strong> Google commissioned to work on an<br />

email program <strong>at</strong> the same time?<br />

Buchheit: No. It’s possible someone else was doing something on the side, but<br />

I don’t know of any.<br />

Livingston: Did you get a Google’s <strong>Founders</strong> Award?<br />

Buchheit: No, most of wh<strong>at</strong> we did pred<strong>at</strong>ed the <strong>Founders</strong> Awards. But things<br />

mostly worked out for us anyway.<br />

Livingston: Wh<strong>at</strong> surprised you most looking back on the whole process? Was<br />

it about 2 years?<br />

Buchheit: It depends where you draw the line, but it was a couple of years. I<br />

think some of the systems problems were a little bit harder than we realized to<br />

start with. I keep mentioning this idea of upd<strong>at</strong>ing d<strong>at</strong>a quickly. It really soaks in<br />

<strong>at</strong> a lot of levels when you have to make your l<strong>at</strong>encies be very low. If you have

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

Saved successfully!

Ooh no, something went wrong!