Startup Lessons Learned

AUGUST 24, 2009

Or follow all of the New York Times columnists equally? This is good news for everyone except those who have huge legacy investments in large-batch distribution. Case Study: Continuous deployment makes releases n. Revisiting the Software Design Manifesto (and what.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 5, 2009

In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. 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. Take your typical scalability bottleneck.

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. Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. Ive taught everyone from hard-core programmers to scripters to HTML-designers to use it properly. to store it.

San Francisco 151

San Francisco Architecture Startup Database 151