Startup Lessons Learned

AUGUST 24, 2009

And thanks to the radical transparency enabled by the internet, the quality of these proposals is actually constantly rising, to the point that it’s almost impossible to judge the quality of the final product – because all the proposals look polished and professional, even the terrible ones.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 5, 2009

It could be fixed by refactoring the code itself, or by partitioning the data horizontally or vertically, or by adding additional capacity at the point of the bottleneck, or by shaping end-user demand, or even by removing the feature itself. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JANUARY 4, 2009

For example, Friendster was famously vertically partitioned at one time in its growth curve. I normally recommend you just store this directory on your master database, but you could use a standalone vertical shard (or even a key-based partition!) This type of vertical partitioning sharding scheme wont work in most cases.

San Francisco 151

San Francisco Architecture Startup Database 151