Algorithm Continuous Deployment Customer Development New York 
Startup Lessons Learned
MARCH 16, 2009
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.
Startup Lessons Learned
NOVEMBER 13, 2008
Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JANUARY 30, 2009
Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. I myself didnt understand it until I had the opportunity to view that failure through the lens of the customer development theory. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
NOVEMBER 29, 2008
For the past couple of years Ive used a question that I once was asked in an interview, in which you have the candidate produce an algorithm for drawing a circle on a pixel grid. As they optimize their solution, they eventually wind up deriving Bresenhams circle algorithm. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
SEPTEMBER 15, 2008
I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JANUARY 4, 2009
More common is to use a one-way hashing algorithm to map the data to be accessed to one of the shards that store it. Theres no complex algorithm to go wrong, just a simple lookup table. Of course, you could use URL-based sharding to "wrap" a CH algorithm (or any hashing scheme you wanted).
Startup Lessons Learned
JULY 29, 2009
The design failure meant that there was constant thrashing as the servers struggled to provision capacity according to the “elegant&# algorithm we’d designed. Are the engineers in the customer development team allowed to push quick and dirty "prototypes" to production? One last thought. Eric, great post.
Expert insights. Personalized for you.
111 
Let's personalize your content