Remove Product Development Remove San Francisco Remove Software Engineering
article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

article thumbnail

Lessons Learned: About the author

Startup Lessons Learned

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. April 23, 2010 in San Francisco. Bring your questions. Take a look and let me know what you think.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

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. April 23, 2010 in San Francisco.

article thumbnail

Middle-East-Meets-West Provides An Edge For B2B Tech Companies

YoungUpstarts

by Melissa Lincoln, Senior Product Marketing Manager at Leadspace. San Francisco and Tel Aviv are two of the greatest cities in the world for tech, each with a distinct culture and unique benefits to offer. Let’s start with San Francisco. In the US, most software engineers enter the workforce following college.

B2B 100
article thumbnail

Lean Startup at Scale

Startup Lessons Learned

But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process. Here''s the simplest form of that cycle: Week -1 - Planning/End-of-Cycle - Software engineers are planning: writing specifications, doing light prototyping, and experimentation.

Lean 167
article thumbnail

Lessons Learned: Continuous integration step-by-step

Startup Lessons Learned

Theoretically, i can visualize the Continuous Integration as RAD ( Rapid action development) along with iterative method, which we used to study in Software Engineering's Process model. April 23, 2010 in San Francisco. March 26, 2010 8:42 AM ankur aggarwal said. Bring your questions. Amazon PostRank

article thumbnail

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

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. Bring your questions.

Agile 76