Remove Aggregator Remove Continuous Deployment Remove IPO Remove Operations
article thumbnail

Case Study: Continuous deployment makes releases non-events

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Please teach kids programming, Mr. President

Startup Lessons Learned

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?

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Validated learning about customers

Startup Lessons Learned

Compared to the million-dollar startup, they are operating at micro-scale. First of all, it means that most aggregate measures of success, like total revenue, are not very useful. Case Study: Continuous deployment makes releases n. How does that stack up? First of all, they are not selling their product by hand.

Customer 167
article thumbnail

Why diversity matters (the meritocracy business)

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Sharding for startups

Startup Lessons Learned

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.