Startup Lessons Learned

NOVEMBER 13, 2008

His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 13, 2009

Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. Many of the startups I talk to - and their boards - seem to equate ability to "hit the schedule" with competence and productivity. Does this sound familiar?

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. Case Study: Continuous deployment makes releases n. We owe a lot to this seminal document.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

SEPTEMBER 8, 2009

Government IT solutions can be iterative, they don't have to be designed down to the last detail by architecture astronauts before implementation. I'm a bit late, and this one might be controversial to some, but long-duration non-competes hurt the development of startups by adding friction to the entrepreneurial economy.

DC 90

DC Washington San Francisco SBIR 90