Startup Lessons Learned

FEBRUARY 11, 2009

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.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MARCH 4, 2009

It connects to the internet to automatically download the necessary codes. Heres a representative view from an actual Amazon customer review : We all know how to operate our own entertainment center, but what happens when you have to explain it to your babysitter, mother-in-law, or your wife? They want to do activities. Expo SF (May.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MARCH 3, 2009

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. The rule is simple: every employee is 100% responsible for how they spend their time. The suggestion is that you implement one single company-wide rule. I asked why.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

DECEMBER 7, 2008

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. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. We eventually discovered (via five whys ) that we also had to get each new employee acculturated to a fearless way of thinking.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

JULY 2, 2009

For example, a site outage may seem like it was caused by a bad piece of code, but: why was that code written? For example, I often cite a real example of a problem that has as its root cause a new employee who was not properly trained. If new employees are causing problems, that will be a routine topic.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Agile VC

JUNE 13, 2019

I know some of the investors in Chewy prior to the PetSmart acquisition, but I am not a shareholder nor do I intend to purchase shares in the IPO. Much of the press on the company’s IPO highlights this fact, which is easy to discern from a casual read of the S-1. I’ll break down Chewy’s business based on their recent S-1 filing here.

Leadership 100

Leadership .Net Revenue Acquisition 100

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. As I found out to my dismay, this is a dangerous game: in many cases, you’re asking trained professionals to violate their own code of best practices, for the good of the company. Any excesses are likely to be moderated by others.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

MARCH 27, 2009

I believe it is a full, company-wide turn through the OODA loop (for a software business, see especially Ideas-Code-Learn ). You need a process for systematically reviewing your costs and eliminating those that slow you down. Combining agile development with customer developm. What counts as an iteration? Expo SF (May.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

JANUARY 30, 2009

Insist on the incredibly high-IQ employees and hold them to incredibly high standards. It never generated positive returns for its investors, and most of its employees walked away dejected. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Every change required a server restart.

PHP 166

PHP Software Review Ruby San Francisco 166

www.vccafe.com

MARCH 11, 2013

VC Cafe highlights everything you need to know from hosting your code in hackathons to open source legal docs. s the new way to code, and quite easy to learn. You can write back end code in javascript, one language conquers all! Code Igniter. Code Hosting and Version Control. code spaces (svn). WorkingPoint.

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

SEPTEMBER 11, 2009

In fact, I am convinced that if you could find some of IMVU’s earliest adopters, they would say something like this: “sure, those guys at IMVU HQ were helpful in writing code and stuff, but in the end they were just the hired help. peer review is NOT working. It was really the community who built that product.&#

Community 158

Community Management Lean Software Review 158