<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 
 <title>Durable Startup</title>
 <link href="http://www.durablestartup.com/atom.xml" rel="self"/>
 <link href="http://www.durablestartup.com/"/>
 <updated>2011-04-22T22:44:29-04:00</updated>
 <id>http://www.durablestartup.com/</id>
 <author>
   <name>Durable Startup</name>
   <email>support@durablestartup.com</email>
 </author>

 
 <entry>
   <title>Why Twilio Wasn’t Affected by Today’s AWS Issues by Evan Cooke</title>
   <link href="http://www.durablestartup.com/2011/04/24/why-twilio-wasnt-affected-by-todays-aws-issues-by-evan-cooke"/>
   <updated>2011-04-24T00:00:00-04:00</updated>
   <id>http://www.durablestartup.com.com/2011/04/24/why-twilio-wasnt-affected-by-todays-aws-issues-by-evan-cooke</id>
   <content type="html">
     &lt;p&gt;The biggest news story in the Internet startup world last week was the &lt;a href=&quot;http://thenextweb.com/industry/2011/04/21/amazon-ec2-troubles-bring-down-reddit-foursquare-quora-hootsuite-and-more/&quot;&gt;unexpected downtime of Amazon Web Services
(AWS) that brought down dozens (if not hundreds) of websites and web applications including Reddit, Quora, and
Foursquare&lt;/a&gt;.
This wasn't the first time AWS experienced an outage though &lt;a href=&quot;http://techcrunch.com/2008/02/15/amazon-web-services-goes-down-takes-many-startup-sites-with-it/&quot;&gt;it has been more than 3 years since the last
one&lt;/a&gt;.
&lt;a href=&quot;http://techcrunch.com/2009/06/29/yes-rackspace-is-down-and-so-are-many-of-your-favorite-sites/&quot;&gt;No cloud hosting is immune to massive outages&lt;/a&gt;
and with most Internet software startups opting to use them instead of building in-house infrastructure it is
important to show some of the architectural strategies that account for such unfortunate events.&lt;/p&gt;

&lt;p&gt;Twilio, a New York startup that connects web applications with phone lines, shares some of their design principles
in their freshly-created &lt;a href=&quot;http://www.twilio.com/engineering/&quot;&gt;engineering blog&lt;/a&gt; that helped them to remain
available during the outage. The main reason is the highly selective use of AWS only when the service offered
matches their strict requirements:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Unit-of-failure is a single host&lt;/li&gt;
&lt;li&gt;Short timeouts and quick retries&lt;/li&gt;
&lt;li&gt;Idempotent service interfaces&lt;/li&gt;
&lt;li&gt;Small stateless services&lt;/li&gt;
&lt;li&gt;Relax consistency requirements&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The blog post is heavy on engineering terms and concepts so see comments for clarifications if needed.&lt;/p&gt;

     
     &lt;a href=&quot;http://www.twilio.com/engineering/2011/04/22/why-twilio-wasnt-affected-by-todays-aws-issues/&quot;&gt;Read Why Twilio Wasn’t Affected by Today’s AWS Issues in full&lt;/a&gt;
     
   </content>
 </entry>
 
 <entry>
   <title>9 Startup Scaling Secrets from Eventbrite by Wade Roush</title>
   <link href="http://www.durablestartup.com/2011/04/22/nine-startup-scaling-secrets-from-eventbrite-by-wade-roush-xconomy"/>
   <updated>2011-04-22T00:00:00-04:00</updated>
   <id>http://www.durablestartup.com.com/2011/04/22/nine-startup-scaling-secrets-from-eventbrite-by-wade-roush-xconomy</id>
   <content type="html">
     &lt;p&gt;Wade Roush, Xconomy's Chief Correspondent, presents a great feature interview with the founders of Eventbrite
Kevin and Julia Hartz (husband and wife and 2/3 of the founding team) about their personal experience and the
company's history. While the biographical trivia, like Kevin Hartz having two degrees in history, is certainly
entertaining, the real value is in the lessons they learned from their successes (surprisingly, no failures
are mentioned anywhere in the story). Wade summed everything up in nine points:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Don't take big checks until you absolutely must&lt;/li&gt;
&lt;li&gt;Pick the right team&lt;/li&gt;
&lt;li&gt;Pick the right trend to follow&lt;/li&gt;
&lt;li&gt;Keep it simple&lt;/li&gt;
&lt;li&gt;Build on existing tools&lt;/li&gt;
&lt;li&gt;Empower your customers&lt;/li&gt;
&lt;li&gt;Trust the value of your product&lt;/li&gt;
&lt;li&gt;Learn from your customers&lt;/li&gt;
&lt;li&gt;Respect the data&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;In the form of a list, they all sound very bland and generic. The complete article has many awesome examples,
like what happened after Eventbrite changed its pricing and how customers discovered a new distribution channel.&lt;/p&gt;

