Architecture Continuous Deployment Development Team Review 
Startup Lessons Learned
JULY 13, 2009
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. Wow, great review! Thanks for the informative 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?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
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.
Startup Lessons Learned
APRIL 26, 2009
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. Open APIs and data-oriented architecture (aka "web 2.0"). Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
153 
Let's personalize your content