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

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

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. krasicki April 3, 2009 7:19 AM control valves said.

Software Review 164

Software Review Engineer Management Technical Review 164

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

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

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. Its an essential discipline of good software development, especially in startups.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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

NOVEMBER 13, 2008

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. link] June 20, 2009 2:52 PM Anonymoussaid. Two Ways to Hold Entrepreneurs Accountable (for Ha.

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. The "just fix it" mentality is counter-productive here. Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

ctotodevelopers.blogspot.com

JULY 11, 2012

The implementation and architecture can also suffer if the team under or over invests engineering time, implementation of standards, or testing discipline in the wrong areas. Left on its own, product owners and development teams just may make debatable and sometimes questionable decisions on priorities or implementation strategy.

Agile 40

Agile Architecture Offshore Software Developers 40

femgineer.com

JULY 18, 2010

If they’re coming up to speed with the product, development cycle, and company dynamics is good to let them ramp up slowly. Yes, building software is cheap and fast unlike other products. Remember people only have two hands! But there is still the overhead of testing, scaling, and securing.

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

San Francisco 146

San Francisco Lean Agile Java 146

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.

Technical Review 164

Technical Review San Francisco Lean Software 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. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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. Agree with all your points. Current rules are good enough now.

DC 90

DC Washington San Francisco SBIR 90

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.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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

VC Cafe

FEBRUARY 1, 2011

Data from the Central Bureau of Statistics show that the number of vacancies in the business sector from December 2009 to December 2010 rose by 57% to 56,800 slots. Twenty-nine processors will rely on the Sandy Bridge architecture, including 15 processors for laptops and 14 processors for PCs. billion in 2009 but up from $1.39

Architecture 92

Architecture Dividend Minneapolis 92

andrewchenblog.com

MARCH 10, 2010

In fact, in many ways talking to your customer and understanding them great detail is often much more powerful before you even go through the product development process. Written by Andrew Chen May 4th, 2009 at 8:30 am Posted in Uncategorized « Bay Area investors I’m following on Twitter Dear readers, I need your help!

Customer 42

Customer Advisory Board RSS Software Review 42

Seeing Both Sides

AUGUST 3, 2012

The chart below shows the company’s strong financial performance from 2009 to the present. This effort leads to the fourth interesting scaling take-away: Just because your first product is successful, it doesn’t mean you’re a product genius. In 2012, analysts forecast the company will achieve nearly $1.5

Distribution 49

Distribution Lean Massachusetts Cofounder 49

Software By Rob

AUGUST 18, 2010

CrazyEgg decided to drop its free plan in Jan of 2009 and they haven’t looked back. But a more important question to which I don’t have a good answer is whether the Free/Premium strategy leads to better or worse product development. If they do then the free offering is a mistake even in terms of product development.

Software Review 78

Software Review Software Revenue Cofounder 78

techcrunch.com

OCTOBER 23, 2010

Tweet View Comments Guest Author Sep 20, 2009 This guest post was written by Meebo CEO Seth Sternberg. your objections are irrelevant [link] I only tell you what to do because I love you Prototype vs. Architecture… The CEO of Meebo, Seth Sternberg, started a TechCrunch series focusing on the decisions a young entrepreneur needs to make.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84