Cofounder Community Continuous Deployment Software Review 
Startup Lessons Learned
FEBRUARY 22, 2009
See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?
Startup Lessons Learned
AUGUST 26, 2009
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. The companies I spoke to all agreed that the community there was extremely supportive, especially in the critical ulta-early-stage.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
MAY 14, 2009
Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. This shift allowed us to crank out working software quickly as a service. Let me know.
Startup Lessons Learned
FEBRUARY 11, 2009
Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.
Startup Lessons Learned
AUGUST 24, 2009
When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. For example, the best book reviewers only review books published by the best publishers, which only accept manuscripts from the best agents. And how could they possibly review a blog? Is that a lot? Is that good?
Startup Lessons Learned
MARCH 3, 2009
At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g. In response to Sean - Intel still runs a very formal process of setting expectations, evaluating employees and reviewing progress on a quarterly basis. love your openness at IMVU.
Startup Lessons Learned
DECEMBER 14, 2009
And passionate players are often the backbone of game communities – especially online. We cultivated a passionate community that nurtured a skilled set of developers. For a consumer internet company in particular, this is often due to a lack of design thinking. Founders struggle with this question.
Expert insights. Personalized for you.
143 
Let's personalize your content