Startup Lessons Learned

SEPTEMBER 13, 2008

BillSeitz - yes, but that was already true back in 2004. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. May 8, 2009 2:27 PM Eric said. Two Ways to Hold Entrepreneurs Accountable (for Ha.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

NOVEMBER 7, 2008

It was fall 2004, and the presidential election was in full swing. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 14, 2008

This was 2004, and we had never even heard of MySpace, let alone had any understanding of social networking. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

FEBRUARY 24, 2009

What happened when we got early press (circa 2004) in violation of our own no-PR rule. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Lean 74

Lean San Francisco Continuous Deployment DC 74

Startup Lessons Learned

JANUARY 12, 2009

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. Thats simply impossible on most platforms.

PHP 166

PHP Software Review Ruby San Francisco 166