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.

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

companies buy more, and people leave those companies and go to other companies<br />

and buy it. They’ve never heard of Joel on Software, but they’re still buying<br />

our stuff. We’ve actually seen th<strong>at</strong> in the curve. Whereas, in the early days,<br />

we would ask people on our website, “How’d you hear about Fog Creek?” when<br />

they purchased things, and 100 percent of the people th<strong>at</strong> filled out th<strong>at</strong> field<br />

would write, “Joel on Software.”<br />

Now it’s down to about 30 percent. It’s dram<strong>at</strong>ically reduced, but it’s still<br />

there, so to some extent I don’t believe this is a replicable model. Because I’ve<br />

seen a lot of people—th<strong>at</strong> maybe can’t write in as exciting a way, or maybe don’t<br />

have things to say th<strong>at</strong> other people happen to want to read—try to replic<strong>at</strong>e<br />

th<strong>at</strong> model and maybe succeed and maybe not. Unfortun<strong>at</strong>ely, startups have to<br />

find something th<strong>at</strong> works for them.<br />

In our case, our software didn’t really have a strong viral n<strong>at</strong>ure to it, and so<br />

using Joel on Software got the word out there th<strong>at</strong> we make software products.<br />

It worked very well for us, but it’s not necessarily a model th<strong>at</strong> anyone else<br />

could be successful following.<br />

I remember one of the stupidest things I ever wrote on Joel on Software. I<br />

was giving advice on writing technical specific<strong>at</strong>ions, and I said, “Be funny.”<br />

The reason th<strong>at</strong> was stupid was th<strong>at</strong> I l<strong>at</strong>er realized th<strong>at</strong> most people, when they<br />

try to be funny, aren’t th<strong>at</strong> funny. They just look kind of sad. Th<strong>at</strong>’s like, “Be<br />

born to rich parents.” It’s not th<strong>at</strong> useful advice for most people.<br />

Livingston: Did you have any competitors th<strong>at</strong> you worried about?<br />

Spolsky: Probably, but I never really worried about them. It’s sort of funny, but,<br />

because Joel on Software has such a wide readership, a lot of people say, “Hey,<br />

if Joel can do this, I can do this too.” And they’ll copy the model all the way<br />

down to the actual product.<br />

I believe there have now been seven clones of FogBugz. The most extreme<br />

example was somebody th<strong>at</strong> reimplemented the whole thing, but copied our<br />

user interface word for word, so the help file was actually a copyright viol<strong>at</strong>ion,<br />

which we had to tell him to change. But it was an exact clone of FogBugz in<br />

every single way. He l<strong>at</strong>er used all kinds of nasty search engine optimiz<strong>at</strong>ion<br />

techniques, got banned from Google, and th<strong>at</strong> was the end of his business. Th<strong>at</strong><br />

was the worst extreme.<br />

On the other hand, there are people, who we generally respect a lot more,<br />

who kind of said, “Oh yeah, bug tracking. We could do th<strong>at</strong>,” or “We have one<br />

of those.” So all told, I think there are probably seven competitors.<br />

The interesting thing is wh<strong>at</strong> they copied. They didn’t really copy the code;<br />

they copied the implement<strong>at</strong>ion of how FogBugz works. But they missed wh<strong>at</strong><br />

made us successful. They didn’t really copy Joel on Software. And I think wh<strong>at</strong>’s<br />

happening to those seven people right now is they are getting an object lesson<br />

th<strong>at</strong> merely copying the product th<strong>at</strong> another company makes does not make<br />

you successful. We’re not afraid of those people by any stretch of the imagin<strong>at</strong>ion.<br />

Sometimes they can be aggrav<strong>at</strong>ing, but we don’t really care.<br />

More than th<strong>at</strong> though, we’ve long had a philosophy of pretty much ignoring<br />

our competitors. When I first went to work <strong>at</strong> Microsoft, there was a person

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

Saved successfully!

Ooh no, something went wrong!