Continuous Deployment Cost Dividend 
Startup Lessons Learned
MARCH 25, 2010
Hence, cutting corners often paid huge dividends. Hence, cutting corners often paid huge dividends. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Are we going too fast?
Startup Lessons Learned
FEBRUARY 20, 2009
Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. When operating with continuous deployment, its almost impossible to have integration conflicts. Case Study: Continuous deployment makes releases n. Small is beautiful.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JULY 2, 2009
Yet in every situation where I have asked, nobody has been tasked with making a realistic estimate, either of the impact of this lack of training or the real costs of the solution. Remember that the cost of the solutions is proportional to the problem caused. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
OCTOBER 19, 2009
Development time is typically no more than two to three weeks, and it generally takes just a few orders to cover development costs. This is the ultimate startup discipline, the hardest to master, and the one that pays biggest dividends. If you can embrace continuous improvement from day one, you can actually speed up as you scale.
Startup Lessons Learned
JANUARY 28, 2009
Stick to some kind of absolute-cost rule, like "no one is allowed to spend more time on the refactoring for a given feature than the feature itself, but also no one is allowed to spend zero time refactoring." Case Study: Continuous deployment makes releases n. Share what you learn. As you refactor, you get smarter.
Expert insights. Personalized for you.
141 
Let's personalize your content