Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Its this second point I want to emphasize.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JANUARY 19, 2009

I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. You are doing the startup community a great service by sharing your insights via your blog. Particularly the Continuous Deployment and Split testing posts. Another terrific post, Eric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

SEPTEMBER 3, 2009

If you look at the typical startup, you will see the vast majority of their energy and time invested in building new technology. We act as if the biggest risk to startup success is that the technology won’t work. Case Study: Continuous deployment makes releases n. Take the example of the Hoverboard.

San Francisco 104

San Francisco DC Continuous Deployment Lean 104

Startup Lessons Learned

AUGUST 8, 2009

Each company would enroll two leaders in the series, one on the technology side, one on the business side. In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. Thanks for all that you have done to help the startup community! I love the business model.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 15, 2009

whorunsgov : Eric Ries: Startups fail not because the technology works, but because no one wants the tech. Its natural at a gathering like this to focus on new technology and applications. I had a comment published in Federal Computer Week last month that covered similar ground from the perspective of introducing new technology.

San Francisco 92

San Francisco DC Washington Lean 92

Startup Lessons Learned

NOVEMBER 19, 2008

What all these teachers had in common were two things: they were technology early adopters that were willing to take a chance on a new software product, and they all had similar problems organizing their classes and students. Im Community Manager at VenCorps, co-host of commandN. Case Study: Continuous deployment makes releases n.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60