Continuous Deployment Hiring Reference Technical Review 
Startup Lessons Learned
JUNE 15, 2009
Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Startup Lessons Learned
JULY 29, 2009
Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Technical debt works the same way, and has the same perils. I won’t pretend that there aren’t teams that take on technical debt for bad reasons.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 30, 2008
What does your Chief Technology Officer do all day? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim." And what about if deployment takes forever?
Startup Lessons Learned
APRIL 29, 2013
Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”). For example, when your company adds ano ther blade to its disposal razors , the product’s technical development, marketing and sales will follow relatively predictable paths.
Startup Lessons Learned
AUGUST 2, 2008
Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. Case Study: Continuous deployment makes releases n. but rest assured they would be.
Startup Lessons Learned
MAY 31, 2010
Its in reverse-chronological order, so start with page 3 or just use Seans handy reference. And a special thanks is due to all of our presenters, panelists, and mentors. Although many of the non-technical folks in the room didnt understand what was happening in the moment, plenty of hackers were on high alert. We all owe you.
Startup Lessons Learned
OCTOBER 20, 2008
Heres my diagnosis of his problem: He has some automated tests, but his team doesnt have a continuous integration server or practice TDD. And has the tension goes down, it will be easier to get the whole team (including the MBAs) to embrace TDD and other good practices as further refinements. Good luck, engineering manager.
Expert insights. Personalized for you.
167 
Let's personalize your content