Startup Lessons Learned

JUNE 8, 2009

I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. It was pretty ugly, the marketing and design sucked, and I was embarrassed by it. So the product development team was busy creating lots of split-tests for lots of hypotheses. Case Study: Continuous deployment makes releases n.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JANUARY 4, 2009

Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. It also doesnt make sense to design your app for scalability from the start, since you may have to create many iterations before you find a version that requires any scalability at all. 21comments: Imran said.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

FEBRUARY 12, 2009

(a guide for hackers) (This post was inspired by a conversation with Nivi from Venture Hacks , but is otherwise not his fault) There has been a proliferation of frameworks and metaphors lately that are designed to help startups avoid the all-too-common fatal mistake of failing to find a market. Expo (and a call for he.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89