Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Both sides start to think of their point of view in moralistic terms: “those guys don’t see the economic value of fast action, they only care about their precious architecture diagrams&# or “those guys are sloppy and have no professional pride.&#

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JUNE 17, 2010

I suggested that we change the underlying architecture of our UI system so that the artists would be able to build their own UI pieces themselves and then integrate them into the product without requiring new code every time. The engineering team wasn’t happy either. The engineering team wasn’t happy either. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. August 8, 2009 6:08 AM Phil Winkler said. August 8, 2009 5:04 PM PetrolHead said. But what about Commodity?

Software Review 87

Software Review Design Software San Francisco 87

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. 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?

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

femgineer.com

JULY 18, 2010

We engineers know that need to be agile in a startup and be able to scrap code and rebuild, but want we don’t want is to have a founder who manic or aimless. If you’re a founder who is still trying to grasp the product roadmap and create a company vision its probably not a good time to hire an engineer. Sweat equity or salary?

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

DECEMBER 28, 2009

Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it. I just dont believe it. Expo SF (May.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. Open APIs and data-oriented architecture (aka "web 2.0"). April 27, 2009 10:54 AM DSarathy said. Great post! hadnt heard of that before. Very useful post.

Product Development 88

Product Development Developer San Francisco Product 88

Hearpreneur

JANUARY 21, 2017

They do a great job at building an amazing culture, and they are able to keep a small company feel in terms of speed and agility because they keep the teams small and have basically broken the company up into a whole bunch of companies. Poems by Anna was a great little business until I developed breast cancer in 2009.

Entrepreneur 48

Entrepreneur Investment Bankers PR Social Media 48

Reid Hoffman

MARCH 1, 2021

Founded in 2009 by JoeBen Bevert, Joby Aviation has been working under the radar at a base in Santa Cruz, California to develop an electric vertical take-off and landing (eVTOL) aircraft. When it comes to safe, clean, super-convenient and technologically amazing transportation options, why should the sky be the limit?

Merger 28

Merger Vertical Mobile Architecture 28

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. July 13, 2009 7:38 AM George said. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

andrewchenblog.com

MARCH 10, 2010

By the way, to mitigate this problem, there's already a discipline called “Information Architecture&#. Especially when startups are generally started by technically-inclined entrepreneurs that know all the benefits of agile, but all the costs of taking a planning/research-oriented approach? what a coincidence. See [link].

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

OCTOBER 5, 2009

Lessons Learned by Eric Ries Monday, October 5, 2009 The curse of prevention Beware! It’s important to invest in good architecture so that your website will scale once customers arrive. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

NOVEMBER 29, 2008

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. To probe for agility, you have to ask the candidate questions involving something that they know little about. At the time, I was a die-heard Java zealot.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. February 11, 2009 8:05 AM Anonymoussaid. June 15, 2009 9:27 PM Mark Graban said. Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

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

SEPTEMBER 8, 2009

Lessons Learned by Eric Ries Tuesday, September 8, 2009 What would you want to tell Washington DC about startups? September 8, 2009 6:12 PM Geoff Hsaid. September 8, 2009 6:25 PM dbsaid. September 9, 2009 12:36 AM Richard Tibbetts said. September 9, 2009 5:05 AM Roger Toennis said. Agree with all your points.

DC 90

DC Washington San Francisco SBIR 90

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. February 17, 2009 9:48 AM Kevin Gadd said.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 22, 2008

Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. 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?

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 30, 2009

Lessons Learned by Eric Ries Friday, January 30, 2009 Achieving a failure We spend a lot of time planning. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Even a great architecture becomes inflexible. Great post!

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

Lessons Learned by Eric Ries Wednesday, January 28, 2009 Refactoring yourself out of business Let me start out by saying I am a big fan of refactoring , the ongoing process of changing code so that it performs the same behaviors but has more elegant structure. January 29, 2009 12:08 AM Mahesh said. Doesnt that sound good?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

blog.expensify.com

APRIL 24, 2012

The vast majority of patterns and architecture patterns that we see in PHP, Ruby and other scripting languages are incomplete implementations of stuff the Java and C# guys created. ALT.NET is a large sector of the.NET community that isn’t satisfied with the status quo and wants to find the best, most agile way to do things.

Java 107

Java PHP Software Review Coder 107