Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

FEBRUARY 22, 2009

When I was a kid, the way I logged onto the internet for the first time (to play MUDs, naturally) was through an open dial-up console at San Diego State University. No logins, no codes, just raw uncensored internet access. Then you set up a web app to co-ordinate volunteers who can wipe a hard drive and install Ubuntu.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JUNE 5, 2009

It’s entirely possible for the startup to be a massive success without having large aggregate numbers, because the startup has succeeded in finding a passionate, but small, early adopter base that has tremendous per-customer behavior. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

FEBRUARY 22, 2010

Two others – that each team member give their input independently and that the results be objectively aggregated – are also key parts of building a meritocracy. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 14, 2009

In an ecosystem, each participant acts according to its own imperatives, but these selfish actions have an aggregate effect. Today, many of these businesses are suffering because the ecosystem no longer balances thanks to the Internet. If you are building a large, viral, ad-support consumer internet property, you just want to go big!

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. This is true of most web application servers, caches like memcached, and all of the network infrastructure that connects them. what is your company web site or email address?

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

APRIL 14, 2009

First of all, it means that most aggregate measures of success, like total revenue, are not very useful. Now that Im in a web based company Im finding a difficult match the framework, culturally. In short: Id love to read your take on a web version of customer development. The Lean Startup Intensive is tomorrow at Web 2.0.

Customer 167

Customer San Francisco Lean Hockey Stick 167