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. Continuous learning -> Continuous feedback!

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 5, 2008

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. Case Study: Continuous deployment makes releases n.

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. Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. But startups rarely have either luxury. And implementing it is easy, too.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 12, 2009

Youll notice a pattern: most of the key features that enabled PHPs success are considered among its defects by experts in language design. Ironically, as PHP has grown up, its designers have been busy "fixing" these shortcomings. I can design with my brain coming first - the way I like it. will make the foundation weak.

PHP 166

PHP Software Review Ruby San Francisco 166