Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

OCTOBER 11, 2010

On the other extreme, modern web-based applications face almost no technical risk, and are governed by high market uncertainty. Eric) In a bar in Amsterdam in 2005, my two cofounders and I came to the sad conclusion that startup we tried to built for two years was doomed. Continuous deployment of hardware is an exciting new capability.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

APRIL 9, 2009

My cofounders and I would hash out nuances and details almost every day, re-drawing diagram after diagram on the whiteboard. MeganMurray : "Behind every technical problem is a human problem. leanstartup #w2e (via @blader ) Amen mcavalcanti : #w2e #leanstartup every technical problem is a usually a human problem.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JULY 3, 2009

davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. ericries #leanstartup Another new idea in the section on continuous deployment and the cluster immune system.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60