3 ms·

I agree in some respects, but there definitely are still some real advantages to being in the Valley. I've been doing a lot of work towards monetizing justin.t

I agree in some respects, but there definitely are still some real advantages to being in the Valley. I've been doing a lot of work towards monetizing justin.tv lately, especially with video ads. These products tend to be very ad-hoc, and are usually quite poorly documented. Sometimes we've tried to get an integration working by having me try to follow the docs, and call/email when things don't work properly. It usually works out in the end, but it's frustrating and takes too long (sometimes several days of back-and-forth). To contrast, with the ad companies that are in the Bay Area, we just ask them to send a developer to our office. Both of us sit on my couch, while I do the integration and make bad jokes about the quality of their documentation. We usually get it done in an hour or so this way.

10ren 18y ago
I think it depends on how integrated vs. modular the business is. Disruptive business ideas usually require many deals between different parties - there's the business integration, and the technical integration that you mention (as video ads become more common, technical and business standards will probably emerge, making it modular). But some business ideas are more modular, in that customers can just slot the produce/service into an existing business role, and into an existing socket in their system. They are plug-compatible, in both senses. This plug-compatibility also applies to partners. If you need to interact with content providers and hardware manufacturers (e.g. as Apple needed for the iPod and iTunes), some kind of Pond is essential, not just for access to those parties, but also access to helpers of the connection (e.g. lawyers who understand the issues in these kinds of deals). I think this is probably true whether you have a novel disruptive business, or just an ordinary one: if you need to make deals, a Pond makes things much easier. But if you can modularize (systematize) your interactions with your "partners" to such an extent that they become "customers", you don't need to be in the same pond. An example is the "partners" of Google Adwords - there's a standard interface that people use all over the world, and it works well even though there's no customer service. New ideas tend to not be modular - standardization comes later - so a Pond there.
- timr 18y ago
  It's true that some businesses are more nimble than others, but Bill is still right: the ability to sit on the couch here is a more efficient integration mechanism than any other. You're far more likely to complete a deal when the technical work can be done extremely quickly. I've worked at startups in Seattle and San Francisco now, and in my experience, the startups here are faster. At the risk of sounding like a cliche, it's just something in the air here. Things are always on fire. Is it worth the cost of living? I don't know. But there's definitely a difference.
axod 18y ago
With email, you can ignore it, and just drag things out. I had a pretty good experience with Google the other day though, they changed something on adsense which just happened to break Mibbit (Their js tried to access something, security permissions, threw an exception Mibbit wasn't expecting etc). I sent an email, and about 10 emails later and about an hour later, we'd sorted out exactly what was going on, and they'd fixed it. I think it can work either way...
dejb 18y ago
Even if I was in the same city as the other developer I would just talk to them on the phone. I think the 'in person' meeting would usually involve enough time wasting to defray the benefits of the small increase in direct communication. If you are going to be doing a lot of work together it can be nice to meet the person but it isn't necessary just to clarify something.

10ren 18y ago

I think it depends on how integrated vs. modular the business is. Disruptive business ideas usually require many deals between different parties - there's the business integration, and the technical integration that you mention (as video ads become more common, technical and business standards will probably emerge, making it modular). But some business ideas are more modular, in that customers can just slot the produce/service into an existing business role, and into an existing socket in their system. They are plug-compatible, in both senses. This plug-compatibility also applies to partners. If you need to interact with content providers and hardware manufacturers (e.g. as Apple needed for the iPod and iTunes), some kind of Pond is essential, not just for access to those parties, but also access to helpers of the connection (e.g. lawyers who understand the issues in these kinds of deals). I think this is probably true whether you have a novel disruptive business, or just an ordinary one: if you need to make deals, a Pond makes things much easier. But if you can modularize (systematize) your interactions with your "partners" to such an extent that they become "customers", you don't need to be in the same pond. An example is the "partners" of Google Adwords - there's a standard interface that people use all over the world, and it works well even though there's no customer service. New ideas tend to not be modular - standardization comes later - so a Pond there.

timr 18y ago
It's true that some businesses are more nimble than others, but Bill is still right: the ability to sit on the couch here is a more efficient integration mechanism than any other. You're far more likely to complete a deal when the technical work can be done extremely quickly. I've worked at startups in Seattle and San Francisco now, and in my experience, the startups here are faster. At the risk of sounding like a cliche, it's just something in the air here. Things are always on fire. Is it worth the cost of living? I don't know. But there's definitely a difference.

axod 18y ago

With email, you can ignore it, and just drag things out. I had a pretty good experience with Google the other day though, they changed something on adsense which just happened to break Mibbit (Their js tried to access something, security permissions, threw an exception Mibbit wasn't expecting etc). I sent an email, and about 10 emails later and about an hour later, we'd sorted out exactly what was going on, and they'd fixed it. I think it can work either way...

dejb 18y ago

Even if I was in the same city as the other developer I would just talk to them on the phone. I think the 'in person' meeting would usually involve enough time wasting to defray the benefits of the small increase in direct communication. If you are going to be doing a lot of work together it can be nice to meet the person but it isn't necessary just to clarify something.