Startup Lessons Learned
OCTOBER 4, 2008
Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). Eric, love the blog.
Startup Lessons Learned
NOVEMBER 29, 2008
Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. At the time, I was a die-heard Java zealot. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. I remember answering "What security model?"
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JANUARY 12, 2009
From e-commerce to blogs to photo galleries, we benefited from tens of thousands of lines of code that had already been battle-tested. The inimitable Paul Graham has an excellent essay called The Python Paradox in which he argues: that you could get smarter programmers to work on a Python project than you could to work on a Java project.
Startup Lessons Learned
JULY 29, 2009
To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. At least in strongly typed languages such as Java. But this blog put into better perspective. One last thought. Eric, great post.
Startup Lessons Learned
FEBRUARY 12, 2009
Remember Java? February 19, 2009 9:17 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)
Expert insights. Personalized for you.
155 
Let's personalize your content