Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Just like in the world of startups, we can start to use micro-scale pilot programs, executed in lean fashion, to gather real facts for making ROI decisions about new project investment. Is that a lot? Is that good?

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 Lean Startup Intensive is tomorrow at Web 2.0. Take your typical scalability bottleneck.

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

Steve Blank

MAY 7, 2009

Reply Thomas Finsterbusch , on May 7, 2009 at 2:24 pm Said: I’m a PhD Student in CS at UT Austin, and Austin too has all the crucial resources necessary for startups (VCs, angels, law firms, top talent, etc.). If you’re text averse like i am, try to diagram these key items and then write-up the diagrams.

Business Plan 148

Business Plan Silicon Valley RSS Venture Capital 148