Startup Lessons Learned

SEPTEMBER 9, 2009

Or, for something more substantive, how about the top five-most-read posts: Why PHP won Dont launch Five Whys Work in small batches The engineering managers lament But wait, theres more! Why Continuous Deployment? * Case Study: Continuous deployment makes releases n. First OODA reference: Ideas.

San Francisco 84

San Francisco Continuous Deployment Lean DC 84

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. I have found this quite rare in engineers.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 27, 2009

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

JANUARY 6, 2009

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 1, 2009

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 11, 2009

This model has not translated well to the world of social networking, because customers of social networks engage sites in a different way than customers of search engines. Case Study: Continuous deployment makes releases n. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 68

San Francisco Social Network Lean Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 13, 2008

Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JANUARY 4, 2009

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 151

San Francisco Architecture Startup Database 151

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

Startup Lessons Learned

JANUARY 30, 2009

After years of engineering effort, changing these assumptions was incredibly hard. This is why agility is such a prized quality in product development. Labels: agile , customer development 5comments: William Pietri said. Seems like all of these problems can be to some degree addressed with agile development methods.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

I was told they werent sure, because all of their engineers were currently busy refactoring. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79