Startup Lessons Learned
AUGUST 24, 2009
When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. My blog has over 14000 subscribers, for example. Is that a lot? I have given more than two-dozen paid speeches this year – is that a lot? Is that good? August 24, 2009 2:17 PM Norbert Mocsnik said.
Austin Startup
FEBRUARY 21, 2020
In addition to entrepreneurship, she has a background in chemical engineering, supply chain management, biomedical engineering research, microbiology research, and new product development for U.S. of investment raised has come from the Baltimore/DC area. and Indian companies. Johns Hopkins University and University of Maryland).
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Steve Blank
SEPTEMBER 28, 2009
Home Books for Startups Secret History-Bibliography Steve Blank Startup Resources Steve Blank Entries RSS | Comments RSS Categories Air Force (9) Ardent (9) Big Companies versus Startups: Durant versus Sloan (29) California Coastal Commission (3) Conservation (2) Convergent Technologies (1) Customer Development (98) Customer Development Manifesto (..)
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. Take your typical scalability bottleneck. At any given point in time, which is the right solution?
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.
Expert insights. Personalized for you.
113 
Let's personalize your content