Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Revisiting the Software Design Manifesto (and what. 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?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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. We need to build on the success of Hemafuse to introduce new product lines. of investment raised has come from the Baltimore/DC area.

Baltimore 62

Baltimore Africa South Africa Michigan 62

Steve Blank

SEPTEMBER 28, 2009

Theme: Digg 3 Column by WP Designer. Blog at WordPress.com.

North Carolina 167

North Carolina Silicon Valley RSS Connecticut 167

Startup Lessons Learned

OCTOBER 5, 2009

In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. By contrast, most investments in traditional prevention are designed to anticipate and fix a specific problem. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc.

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. Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start.

San Francisco 151

San Francisco Architecture Startup Database 151