Remove Architecture Remove Continuous Deployment Remove Development Team Review Remove Engineer
article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Product development leverage

Startup Lessons Learned

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers.

Insiders

Sign Up for our Newsletter

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

article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

But it goes beyond that, including techniques for improving the economics of product development. Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. That is what we started with on the Internet 30 years ago.

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. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. I have found this quite rare in engineers. At the time, I was a die-heard Java zealot.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. Hire a CTO or VP Engineering. Just change it.