Remove Cofounder Remove Continuous Deployment Remove Hiring Remove Software Engineering
article thumbnail

Lessons Learned: About the author

Startup Lessons Learned

He previously co-founded and served as Chief Technology Officer of IMVU. In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.

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.

Agile 76
Insiders

Sign Up for our Newsletter

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

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. Take a look and let me know what you think.

article thumbnail

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

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. Finding great engineers is hard; figuring out whos good is even harder. This second objective plays no small part in allowing you to hire the best.

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.

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. Case Study: Continuous deployment makes releases n. But what about Commodity?