Remove Continuous Deployment Remove Definition Remove Metrics Remove Software Review
article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

article thumbnail

Lessons Learned: Continuous deployment and continuous learning

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Our code pushes take another six minutes.

Insiders

Sign Up for our Newsletter

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

article thumbnail

The free software hiring advantage

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

We lack a consistent and clear definition of the job. It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Massive proprietary databases?

CTO 168
article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.

article thumbnail

Minimum Viable Product: a guide

Startup Lessons Learned

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Great Post - could not agree more.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

As a last disclaimer, please consult the definition of the word hacker if youre not familiar with the controversies surrounding that term.) When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. All is not lost, though.