Remove Australia Remove Distribution Remove Product Development Remove Software Review
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. Do you fix bugs before writing code? Completely necessary.

article thumbnail

Smarticus — 10 things you could be doing to your code right now

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How to get distribution advantage on the iPhone

Startup Lessons Learned

Lessons Learned by Eric Ries Thursday, September 18, 2008 How to get distribution advantage on the iPhone I have had the opportunity to meet a lot of iPhone-related companies lately. All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. I cant really tell.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168
article thumbnail

Lessons Learned: Continuous deployment and continuous learning

Startup Lessons Learned

Our tests suite takes nine minutes to run (distributed across 30-40 machines). Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day.

article thumbnail

Good enough never is (or is it?)

Startup Lessons Learned

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Over time, such teams either explode due to irreconcilable differences or dramatically slow down.

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