Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. The artists on the team had called in the big guns, and VP-level folks were there to explain the importance of certain aspects of the visual design that threatened to be cut. Startups are companies. Why do companies have departments?

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

OCTOBER 20, 2008

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. It might be more precise to categorize them of two kinds of flaws: flaws in implementation, and flaws in design. Eric, Is this post about Architecture?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n. April 23, 2010 in San Francisco. Were in a new wave of platform evolution.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

APRIL 26, 2009

Making UGC work requires good tools, open standards, and proper incentive design. Open APIs and data-oriented architecture (aka "web 2.0"). Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n. A true follower of Wikinomics concepts.

Product Development 88

Product Development Developer San Francisco Product 88

www.subelsky.com

FEBRUARY 25, 2010

His descriptions of lean startup techniques and philosophies have had a big influence on the way I design and build software. Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuous deployment system. I'm a lighting audio and video designer.

Lean 41

Lean Baltimore Ruby Maryland 41

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JULY 13, 2009

Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. Product development deals in designs, which are fundamentally intangible. Team New Zealand designed the yacht that won the Americas Cup.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 29, 2008

and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. Its nearly impossible to get a good read on all six attributes in a single interview, so its important to design an interview process that will give you a good sampling of data to look at.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. Its common to find a hacker at the heart of almost any successful technology company.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. But startups rarely have either luxury. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

SEPTEMBER 8, 2009

Policy makers need to know: regulations designed to manage big-companies actually protect those companies by stifling innovation (and competition) from startups. You can see the design of the program here. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 22, 2008

A second idea is that less is more in product design: A key tenet of the philosophy is that uncluttered products with fewer, better features are preferred to similar products with more features. Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 30, 2009

Insist on high levels of usability, UI design, and polish. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

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. On the other, they already have a team fully engaged on making their product architecture better.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79