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

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. Which makes them exactly the kind of programmers companies should want to hire.

PHP 166

PHP Software Review Ruby San Francisco 166

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 if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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

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

Most engineers are terrible visual designers, but if the designer on their team is struggling, maybe they can help out with an icon or two. And wait until you see a "non-technical" designer writing simple code to try and speed up a release. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68