Remove .Net Remove Continuous Deployment Remove Management Remove Software Review
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 take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Case Study: Continuous deployment makes releases n.

Agile 76
article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

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

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

Lo, my 2295 subscribers, who are you?

Startup Lessons Learned

Thanks to those of you who were willing to fill out the survey, I learned my net promoter score (about 25) as well as some clear other segmentation insights: about 80% of you are founders of or work at a startup, you read many of the same other blogs, and many of you would like to engage with Lessons Learned in formats and venues beyond this blog.

article thumbnail

How to conduct a Five Whys root cause analysis

Startup Lessons Learned

The person running the meeting does not have to be a manager or executive. For example, a site outage may seem like it was caused by a bad piece of code, but: why was that code written? You can almost hear a manager now: “sure, if you want me to spend the next six weeks setting this up, just let me know.

article thumbnail

Lessons Learned: Cash is not king

Startup Lessons Learned

These successful startups managed to have enough tries to get it right. I believe it is a full, company-wide turn through the OODA loop (for a software business, see especially Ideas-Code-Learn ). Even if it helps optimize one stage, if it slows you down somewhere else, it might not be a net win.

article thumbnail

Lessons Learned: Why PHP won

Startup Lessons Learned

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Every change required a server restart.

PHP 166