Continuous Deployment Email Software Review 
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 13, 2008
A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 10, 2008
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.
Startup Lessons Learned
DECEMBER 8, 2008
Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.
Startup Lessons Learned
FEBRUARY 16, 2009
Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us.
Startup Lessons Learned
FEBRUARY 20, 2009
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. This is easiest to see in deployment.
Startup Lessons Learned
SEPTEMBER 30, 2008
It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.
Expert insights. Personalized for you.
167 
Let's personalize your content