Startup Lessons Learned

SEPTEMBER 2, 2008

You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n. Update: PDF version for "lazy linux users" and others who love freedom.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 13, 2008

It just answered this question: for any given time range, for the 100% of people who registered in that period, what percentage of them downloaded? chatted five times? Case Study: Continuous deployment makes releases n. Its simplicity made it effective - everyone in the company could use and understand it.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 18, 2008

I downloaded and tried all four of them (because I had time to kill) - and Im still not sure which one was the best. Nevertheless, we are getting healthy downloads, and anecdotal evidence suggests that its often from people just browsing through apps. Case Study: Continuous deployment makes releases n.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 6, 2008

I tried your compiler and it generted the XPI file but when I link to it and click the link it actually downloads the binary into my browser window instead of popping up the Firefox plugin window. Case Study: Continuous deployment makes releases n. As I make more, youll find them (with source) at my Greasemonkey Compiler page.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 15, 2008

I usually use a "funnel report" that looks like this: Control Hypothesis A Hypothesis B Registered 1000 (100%) 1000 (100%) 500 (100%) Downloaded 650 (65%) 750 (75%) 200 (40%) Chatted 350 (35%) 350 (35%) 100 (20%) Purchased 100 (10%) 100 (10%) 25 (5%) In this case, you could run the report for any time period.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JANUARY 12, 2009

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. Which makes them exactly the kind of programmers companies should want to hire. In my role as a CTO, Ive always tried to choose the right tool for the right job.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 18, 2008

For example, we used to be baffled at IMVU by the significant minority of people who would download the software but never chat with anyone. b) If your product has areas where people read and then different areas where people interact, are there ways to do metrics to determine where people spend their time?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133