Remove Continuous Deployment Remove Hosting Remove Operations Remove Technical Review
article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

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.

article thumbnail

Embrace technical debt

Startup Lessons Learned

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. Technical debt works the same way, and has the same perils. I won’t pretend that there aren’t teams that take on technical debt for bad reasons.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How to Get Picked as a Speaker for The Lean Startup Conference

Startup Lessons Learned

This post was written by Sarah Milstein, co-host of The Lean Startup Conference. Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”). We’re looking for speakers for the 2013 Lean Startup Conference. in ten years?

Lean 165
article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Similar results apply in product management, design, testing, and even operations. Normally I focus on the techniques you need to reduce batch size, like continuous integration.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

Heres my diagnosis of his problem: He has some automated tests, but his team doesnt have a continuous integration server or practice TDD. Because there are no tests for new features (or operational alerts for the production code), the code that supports those new features could go bad at any moment. Excellent post Eric.

article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

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. You can follow some of that debate here and here ; I continue to believe that this idea is correct.

article thumbnail

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Agile 76