Remove Continuous Deployment Remove Engineer Remove Product Development Remove Silicon Valley
article thumbnail

Building a new startup hub

Startup Lessons Learned

Its easy to take Silicon Valley for granted. Ive written a little bit about the origins of Silicon Valley because I think its important for us to understand how we got here in order to make sure we preserve what is best about our community. And do your customer development. Articulate, inspirational.

article thumbnail

Paul Graham on fundraising

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. Case Study: Continuous deployment makes releases n. but rest assured they would be.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Our bias as technologists is to over-focus on the product part of the problem, and five whys tends to counteract that tendency. Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day.

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.

Agile 76
article thumbnail

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

Startup Lessons Learned

Finding great engineers is hard; figuring out whos good is even harder. 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. I have found this quite rare in engineers. Thats OK, were not trying to hire a therapist.

article thumbnail

Lessons Learned: Achieving a failure

Startup Lessons Learned

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. After years of engineering effort, changing these assumptions was incredibly hard. This is why agility is such a prized quality in product development.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time!