Startup Lessons Learned

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. All is not lost, though.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good? It didnt work.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. Kent Beck is deservedly famous for his many contributions in the software industry. We all owe him our thanks for persevering.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 6, 2008

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. What is customer development?

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

FEBRUARY 10, 2009

Code reviews and pairing Great practices. They’ll increase code quality, prevent defects and educate your developers. You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development?

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 2, 2009

That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. But if we stay stuck at the technical parts of the problem, and never uncover the human problems behind them, we’re not going far enough.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. Another is used by marketing to refer to what customers see.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. Im also excited to share two long-form reviews from actual attendees. Technically you argue it goes back 30 years when StorageTek was founded. More recently it's skewed to software & web. Revisiting the Software Design Manifesto (and what.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

techcrunch.com

OCTOBER 23, 2010

Tech Gadgets Mobile Enterprise GreenTech CrunchBase TechCrunch TV Disrupt SF More TechCrunch TV Beta Invites Crunchies Elevator Pitches Gillmor Gang Podcasts TechCrunch Europe TechCrunch Trends TechCrunch France TechCrunch Japan Whats Hot: Android Apple Facebook Google Microsoft Twitter Yahoo Zynga Subscribe: From Nothing To Something.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I joined a financial services tech startup in 1999. For now, Id like to ask a favor.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. There would be no Microsoft, Sun Microsystems, or countless other job-creating tech companies today if early computers required corporate authorization to use.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

FEBRUARY 16, 2009

Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all. Its design goals arent geared towards efficiency in terms of technical costs.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. Even in the narrow field of giant tech companies, their early products were wildly different.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JANUARY 12, 2009

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. As always, Paul is right. Nice article.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

I think this is one of your better posts this year, because you are addressing a risk that you face AFTER some early success, when your guard is down and you are more inclined to believe that you know what you are doing and therefore do not need to be as diligent at framing your hypotheses and how you plan to verify them.

Community 158

Community Management Lean Software Review 158