Continuous Deployment Employee Internet 
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
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. why did that code get written?
Startup Lessons Learned
OCTOBER 4, 2008
Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. I got my start programming on an old IBM XT; it was thanks to MUDs that I first discovered the internet. So much for timing.
Startup Lessons Learned
JULY 28, 2010
If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. With 21 employees today, kaChing is devoted to recruiting professional managers and finding product/market fit , first for money managers, then for consumers. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
SEPTEMBER 10, 2008
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?
Startup Lessons Learned
SEPTEMBER 30, 2008
When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
146 
Let's personalize your content