Startup Lessons Learned

AUGUST 24, 2009

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. If they don’t, there are a new breed of lean startups who understand this deep in the bones ready to take their place. 12comments: Dougvs said.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 5, 2009

In other words, a principled way to combine agility with stability. In other words, you can always invest in process, batch size reduction, and agility as an alternative to preventing a specific problem. In other words, a principled way to combine agility with stability. Many problems are catastrophic only if allowed to fester.

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

blog.expensify.com

APRIL 24, 2012

It’s like arguing against vertical software. Just as.NET is both a lock-in and very restricting, and Java violates both “lean cuisine class hierarchy” and “objects if necessary, but not necessarily objects”, the “we’ll just use XML” mantra deserves to die. March 26, 2011 at 9:02 am.

Java 107

Java PHP Software Review Coder 107