Continuous Deployment Employee Founder New York 
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.
Startup Lessons Learned
MAY 7, 2009
I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JULY 28, 2010
If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here.
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. This company had disciplined schedules, milestones, employee evaluations, and a culture of execution. Build a truly mainstream product.
Startup Lessons Learned
JULY 5, 2010
I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. I used to give copies of Four Steps out to my employees, in the hopes that it would instantly indoctrinate them into the methodology of Customer Development.
Startup Lessons Learned
NOVEMBER 13, 2008
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. Instead, five whys kept leading to problems caused by an improperly trained new employee, and wed make a small adjustment.
Startup Lessons Learned
OCTOBER 4, 2008
Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. That institution will touch many people in its life: customers, investors, employees, and everyone they touch as well. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
146 
Let's personalize your content