Startup Lessons Learned

SEPTEMBER 7, 2008

Customers found it confusing and it turned out to be at odds with our fundamental value proposition (which really requires an independant IM network). Names have, of course, been changed to protect the innocent: Hope youre well; I thought Id relay a recent experience and thank you. Case Study: Continuous deployment makes releases n.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JUNE 22, 2009

Ive spoken in some detail about a specific pivot that we went through at IMVU , when we decided to abandon the instant messaging add-on concept, and switch to a standalone instant messaging network. We went through another pivot when we switched again from instant messaging to social networking. Thank you for your nice posting.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

AUGUST 26, 2009

And they expose the startups to a vast network of mentors, none of whom get paid for their involvement. Accept that many successful companies are going to want to be backed by big-name firms in other cities. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Articulate, inspirational.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. And in some markets its decisive, because of well-known network effects (as happened with Microsoft, eBay, and many others). This can even vary by category, as people apply different criteria to games vs. utilities vs. social networking apps.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JULY 29, 2009

For example, I’ve talked often about our belief that an instant messaging add-on product would allow IMVU to take advantage of a network effects strategy. To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 1, 2009

In talking with Mary Poppendieck about it, she said that the Chief Engineer role at 3M was called a "Product Champion" The name is less important than understanding the depth of competence that this person has, and what it takes to build it. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JANUARY 4, 2009

This is true of most web application servers, caches like memcached, and all of the network infrastructure that connects them. Imagine you want to store data about customers, each of whom has "last name" field in your database. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151