Audio Continuous Deployment Conversion Software Review 
Startup Lessons Learned
MARCH 25, 2010
(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).
Startup Lessons Learned
MAY 7, 2009
I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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. The same might be said of good software. Here we have the beginnings of a theory of design for software.
Startup Lessons Learned
JULY 29, 2009
But there is more to technical debt than just the interest payments that come due. In particular, try these three things: Invest in technical debts that may never come due. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.
Startup Lessons Learned
MAY 31, 2010
And a special thanks is due to all of our presenters, panelists, and mentors. Kent Beck is deservedly famous for his many contributions in the software industry. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.
Startup Lessons Learned
JULY 5, 2010
When I wrote a review of Four Steps on this blog in November, 2008, I did my best to be candid and warn of a few shortcomings: And Steve is the first to admit that its a "turgid" read, without a great deal of narrative flow. It is written in a conversational tone, doesnt take itself too seriously, and avoids extraneous fluff.
Startup Lessons Learned
SEPTEMBER 15, 2008
Code To make split-testing pervasive, it has to be incredibly easy. The only change you have to get used to as you start to code in this style, is to wrap your changes in a simple one-line condition. Now, it may be that these code examples have scared off our non-technical friends. October 4, 2008 10:33 AM Amitt Mahajan said.
Expert insights. Personalized for you.
141 
Let's personalize your content