Remove Continuous Deployment Remove Hosting Remove Software Review
article thumbnail

How to Get Picked as a Speaker for The Lean Startup Conference

Startup Lessons Learned

This post was written by Sarah Milstein, co-host of The Lean Startup Conference. You may have to pay the writer and photographer, and perhaps you’ll spend some money on training the writer to use blogging software and social media tools that help them build a following. Applications are due by May 9. Do follow the directions.

Lean 165
article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

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: Continuous deployment and continuous learning

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Our code pushes take another six minutes.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.

article thumbnail

Embrace technical debt

Startup Lessons Learned

But there is more to technical debt than just the interest payments that come due. In particular, try these three things: Invest in technical debts that may never come due. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.