Remove Continuous Deployment Remove PHP Remove Product Development Remove Software Review
article thumbnail

Lessons Learned: Why PHP won

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. But by the time I was building my first websites for commercial use , PHP had taken over. Writing unit tests or mock objects in PHP is an exercise in constant frustration.

PHP 166
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.

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: 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

Fear is the mind-killer

Startup Lessons Learned

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place.

article thumbnail

Lessons Learned: The one line split-test, or how to A/B all the time

Startup Lessons Learned

And we were fortunate to have Steve Blank , the originator of customer development, on our board to keep us honest. Code To make split-testing pervasive, it has to be incredibly easy. Whenever you are developing a new feature, or modifying an existing feature, you already have a split-test situation. Great post Eric!

article thumbnail

Lessons Learned: Achieving a failure

Startup Lessons Learned

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. Case Study: Continuous deployment makes releases n. Even a great architecture becomes inflexible.