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

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

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. For example, you might notice that caching gets a lot easier if you have good metadat about which queries are associated with the same entity. January 19, 2009 9:45 AM Anonymoussaid. Agree with BillG.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. And yet I keep returning to PHP as a development platform, as have most of my fellow startup CTOs. But by the time I was building my first websites for commercial use , PHP had taken over.

PHP 166

PHP Software Review Ruby San Francisco 166