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.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 15, 2008

You need to make sure you dont get away from trying bold new things, using some combination of your vision and in-depth customer conversations to come up with the next idea to try. Case Study: Continuous deployment makes releases n. But where do those ideas come from in the first place?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JUNE 22, 2009

Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. As the CTO/VP Engineering, I was the worst offender. Case Study: Continuous deployment makes releases n. And how do you pick a new direction?

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

SEPTEMBER 13, 2008

And then we would use that simple analytics system I mentioned to monitor the conversion rates of customers from each campaign. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

SEM 164

SEM San Francisco Lean Continuous Deployment 164