Austin Operations Product Development Software Engineering 
Steve Blank
AUGUST 3, 2012
consisted of product manager, hardware-engineering manager, software-engineering manager, applications analyst, and software designer. We did a quick overview of the product. We followed that with an hour-long design review, including disclosure of product limitations.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
AUGUST 8, 2009
I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)
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.
Startup Lessons Learned
DECEMBER 8, 2008
Maybe two different developers made changes to the same underlying subsystem, but in incompatible ways. Maybe operations has changed the OS configuration in production in a way that is incompatible with some developers change. The reason its a risk is that, until you integrate, you dont know if the code is going to work.
Expert insights. Personalized for you.
259 
Let's personalize your content