2009 Architecture Continuous Deployment Metrics 
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
DECEMBER 28, 2009
Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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? That means knowing whats written and whats not, what the architecture can and cant support, and how long it would take to build something new. Thats more than just drawing architecture diagrams, though.
Startup Lessons Learned
SEPTEMBER 2, 2008
We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JULY 29, 2009
Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Outside the world of hypothetical examples, its more important to make continual progress than to build the ultimate design. Remember Hamlet? It was still a good trade.
Startup Lessons Learned
SEPTEMBER 7, 2008
We talk about taking advantages of the incredible agility offered by modern web architecture for extremely rapid deployment, etc. Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
AUGUST 8, 2009
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. August 8, 2009 6:08 AM Phil Winkler said. August 8, 2009 5:04 PM PetrolHead said. But what about Commodity?
Expert insights. Personalized for you.
167 
Let's personalize your content