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.

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

Right around the same time a friend of mine, Elsa Dorfman, the photographer,<br />

asked if I knew anyone who would rent her house. I said, “How would<br />

you feel about renting it to a little group of programmers, and we’ll use it as a<br />

company office?” She agreed.<br />

So we moved into Elsa’s house, and once you’ve gotten an office and you<br />

have customers, things kind of take on a life of their own. The toolkit got more<br />

and more popular, and we amazed the customers. Most computer programmers<br />

don’t listen to wh<strong>at</strong> the customer wants. They have their own ideas of<br />

wh<strong>at</strong> would be cool, so they spend a lot of time building stuff th<strong>at</strong> the customer<br />

doesn’t want. They don’t have an investment in the user experience.<br />

A friend of mine was just telling me the other day th<strong>at</strong> his company offshored<br />

a product design to India, and said, “These programmers in India, they<br />

did exactly wh<strong>at</strong> we told them, no m<strong>at</strong>ter how ridiculous!” Most programmers<br />

don’t think about the user experience. They get a spec book, and they say,<br />

“Well, I’m going to meet this spec to make the customer happy.” Th<strong>at</strong>’s not<br />

really enough; you have to make something good for the user if you want to call<br />

yourself an engineer.<br />

The third element is just meeting the deadlines. If we’d said we were going<br />

to do something by a certain d<strong>at</strong>e, we did it, and the customers were stunned.<br />

Livingston: How many of you were there when you first started?<br />

Greenspun: About five, and then we grew pretty quickly to ten. There was so<br />

much repe<strong>at</strong> business because customers would be amazed th<strong>at</strong> we delivered<br />

on time and th<strong>at</strong> it was more or less wh<strong>at</strong> they wanted and actually usable for<br />

the end user.<br />

Livingston: When you started, it sort of grew out of your own interest in<br />

the Web?<br />

Greenspun: Well, in response to people downloading the software. They<br />

weren’t really interested in photo.net, but they had decided to adopt our software<br />

toolkit. In some cases, they’d heard from Edward Tufte in his lectures.<br />

People would ask, “Wh<strong>at</strong>’s good on the Web?” and he’d say, “Nothing’s good on<br />

the Web,” and they’d say, “C’mon, give us two good websites.” And one of the<br />

ones he’d mention would be photo.net as an example with good design.<br />

But most of the business was because we’d released free open source software.<br />

The 15-year-olds would just use it, and the big companies would decide<br />

th<strong>at</strong>, since they had so much money and I guess not enough good programmers,<br />

it made sense for them to pay us to help them out with it.<br />

Livingston: Wh<strong>at</strong> was unique about ArsDigita?<br />

Greenspun: We tried to help each programmer develop an independent, professional<br />

reput<strong>at</strong>ion. We had this idea th<strong>at</strong> programmers could be professionals,<br />

like doctors or lawyers, and, to th<strong>at</strong> end, we wanted the programmers to be real<br />

engineers—to sit down face to face with the customer, find out wh<strong>at</strong> was<br />

needed, come up with some suggestions or changes based on the programmer’s<br />

experience with similar services, and then take a lot of responsibility for making<br />

it happen.

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

Saved successfully!

Ooh no, something went wrong!