Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

FEBRUARY 24, 2009

What happened when we got early press (circa 2004) in violation of our own no-PR rule. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

Lean 74

Lean San Francisco Continuous Deployment DC 74

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. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. As always, Paul is right.

PHP 166

PHP Software Review Ruby San Francisco 166