Remove Agile Remove API Remove Continuous Deployment Remove Design
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

Continuous deployment for mission-critical applications

Startup Lessons Learned

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Embrace technical debt

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Sharding for startups

Startup Lessons Learned

Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. It also doesnt make sense to design your app for scalability from the start, since you may have to create many iterations before you find a version that requires any scalability at all.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

The idea is that once we move to the new system (or coding standard, or API, or.) When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. By shipping software early, you give them continuous feedback about how it well its working.

article thumbnail

Lessons Learned: Cash is not king

Startup Lessons Learned

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Combining agile development with customer developm.

article thumbnail

Lessons Learned: Why PHP won

Startup Lessons Learned

Youll notice a pattern: most of the key features that enabled PHPs success are considered among its defects by experts in language design. Ironically, as PHP has grown up, its designers have been busy "fixing" these shortcomings. And I think a bad choice, a bad library, a horrible API, lack of documentation etc. Expo SF (May.

PHP 166