Startup Lessons Learned

AUGUST 24, 2009

Despite all the energy invested in talking to authors about the size of their platform, very few gatekeepers have a rigorous set of metrics for measuring it. The problem is that there are no other metrics they can look at to judge the content of a book to know if it’s worth reviewing. Is that a lot? In that I see opportunity.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 5, 2009

If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. Case Study: Continuous deployment makes releases n. We can also ask: how would we fix the problem if it does occur?

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