Aggregator Continuous Deployment Founder Operations 
Startup Lessons Learned
JANUARY 18, 2010
Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.
Startup Lessons Learned
FEBRUARY 22, 2010
I’ve seen many times what happens when a single department get’s holed-up in its own space, like the terrifying “ operations cave.&# Two others – that each team member give their input independently and that the results be objectively aggregated – are also key parts of building a meritocracy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
FEBRUARY 22, 2009
But aggregated across many schools, there are thousands or tens of thousands of them. these devices all need human instruction to enable correct and desired operation. Case Study: Continuous deployment makes releases n. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you?
Startup Lessons Learned
APRIL 14, 2009
It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process. Compared to the million-dollar startup, they are operating at micro-scale.
Startup Lessons Learned
JANUARY 4, 2009
Im talking about the actual data-fetching operation. Using memcacheds multiget, which allows the fetching of many keys in parallel, I have written code to aggregate all the shard lookups for a given page and prefetch them, reducing the overhead even further. This information is normally maintained by your operations team.
Expert insights. Personalized for you.
151 
Let's personalize your content