Remove Continuous Deployment Remove Programming Remove Software Engineering
article thumbnail

Lean Startup at Scale

Startup Lessons Learned

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.

Lean 167
article thumbnail

Lessons Learned: About the author

Startup Lessons Learned

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Continuous integration step-by-step

Startup Lessons Learned

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. Case Study: Continuous deployment makes releases n. March 26, 2010 8:42 AM ankur aggarwal said. for Harvard Business Revie.

article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. The same might be said of good software. Case Study: Continuous deployment makes releases n.

article thumbnail

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way. Amazon PostRank

Agile 76