&lt;p&gt;The lessons learned are at the end of the story if you want to skip over the biographies and the history.&lt;/p&gt;

     
     &lt;a href=&quot;http://www.xconomy.com/san-francisco/2011/01/24/nine-startup-scaling-secrets-from-eventbrite/?single_page=true&quot;&gt;Read 9 Startup Scaling Secrets from Eventbrite in full&lt;/a&gt;
     
   </content>
 </entry>
 
 <entry>
   <title>From Minimally Viable To Maximally Buyable Product by Dharmesh Shah</title>
   <link href="http://www.durablestartup.com/2011/04/21/from-minimally-viable-to-maximally-buyable-product-by-dharmesh-shah"/>
   <updated>2011-04-21T00:00:00-04:00</updated>
   <id>http://www.durablestartup.com.com/2011/04/21/from-minimally-viable-to-maximally-buyable-product-by-dharmesh-shah</id>
   <content type="html">
     &lt;p&gt;There is no consensus on what constitutes the first version of a product worthy of a broad exposure to potential
customers. Some prefer to test just the concept by producing marketing materials to measure public's interest like
&lt;a href=&quot;http://www.ashmaurya.com/2011/01/meta-principles-i-learned-from-running-lean/&quot; title=&quot;Ash
Maurya on meta principles of lean startup&quot;&gt;Ash Maurya did for his book&lt;/a&gt;. Others test a basic solution to the market problem with a &quot;minimal
viable product&quot; (MVP), which is well explained in &lt;a href=&quot;http://vlaskovits.com/2010/12/graham-blank-ries-mvps/&quot; title=&quot;Graham, Blank and Ries on MVPs by Patrick Vlaskovits&quot;&gt;quotes from Paul Graham, Steve Blank, and Eric
Ries&lt;/a&gt;.
Others ship only the fully executeted product because they either are perfectionists or cannot change much
once production begins, like it is the case with physical mass-produced goods.&lt;/p&gt;

&lt;p&gt;Dharmesh Shah, founder &amp;amp; CTO of &lt;a href=&quot;http://www.hubspot.com&quot;&gt;HubSpot&lt;/a&gt;, offers a middle ground that he calls a
&quot;maximally buyable product&quot;. Although he says it is the next stage of product development after the MVP, we believe
that most of the qualities he outlines affect &lt;a href=&quot;/methodology&quot; title=&quot;See our review
methodology for what we consider important to a company's success&quot;&gt;any product's success in the market&lt;/a&gt;.&lt;/p&gt;

     
     &lt;a href=&quot;http://onstartups.com/tabid/3339/bid/12999/From-Minimally-Viable-To-Maximally-Buyable-Product.aspx&quot;&gt;Read From Minimally Viable To Maximally Buyable Product in full&lt;/a&gt;
     
   </content>
 </entry>
 
 <entry>
   <title>Bad Copy Kills – Read It Out Loud by Cindy Alvarez</title>
   <link href="http://www.durablestartup.com/2011/04/20/bad-copy-kills-by-cindy-alvarez"/>
   <updated>2011-04-20T00:00:00-04:00</updated>
   <id>http://www.durablestartup.com.com/2011/04/20/bad-copy-kills-by-cindy-alvarez</id>
   <content type="html">
     &lt;p&gt;To industry insiders, user experience (UX) and interface (UI) aren't just pretty graphics, nifty visuals, hot
colors, and eye movement. The quality of the text presented (the copy) can have great impact on people's behavior as
well. Professional copywriters produce amazing engaging &lt;em&gt;personable&lt;/em&gt; copy. Unfortunately, not every young company has
one on their team or can afford to retain one making the task a typical hit-or-miss gamble.&lt;/p&gt;

&lt;p&gt;Cindy Alvarez, the head of product management and customer development a &lt;a href=&quot;http://www.kissmetrics.com&quot;&gt;KISSmetrics&lt;/a&gt;,
suggests an easy way to spot bad copy: &lt;strong&gt;read it out loud&lt;/strong&gt;. She says she does it for every piece of communication
she sends to customers and for nearly every interface element in their applications. Cindy's tip might not sound
revolutionary or new. Some might have heard about the technique in high school but the amounts of bad copy we
encounter suggest few are really using it.&lt;/p&gt;

&lt;p&gt;Cindy explains four common copy mistakes that can be weeded out with this quality assurance method: &lt;strong&gt;lack of flow&lt;/strong&gt;,
&lt;strong&gt;embarrassing buzzwords&lt;/strong&gt;, &lt;strong&gt;lack of context&lt;/strong&gt;, and &lt;strong&gt;being boring&lt;/strong&gt;. Unfortunately, style issues like jargon
might not be uncovered this way.&lt;/p&gt;

&lt;p&gt;What is your secret sauce for writing a great copy?&lt;/p&gt;

     
     &lt;a href=&quot;http://www.cindyalvarez.com/communication/bad-copy-kills-read-it-out-loud&quot;&gt;Read Bad Copy Kills – Read It Out Loud in full&lt;/a&gt;
     
   </content>
 </entry>
 
 
</feed>