2008 Agile API Continuous Deployment 
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
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. The idea is that once we move to the new system (or coding standard, or API, or.)
Startup Lessons Learned
JULY 29, 2009
I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.
Startup Lessons Learned
MARCH 27, 2009
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.
Startup Lessons Learned
JANUARY 4, 2009
A given customer would have an entity URL that looked like this: customer://1234 Somewhere in your API, you have a way to access data about a given customer. Whichever API you use, URL-based sharding is very easy to understand. The better your internal APIs and data architecture, the easier this step will be.
Startup Lessons Learned
APRIL 26, 2009
Open APIs and data-oriented architecture (aka "web 2.0"). 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.
Expert insights. Personalized for you.
167 
Let's personalize your content