2009 Architecture Continuous Deployment Development Team Review 
Startup Lessons Learned
OCTOBER 20, 2008
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. A project usually has an absolute duration and budget whereas the time and money dedicated to development within the project is where the tradeoffs are made.
Startup Lessons Learned
APRIL 26, 2009
Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Open APIs and data-oriented architecture (aka "web 2.0").
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JULY 13, 2009
Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Wow, great review!
Startup Lessons Learned
NOVEMBER 29, 2008
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?
Startup Lessons Learned
DECEMBER 7, 2008
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.
Expert insights. Personalized for you.
164 
Let's personalize your content