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

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. It might be more precise to categorize them of two kinds of flaws: flaws in implementation, and flaws in design. Eric, Is this post about Architecture?

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. Making UGC work requires good tools, open standards, and proper incentive design. Its a key lean startup concept.

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. Product development deals in designs, which are fundamentally intangible.

article thumbnail

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

Startup Lessons Learned

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. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When they see a problem with the teams process, why dont they just fix it? When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding.