Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JANUARY 4, 2009

This is true of most web application servers, caches like memcached, and all of the network infrastructure that connects them. Imagine you want to store data about customers, each of whom has "last name" field in your database. Customer data is normally partitioned according to customer id. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

SEPTEMBER 5, 2008

Three of my favorite: memcached - an in-memory object caching system. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. How to listen to customers, and not just the loud. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

JANUARY 12, 2009

The next time you needed to handle that page, you could take advantage of caching for excellent performance. There are also solutions to performance issues resulting from abstraction and runtime compilation (check out op-code caches such as APC). The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

PHP 166

PHP Software Review Ruby San Francisco 166