Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. I know many people who think that software works like magic, but to me it actually was magic.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. Thats OK, were not trying to hire a therapist.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

DECEMBER 8, 2008

Maybe operations has changed the OS configuration in production in a way that is incompatible with some developers change. In many traditional software organizations, branches can be extremely long-lived, and integrations can take weeks or months. I would like the users of my software to test and give their feedback to me.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136