Continuous Deployment Demand Design Hiring 
Startup Lessons Learned
JUNE 15, 2009
Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Startup Lessons Learned
NOVEMBER 7, 2008
Lessons Learned by Eric Ries Friday, November 7, 2008 Using AdWords to assess demand for your new online service, step-by-step If you want to build an online service, and you dont test it with a fake AdWords campaign ahead of time, youre crazy. Turns out, there was aboslutely no demand whatsoever for that particular product.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
FEBRUARY 10, 2009
Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.
Startup Lessons Learned
SEPTEMBER 22, 2008
For eBay, this is caused by the incredible network effects of their business (so-called demand-side increasing returns and supply-side increasing returns). For Neopets, its simply a side-effect of their game-like product design. Case Study: Continuous deployment makes releases n. This has led to exponential growth.
Startup Lessons Learned
NOVEMBER 6, 2008
They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. You dont need "war team meetings," and you dont need status reports I even believe in doing launches on a continuous basis (see continuous ship ). Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JULY 29, 2009
Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.
Startup Lessons Learned
SEPTEMBER 30, 2008
If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.
Expert insights. Personalized for you.
167 
Let's personalize your content