Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

DECEMBER 7, 2008

And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Even with the highest standards imaginable, theres no way to hire just genius hackers. Hire a CTO or VP Engineering. Worst of all, your teammates are constantly wanting to have meetings.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JUNE 22, 2009

As the CTO/VP Engineering, I was the worst offender. Instead of these dead-ends, use the problem and solution team framework and then: pivot, dont jump. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment? 15comments: chrislunt said.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

SEPTEMBER 22, 2008

It also has the nice side-effect of driving down the batch size of work, but thats for another post) This framework for making progress evident applies to more than just scheduling, of course. Case Study: Continuous deployment makes releases n. If the task is not complete, you force people to surface the issue quickly. (It

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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