Startup Lessons Learned

AUGUST 24, 2009

And once you have a relationship with an author, musician, or journalist, it will be quite easy for them to offer new products and services – and for you to give them feedback that helps them shape ever more interesting (and ever more profitable) offerings. There are too many products clamoring for attention. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 5, 2009

I’ve lived through the over-architecture failure – where attempting to prevent all kinds of problems wound up delaying the company from putting out any product at all. There are just so many ways for a startup to fail. Then, we’d know immediately if the problem ever manifests, and get a simultaneous report on its severity.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JANUARY 4, 2009

In this scheme, all of the data related to a specific feature of a product are stored on the same machines. For example, Friendster was famously vertically partitioned at one time in its growth curve. This type of vertical partitioning sharding scheme wont work in most cases. Key-based partitioning. to store it.

San Francisco 151

San Francisco Architecture Startup Database 151