Continuous Deployment Design Programming Software Engineering 
Startup Lessons Learned
AUGUST 8, 2009
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.
Startup Lessons Learned
OCTOBER 16, 2013
Here''s the simplest form of that cycle: Week -1 - Planning/End-of-Cycle - Software engineers are planning: writing specifications, doing light prototyping, and experimentation. Week 0 - New Feature 1 - Software engineers are busy building brand new features. But that doesn’t mean that we don’t take these ideas seriously.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
NOVEMBER 6, 2008
Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Case Study: Continuous deployment makes releases n.
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. Case Study: Continuous deployment makes releases n. for Harvard Business Revie.
Startup Lessons Learned
OCTOBER 4, 2008
He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). 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.
Startup Lessons Learned
DECEMBER 8, 2008
Theoretically, i can visualize the Continuous Integration as RAD ( Rapid action development) along with iterative method, which we used to study in Software Engineering's Process model. This will help me improving me my work skills in term of coding and designing. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
NOVEMBER 29, 2008
Finding great engineers is hard; figuring out whos good is even harder. If done right, a programming interview serves two purposes simultaneously. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. If it doesnt require a whiteboard, it doesnt count.
Expert insights. Personalized for you.
87 
Let's personalize your content