Startup Lessons Learned

JANUARY 12, 2009

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

PHP Software Review Ruby San Francisco 166

This is going to be BIG.

APRIL 27, 2010

I mean, you don’t have to build an actual business—you can just mimic the movements and demonstrate something that looks like a startup on paper, without any of the necessary risk taking, lessons learned or even a fraction of the effort—all the stuff that investors like to see. ” It’s true. No revenues, no costs.

New York 132

New York CTO Hire Technical Review New York City 132

Startup Lessons Learned

SEPTEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim."

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

sivers.org

JUNE 25, 2010

Derek Sivers about me blog books email list contact How to hire a programmer to make your ideas happen 2010-06-19 Do you have an idea for a website, online business, or application, but need a programmer to turn that idea into reality? Say, “We are hiring a developer to create only the beginning of an application. Hire one from each.

CTO Hire 84

CTO Hire Hiring Software Review Technical Review 84

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. We eventually discovered (via five whys ) that we also had to get each new employee acculturated to a fearless way of thinking.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 15, 2008

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. Whenever you are developing a new feature, or modifying an existing feature, you already have a split-test situation. Great post Eric!

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166