Continuous Deployment Employee Hiring Search 
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. This approach gives you an edge in hiring. Instead, engage with the project.
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. Now he really thought I was nuts, replying "from the recruiter who hired me, of course!"
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.
Startup Lessons Learned
JANUARY 30, 2009
Hire the absolute best and the brightest, true experts in their fields, who in turn can hire the smartest people possible to staff their departments. Insist on the incredibly high-IQ employees and hold them to incredibly high standards. I know of at least five former employees that went on to become startup founders.
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
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
NOVEMBER 29, 2008
Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. On the one hand, it gives you insight into what kind of employee the candidate might be. Thats OK, were not trying to hire a therapist.
Expert insights. Personalized for you.
68 
Let's personalize your content