Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test? Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MARCH 22, 2010

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

FEBRUARY 10, 2009

Our tests suite takes nine minutes to run (distributed across 30-40 machines). Code reviews and pairing Great practices. Heck, thats what it says right there in the agile manifesto. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. We already know who to distribute the product to (or else why would we care what they think?).

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JUNE 29, 2020

fast.ai , the company he co-founded with Rachel Thomas and Sylvain Gugger is working to "radically democratize" deep learning by making it accessible to people beyond the tech world through courses, software and other methods. And that would never get past an Ethics Review Board because you can't. He's a good friend.

Czech Republic 113

Czech Republic San Francisco Campaign Washington 113

Startup Lessons Learned

JANUARY 12, 2009

For most of its existence, PHP didnt have a standard package-distribution system or very good module support. However, it made me remember that Im tired of technology arguments. I believe that if you practice TDD, continuous integration, and active refactoring from the start, you can write maintainable code in any language.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

I think this is one of your better posts this year, because you are addressing a risk that you face AFTER some early success, when your guard is down and you are more inclined to believe that you know what you are doing and therefore do not need to be as diligent at framing your hypotheses and how you plan to verify them.

Community 158

Community Management Lean Software Review 158