Algorithm Continuous Deployment Engineer Startup 
Startup Lessons Learned
MARCH 16, 2009
Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully. Embedded in that assumption is why startups fail. Hes often felt that there was something missing. This is a significant improvement on the traditional waterfall methodology. Enter Jims post.
Startup Lessons Learned
JULY 29, 2009
We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. In a startup, we should take full advantage of our options, even if they feel dirty or riddled with technical debt.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?
Startup Lessons Learned
NOVEMBER 29, 2008
Finding great engineers is hard; figuring out whos good is even harder. By far the most important thing you want to hire for in a startup is the ability to handle the unexpected. Those people also tend to go crazy in a startup. The "lone wolf" superstar is usually a disaster in a team context, and startups are all about teams.
Startup Lessons Learned
NOVEMBER 13, 2008
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. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.
Startup Lessons Learned
JANUARY 4, 2009
Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. More common is to use a one-way hashing algorithm to map the data to be accessed to one of the shards that store it. But startups rarely have either luxury. to store it.
Startup Lessons Learned
APRIL 7, 2010
Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. When people (ok, engineers) who have been trained in this model enter most startups, they quickly get confused. In Google’s case, often in the millions of people.
Expert insights. Personalized for you.
111 
Let's personalize your content