So You Have a Startup…

Things that will help it succeed
– Novel feature(s) that people talk about
– A more useful, faster, cheaper product/service = great retention
– Non-trivial technical innovation
– Network effects (experience gets better as more people use it)

Things that will help it fail
– Bad product
– Failure to launch
– A competitor with an equal or better product launches first
– A terrible name
– No retention
– Running out of $
– Getting hit by a bus

Things that won’t guarantee success
– Good name
– Investment $
– Celebrity endorsements
– Brand name investors
– Media buzz / being on Techcrunch
– Lots of users

Things that won’t guarantee failure
– Mediocre name
– Lack of monetization

How to evaluate a startup idea

1. Fill in the blank:
“Wow, [new product/service] is great! Can you imagine how hard it was for people to ____________ before it?”

2. Thought experiment:
The servers have crashed, and [new product/service] has been unavailable for the past day. How do you feel?
a. suicidal
b. annoyed
c. indifferent
d. elated

Blippy is Dead… Long Live Blippy

There was an article today about the end of Blippy. The only thing surprising about this is how long it took for them to realize it was going nowhere. Their copycat, Swipely, months ago had already realized the concept of publicly sharing credit card transactions was going nowhere. Their CEO was quoted, “We don’t think people want to share their purchases. Period.”

But I hope Blippy stays in the minds of entrepreneurs for a long time. There are lots of lessons to be learned from them. Back when they first launched, I remarked to friends that Blippy would be an awesome case study- a rare and perfect example of an awful idea perfectly executed. In the ongoing debate among entrepreneurs of the value of ideas vs. execution, Blippy is solid evidence that regardless of how awesome the team is, a startup idea has to not be totally useless. What, you’re not surprised by that?

AWS::S3 connection timeout

This morning our servers were having problems uploading photos to Amazon S3. After poking around a bit, I discovered that the connections were only sporadically failing- most of the time they worked, but the few that were not tied up all the available processes.

Unfortunately the aws/s3 gem does not allow you to specify timeouts as options, so I had to hack up the gem source code itself. I added to the create_connection method in /usr/lib/ruby/gems/1.8/gems/aws-s3-0.6.2/lib/aws/s3/connection.rb


http.open_timeout = 1
http.read_timeout = 5

That seems to have cleared things up for now.

Trying to get Rails to work with Ruby 1.9 again. Kept getting the error

ArgumentError (invalid byte sequence in US-ASCII):

Sticking this at the top of environment.rb seems to have fixed it:

if RUBY_VERSION =~ /1.9/
Encoding.default_external = Encoding::UTF_8
Encoding.default_internal = Encoding::UTF_8
end

Found the solution here.

cargo cult startups

Richard Feynman famously likened bad science to cargo cults:

In the South Seas there is a cargo cult of people. During the war they saw
airplanes land with lots of good materials, and they want the same
thing to happen now. So they’ve arranged to imitate things like
runways, to put fires along the sides of the runways, to make a
wooden hut for a man to sit in, with two wooden pieces on his head
like headphones and bars of bamboo sticking out like antennas–he’s
the controller–and they wait for the airplanes to land. They’re
doing everything right. The form is perfect. It looks exactly the
way it looked before. But it doesn’t work. No airplanes land. So
I call these things cargo cult science, because they follow all the
apparent precepts and forms of scientific investigation, but
they’re missing something essential, because the planes don’t land.

in the tech startup world there are some companies that appear as if they are doing everything right: they raise tons of money from top-tier angels and vcs; hire engineers, mbas, and designers who have worked at well known companies; get written up extensively in techcrunch, mashable, or even the new york times. the founders blog and tweet, and respond personally to customer emails.

however, despite all that, few people actually use or like the company’s product. this problem can be easily overlooked while investors and the press are enthralled with the company’s amazing team and vision. but eventually the startup will need to demonstrate “traction” and make an effort to boost user signups and retention. a surprising amount of time, the strategy the company comes up with is to do more of the same- get more press, hire more people, blog more- that is, do the things that had already failed to achieve traction, but with more vigor.

if you ever see this pattern, there is a good chance that the company is a cargo cult startup, and the founders are merely mimicking the appearance of a successful company, and have little idea how to actually become successful. here are a few telltale signs- the wooden headphones- of a cargo cult startup.

  • many staff members whose job titles begin with “Director” or “Vice President”
  • a founder who has a book deal or is available for “speaking engagements”
  • launch new product via major media or advertising campaign (nytimes article, super bowl ad)
  • plans to make a big push at SXSW
  • any office furniture not acquired from ikea or craigslist
  • insistence on unit testing, pair programming, or other fashionable programming methodologies

the common thread above is that they are all reasonable in the context of an established, successful company, but make very little sense for embryonic startups yet to find traction.

ironically, it’s probably easier for an entrepreneur to make money by building a cargo cult startup. all you have to do is convince a few key executives at a large corporation, such as aol, to acquire you. in order to build a “real” business, you have to deliver real value to thousands or millions of users. so perhaps the cargo cult startups aren’t cargo cults after all- they may know exactly what they are doing.

wordpress > tumblr, posterous

I had been trying to figure out whether to use Tumblr or Posterous for my personal and company blogs. Tumblr is slow and doesn’t have built-in support for comments (wtf?). Posterous is good, but somehow seems too pushy. Also, Garry just quit recently, so that creates some doubt in my mind as to its future.

Not happy with either of them, I decided to revisit WordPress. Wow, this is really good! It’s snappy (especially relative to Tumblr), and straightforward to use.