Continuous Deployment Cost Engineer Information 
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. This engineering manager is a smart guy, and very experienced.
Startup Lessons Learned
NOVEMBER 14, 2013
We’ve structured the workshops around last year’s feedback, in which you suggested that you wanted more information about specific practices and contexts. We asked him a few questions to learn about continuous delivery, why it’s useful, and what engineers and management need to do to implement it. How do you address that?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JUNE 17, 2010
I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. The engineering team would then build that feature, mimicking the UI as close as they could using the current primitives supported by the system. The meeting was tense.
Startup Lessons Learned
SEPTEMBER 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). I mean, have you seen other people? Heres my take.
Startup Lessons Learned
FEBRUARY 16, 2009
Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us.
Startup Lessons Learned
NOVEMBER 7, 2008
We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
APRIL 29, 2013
Not to mention $200,000 in staff time and hard costs. Generously, it might cost you $20,000. In other words, you could test ten book ideas for the cost of publishing one. Our talks range from five minutes to three hours, and we structure them based on the information you have to share, so don’t worry too much about length.
Expert insights. Personalized for you.
164 
Let's personalize your content