Agile Continuous Deployment Engineer Open Source 
Startup Lessons Learned
SEPTEMBER 7, 2008
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.
Startup Lessons Learned
SEPTEMBER 5, 2008
Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. Case Study: Continuous deployment makes releases n.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") The lean startup is an application of Lean Thinking.
Startup Lessons Learned
OCTOBER 16, 2013
One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. Week 0 - New Feature 1 - Software engineers are busy building brand new features.
Startup Lessons Learned
SEPTEMBER 2, 2008
We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
NOVEMBER 13, 2008
Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.
Startup Lessons Learned
SEPTEMBER 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? And what about if deployment takes forever? If not, whos going to insist we switch to free and open source software?
Expert insights. Personalized for you.
131 
Let's personalize your content